Configuration and Change Management only contains Request Change and contains
no Coniguration Management content. "Integrate and create build" is currently
in the development package and missing deployment content has been discussed in
bug 140074.
The way I see it we have two options:
1) Change the name to Change Mangement to reflect reality (otherwise we will
have dashed expectations);
2) Enhance the Configuration Management content.
I actually favor the latter since a complete process for softare development
that is mute on configuration management seems like a contradiction to me.
To implement option 2) I would propose:
a) Include Task:Integrate and Create build within the Configuration and Change
management package/discipline. This is still performed by the Role:Developer
on a small team. There is relatively good content for this task already.
b) Keep the Concept:Workspace and Guideline:Continuous Integration that are
currently associate with this task. There is relatively complete content for
these now.
c) Remove the Guideline:Promote Builds as this can be addressed in the
Continuous Integration Guideline.
d) Take the opportunity to review the proposed Deployment content and perhaps
incorporate some of the essentials into the Configuration and Change Management
discipline.
Cheers,
Chris
-------------------------------------------------------------------------------- Telelogic Lifecycle Solutions: Helping You Define, Design & Deliver Advanced Systems & Software Learn More at www.telelogic.com
Chris Sibbald
Vice President, Standards and Technology Telelogic North America Inc.
255 Albert Street, Suite 600 Ottawa Ontario
K1P 6A9 Canada
The information contained in this e-mail, including any attachment or enclosure, is intended only for the person or entity to which it is addressed and may contain confidential material. Any unauthorized use, review, retransmissions, dissemination, copying or other use of this information by persons or entities other than the intended recipient is prohibited.
