Closed stanpinteTheSignallingCompany closed 10 years ago
1) no justification is provided for element tag as "definition" (cf issue definition vs requirement and current state of the model)
2) for element tag as "non implemantable" no justification is provided in the current state of the model for example §3.1.4.1.2 in the current model, the element s "not implementable" but no comment or no specification issue is provided.
How tool allow to detect that for each "non implementable" items at least a comment or a spec issue is provided ? Such a mechanism will participate to the verification and traceability activities on the model.
This comment is not acceptable, as not based on facts. 1 means "weakly rejected", therefore we cannot accept it for "Management of requirement justification" and "Traceability of exported requirements".
We shall appeal to the WP leader if 1 is maintained.
This comment is not acceptable, as not based on facts. 1 means "weakly rejected", therefore we cannot accept it for "Management of requirement justification" and "Traceability of exported requirements".
We shall appeal to the WP leader if 1 is maintained.
there is the following note:
"Concerning management of requirement justification and traceability to exported requirements, the current model do not show how this can be systematically covered."
Incorrect statement. The ERTMSFormalSpecs toolchain allow for complete traceability, and provide complete tooling support to enforce this traceability.
Justify why 1 instead of 3 for "Management of requirement justification" and "Traceability of exported requirements"