MeetingTracebility20140206

Agenda

Results

Definitions

Traceability

• A connection between exactly
  • two elements
  • or groups of elements
• May be directed
• Has a Type
• can carry metadata

Granularity and Versioning

Goals

• Change Mangement

• Cenelec Norms 50128, 50129, 50126 --> Safety Argument
  --> Assessment

• Verification

• Refinement

• Decision Management

• Documentation

• Don't reinvent wheel

Requirements

• Supports different types of traces
• Traceability is "robust"
• Traces can be grouped
• Detect changes in source or data of a trace
• It shall be possible to pin source/target to a specific version?
  Is this a duplicate to "robustness"
• We need baselining

Use Cases

• Coverage of Requirements by Model / Test Cases

• Based on text-strings

• Subset --> Refined Requirement + Decision

• Derive (N:M) [Source,Target] N <= M

• Refine(1:1) [Source,Target]

• Gathering(N:M) [Source,Target] N > M

• New Requirements(N:M) [Source,Target]

• Req -> SysML

• Requirement Model -> Design Model <- Test Model Internal and External References use satisfy link in model ( source, target, status?) also has to consider traces inside model

Tools

Artifacts

• Requirements
• Refined Requirements
• Specifications
• Implementation
• Tests
• Test Cases / Test Sequences

Some Data Models

Unrelated insight that we may have