https://bartwullems.blogspot.com/2023/05/lehmans-laws-of-software-evolution.html
Skip to main content
The art of simplicity
Search
Search This Blog
[ ]
[SUBMIT]
Pages
* Home
* Reading List
More...
Lehman's Laws of Software Evolution
May 12, 2023
In the world of software engineering, the Lehman's Laws of Software
Evolution are widely recognized as a fundamental framework for
understanding how software systems evolve over time. These laws were
introduced by British computer scientist, Meir Lehman, in the 1980s
(!) in his paper "Programs, Life Cycles, and Laws of Software
Evolution", and they remain relevant to this day.
Lehman's Laws describe how software systems evolve and how they can
be managed over their lifespan. In this blog post, we will explore
these laws in detail and their significance in software development.
From the paper:
[tsgcokzluB]
The first law of software evolution states that software systems must
evolve or they will become progressively less useful. This law
recognizes that software is not static and unchanging, but instead
must adapt and grow to meet changing user needs and technological
advancements. Failure to evolve software systems can result in
decreased usefulness or even obsolescence. This means that software
systems are never "DONE", they only become obsolete.
The second law of software evolution states that the complexity of
software systems will increase over time unless they are actively
reduced. As software systems grow and evolve, they become more
complex, which can make them more difficult to maintain, debug, and
enhance. This complexity can also lead to an increase in defects and
errors. To combat this, it is essential to take active steps to
reduce complexity and streamline software systems. Yes, we are
talking about technical debt.
Side note: Check out this interesting talk about technical debt:
The third law of software evolution states that software evolution is
a continuous process. This law recognizes that software systems are
not static and unchanging, but rather they are continuously evolving.
As such, software development is an ongoing process that requires
continual improvement and adaptation.
The fourth law of software evolution states that software systems are
subject to feedback loops. As software systems evolve, they receive
feedback from users, stakeholders, and other sources. This feedback
can help guide the evolution of the software, ensuring that it
continues to meet user needs and remains relevant in the face of
changing technologies.
The fifth law of software evolution states that software systems are
subject to both incremental and radical change. As software systems
evolve, they can undergo incremental changes that build on existing
functionality and improve the system gradually. Alternatively,
software systems can undergo radical changes that fundamentally alter
the system's architecture or functionality.
The sixth law of software evolution states that software evolution is
constrained by organizational stability and the ability of developers
to understand the system. This law recognizes that software
development is an inherently human activity, and as such, the people
involved in the process play a crucial role in shaping the evolution
of the software.
The seventh law of software evolution states that the evolution of a
software system is limited by its architecture. This law recognizes
that the architecture of a software system plays a critical role in
determining its evolution. A well-designed architecture can
facilitate the evolution of the system, while a poorly designed
architecture can limit its potential.
In conclusion, the Lehman's Laws of Software Evolution provide a
valuable framework for understanding how software systems evolve over
time. By recognizing the continuous nature of software development
and the role of people, architecture, and feedback in shaping
software evolution, developers can create more robust and adaptable
software systems.
Share
* Get link
* Facebook
* Twitter
* Pinterest
* Email
* Other Apps
Labels
Architecture
Labels: Architecture
Share
* Get link
* Facebook
* Twitter
* Pinterest
* Email
* Other Apps
Popular posts from this blog
XUnit - Assert.Collection
March 09, 2020
A colleague asked me to take a look at the following code inside a
test project: My first guess would be that this code checks that the
specified condition(the contains) is true for every element in the
list. This turns out not to be the case. The Assert.Collection
expects a list of element inspectors, one for every item in the list.
The first inspector is used to check the first item, the second
inspector the second item and so on. The number of inspectors should
match the number of elements in the list. An example: The behavior I
expected could be achieved using the Assert.All method:
Share
* Get link
* Facebook
* Twitter
* Pinterest
* Email
* Other Apps
Read more
Azure DevOps/ GitHub emoji
August 20, 2020
I'm really bad at remembering emoji's. So here is cheat sheet with
all emoji's that can be used in tools that support the github emoji
markdown markup: All credits go to rcaviers who created this list.
Share
* Get link
* Facebook
* Twitter
* Pinterest
* Email
* Other Apps
Read more
Angular --deploy-url and --base-href
April 14, 2021
As long you are running your Angular application at a root URL (e.g.
www.myangularapp.com ) you don't need to worry that much about either
the '--deploy-url' and '--base-href' parameters. But once you want to
serve your Angular application from a server sub folder(e.g.
www.mywebsite.com/angularapp ) these parameters become important.
--base-href If you deploy your Angular app to a subfolder, the
'--base-href' is important to generate the correct routes. This
parameter will update the tag inside the index.html. For
example, if the index.html is on the server at /angularapp/index.html
, the base href should be set to . More
information: https://angular.io/guide/deployment --deploy-url A
second parameter that is important is '--deploy-url'. This parameter
will update the generated url's for our assets(scripts, css) inside
the index.html. To make your assets available at /angularapp/, the
deploy url should
Share
* Get link
* Facebook
* Twitter
* Pinterest
* Email
* Other Apps
Read more
About me
My photo
Bart Wullems
Visit profile
[MVP_Logo_Horizontal_Preferr]
Blog Archive
* 2023 93
+ May 15
o Visual Studio 2022 17.6-Http Endpoint explorer
o Azure Artifacts-NU1301 error
o Writing asynchronous code in .NET
o An alternative approach to structuring your tests ...
o Progressive Web App-Icon is not loaded
o Using IAsyncEnumerable with Dapper
o Lehman's Laws of Software Evolution
o ASP.NET Core-Factory based vs Convention based mid...
o How Microsoft is using GraphQL in their new Teams ...
o HotChocolate GraphQL-Include Exception details
o Disable TypeScript compilation in Visual Studio
o The pursuit of happiness
o Visual Studio-Generate C# client for OpenAPI
o MassTransit-Minimal Message Handlers
o Make your ASP.NET Core application always running ...
+ April 15
+ March 23
+ February 20
+ January 20
* 2022 218
+ December 17
+ November 13
+ October 21
+ September 20
+ August 7
+ July 20
+ June 21
+ May 21
+ April 16
+ March 23
+ February 20
+ January 19
* 2021 215
+ December 18
+ November 13
+ October 21
+ September 19
+ August 2
+ July 22
+ June 22
+ May 19
+ April 19
+ March 20
+ February 19
+ January 21
* 2020 218
+ December 9
+ November 22
+ October 20
+ September 22
+ August 10
+ July 18
+ June 21
+ May 17
+ April 19
+ March 22
+ February 18
+ January 20
* 2019 217
+ December 18
+ November 16
+ October 15
+ September 21
+ August 15
+ July 16
+ June 19
+ May 11
+ April 23
+ March 21
+ February 20
+ January 22
* 2018 214
+ December 19
+ November 21
+ October 20
+ September 20
+ August 19
+ July 10
+ June 21
+ May 12
+ April 18
+ March 15
+ February 18
+ January 21
* 2017 221
+ December 16
+ November 21
+ October 17
+ September 21
+ August 13
+ July 14
+ June 15
+ May 23
+ April 20
+ March 23
+ February 18
+ January 20
* 2016 219
+ December 15
+ November 16
+ October 21
+ September 17
+ August 22
+ July 19
+ June 22
+ May 10
+ April 22
+ March 20
+ February 21
+ January 14
* 2015 214
+ December 18
+ November 8
+ October 22
+ September 13
+ August 15
+ July 20
+ June 20
+ May 19
+ April 17
+ March 22
+ February 20
+ January 20
* 2014 222
+ December 18
+ November 15
+ October 20
+ September 21
+ August 16
+ July 19
+ June 20
+ May 18
+ April 19
+ March 16
+ February 20
+ January 20
* 2013 236
+ December 15
+ November 18
+ October 21
+ September 20
+ August 22
+ July 18
+ June 20
+ May 20
+ April 19
+ March 21
+ February 20
+ January 22
* 2012 246
+ December 16
+ November 25
+ October 24
+ September 20
+ August 20
+ July 11
+ June 22
+ May 23
+ April 20
+ March 21
+ February 22
+ January 22
* 2011 271
+ December 17
+ November 21
+ October 21
+ September 14
+ August 23
+ July 16
+ June 24
+ May 29
+ April 25
+ March 26
+ February 23
+ January 32
* 2010 345
+ December 29
+ November 33
+ October 34
+ September 23
+ August 28
+ July 30
+ June 21
+ May 33
+ April 27
+ March 28
+ February 32
+ January 27
* 2009 119
+ December 37
+ November 35
+ October 30
+ September 12
+ August 5
Show more Show less
Labels
* .NET
* .NET 4.5
* .NET 4.6
* .NET 4.7
* .NET 5
* .NET 6
* .NET 7
* .NET Core
* .NET Standard
* Actor Model
* ADFS
* Agile
* AI
* Akka.net
* ALM
* Android
* Angular
* Angular.js
* Application Insights
* Architect
* Architecture
* ASP.NET
* ASP.NET MVC
* ASP.NET Web API
* Async
* Autofac
* Azman
* Azure
* Azure DevOps
* BDD
* Blazor
* Bootstrap
* Build
* C#
* Cloud
* CSS
* dapr
* Data Annotations
* Data Science
* Dataflow
* DB2
* DDD
* Dependency Injection
* Design Patterns
* DevOps
* Docker
* Domain Driven Design
* Durandal
* ElasticSearch
* Enterprise Library
* Entity Framework
* EPM
* Event Sourcing
* Event Storming
* F#
* Git
* GitHub
* GraphQL
* gRPC
* HTML
* HTML 5
* IIS
* IoC
* Ionic
* iOS
* IoT
* Jamstack
* Javascript
* jQuery
* Kafka
* Kendo UI
* Kibana
* Knockout
* Kubernetes
* Leadership
* Linux
* machine learning
* Marten
* MassTransit
* microservices
* Mobile
* MongoDB
* MS Project Server
* MSBuild
* NDC
* NDepend
* Neo4J
* NEventStore
* NHibernate
* node.js
* NoSQL
* npm
* NSubstitute
* NuGet
* NUnit
* OData
* OpenTelemetry
* OpenXML
* Oracle
* Orleans
* OWIN
* Performance
* PostgreSQL
* Postman
* Powershell
* Product Management
* RabbitMQ
* RavenDB
* Razor
* React
* Redis
* Reporting Services
* REST
* RIA
* Rider
* Ruby
* Rx
* Scrum
* Security
* Selenium
* Serilog
* Service Fabric
* Sharepoint
* SignalR
* Silverlight
* Silverlight 4
* SOA
* Software Development
* SonarQube
* SPA
* SpecFlow
* SQL Server
* TDD
* Team System
* Test
* Testing
* TFS 11
* TFS 2010
* TFS 2012
* TFS 2013
* TFS 2015
* TFS 2017
* TFS 2018
* Tools
* TypeScript
* UI
* UX
* Visual Studio
* Visual Studio 2017
* Visual Studio 2019
* Visual Studio 2022
* Visual Studio Code
* Visual Studio Team Services
* VS 11
* VS 2010
* VS 2012
* VS 2013
* VS 2015
* VSCode
* VSTO
* WCF
* Web development
* Webpack
* WF
* WIF
* Windows 10
* Windows 8
* Windows Forms
* Windows Phone
* WinRM
* WPF
* WSS
* Xamarin
* XAML
* XUnit
Show more Show less
Report Abuse
Powered by Blogger
Theme images by Jason Morrow