HistoryViewLinks to this page Revision from: 2012 August 28 | 11:12 am
This is the revision from 2012 August 28 at 11:12 amView the current live version of the article.

This document provides high-level scenario descriptions that have been identified as priority scenarios that need to defined in the specification and validated by product implementations.

Collaborative Application Lifecycle Management (C/ALM) Scenarios

The following two scenarios are defining the scope of a V1.0 of the specification.

The following scenarios were considered for inclusion in the V1.0 scope but were not included.

Review comments for these scenarios are to be found here RM C/ALM review comments

The following scenarios are being investigated:

Systems Engineering Scenarios

Here is a starting point for the general RM use cases for Systems Engineering:

  • Prepare a response to a Customer Requirement/RFP
  • Evaluate proposal response(s) from suppliers
  • Author Requirements
–Discover
–Analyse
–Refine
–Decompose/Derive
–Categorise
–Prioritise
  • Review Requirements
–Completeness
–Consistency
–Correctness
Linguistic
Technical
  • Manage Requirement Changes
–Identify
–Evaluate
–Take Action
  • Measure Requirements
  • Publish Requirements
  • Assess RM Processes
–Volatility
–Maturity
  • Verify Requirements
  • Validate Requirements
  • PLM Integration

Reporting Scenarios

See ReportingSpecifications.

Traceability Scenarios

Traceability scenarios can be found here.

Scenario Brainstorming and Gathering

References