This page is an experimental feature that shows traceability between the ITK transport and distribution requirements and the codebase (including the API, reference implementation and samples project).
The intention is both to show the requirments coverage of the reference implementation as well as allowing readers to jump to the specific parts of the API and reference implementation that trace to a particular requirement they are interested in.
Currently there are some requirement annotations in the API and reference implementation codebase to illustrate how the traceability might function. The traceability is not complete - however we are looking for feedback (positive and negative) to understand how useful (or not) such tracebility is.
At the moment the trace table (below) is entirely built from the annotation references in the source code. Our ambition is to eventually show the requirement text in the table below however we would need a machine processable list of requirements to achieve this.
| Requirement | Reference Implementation Code |
|---|---|
| COR-DEH-09 |
|
| COR-DEH-02 |
|
| COR-DEH-01 |
|
| COR-DEH-04 |
|
| Requirement | Reference Implementation Code |
|---|---|
| IFA-SEC-02 |
|
The following table is a guide to the implementation status of the traced requirements
| Item | Description |
|---|---|
| - | If the requirement you are interested in is not represented in the trace table (above) then it has not been traced to the API and reference implementation codebase - the implementation status is effectively "unknown" |
| REQ-## | The requirement has been traced to the codebase, however implementation of the necessary logic has not been started - i.e. there are only code stubs |
| REQ-## | Traced requirements in the codebase indicate that the of the functionality is in-place but the requirement has not been fully realised |
| REQ-## | All traced references of the requirement in the codebase indicate that the requirement has been fully-implemented |