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
>
CmHome
>
CmSpecificationV1
>
CmResourceDefinitionsV1
>
CmResourceDefinitionsFuture
(28 May 2009,
ScottBosworth
)
(raw view)
<h1 id="titleL2-community">Change Management Resources Definition (Future Topics)</h1> _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 [[CMResourceDefinitions][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 <pre><pre><?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> </pre><p> </p></pre> <table width="100%" cellspacing="0" cellpadding="0" border="1"> <tbody> <tr> <td colspan="2" valign="top"> *XML Representation Summary:* request *Element* </td> </tr> <tr> <td colspan="2" valign="top"><request<br /> href = xsd:anyURI > <br /> _Content_: (dc:title, dc:identifier, dc:type?, dc:description?, dc:subject?, dc:creator?, alm:owner?, alm:state?, alm:discussion?, alm:project?, alm:category?, parent?, severity?, priority?, alm:creationDate?, dc:date?)<br /> </request> </td> </tr> <tr> <td valign="top"> *Property* </td> <td valign="top"> *Representation* </td> </tr> <tr> <td valign="top">{dc:title}</td> <td valign="top">The *required* title string. Note that this element comes from the DC namespace, allowing tools unaware of the change management domain to access this element. This is sometimes also referred to as the headline or summary of the request.</td> </tr> <tr> <td valign="top">{dc:identifier}</td> <td valign="top">The *required*, *read-only* identifier string. This is assigned by a change management system when a request resource has been created.</td> </tr> <tr> <td valign="top">{dc:type}</td> <td valign="top">The *optional* type string. The type of request that is represented, such as: defect, enhancement, etc.</td> </tr> <tr> <td valign="top">{dc:description}</td> <td valign="top">The *required* description string. This element comes from the DC namespace, allowing tools completely unaware of the change management domain to access this element. </td> </tr> <tr> <td valign="top">{dc:subject}</td> <td valign="top">The *optional* subject string. The DC namespace defines this element to be a collection of keywords. The subject element will contain keywords and tags assigned to this request.</td> </tr> <tr> <td valign="top">{dc:creator}</td> <td valign="top">The *optional* creator element, identifying the originating user of this request.</td> </tr> <tr> <td valign="top">{jzalm:owner}</td> <td valign="top">The *optional* owner element, identifying the owner of this request. The owner is the person (or entity) responsible for completing the request.</td> </tr> <tr> <td valign="top">{jzalm:state}</td> <td valign="top">The *optional* state -- this may take on any permissible value according to the associated process.</td> </tr> <tr> <td valign="top">{jzalm:discussion}</td> <td valign="top">The *optional* discussion element which contains individual discussion nodes associated with this request. Some change management systems refer to these as notes.</td> </tr> <tr> <td valign="top">{jzalm:project}</td> <td valign="top">The *optional* string describing the associated project to this request. Project is a container for requests.</td> </tr> <tr> <td valign="top">{jzalm:category}</td> <td valign="top">The *optional* string describing the associated category. The category is a container for requests and can span projects.</td> </tr> <tr> <td valign="top">{parent}</td> <td valign="top">The *optional* element has a @href attribute to define the location of the parent request resource.</td> </tr> <tr> <td valign="top">{severity}</td> <td valign="top">The *optional* string describing the severity or impact of the request. Some typical values are: blocker, high, medium, low, etc.</td> </tr> <tr> <td valign="top">{priority}</td> <td valign="top">The *optional* string describing the priority or relative urgency of the request. Some typical values are: high, medium, low, etc.</td> </tr> <tr> <td valign="top">{jzalm:creationDate}</td> <td valign="top">The *optional* dateTime defining when the request was created or submitted.</td> </tr> <tr> <td valign="top">{dc:date}</td> <td valign="top">The *optional* string defining a timestamp of the current state of the request or simply when it was last modified.</td> </tr> </tbody> </table>
E
dit
|
A
ttach
|
P
rint version
|
H
istory
: r2
<
r1
|
B
acklinks
|
V
iew topic
|
Ra
w
edit
|
M
ore topic actions
Topic revision: r2 - 28 May 2009 - 14:12:47 -
ScottBosworth
Main
Main Web
Create New Topic
Index
Search
Changes
Notifications
RSS Feed
Statistics
Preferences
Webs
Main
Sandbox
TWiki
Български
Cesky
Dansk
Deutsch
English
Español
Français
Italiano
日本語
Nederlands
Polski
Português
Русский
Svenska
简体中文
簡體中文
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