| OTE traceability [message #575105] |
Thu, 13 August 2009 04:17  |
Nirmal Sasidharan
Messages: 120
Registered: July 2009
Location: Germany |
Senior Member |
|
|
Does OTE offer end-end traceability together with OSEE define? Requirements <-> Design <-> Code <-> Test. It the traceability achieved using the standard relations tree editor in OSEE or is there any other UI support for this?
Thanks and regards,
Nirmal
|
|
|
| Re: OTE traceability [message #575874 is a reply to message #575105] |
Sun, 25 October 2009 22:32  |
 Ryan D. Brooks
Messages: 100
Registered: July 2009 |
Senior Member |
|
|
Nirmal,
OSEE uses relations to provide all types of traceability. The basic method for managing this traceability is through the relations
section of the artifact edtior using drag-n-drop to create new relations. There are a number of predefined relation types used for
traceability including:
Relation Type: Artifact Type <-> Artifact Type
Allocation: Requirement <-> Component
Code-Requirement: Code Unit <-> Requirement
Design: Requirement <-> Design
Requirement Trace Requirement <-> Requirement
Validation: Requirement <-> Artifact
Verification: Requirement <-> Test Unit
This type definition is using inheritence so for example the type "Artifact" for the "Validation" relation type means all artifact
types since all types extend "Artifact".
There are a number of BLAMs used to create traceability reports. For example, org.eclipse.osee.define.blam.operation.PublishSubsystemToDes ignTraceability generate an
Excel xml file showing the traceability between "Subsystem Design" and "Subsystem Requirement" artifacts. Since traceability is stored using relations, all
the standard change management and version control capabilities are used with traceability.
Thanks,
Ryan
Thanks,
Ryan Brooks
|
|
|
Powered by
FUDForum. Page generated in 0.01403 seconds
] 
Search
Help
Register
Login
Home
