The difference between software\narchitecture and software design is not really known to most of the people.\nEven for developers, the line is often shadowy and they might mix up elements\nof software architecture patterns and design patterns. In this blog, I would\nlike to simplify these concepts and explain the differences between software\ndesign and software architecture. In addition, I will show you why it is\nimportant for a developer to know about software architecture and software\ndesign. <\/p>\n\n\n\n
The Definition of Software Architecture<\/strong><\/p>\n\n\n\n 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. This definition leads us to ask about the characteristics of a software that can affect a software architecture design. There is a long list<\/a> of characteristics which mainly represent the business, functional & non-functional or the operational requirements, in addition to the technical requirements.<\/p>\n\n\n\n The Characteristics of Software Architecture<\/strong><\/p>\n\n\n\n As explained, software\ncharacteristics describe the requirements and the expectations of a software in\noperational and technical levels. Thus, when a product owner says they are\ncompeting in a rapidly changing markets, and they should adapt their business\nmodel quickly. The software should be \u201cextendable, modular and maintainable\u201d if\na business deals with urgent requests that need to be completed successfully in\nthe matter of time. As a software architect, you should note that the\nperformance and low fault tolerance, scalability and reliability are your key\ncharacteristics. Now, after defining the previous characteristics the business\nowner tells you that they have a limited budget for that project, another\ncharacteristic comes up here which is \u201cthe feasibility\u201d.<\/p>\n\n\n\n Software Design<\/strong><\/p>\n\n\n\n While software architecture is\nresponsible for the skeleton and the high-level infrastructure of a software,\nthe software design is responsible for the code level design such as, what each\nmodule is doing, the classes scope, and the functions purposes, etc.<\/p>\n\n\n\n If you are a developer, it is important for you to know what the SOLID principles is and how a design pattern should solve regular problems.<\/p>\n\n\n\n Single Responsibility Principle<\/strong>: means that each class has to have one single purpose, a responsibility and a reason to change.<\/p>\n\n\n\n Open Closed Principle<\/strong>: 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.<\/p>\n\n\n\n Liskov substitution Principle<\/strong>: this principle guides the developer to use inheritance in a way that will not break the application logic at any point. Thus, if a child class called \u201cXyClass\u201d inherits from a parent class \u201cAbClass\u201d, the child class shall not replicate a functionality of the parent class in a way that change the behavior parent class. So you can easily use the object of XyClass instead of the object of AbClass without breaking the application logic.<\/p>\n\n\n\n Interface Segregation Principle<\/strong>: Simply, since a class can implement multiple interfaces, then structure your code in a way that a class will never be forced to implement a function that is not important to its purpose. So, categorize your interfaces.<\/p>\n\n\n\n Dependency Inversion Principle<\/strong>: If you ever followed TDD for your application development, then you know how decoupling your code is important for testability and modularity. In other words, If a certain Class \u201cex: Purchase\u201d depends on \u201cUsers\u201d Class then the User object instantiation should come from outside the \u201cPurchase\u201d class.<\/p>\n\n\n\n Remember there is a difference between a software architect and a software developer. Software architects have usually experienced team leaders, who have good knowledge about existing solutions which help them make right decisions in the planning phase. A software developer should know more about software design and enough about software architecture to make internal communication easier within the team.<\/em><\/p>\n","protected":false},"excerpt":{"rendered":" The difference between software architecture and software design is not really known to most of the people. Even for developers, the line is often shadowy and they might mix up elements of software architecture patterns and design patterns. In this blog, I would like to simplify these concepts and explain the differences between software design … Continue reading “The Difference between Software Architecture and Design”<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[4],"tags":[28,29],"class_list":["post-79","post","type-post","status-publish","format-standard","hentry","category-computing","tag-software-architecture","tag-software-design"],"_links":{"self":[{"href":"https:\/\/axedgeconsulting.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/79","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/axedgeconsulting.com\/blog\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/axedgeconsulting.com\/blog\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/axedgeconsulting.com\/blog\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/axedgeconsulting.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=79"}],"version-history":[{"count":1,"href":"https:\/\/axedgeconsulting.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/79\/revisions"}],"predecessor-version":[{"id":80,"href":"https:\/\/axedgeconsulting.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/79\/revisions\/80"}],"wp:attachment":[{"href":"https:\/\/axedgeconsulting.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=79"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/axedgeconsulting.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=79"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/axedgeconsulting.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=79"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}