Please enable JavaScript.
Coggle requires JavaScript to display documents.
The Blueprint - Coggle Diagram
The Blueprint
Quality Attributes | non-functional requirements
Availability
Security
Scalability
Disaster Recovery
Performance
Response time
Latency
Extensibility
Accessibility
Monitoring
Management
Audit
Flexibility
Maintainability
Legal, Regulatory and Compliance
Internationalisation (i18n)
Localisation (L10n)
Effective sketches
Shapes
Responsibilities
Label
Lines
Title
Color
Layout
Borders
Orientation
Keys
Principles
Architecture principles
Layering strategy
Placement of business logic
High cohesion, low coupling
Stateless components
Stored procedures
Domain model - rich vs anaemic
Use of the HTTP session
Always consistent vs eventually consistent
Development principles
Codingstandardsandconventions
Automated unit testing
Static analysis tools
Role
Technical Risks
Architecture Evolution
Designing Software
Coding
Quality Assurance
Architectural drivers
C4
Component
Context
Context diagram
Interactions
Motivation
IT systems
Users, actors, roles, personas, etc
Classes
Container
Constraints
Time and budget constraints
Technology constraints
Existing systems and interoperability
Targetdeploymentplatform
Technology maturity
Approvedtechnologylists
Open source
Vendor“relationships
Internal intellectual property
Past failures
People constraints
Organisational constraints
Tech stack
Do you have constraints?
Do you want consistency?
Do you have complex non-functional requirements?
Designing Software
Architectural Drivers
Quality Attributes
Constraints
Functional requirements
Principles
Document