Tracecing Requirements and SCADE Models

openETCS / toolchain

WP7: Top Level Project for the toolchain

26 stars 30 forks source link

Tracecing Requirements and SCADE Models #306

Closed UweSteinkeFromSiemens closed 8 years ago

UweSteinkeFromSiemens commented 10 years ago

When starting with SCADE modelling in WP3, the requirements have to be linked to model artefacts from the beginning. How can this be achieved?

jastram commented 10 years ago

@UweSteinkeFromSiemens good question.

@MarcPantel considering that you volunteered to contribute to traceability in WP7, can you take this on?

UweSteinkeFromSiemens commented 10 years ago

As long as this issue is not fixed, the links to the requirements should be set in this way for SCADE System and SCADE Suite:

Decorate the comment fields with the entry: "covers: #REQ#ReqID#REAL#"

@christianstahl, @VNuhaan : fyi.

MERCEmentre commented 10 years ago

Le 13/03/2014 15:46, Uwe Steinke a écrit :

Decorate the comment fields with the entry: "covers: #REQ#ReqID#REAL#"

https://github.com/christianstahl

What are "REQ", "ReqID" and "REAL"? Could you provide an example ?

Best regards, d.

UweSteinkeFromSiemens commented 10 years ago

Here is an example: covers: #REQ#Subset_026_3.3.0_3.5.2.3.2#REAL# The ReqID: Subset_026 is the document, 3.3.0 its version number, 3.5.2.3.2 the paragraph number in the document. If an unique requirement ID is already available from ProR, this could be taken instead, but with #REQ# and #REAL# as delimiters.

@janWelte : The requirement IDs should not be chosen in an improper way. Is this workaround suitable until linking with ProR becomes available for SCADE?

janWelte commented 10 years ago

Dear Uwe, dear Michael,

for me this is a perfect and very suitable workaround. As it seams to be suitable with Reqtify and some other traceing solutions looking for tags.

We can improve it if we, (now and forever) define a unique readable Requirement ID.

[ ] define unique Requirement ID (WP2, WP3, WP4 @sbaro @UweSteinkeFromSiemens @BerndHekele @MarcBehrens )
[ ] Add Requirement ID to Requirement files (@janWelte)
[ ] Add manual for traceability comment to modeling guidelines (@UweSteinkeFromSiemens)

Should be a fast thing and actually also an option for SysML fallback (maybe automatic creation by linking @jastram)

Best regards Jan

jastram commented 10 years ago

No idea why this was assigned to @MarcPantel . I assigned it to @janWelte . @janWelte - you said you'll write the spec today. Once it's done, this one can be closed.

janWelte commented 10 years ago

Specification have been added in issue #349

jastram commented 8 years ago

@UweSteinkeFromSiemens - I think this is now resolved with Raphael's traceability document. I will close - please reopen, if you disagree.