Content deleted Content added
Magioladitis (talk | contribs) m Moved punctuation mark to correct place + other fixes, References after punctuation per WP:CITEFOOT and WP:PAIC |
No edit summary |
||
Line 13:
[[Software documentation|Documenting software]] architecture facilitates communication between [[Stakeholder (corporate)#In management|stakeholders]], captures early decisions about the high-level design, and allows the reuse of design components between projects.<ref name="SAP2">{{cite book|last=Bass|first=Len|author2=Paul Clements |author3=Rick Kazman |title=Software Architecture in Practice, Third Edition|publisher = Addison-Wesley|year=2012|___location=Boston|isbn=978-0-321-81573-6}}</ref>{{rp|29–35}}
It's [[software architect]]'s responsibility to match [[List of system quality attributes|architectural characteristics]] (aka [[non-functional requirement]]s) with business and user requirements. For example "[[Customer satisfaction|user satisfactions]]" requires availability, fault tolerance, security, testability, recoverability, agility and performance in the system. As another example, [[Time to market|time-to-market]] requires maintainability, testability and deplorability. <ref name="O'Reilly Media" />
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 requirement]]s.
| |||