Change Requests
Records use stable project-prefixed sequence numbers in original request order, not retrospective file creation time. The initial request is reconstructed from available evidence; see its provenance. Canonical requirement IDs and historical acceptance records remain unchanged.
Each request is a change_request Need with Draft / Accepted / Implemented
status. Implementation status describes completed agreed scope; requirement
acceptance, verification and release approval remain separate.
ID |
Title |
Status |
|---|---|---|
Initial project request: traceability exploration |
implemented |
|
Starting-node requirement amendment |
implemented |
|
Draft usability problem resolution |
implemented |
|
Problem-report model and folder handover |
implemented |
|
Draft relationship-control ordering |
implemented |
|
Centered parents and interactive seed selection |
implemented |
|
STV_CR_007: Record folder layout |
implemented |
|
STV_CR_008: Trace software elements to component code and tests |
implemented |
|
STV_CR_009: Requirement filenames and verification levels |
implemented |
|
STV_CR_010: Consolidate system and software test specifications |
implemented |
|
STV_CR_011: MIT license and author attribution |
implemented |
|
STV_CR_012: Cancel release and close preparation findings |
implemented |
|
STV_CR_013: Vertical target levels for artifacts and test records |
implemented |
|
STV_CR_014: Persistent artifact details on the right side |
implemented |
|
Collapse all graph relationships |
implemented |
|
Save the visible view as SVG |
implemented |
|
Smaller configurable detail text |
implemented |
|
Page-wide Need attribute controls |
implemented |
|
Remember current view across page reloads |
implemented |
- Initial project request: traceability exploration
- Starting-node requirement amendment
- Draft usability problem resolution
- Problem-report model and folder handover
- Draft relationship-control ordering
- Centered parents and interactive seed selection
- STV_CR_007: Record folder layout
- STV_CR_008: Trace software elements to component code and tests
- STV_CR_009: Requirement filenames and verification levels
- STV_CR_010: Consolidate system and software test specifications
- STV_CR_011: MIT license and author attribution
- STV_CR_012: Cancel release and close preparation findings
- STV_CR_013: Vertical target levels for artifacts and test records
- STV_CR_014: Persistent artifact details on the right side
- STV_CR_015: Collapse all graph relationships
- STV_CR_016: Save the visible view as SVG
- STV_CR_017: Smaller configurable detail text
- STV_CR_018: Page-wide Need attribute controls
- STV_CR_019: Remember current view across page reloads