Software architecture: Difference between revisions

Revision as of 11:20, 29 December 2024

Revision as of 07:12, 30 December 2024

Line 31:

There is no sharp distinction between software architecture versus design and requirements engineering (see [[#Related fields|Related fields]] below). They are all part of a "chain of intentionality" from high-level intentions to low-level details.<ref name="FAIRBANKS2010">{{cite book|author=George Fairbanks|title=Just Enough Software Architecture|year=2010|publisher=Marshall & Brainerd}}</ref>{{rp|18}}

== Software architecture style vs. software architecture pattern ==

{{Main article|List of software architecture styles and patterns}}

'''Software architecture style''' refers to a high-level structural organization that defines a family of systems, including a vocabulary of components, connector types, constraints on combinations, and semantic models for determining overall system properties. <ref name="O'Reilly Media" />

'''Software architecture pattern''' is a reusable, proven solution to a specific, recurring problem focused on architectural design challenges, which can be applied within various architectural styles. <ref name="O'Reilly Media" />

== Anti-patterns ==

Line 203 ⟶ 209:

*[[Systems design]]

*[[Software Architecture Analysis Method]]

*[[List of software architecture styles and patterns]]

*[[Software architecture description]]

*[[Time-triggered system]]