This wiki is locked. Future workgroup activity and specification development must take place at our new wiki. For more information, see this blog post about the new governance model and this post about changes to the website.
TWiki> Main Web>RmHome>RmScenarios (revision 15)

Requirements Management Scenarios

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:

  • Scenario C: [[FixProblemRequirement][Find and fix an unsatisfied requirement]
  • RmRequirementElaboration
  • RmRequirementChangeNotification
  • Requirements organisation
    • static classification of related requirement (eg into a specification document, or a baseline)
    • dynamic classification (lifecycle state?)
    • supporting discovery (e.g., tagging, searching)
  • Scenario S1: Define Requirements Baseline (See RmScenariosSiemens.) How to acheive the precondition of RmRequirementCompletedScenario scenario - a known collection of requirements to be considered for a release and/or milestone.
  • "Suspect links" scenarios
    • What does "suspect" mean?
    • Definition, Identification, Resolution (Is it a notification, or a state? Is it user-bound or data-bound?)

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

Edit | Attach | Print version | History: r17 < r16 < r15 < r14 < r13 | Backlinks | Raw View | Raw edit | More topic actions...
Topic revision: r15 - 22 Aug 2011 - 09:18:38 - IanGreen
 
This site is powered by the TWiki collaboration platform Copyright � by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Contributions are governed by our Terms of Use
Ideas, requests, problems regarding this site? Send feedback