Please enable JavaScript.
Coggle requires JavaScript to display documents.
Document Software Architecture - Coggle Diagram
Document Software Architecture
WHY we document
Analysis
Education
Construction - it is blueprint
Views
deployment
how component works in runtime
processes
...
modules
View based architecture
View 1
View 2
Types of Views (standart template includes all of them)
component and connector view (CNC) - how system is structured as a set elements with runtime behaviours and interactions
RelationShips: interface and protocol
Properties: runtime quality attributes: latency, throughput, etc
Elements: component and connections, REST-API, data stores etc
Examples
Pipe and Filter view, topology
SOA: Service Oriented Arhitecture View
Shared Data View
Allocation views - how the system relates to non-software structures in its environment
RelationShips: how software elements allocates to/on environment elements
Properties: requires properties to allocate software to environment
Elements: software ellements, enviroment elements
Examples:
Implementation View. (jar, war file and container relations)
Deployment
Modules views - how system is structured as a set of code units
Properties - includes names and its responsibility
RelationShips - relation among modules. (A is part of B, A depends on B, etc)
Elements - code unit names, that implements responsibility (blueprint od the code)
Important examples:
Generalization views
Decompotions Views
Layered View
Marketecture - view for stakeholds, non technical, mix of C&C, Modules and Allocation views
View details
view explains what elements responsibilities, important properties
properties describe usually QA
show this structures and relationship among them
primary function - show the structures whith represent the view
View details
dynemic arhcitecture - compenents/parts which can be changes. Like cloud options with scale
contex - external enviroment and how it is relates
variability - replacable options
behaviour - how elements relates - can be tricky to document. can be
2) Comprehensive language - shows the complete behaviour of the syste,, usualy state based
Types: statechart, SDL diagram, Z pecification
(Both can describe whole system, parts of hte system, or individual elements)
1) Trace Oriented language: describe how System reacts to the particular stimulus, A calls B etc. It is provide only
types: usecases, communacation diagrams, sequesnce diagram,
Rationale - document why we did this decitions
Interfaces - must be documented as a part of architecture
View Strucutre
Types'
Semi formal - UML, have some standarts, UML diagam
Formal - views describiss in precized semantic, ussualy mathematic.
Informal - draw.io, any digram, any style. Can't be formally analyzed, written in natural langauage:
box and line drawing, need explanation
tables or lists
Which Views I need to add to SAD
Methid to chose the view
note that views which stakeholders needs
combine it, prioritized basxed on needs
Build a stakeholdes/view table