History   View   Links to this page Revision from: 2013 February 19 | 05:29 pm
This is the revision from 2013 February 19 at 05:29 pm   View the current live version of the article.

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

Contents

Inprogress/Done Scenarios

Backlog Scenarios

Ranked by SteveSpeicher as of March 15, 2011:

Ranked List:

  1. ITOpsToDev
    • Possible spec needs: properties, resource types, terminology alignment, may have state transition part
  2. Mylyn Scenario
    • Possible spec needs: attachments, severity/priority, state transitions
  3. Query For Change Requests matching multiple states
    • Possible spec needs: additional statepredicate property for change requests
  4. Report problems for application analysis tools
    • Possible spec needs: attachments, severity/priority
  5. Tracking progress of change requests
    • Possible spec needs: resource type, properties

Proposed CM 3.0 content above this, and future backlog below

  1. Change Management of Requirements (state transition part)
    • Possible spec needs: state transition
  2. Change Request mass create
    • Possible spec needs: guidance on using existing methods, few enhancements
  3. Code Review
    • Possible spec needs: approvals/reviews
  4. Resource editor, embedding minimal web ui
    • Possible spec needs: embedding Web UI fragment

Proposed 3.0 Roadmap

Scenario Introduce Topic Complete Scenario Create Draft Specs Start Convergence Finalize Specs
See above Nov 2010 2Q 2011 2Q 2011 2H 2011 V3.0 1Q 2012

See OSLC CM Specification Technical Backlog

Cross-cutting scenarios (from other domains)

  • PLM: baselines
  • ChangeLog
  • state transition

Completed scenarios where some additional spec work could still occur

Feedback

Specification comments and issues

References

Category:Supporting Documents

Categories