Many people don’t really know the difference between software architecture and software design. Even for developers, the line is often blurry and they might mix up elements of software architecture patterns and design patterns.
The Definition of Software Architecture
In simple words, software architecture is the process of converting software characteristics such as flexibility, scalability, feasibility, reusability, and security into a structured solution that meets the technical and the business expectations.
The Characteristics of Software Architecture
As explained, software characteristics describe the requirements and the expectations of a software in operational and technical levels. Thus, when a product owner says they are competing in a rapidly changing markets, and they should adapt their business model quickly. The software should be “extendable, modular and maintainable” if a business deals with urgent requests that need to be completed successfully in the matter of time. As a software architect, you should note that the performance and low fault tolerance, scalability and reliability are your key characteristics. Now, after defining the previous characteristics the business owner tells you that they have a limited budget for that project, another characteristic
comes up here which is “the feasibility.”
Here you can find a full list of software characteristics, also known as “quality attributes,” here.
SOLID refers to Single Responsibility, Open Closed, Liskov substitution, Interface Segregation and Dependency Inversion Principles.
Software Design
While software architecture is responsible for the skeleton and the high-level infrastructure of a software, the software design is responsible for the code level design such as, what each module is doing, the classes scope, and the functions purposes, etc.
- Single Responsibility Principle means that each class has to have one single purpose, a responsibility and a reason to change.
- Open Closed Principle: a class should be open for extension, but closed for modification. In simple words, you should be able to add more functionality to the class but do not edit current functions in a way that breaks existing code that uses it
SOLID refers to Single Responsibility, Open Closed, Liskov substitution, Interface Segregation and Dependency Inversion Principles.
Risemotionadmin
I help fin-tech digital product teams to create amazing experiences by crafting top-level UI/UX.
Other articles
Risemotionadmin
December 10, 2020The Winner of the Vice Presidential Debate? Kamala’s Faces.
This is a longer card with supporting text below as a natural lead-in to additional content. This content is a little bit longer.
Risemotionadmin
December 11, 2020Funds adding fuel in tech’s climate race
Vitae semper quis lectus nulla at volutpat diam. Sed viverra ipsum nunc aliquet .
Risemotionadmin
December 11, 2020Satellite tags shed light on sea turtle treks
Vitae semper quis lectus nulla at volutpat diam. Sed viverra ipsum nunc aliquet .
Risemotionadmin
December 11, 2020As climate warms, Ecuador fights fires with forecasts
Vitae semper quis lectus nulla at volutpat diam. Sed viverra ipsum nunc aliquet .
Risemotionadmin
December 12, 2020When Autumn Leaves Begin to Fall As the Climate Warms, Leaves on Some Trees are Dying Earlier
Vitae semper quis lectus nulla at volutpat diam. Sed viverra ipsum nunc aliquet .