search

openETCS / model-evaluation

part of WP7: collects the various activities regarding selecting a tool and formal specification for modeling
13 stars 20 forks source link

ProR Review: Traceability to different kinds models and documents #59

Closed UweSteinkeFromSiemens closed 11 years ago

UweSteinkeFromSiemens commented 11 years ago

With reference to https://github.com/openETCS/model-evaluation/tree/master/management/ProR_FormalMind, chapt. 3.8: ProR must not only be able to import and trace requirements from the ERA documents, but also be capable of managing, tracing and linking requirements to artefacts in all other kinds of documents like test cases, test reports, source code, not-EMF-based models, ... In sum, to any kind of intermediate and final results produced in openETCS. The document "pror_evaluation" therefore should be complemented with this requirement.

jastram commented 11 years ago

This has been addressed in c0674a1497cd0d7fc16a84441214af094b814f62 (resulting in Section 3.5).

@UweSteinkeFromSiemens Please close if this provides a satisfying answer.

UweSteinkeFromSiemens commented 11 years ago

"It is conceivable that traceability to other artefacts may become necessary ..." is phrased too weak. Traceability to such other artefacts like test cases, test reports, source code, other not-EMF-based models, in short to all relevant results produced in the development process is simply required and therefore mandatory. Requirements management and traceability must not be a closed shop, but interferes with almost all and everything in the project. Please rephrase.

jastram commented 11 years ago

Changed conceivable -> certain Addressed in 623dd179b4cddfc48302e4493821fadc26605fec

@UweSteinkeFromSiemens Please close if this provides a satisfying answer.