What is Software Architecture?
That’s right, Agile Architecture is not some new type of building that can bend over and touch its toes. Agile Architecture involves software architects, not building architects. However, in both software and buildings, architecture serves a similar function.
Construction architects design buildings to have a purpose, whether they are movie theaters, libraries, or private homes. They have to take into account the tastes and preferences of their audience, the space and monetary resources available, and the environment around their building. Then, they might design a blueprint, detailing the organization of components inside and outside the building. What color is the carpet? How wide is the door? How many windows, tables, chairs? Most architects simplify this process by creating general guiding principles. Maybe they are designing a dance studio. The architect might decide there should be a mirror along one wall of every practice room, and that all floors should be made of polished wood. Such principles would also guide the building’s future evolution. If the dance studio adds another practice room, it would also have polished wood floors and a mirror on one wall.
Software architecture is remarkably similar. Just like a building, software has a purpose, whether it makes up a Google Spreadsheet or Temple Run 2. To suit its purpose, software must be organized; it must have different components that interact with each other and with the environment around them. Just like in our dance studio, the organization of these components follows general principles that guide the design and evolution of the product. In Microsoft Word, the software has a toolbar across the top. If Word adds a new component to erase text, then an eraser symbol might appear on the toolbar. It might be activated when you click on it. A neon pink flashing eraser symbol wouldn’t just appear in the middle of the screen and start randomly erasing your text. The new component would have to act according to Microsoft Word’s pre-established guiding principles: its architecture. Thus, architecture governs both the current and future design of a product. According the Institute of Electrical and Electronics Engineers (IEEE), software architecture is the fundamental organization of a system embodied in its components, their relationships to each other, and to the environment, and the principles guiding its design and evolution.
So, What is Agile Architecture?
Just like buildings, software cannot be static. It must constantly react to changes in its environment, and it must improve to stay ahead of its competition and continue to please its customers. A building in an earthquake zone might need to be retrofitted. Software vulnerable to hacking might need an antivirus or other security components. Agile architecture is software architecture that is made to adapt: to react to changes in its environment quickly and evolve constantly. To accomplish these goals, Agile Architecture has a few defining characteristics.
First, it is designed so future changes will be inexpensive. Agile Architects try to include independent components in their software, so they can be added or subtracted without disrupting other processes. They try to avoid building constraints into their architecture that could prevent inexpensive future growth or adaptation.
Second, Agile Architecture focuses on simplicity, efficiency, and functionality. Agile Architects do not add unnecessary components to their software. An Agile Architect would not add an eraser component to Microsoft Word, because the delete key already serves this function. Instead, they always consider long-term goals when making changes. They ensure that each change appeals to users of their software and enhances its purpose. When adding improvements, they also consider whether there are components of the software that are no longer necessary, and remove these components to maintain its efficiency and flexibility.
Third, Agile Architecture requires teamwork and forward-thinking. Teams of software developers and designers often include an Agile Architect to try to anticipate future problems. Agile Architects understand that constant innovation is necessary to succeed in the competitive market for technology. So, they believe in small coordinated groups with clearly defined roles. They encourage group members to specialize in a certain aspect of the project, encouraging responsibility, expertise, and independent work. Each individual portion can then be fitted seamlessly into the larger whole with minimal effort, and if opportunities for improvement arise, the group member responsible for that aspect can be contacted. Both on their computers and in the workplace, Agile Architects have systems in place to improve their product and react to outside changes in the most efficient way possible.
In summary, software architecture is the organization and guiding principles of a system. Agile Architects work to stay ahead of competition and please customers by constantly innovating and improving their product. They design their software to be easily adaptable, making their products both efficient and inexpensive. Also, they are key group players, recognizing that efficiency and adaptability in the work environment will transfer to their product. Agile Architecture is the software of the future, designed to keep up with the rapidly changing modern world.
Works Cited
Eeles, Peter. “What Is a Software Architecture?” IBM Cognitive Advantage Reports, IBM Corporation, 15 Feb. 2006, www.ibm.com/developerworks/rational/library/feb06/eeles/index.html.
Veerasingam, Warren. “7 Things You Don’t Know about Agile Architecture – Warren Veerasingam – Medium.” Medium, 29 Apr. 2018, www.medium.com/@warrensbox/7-things-you-dont-know-about-agile-architecture-c1125e53e5d6.