4. Document archetypes
StrictDoc shall support the following document archetypes: requirements document and specification document. For both archetypes, StrictDoc shall further support the following options.
Requirements document | Specification document | |
---|---|---|
Examples | Most typical: requirements lists split by categories (e.g., Functional Requirements, Interface Requirements, Performance Requirements, etc.) | Often: a standard document |
Structure | Not nested or not too deeply nested | Nested |
Visual presentation | Requirements are often presented as table cells. Cells can be standalone or the whole section or document can be a long table with cells. | Requirements are rather presented as header + text |
Unique requirement identifiers (UID) | Most always |
|
Requirement titles |
|
Requirement titles are most often section titles |
Real-world examples |
|
|
This draft requirement is the first attempt to organize this information.