Issue 5331: Trace should not apply only on WorkDefinition but on every model element (spem-rtf) Source: Softeam (Mr. Philippe Desfray, phd@softeam.fr Philippe.Desfray@softeam.fr philippe.desfray@softeam.fr) Nature: Uncategorized Issue Severity: Summary: The SPEM standard says : "A Trace dependency acts between WorkDefinitions and is mainly used to trace requirements and changes across models. It has the same semantics as UML Trace." Trace should not apply only on WorkDefinition but on every model element. We could have for examples a requirement on process, and trace a specific activity to the requirement, thus expressing that we have defined this activity to fulfill the requirement. This is in line with the UML semantics. Resolution: This is a change to the specification text, with no change to the metamodel. Revised Text: Modify the text in section 6.1, page 6-4: “A Trace dependency acts between two model elements of any type and is mainly used to trace requirements and changes across models. It has the same semantics as UML Trace.” Actions taken: May 29, 2002: received issue September 24, 2004: closed issue Discussion: End of Annotations:===== Reply-To: From: "DESFRAY Philippe" To: Subject: May be an issue Date: Wed, 29 May 2002 12:40:05 +0200 X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0) Importance: Normal Dear all, I have receive a question from 'Vivienne Suen' and provided the following answer : (Question) I am curious about how Trace dependencies are expected to be used. (Answer) ==> (SPEM) A Trace dependency acts between WorkDefinitions and is mainly used to trace requirements and changes across models. It has the same semantics as UML Trace. In UML its purpose is to manage traceability. That can be used to trace a design model that refines an analysis model. I'll log a question about this to the spem ftf, because I am not sure why does it applies only on WorkDefinition. We could have for examples a requirement on process, and trace a specific activity to the requirement, thus expressing that we have defined this activity to fulfill the requirement. So SPEM says that "Trace acts between workdefinition". Why is there this restriction? In my opinion we should not restrict Traceability, and stick to the general purpose aimed in the UML spec. In the other alternative, it should be expressed in OCL. I beleive this is an issue. Regards -- Philippe DESFRAY VP for R& D phd@softeam.fr SOFTEAM --------Think Object 144 avenue des Champs Elys es - 75008 PARIS - Tel (33 1) 53968400 - Fax (33 1) 53968401 Reply-To: From: "DESFRAY Philippe" To: Subject: Issue to the SPEM standard Date: Wed, 29 May 2002 15:25:41 +0200 X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0) Importance: Normal The SPEM standard says : "A Trace dependency acts between WorkDefinitions and is mainly used to trace requirements and changes across models. It has the same semantics as UML Trace." Trace should not apply only on WorkDefinition but on every model element. We could have for examples a requirement on process, and trace a specific activity to the requirement, thus expressing that we have defined this activity to fulfill the requirement. This is in line with the UML semantics. -- Philippe DESFRAY VP for R& D phd@softeam.fr SOFTEAM --------Think Object 144 avenue des Champs Elys es - 75008 PARIS - Tel (33 1) 53968400 - Fax (33 1) 53968401