Please enable JavaScript.
Coggle requires JavaScript to display documents.
Software Architectures & Design - Coggle Diagram
Software Architectures & Design
Documentation
Is for communicating cpmplex information and ideas
7 Principles
Record rationale
Keep documentation current but not too current
Avoid ambiguity
Review documentation for fitness of purpose
Avoid unnecessary repetition
Use a standard organization
Write from the point of view of the stakeholder
The Business context
Qualiti Attrinbutes
Evaluation
Architecture Tradeoff Analysis Method (ATAM)
Purpose
Assess the consequences of architectural decisions in light of quality attribute requirements and business goals
ATAM is a stakeholder centric approach
When
Be used throughout the lifecycle
Phase
Phase 0: Partnership and Preparation
Phase 1: Intial Evaluation
Phase 2: Complete Evaluation
Phase 3: Follow-up
Team
4 to 6 people
Architectural Structures
Architectural Drivers
Overview
Architectural Views
Module View
Definition
Shows elements that are units of implementation (static perspective)
Relations
Attachments of components to connectors
Allocation view
Definition
How software structures are allocated to non-software structures
Relations
Varies,but often includes "allocated to", "connected to"
C&C View
Definition
Shows elements that have run-time behavior and interaction
Relations
A is part of B
A depends on B
A is a B