B03

• Input: Stakeholder needs, requirements, origins, dependencies, design elements, tests, and changes.
• Operation: Specify required information items and maintain forward/backward links through origin, refinement, implementation, verification, and revision.
• Output: Requirements baseline and trace graph supporting coverage and impact analysis.
• Scope conditions: Systems/software products and services across their lifecycle.
• Failure conditions: Link rationale is absent; granularity is wrong; links become stale.
• Predicted effect: Higher change-impact recall and requirement-verification coverage.
• Measurement: Trace precision/recall, orphan rate, and affected-item recall.
• Implementation test: Seed a requirement change; independent analyst identifies affected artifacts and tests.
• Decision rights: Requirements authority owns baseline; change control approves revisions.
• Uncertainty handling: TBDs, rationale, and unresolved conflicts.
• Verification: Bidirectional trace and coverage audit.
• Provenance: Origin and lifecycle history are core.
• Implementation cost: Link creation and maintenance.
• Limitations: Traceability alone does not guarantee quality. Direct: standard and original empirical analysis. Inference: metrics.