...
| Table of Contents | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Requirement types fulfill fulfil 3 needs:
Defining key patterns: As a project is gaining maturity, key patterns for requirements are established. Administrators can define which are the main keys, and even lock down the keys that can be inserted in spaces,
Validations: Administrators can define properties and dependencies which are required for a type of requirement.
Templates: When users insert such keys in an empty table, it will setup the table with all the properties, by default.
...
We only display invalid requirements from requirement properties, not optional properties.
...
Inserting a requirement type as a template
When users insert a new requirement in a new page, which belongs to a Requirement Type, it creates the entire table:
...
If requirements are already inserted, then “Quick Fixes” Fix” will also update the table dynamically:
...
Only space administrators can configure requirement types. Users have access to this screen in read-only mode, the only action they can perform is reset the sequences.
...
Editing requirement types
Properties are described as a horizontal table, so it looks like the final page.
...