Provide an overview over the information on this document. Readers may decide on this description if the document contains relevant information to them.
Section
title
Summary
Provide a summary of the documents structure and key points. This is an informative abstract typically of about 100 to 200 words.
Section
title
Technical Constraints
List all technical constraints in this section. This category covers hardware and software infrastructure, applied technologies (operating systems, middleware, databases, programming languages, ...).
Expand
title
Expand for detailed information from https://github.com/arc42
More help to document quality goals in this overview is found on arc42 on GitHub.
Tip Box
title
Using projectdoc
Typically you add documents of type Project Constraint to the homepage of constraints and then reference all technical constrains with the Display Table Macro.
You may also create a Section document and attach this section as a child to this document. Section documents share the lifespan of the parent and are removed with them. If you use a section document, the requirement overview may be easier to reference if requested. The document can be edited independently of other information. Typically is depends on the amount of information specified, if a separate document is advisable.
Section
title
Organizational Constraints
List all organizational, structural, and resource-related constraints. This category also covers standards and legal constraints that you must comply with.
Expand
title
Expand for detailed information from https://github.com/arc42
Source:
More help to document quality goals in this overview is found on arc42 on GitHub.