Requirements Specification ¶
1 Overview ¶
This is an example of software requirements specification.
2 Requirements ¶
This is a regular paragraph in the document.
| # | UL | DL | COV | DR | |
|---|---|---|---|---|---|
| REQ-001 | This is a first requirement (controlled paragraph with ID equal to "REQ-001"). | ||||
| REQ-002 | This is a second requirement. |
3 Data Protection Requirements ¶
The requirements in this section mitigate the minimal cut sets identified by the Fault Tree Analysis of the "Permanent loss of user data" top event.
| # | UL | DL | COV | DR | |
|---|---|---|---|---|---|
| REQ-020 | The software shall verify every completed backup by restoring it to a scratch area and comparing record checksums against the primary copy. | FTA-002 | |||
| REQ-021 | The software shall alert the user when a scheduled backup has not completed successfully within its configured period. | FTA-001 | |||
| REQ-022 | The software shall retain deleted records for at least 30 days and shall require an explicit second confirmation for any bulk deletion. | FTA-003 |
4 Reporting Integrity Requirements ¶
The requirements in this section mitigate the minimal cut sets identified by the Fault Tree Analysis of the "Misleading report delivered" top event.
| # | UL | DL | COV | DR | |
|---|---|---|---|---|---|
| REQ-023 | The software shall carry the measurement unit with the value from the data model into every report column. | FTA-004 | |||
| REQ-024 | The software shall invalidate cached report data when the underlying records change and shall stamp every report with the time of its data snapshot. | FTA-005 |
5 Document History ¶
| Revision | Description of changes | Date |
|---|---|---|
| A | Initial version | 2026-07-09 |