Cross-cutting concepts
How to
- Contents
The subpages available via the table below cover cross-cutting concerns (a.k.a. aspects in some programming languages) Fill in these chapters if there is NO building block that covers this aspect. If some of the concepts are not relevant for your project mention this fact instead of removing the section.
- Motivation
Some concept cannot be “factored” into a separate building block of the architecture (e.g. the topic “security”). This section of the template is the location where you can describe all decision for such a cross cutting topic in one central place. Nevertheless, you have to make sure that all your building blocks conform to such decisions.
- Form
.. can be varied. Some concepts are plain natural language text with a freely chosen structure, some others may include models/scenarios using notations that are also applied in architecture views.
| Aspect | Importance/Rationale |
|---|---|
| Domain Models | City GML |
| Recurring or Generic Structures and Patterns | |
| Persistency | |
| User Interface | |
| Ergonomics | |
| Flow of Control | |
| Transaction Procession | |
| Session Handling | |
| Security | |
| Safety | |
| Communications and Integration with other Software Systems | |
| Plausibility and Validity Checks | |
| Exception/Error Handling | |
| System Management and Administration | |
| Logging, Tracing | |
| Business Rules | |
| Configurability | |
| Parallelization and Threading | |
| Internationalization | |
| Migration | |
| Testability | |
| Scaling, Clustering | |
| High Availability | |
| Code Generation | |
| Build-Management |
