Content deleted Content added
m v2.05b - Bot T18 CW#553 - Fix errors for CW project (<nowiki> tags) |
No edit summary |
||
Line 10:
# "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 requirement|non functional requirements]]) then models the components accordingly. The team can use [[C4 model|C4 Model]] which is a flexible method to model the architecture just enough. Note that synchronous communication between software architectural components, entangles them and they must share the same architectural characteristics. <ref>{{Cite book |title=Fundamentals of Software Architecture An Engineering Approach |publisher=O'Reilly Media |year=2020 |isbn=9781492043423}}</ref>
[[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}}
| |||