FAQ says OSEE Define can be used to track a application's requirements, code and test? Does this mean DEFINE provides inbuild support for traceability to code and test or the user needs to create artifact types for code and test and use relations tree editor to create traceabilty?
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
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
These type definitions use 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.