Document an aspect of your architecture. Something orthogonal or cross-functional like logging, exception handling or configurability.
Documents an orthogonal or cross-cutting concern for the architecture of the system. By describing these aspects in their own documents, components applying those concerns may just reference them.
Examples for architecture aspects are:
- Exception Handling
- Component Configuration
The document type architecture aspect provides the following properties:
Please note that only information about specific properties is provided here. Common document property used by all document types are documented by Document Properties.
A detailed description of the architecture aspect.
Add any additional sections to this one (if required) to document details on the aspect.
Quality scenarios document the important quality aspects of the architecure aspect. Add a reference to a quality scenario document for each important quality of the aspect.
Use cases allow to define how the aspect is used.
List the constraints that limit the solution space for the aspect.
The design or implementation of an architecture aspect may be based on some decisions. List those that are important to understand the aspect.
Provide information about how to apply the solution.
Discuss open issues and provide an overview over possible next steps.
Divide a complex aspect into smaller parts.
The related doctypes are already mentioned in the sections:
Components usually reference architecture aspects that have an impact on them.