Revision: Change Management Scenarios

Sort of a ghost town here
Active specification development is now at Change and Configuration Management TC

Want to contribute?

History View Links to this page Revision from: 2013 October 31 | 01:52 pm

This is the revision from 2013 October 31 at 01:52 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
- Cross-cutting scenarios (from other domains)
- Completed scenarios where some additional spec work could still occur
Feedback
References

Inprogress/Done Scenarios

OSLC-CM 3.0 :
- Change Management of Requirements (state transition part)
- Mylyn Scenario (attachments, severity/priority, state transitions)
- Query For Change Requests matching multiple states (additional state predicate property for change requests)
- Report problems for application analysis tools (attachments, severity/priority)
- Tracking progress of change requests (resource types, properties)
OSLC-CM 2.0 :
- Streamlined developer task management in an IDE
- CmScenariosReporting
- Change Management of Requirements
- Change Request linked to a source control change set resource
  - See related work done in SCM domain ScmWorkItemIntegrationStory
OSLC-CM 1.0:

Backlog Scenarios

ITOpsToDev
- Possible spec needs: properties, resource types, terminology alignment, may have state transition part
Change Request mass create
- Possible spec needs: guidance on using existing methods, few enhancements
Code Review
- Possible spec needs: approvals/reviews
Resource editor, embedding minimal web ui
- Possible spec needs: embedding Web UI fragment