Back معمارية برمجيات Arabic Софтуерна архитектура Bulgarian সফটওয়্যার আর্কিটেকচার Bengali/Bangla Arquitectura de programari Catalan It-arkitektur Danish Softwarearchitektur German Arquitectura de software Spanish Software arkitektura Basque معماری نرمافزار Persian Ohjelmistoarkkitehtuuri Finnish
| Part of a series on |
| Software development |
|---|
Software architecture is the set of structures needed to reason about a software system and the discipline of creating such structures and systems. Each structure comprises software elements, relations among them, and properties of both elements and relations.[1][2]
The architecture of a software system is a metaphor, analogous to the architecture of a building.[3] It functions as the blueprints for the system and the development project, which project management can later use to extrapolate the tasks necessary to be executed by the teams and people involved.
Software architecture is about making fundamental structural choices that are costly to change once implemented. Software architecture choices include specific structural options from possibilities in the design of the software. There are two fundamental laws in software architecture:[4][5]
- Everything is a trade-off
- "Why is more important than how"
"Architectural Kata" is a teamwork which can be used to produce an architectural solution that fits the needs. Each team extracts and prioritizes architectural characteristics (aka non functional requirements) then models the components accordingly. The team can use C4 Model which is a flexible method to model the architecture just enough.[6]
Documenting software architecture facilitates communication between stakeholders, captures early decisions about the high-level design, and allows the reuse of design components between projects.[7]: 29–35
Software architecture design is commonly juxtaposed with software application design. Whilst application design focuses on the design of the processes and data supporting the required functionality (the services offered by the system), software architecture design focuses on designing the infrastructure within which application functionality can be realized and executed such that the functionality is provided in a way which meets the system's non-functional requirements.
Software architectures can be categorized into two main types: monolith and distributed architecture, each has its own subcategories.[5]
Software architecture tends to become more complex over time. Software architects should use "fitness functions" to continuously keep the architecture in check.[5]
- ^ Clements, Paul; Felix Bachmann; Len Bass; David Garlan; James Ivers; Reed Little; Paulo Merson; Robert Nord; Judith Stafford (2010). Documenting Software Architectures: Views and Beyond, Second Edition. Boston: Addison-Wesley. ISBN 978-0-321-55268-6.
- ^ "Software Architecture". www.sei.cmu.edu. Retrieved 2018-07-23.
- ^ Perry, D. E.; Wolf, A. L. (1992). "Foundations for the study of software architecture" (PDF). ACM SIGSOFT Software Engineering Notes. 17 (4): 40. CiteSeerX 10.1.1.40.5174. doi:10.1145/141874.141884. S2CID 628695.
- ^ Head First Software Architecture. O'Reilly Media. 2024. ISBN 978-1098134358.
- ^ a b c Fundamentals of Software Architecture: An Engineering Approach. O'Reilly Media. 2020. ISBN 978-1492043454.
- ^ Fundamentals of Software Architecture An Engineering Approach. O'Reilly Media. 2020. ISBN 9781492043423.
- ^ Bass, Len; Paul Clements; Rick Kazman (2012). Software Architecture in Practice, Third Edition. Boston: Addison-Wesley. ISBN 978-0-321-81573-6.