Change Management Resources Definition (Future Topics)

SPECIFICATION NOTES : This is NOT a specification. This document is used to collect current out-of-scope items for consideration for future specification work. See the current resource defintion specification work? .

Introduction

Change Management resources define the change requests, activities and tasks of the software delivery lifecycle. They represent individual change requests, activities and tasks, along with their relationships to other shared resource types such as project, category, release and plan.

Referenced Namespaces:

• http://open-services.net/cm/0.1/ - The Open Services for Lifecycle Collaboration Change Management Namespace (default -- unless otherwise specified, the elements and attributes defined in this specification are from this namespace).
• http://open-services.net/alm/0.1/ - The Open Services for Lifecycle Collaboration Namespace
• http://purl.org/dc/elements/1.1/ - The "simple" Dublin Core Metadata Element Set Version 1.1

Summary of Core Resources:

• request - A request for change to an application or product. Typically a product request for enhancement or a report for a resolution of a product defect.
• task - A unit of work assign to an individual. A change request is typically decomposed into tasks to satisfy the requested change.

Secondary Resources

Note: these resources will not be modeled as separate resources but be types of core resources.

• workitem - A piece of work that is a decomposition into smaller units for the purpose of progress tracking.
• activity - A unit of work to complete a request.

Ancillary/Related Resources:

• project - A container for the request.
• category - A sub-container for the request.
• release - For products or applications, a release identifier.
• plan - The associated project/iteration plan assigned to.

Resource Descriptions

XML Representation of the Request Resource

A request is a description of a change requested to an application or product. Requests have associated workflows that include state models, approvals and reviews. In order to accomplish the change requested, it is often broken down into activities and tasks that get assigned to individuals to complete.

Example

<?xml version="1.0" encoding="utf-8"?> <request     xmlns="http://open-services.net/cm/0.1/"    xmlns:alm="http://open-services.net/alm/0.1/"    xmlns:dc="http://purl.org/dc/elements/1.1/"    xmlns:xml="http://www.w3.org/XML/1998/namespace"    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"    xsi:schemaLocation="http://open-services.net/cm/0.1/ open_services_cm.xsd"    xml:base="http://localhost:9080/jazz/" href="workitems/2314">     <dc:title> Provide import </dc:title>     <dc:identifier> 2314 </dc:identifier>     <dc:type> Enhancement </dc:type>     <dc:description>       Implement the system's import capabilities.     </dc:description>     <dc:subject> import, blocker </dc:subject>     <dc:creator> mailto:aadams@someemail.com </dc:creator>     <alm:owner>       <alm:name> Laura Lyons </alm:name>       <alm:userid> llyons </alm:userid>     </alm:owner>     <alm:state> Completed </alm:state>     <alm:discussion  href="workitems/2314/notes" />     <alm:project> Tools </alm:project>     <alm:category> tools/import </alm:category>     <parent href="workitems/2199" />     <severity> Blocker </severity>     <priority> High </priority>     <alm:creationDate>2001-12-31T12:00:00</alm:creationDate>    <dc:date>2008-10-06T12:00:00</dc:date> </request>