1. Trace Requirement

Question 1

Purpose

Answer 1

To ensure that r&d at different levels are aligned to one another,
and to manage the effects of change to one level on related reqs.

Question 2

Description of traceability

Answer 2

Reqs traceability identified and document the lineage of each reqs, include it backward traceability, its forward traceability, and its relationship to other reqs

Traceability help ensure that the solution conforms to the to reqs and assist in scope, change, risk, time, cost and commu mng. Detect missing function or function not supported by any reqs

Question 3

Description
Traceability enables:

Answer 3

Traceability enables
- faster and simpler impact analysis
- more reliable discovery of inconsistencies and gap reqs
- deeper insights into scope and complexity of change
- reliable assessment which reqs have been address which have not

Question 4

Description
Process & software reqs traceabilty

Answer 4

Process traceability:
Value chain <->
biz process <->
sub process <->
activity <->
task

Software reqs traceability:
Biz needs <->
Biz reqs <->
SH reqs <->
Solution reqs ( design - code - test)

Question 5

Input

Answer 5

Reqs: may be traced to other reqs, solution components, visuals, biz rules, other work products

Designs: may be traced to other reqs, solution component and other work products

Question 6

Elements 1

Answer 6

1. Level of formality
   The effort to trace reqs grows signification when the number of reqs or level formality increases

Question 7

Elements 2

Answer 7

2. Relationships
   - derive: between 2 reqs, used when a reqs is derived from other reqs. Solution derived from biz or SH reqs

• depends: between 2reqs, used when a reqs depends on another reqs
  ++ necessity: it only makes sense to implement a particular reqs if related reqs also implemented
  ++ effort: a reqs easier to implement if a related reqs also implemented
• satisfy: between an implementation and the reqs it is satisfying. Function reqs and solution component that implementing it
• validate: a reqs and a test case or other element that can determine whether solution fulfill reqs

Question 8

Elements 3

Answer 8

3. Traceability repository
   Reqs traceability is document and maintained
   Reqs mng tools can provide significant benefit when trace large number reqs

Question 9

Guidelines and tools

Answer 9

Domain knoledge

Information mng approach

Legal/regulatory information: rule or regulatory must be followed

Reqs mng tools/repository: use store and manage, may be simple text document or conplex as reqs mng tool

Question 10

Techniques

Answer 10

Biz rule analysis: trace biz rule to reqs, or rule support reqs

Functional decomposition: break down solution scope into smaller component for allocation, traced high to low concept

Process modeling: visually the future state process

Scope modeling: visually depict scope, trace reqs to the area of scope the reqs support

Question 11

Stakeholder

Answer 11

Customer: consulted, agree to traceability relationships

Domain sme: recommendation reqs link to solution conponent or release

Implementation sme: brings awareness of dependencies between solution component

End user: may required specific dependency relationship

Operational support: provide another refer source for help desk support

Project manager: support project change and scope mng

Sponsor: approve the various relationships

Suppliers: affected by how-when reqs are implemented

Tester: understand how-when reqs implemented, trace test case to reqs

Question 12

Outputs

Answer 12

Reqs (traced) & Design (traced)

Have clearly defined relationship to other reqs, solution component, release, phases, iterations, within a solution scope such that coverage and the effects of change are clearly identifiable