5 Common Misconceptions About Software Architecture
By Arijit Banerjee
Software or IT architecture is a word that gets thrown around quite often in the tech world. We may claim to understand what it means, but there isn't a single globally accepted definition of the term. Consequently, it leads to various misconceptions about its meaning. In this blog, we will look at some common misconceptions about software architecture.
Software Architecture revolves only around infrastructure
Yes, it is the foundation, but there's a lot more to architecture than just the infrastructure. Architects have to look at the whole problem domain, including the applications involved. A narrow view might lead to the creation of an appealing infrastructure, but it might end up being the wrong one for the problem at hand.
Software Architecture is all about the database
Architecture is more than just a technology watch. Yes, network/database/transaction server/ GUI etc plays a big role in the architecture, but it is not only about just one aspect. Hence, it is much more than that.
Software Architecture is one dimensional
Many people try to make the architectural description flat - one or two dimensional. It is difficult to describe the intricacies of a complex system using flat language. Many people try to communicate various aspects of architecture using a single family of components and connectors or just one type of concept. Architecture is a complex beast. We need multiple blueprints to address the various concerns and structures that are a part of software architecture.
Software architecture comes after system architecture
Sometimes system engineers design software-intensive systems without involving software engineers in the beginning of the process. Hence, it leads to isolation of clusters of software on various computers. It then becomes a rigid system, and the final system isn't adaptable to changes in the underlying hardware.
Software Architecture is majorly about design
The design is just one aspect of architecture, which focuses on the elements that are structurally important, and have an impact on the performance and adaptability of the system. It also involves choosing a small set of patterns and styles that will permeate the rest of the design. Hence, it is majorly about design.
What misconceptions have you heard about software architecture? Tell us in the comments section below.
About the Author:
Head of Programs
Manipal Global Academy of IT (MGAIT)
Vishnupriya Raghavan has a PhD in Information Systems and Operations. She also holds Master’s degrees in Mathematics and Information Systems. An educational professional with a distinguished career in providing educational instruction and overseeing academic affairs, she has served as the Director of Programs at Institute of Product Leadership, Program Head for MBA and MSc programs affiliated to Edith Cowan University - Australia, Asia Pacific University - Malaysia, Cardiff Metropolitan University and Anglia Ruskin University - UK, Bangalore University and Visveswaraya Technological University - Belgaum.
She has spearheaded the development of Masters in Science (Information Technology with specialization in Mobile Apps) curriculum in collaboration with Anglia Ruskin University and Cardiff Metropolitan University, UK, Masters in Business Administration (specialization in Information Systems) curriculum in collaboration with Edith Cowan University, Australia. As the Director of Academic Programs Office at the Institute of Product Leadership, she was instrumental in shaping the curriculum and crafting the combination of content, instructional methods and assessments for the Masters in Business Administration program in Product Leadership.