This section contains lists of the processes needed for each configuration management activity. The lists here are "flat," whereas in a live project, the processes may be multidimensional: variations may exist, depending on the nature of the project and the configuration management. All the contents of the processesprocedures, conventions, and templatesare listed separately here, but they may well be combined. Identification requires
Storage requires
Change control requires
Status reporting requires
Special Requirements for Configuration Management ProcessesThe fact that configuration management is performed during the entire lifetime of a product, for a number of different types of items, and under various circumstances imposes certain requirements on process descriptions. On one hand, they must be integrated with process descriptions for all other processes for which configuration management is performed. These may be coding, test, project management, and quality assurance, to mention a few. Special product requirements may also have to be taken into consideration, as well as special conditions that apply to a project. This could be integrated product development, multivariants , or product-line development of items for reuse. On the other hand, variants of some process descriptions may be necessary, depending on the types of configuration items and/or degree of formalism required. Types of configuration items may be source code or plans, to mention just two. More comprehensive lists of both types can be found elsewhere in this book. |