Software configuration management principles and process overview

Configuration Management

Design Methodology for producing Modularity

Aspects of modular product design:

Attribute integrity

Process integrity

Process stability

Details oriented

Scope, procedures, goals, and objectives

Simple configuration control

Minimum requirement for labor

Precise and absolute descriptions of changes in question

Cooperative and responsive customers'

Effective coordination among project team members

111.2 CONFIGURATION Management TERMS AND DEFINITIONS

Software Configuration Management

Configuration Item

Engineering Change Request

121.3 ROLES & RESPONSIBILITIES

Configuration Control Board

Parallels between the data and functional design of the plan

Advantages of modularity

142. CONSIDERATIONS

RELATIONSHIP TO SYSTEMS ENGINEERING

142.2 RELATIONSHIP TO PROGRAM Management

142.3 RELATIONSHIP TO SOFTWARE ENGINEERING

163. CONFIGURATION Management (CM)

173.1 CM PROCESS

Process Overview

183.2 CM PLANNING AND Management

183.4 CONFIGURATION CHANGE Management

193.5 CONFIGURATION STATUS ACCOUNTING

213.6 CONFIGURATION VERIFICATION AND AUDIT

Conclusion

234. APPENDIX A REFERENCES

255. APPENDIX B. SAMPLE CM PLAN

Acronyms Used

CM -- Configuration Management

SOA - Service Oriented Architecture

CCBs - Configuration Control Boards

CI -- configuration Item

SMEs -- subject Matter Experts

ERBs -- Engineering Review Boards

NASA - National Aeronautics and Space Administration

Configuration management

1. INTRODUCTION

Configuration management is a concept coined from the blending of the two terms, configuration and management. In order to have a precise understanding of the terms, it is essential to define these two words separately. This helps in having a deeper meaning of the terms. Considering the term configuration, it involves the organization of segments of a particular the entire product or constituent. Configuration entails the comprehensive section of the management system employed (Watts 213-245).

On the other hand, considering the term management, it entails the aspect of looking over the manner in which the organizational arrangement of the various sections is carried out. After the integration of these two terms, then, we arrive at the literal meaning of the two terms. Therefore, Configuration management is the management of the various parts of the product until they produce the final product. However, in depth clarity of the concept leads to the recognition of the management further (Watts 213-245). For that reason, configuration management is a field that provides a coherent methodology for the anticipation, identification and the preservation of a particular section of the whole system. This discipline is significant, since it holds the responsibility for the management of the item from its roots to its end.

Configuration management started in 1950. This was the period artists and scientists deeply rooted with the program for initiating the missile accepted that in the orbit, there existed prototype units. They furthered their investigation by focusing on the issue, subsequent to the findings they identified poor recording of information. Configuration Management throughout the Development and Acquisition Phases was unrestricted information by the United States Air Force. This was a manual that engineers and other experts could apply in their respective fields which carrying out their tasks. It was essential as it defines the necessary policies in the operation of the force (Software Program Managers Network 111-187).

The manual was to be free from errors. After the discharge of this documentation, National Aeronautics and Space Administration (NASA) generated a comparable documentation. The record was significant as it provided strategies in the induction and the management of the Apollo .The firsts venture took place in the place in 1964. It was also crucial, as it appeared in diverse orbits depending on the venture taken, and therefore, extreme prudence was necessary. In the subsequent year, the American Army as well came up with a related record for the organization of their operating machines and definition of their policies. Soon after in 1967, the American Navy too generated a distinct configuration management record. Regardless of the fact that, the American Army, the Navy and the Air Force settled to invent diverse configuration management system and was successful, the government was unsatisfied with such documentation.

The American Secretary of Defense by then ordered for the unification of configuration system for all the three units to be adjoined .This explained the reason the three units functioned in unanimity. Subsequently, in 1968, defense department invented a solitary configuration system for the three units and provided military principles implicated with the running. The policies set in the year 1968 ruled the United States Military and applied them in all their undertakings (Software Program Managers Network 111-187).

On the other hand, in the year 1992, the United States department of defense invented another configuration management policy intended at optimizing the deeds of the military. Consequently, in the year 1998, the American National Standards Institute came up with the National Consensus Standard for Configuration Management. Throughout the years, there were numerous dynamic changes in the configuration management and the aspects used in its operation (Smith & Bayne 123-156).

Design Methodology for producing Modularity

This technique is rather diverse from preserving form/function autonomy. Modular design patterns are the core of this discussion. It is the rationale of modular system to classify all values with analogous procedures into an entity module and decouple them from all other significant aspects and processes. Structuring modular products comprise ascertaining that, at each stage of modulation; the product's features are as different from each other as plausible for each stage of concept of the production tasks. If, therefore, the concept of existence exists, it must occur within a module, most probably within a section. This is rather different from designing products with dependable or reconfigured aspects. Each of the production procedures ought to be similar for every attribute. For instance, many diverse sectors can have black features and stay modular.

Aspects of modular product design:

a). Attribute integrity

Buckley & Fletcher (19) confirms that attribute integrity relates to component attributes, which essentially have less reliance on attributes of elements outside the units, called external characteristics.

b). Process integrity

Buckley & Fletcher (19) asserts that each manufacturing procedure of each segment less dependencies on the processes of small components. This facilitates that the production procedure (comprising all tasks) that the unit's encounters are self-determining of the developments faced by external elements and modules.

c). Process stability

Buckley & Fletcher (19) propose that the product designer should assemble units and sub-assemblies that goes through the similar productions processes into the same company where feasible. This decreases the variety of numbers of external elements, which the production designer subjects to comparable procedures and develop a powerful distinction between modules. For instance, strong plastic elements for a motorbike such as rear swing arm, rear forks, wheel and discs can be chopped fibers, woven fabric, permanent lengths of fiber, or slightly bent materials. An example comprises a coffee maker.

Scope, procedures, goals, and objectives

These features are necessary for successful configuration management. Precision in planning and setting of objectives ensures proficient and timely completion of projects. Definition of management gives appropriate perceptive of work in progress. The perception facilitates effectiveness in accomplishing the set objectives.

Simple configuration control

Use of simple configuration control measures and accounting is a significant feature. Accurate accounting ascertains that the resources offered for diverse activities are adequate for implementation of the activities. Any mistake of accounting can obstruct the success of the project (Estublier 146-49).

Minimum requirement for labor

The employment requirements require an evaluation so that the smallest number of workforce undertakes a particular project. Uncalled for employment increases the costs incurred in the firm.

Precise and absolute descriptions of changes in question

Any changes made in the management or configuration processes require reorganization in a cordial manner. It is the responsibility of the managers to conduct appropriate documentation, which describes various adjustments. Communication that concerns changes to the product developers assist in completion of the projects in a competent manner. Other features comprise, guaranteeing an appropriate change analysis and processing. This feature involves careful extent of different changes by assessment to establish which changes suits an operation .The number of forms to implement changes should be less to facilitate easy access of information. If there are many forms and presence of other documents, it becomes very difficult to handle management (Estublier 146-49).

Cooperative and responsive customers'

appropriate system of management ensures efficient communication and response to customers. The system blends well with consumers towards attaining suitable control of products and documentation.

Effective coordination among project team members

Harmony created among the team members is significant. These members have a team leadership expertise, while the manager has a responsibility of coordinating and controlling.

1.1 CONFIGURATION Management OVERVIEW

Configuration Management is the strategic evaluation of all the aspects of a firm with the sole purpose of attaining the objectives of the organization. This discussion shall look at the various capacities of management, which after incorporation incorporated jointly provides or promotes competence in a firm. This involves both the guiding principles in addition to the varied systems prearranged in a particular way to reduce much human intrusion in carrying out different tasks. For example, configuration controller that involves integration of accounting information that will facilitate excellent accounting system (Smith and Bayne 123-156).

In dealing with and evaluating different constituents of management, it acknowledges the different values that originate from good use of configuration management features that involve huge proficiency. Given that, there are different types of systems required in accomplishing and fulfill the set objectives, their operation also differs. For instance, if the system requires usage of technological expertise, like electronic in setting up particular software to aid in accomplishing the task required (McQueen and Judy 145- 69).

The report comprises the systems control limits that are under strict maintenance, particularly in Engineering and process control fields. System control involves either a set restrictions or functioning from the reference of past objectives which the system designer or programmer introduces in the system. Therefore, acting as reminiscence, that reminds the system about its operation period and its limits. In general, this involves management work, whereby it acts as a reference about the past operations and identifying the best system regardless of the presence of the various machines. In essence, Configuration management involves diverse operations emanating from the guiding principles to the efficient working of various systems and, thus, analyzing the values generated from every aspect, for example, the modularity values (McQueen and Judy 145- 69).

1.2 CONFIGURATION Management TERMS AND DEFINITIONS

This section explains the various terms used when dealing with aspects of configuration management in various sections.

Software Configuration Management

This is a section of the whole configuration management and deals with the issues concerned with the software systems of the general system that is under investigation. Another term to classify with is Configuration Planning.

Configuration Item

A term used to explain a specific section of the system that requires review for any essentials changes and amendments. However, the application of changes is crucial after discovering the errors affecting a particular area.

Baseline

This term refers to a point that provides the setters of the configuration management plan. In addition, this point is essential as a reference or standard kept under observation in the process of system configuration. Baseline is very crucial in the process of management and maintenance of the system to ascertain that the system operates based on the plan.

Engineering Change Request

In most cases, this physical recording is present mostly in the offices of the people concerned with configuring. This form is available to all human population if they have information that may help in the recognition of challenges in the configuration.

1.3 ROLES & RESPONSIBILITIES

Configuration Control Board

It refers to set of proficient and expert credited for the evaluation of the amendments conducted to the engineering elements of a system.

Parallels between the data and functional design of the plan

Decrease of peripheral links between physical elements: In a broader sense, Buckley & Fletcher (19) confirms that a modular of produced goods or sub-assembly has "a one-to-one connection from fundamental components in the function arrangement to the considerable units of the product. This specification is only applicable for the valuable aspects of a product, disregarding all other production characteristics.

Advantages of modularity

In establishing the advantages of modularity of project; it is very important to identify that all information pertaining to the costs and the gains of modular products. The advantages of product design they consider comprises:

i. Basic economies of scale through the value of units across the product families

ii. Likelihood of product improvement because of practical units, iii. Enhanced product variety from a smaller set of elements, reduced level lead-time because of substandard elements.

The costs of configurations comprise:

i. Lack performance monitoring because of lack of concern, sharing and larger size

ii. Increased cell changeable costs iii. Lack of unit optimization

2. CONSIDERATIONS

2.1 RELATIONSHIP TO SYSTEMS ENGINEERING

This entails developing systems products or processes based on total systems viewpoint and using a systems engineering strategy. This field defines the demands of the customer and the required functionality early in the growth cycle, recording requirements and then continuing with design thesis and systems validation while taking into consideration the entire problem.

2.2 RELATIONSHIP TO PROGRAM Management

There is a very close link between CM and program management. Configuration Management (CM) details the composition of a program, recording defining the project, and other data that endorses the program. In other words, CM acts as a baseline and a requirement management procedure that offers regulated control to the life cycle of a program.

2.3 RELATIONSHIP TO SOFTWARE ENGINEERING

Current systems, regardless of their intricacy become difficult with time, because inventions ascertain their changing development. Software configuration management makes systems' intricacy efficient and controlled, thus, giving way to consistency with its different elements. Presently, configuration management gives a more comparison between the software and hardware CM. However, software CM has almost similar objectives with hardware, especially in fulfilling the intended objectives (Estublier 146-49).

The individual designer of the hardware system sometimes bears a minor difference or almost alike, but the huge variance occurs in the goals they have to fulfill. Software CM comprises four groups, which include; the process control, the environmental management, building management and the version control. Configuration Management falls under Software Engineering field and it plays a significant role to the success of the project as systems turns intricate and varied (Magnusson 390-96).

The increased application of Service Oriented Architecture (SOA) and disseminated systems makes it intricate for firms to preserve configuration constancy and reliability. Configuration Management plays a larger role in the accomplishment of large, multifaceted projects. ATG perceives CM in four principled ways;

1) Configuration identification,

2) Configuration control,

3) Configuration verification

4) Configuration status

ATG offers services essential for each project to preserving a strong CM: eradicating program threats and speeding up the time used in market for the software systems. In configuration identification, ATG expert's acts as both requirement analysts and business analysts to work with program stakeholders. The software engineers are continuously developing their toolset as technology progresses. In the field of configuration control, ATG has broad skill in developing, operating and running Configuration Control Boards (CCBs) intended for the purpose of assessing, approving and observing all adjustments to Configuration Items (CIs) described by the CM process (Magnusson 390-96).

In addition, ATG offers direct implementation oversight and Subject Matter Experts (SMEs) for CCBs and Engineering Review Boards (ERBs) to offer the program with absolute CM implementation and conformity. ATG also surpasses at configuration authentication throughout wide Quality Assurance (QA) and testing proficiency. The engineers have the best industry training expertise according to the standards and quality practices of QA and testing methods to use at all stages of the S.D.L.C. These engineers also offer efficient confirmation and validation of software releases and performance testing to create baseline metrics and Key Performance constraints. In the field of configuration status, the ATG engineers offer numerous services that facilitate the success of the program. Configuration auditing devices are necessary in maintaining and recoding baseline hardware/software configurations for the CM control (Magnusson 390-96).

3. CONFIGURATION Management (CM)

Configuration management is a concept coined from the blending of the two terms, configuration and management. In order to have a precise understanding of the terms, it is essential to define these two words separately. This helps in having a deeper meaning of the terms. Considering the term configuration, it involves the organization of segments of a particular the entire product or constituent. Configuration entails the comprehensive section of the management system employed (Watts 213-245).

Configuration management is, therefore, the management of the various parts of the product until they produce the final product. However, in depth clarity of the concept leads to the recognition of the management further (Watts 213-245). For that reason, configuration management is a field that provides a coherent methodology for the anticipation, identification and the preservation of a particular section of the whole system. This discipline is significant, since it holds the responsibility for the management of the item from its roots to its end.

Configuration management started in 1950. This was the period artists and scientists deeply rooted with the program for initiating the missile accepted that in the orbit, there existed prototype units. They furthered their investigation by focusing on the issue, subsequent to the findings they identified poor recording of information. Configuration Management throughout the Development and Acquisition Phases was unrestricted information by the United States Air Force. This was a manual that engineers and other experts could apply in their respective fields which carrying out their tasks. It was essential as it defines the necessary policies in the operation of the force (Software Program Managers Network 111-187).

3.1 CM PROCESS

This section presents the configuration management process. This process provides a verbal and pictorial description on activities and flow of CM. The activity descriptions provide sufficient information to enable personnel to make CM decisions, but are absent at the procedure level of detail.

Process Overview

The CM process consists of four phases:

a) Classification -- An event or change is discovered and routed to the suitable organization for decision

b) Evaluation -- involves identification of Initial solution, thereafter, either the SN Change Control Board (CCB) or Working Group (WG) offers the CM control. The control is reliant on the nature of the suggested solution (component-only or SN architecture).

c) Modeling and Testing -- If the suggested solution involves an architectural change; the change is amended and tested to establish its impact on the existing SN architecture.

d) Implementation -- The final solution is accepted and implemented to the SN.

3.2 CM PLANNING AND Management

CM planning and management is engineering technique that includes a product's individual standards such as strength at the untimely stages of product design. These standards may have product sequestration, functionality, overhaul, business concerns, mechanized assembly, and any other essentials put on the produced goods from start to end is plummeting the quantity of components.

3.3 CONFIGURATION IDENTIFICATION

Configuration identification (CI) includes identifying the constituents of the network, exceptionally discovering the individual components, and availing them in a particular form. A suitable configuration identification scheme identifies each constituent of the network and offers traceability between the constituent and its configuration status information. Suitable configuration identification answers the following questions:

What is the configuration of the network?

What are the components of the network?

What are the versions of the network components?

The major activities of configuration identification comprise:

Selecting network components to be placed under CM control

Creating an identification scheme for the components to uniquely identify each individual component

3.4 CONFIGURATION CHANGE Management

Configuration refers to the functional features of a particular product comprised in the technical records and accomplished in the product. The terms also refer to the sequentiality developed by differences of a product. Configuration management plan consists of four phases. These phases assist in applying technical direction in the manufacturing period of a specific product. They include:

i. Concept formulation phase

ii. Definition phase iii. Acquisition phase

iv. Operational phase

The first three phases of the configuration management comprises of three termination baselines. The role of the termination baselines is to demonstrate the checkpoint in the process of design and growth of the product in the process of production. There are several disciplines integrated in the product's life cycle in the configuration management. The disciplines encompassed in product's lifecycle comprise the following:

a) Specification

b) Schedule

c) Contract

3.5 CONFIGURATION STATUS ACCOUNTING

It is a procedure used by concerned people in the related field. The accounting part explains about the identification of the state of the affairs and the full recording of any information linked with the configuration. The means that the system keeps track of the state on its entire configuration items, the entire all-awaiting proposed changes, and all accepted changes to configuration items as illustrated by figure 5 below.

Configuration status accounting comprises the recording and reporting of the change process. The objective of configuration status accounting is to preserve a status record of all items in the network baseline, thus enhancing traceability of all changes to the network. Suitable configuration status accounting answers the following questions:

a) What are the changes made to the system and when were the changes were made?

b) What components were affected by this change?

The major activities of configuration status accounting are:

a) Identifying the configuration status information to be recorded

b) Maintaining a record of configuration changes

c) Reporting the status of network configuration management

3.6 CONFIGURATION VERIFICATION AND AUDIT

The CCB reviews Configuration status information occasionally in order to authenticate its accuracy and cohesiveness. The CCB will discover the configuration reviews that require evaluation. The following consists of a preliminary list of configuration evaluations:

Physical Network Review

The Physical Network Review will evaluate and discover any inconsistencies between the configuration status information and the physical SN network. This is a comprehensive review, which compares the data in the repository and CFs with the actual physical configuration of the deployed network components. This review is roughly comparable to the Physical Configuration Audit in traditional CM.

Conclusion

Configuration management since its conception proves effective and firms used this concept in determining the success of the organizations. Configuration management ensures that, the various sections in the organization maintain the necessary aspects required for the success of the organization. However, there are limitations that stems from the loopholes not yet covered by this concept. Some of the limitations include, requiring and waiting for other members decisions coupled with poor management of record that may compromise confidentiality.

The information passed should be confidential and secured because if it falls on the wrong hands, this might bring down every effort put forth for the success of the organization. Any malevolent acts may cause immense suffering to the organization; therefore, configuration management requires appropriate instillation using the right principles. The quandaries that emanates from configuration management are effectively solved through changing the process used in sharing files and documents, therefore, preserving firm's confidentiality.

4. APPENDIX A REFERENCES

Buckley, Fletcher J., Implementing Configuration Management: Hardware, Software, Firmware,

Second Edition, IEEE Press, Piscataway, NJ: 1993

Daniels, M.A., Principles of Configuration Management, Advanced Application Consultants,

Inc., Rockville, MD: 1985

Estublier, Jacky, (Ed.) System Configuration Management, 9th International Symposium, SCM-9,

Conference Proceedings, Springer-Verlag, Berlin: 1999

Hajek, Victor G., Configuration management: Describing how engineering and management disciplines can be applied to achieve the effective use of resources and the complete and accurate description of the end products, Industrial and Commercial Techniques, Ltd.,

London: 1968

IEEE Standard, IEEE Std 828-1998, IEEE Standard for Software Configuration Management

Plans, Institute of Electrical and Electronics Engineers, Inc., New York: 1998

Kelly, Marion V., Configuration Management: The Changing Image, McGraw-Hill Book

Company, Berkshire, England: 1996

Lyon, David D., Practical CM: Best Configuration Management Practices for the Twenty-First

Century, Butterworth-Heineman, Oxford: 2000

Magnusson, Boris (Ed.) System Configuration Management, ECOOP '98, SCM-8 Symposium

Conference Proceedings, Springer-Verlag, Berlin: 1998

McQueen, Bob and Judy McQueen, Intelligent Transportation Systems Architectures, Artech

House, Inc., Boston: 1999

Smith, Brian L. And Bayne E. Smith, "An Evaluation of the Need for Configuration Management

in Transportation Management Systems," The Transportation Research Board, November

2000

Software Program Managers Network, The Condensed Guide to Software Acquisition Best

Practices, February, 1997

Software Program Managers Network, Little Yellow Book of Software Management Questions,

Watts, Frank B., Engineering Documentation Control Handbook: Configuration Management,

Second Edition, No/yes Publications, Park Ridge, NJ: 2000

The derivation of the following model is from the CCB Charter outline presented in Cultivating Successful Software Development: A Practitioner's View.

5. APPENDIX B. SAMPLE CM PLAN

Configuration Control Board (CCB)

Charter Template

1.0 CCB Purpose

The purpose of the Change Control Board is to ensure that the related programmatic changes in a process that is visible and traceable. The CCB is the forum in which the programmers come together and discuss the requirements of program. (2) CCB then selects responsible personnel for performing the work agreed-upon (3) the CCB then records the decision agreed upon and necessary course of actions.

2.0 CCB Membership

The CCB will involve of the following representatives from the IT Services Directorate:

a) Architecture Group - [TBD -- identify representative(s) by name and/or title]

b) Operation Group - [TBD -- identify representative(s) by name and/or title]

c) Deployment Group - [TBD -- identify representative(s) by name and/or title]

Representatives from other organizations may join on an as-needed basis.

[TBD -- identify by name and/or title] will be in charge of recording the CCB meetings.

The CCB Chair is [TBD -- identify by name and/or title]. The CCB Chair will conduct the meeting in such a way that, it will invite any input and discussion from all participants. The CCB resolves product and programmatic disputes and solutions recorded in the meeting documentation.

4.0 CCB Activities

The CCB will assemble every [TBD -- specify occurrence of CCB meetings; also specify any requirements for meeting notification, quorum of attendees, etc.]

The CCB will conduct the following activities: [TBD -- the following activities have examples of the CCB activities to be included. This list is remains incomplete until proven by the IT organizations participating in the CCB.

Reviewing and managing proposed changes to the CM.

a) Reviewing and managing cross-organizational CM issues

b) Reviewing and managing configuration management process

c) Recording CCB minutes

d) Reviewing, approving, and, if necessary, recording changes to CCB minutes from the previous CCB meeting.

5.0 CCB Meeting Documentation

The following is the information recorded for each CCB meeting: the following activities have examples of the CCB activities to be included. This list is remains incomplete until proven by the IT organizations participating in the CCB.

a) Meeting date, time, and duration

b) List of attendees and their organizations

c) Items discussed

d) Existing action items

e) New action items

f) Decisions made