Configuration status accounting (CSA) defines the
procedures for obtaining and reporting information on the nontechnical status
of proposed changes, pending changes, and baselines. Such information is derived
Types of Configuration Management Changes
from the configuration identification and control processes. CM identifies systems configuration and
components (hardware, software, documentation, and data) and develops and
implements the change control process as specified in the configuration
The allocation of responsibilities within these functions (tailoring) must be accomplished during the CM planning activity and should take into account the degree to which the information technology infrastructure has been upgraded. Another advantage is that the user documentation development process serves double duty as a functional test. As the analyst or tech writer is developing the tutorial, he or she might just uncover some bugs.
As one can see, configuration documentation is consistent with the documentation produced throughout the life cycle of a typical systems development effort. Configuration change control is the systematic evaluation,
coordination, approval or disapproval, and implementation status accounting of all approved
changes in the configuration of a configuration item after formal establishment
of its identification. Configuration control covers the evaluation of all
Financial Accounting Standards Board (FASB)
change requests and change proposals and their subsequent approval and
It is a description that contains the CSCI type (Computer Software Configuration Item), a project identifier and version information. While use cases form the basis of the initial set of test cases, they are but a small subset of test cases. An entire chapter has been dedicated to software testing, so we will not prolong the discussion here. Suffice it to say that any and all test cases used in conjunction with the system ” along with the results of those test cases ” should be included in the system documentation. A knowledge base of key content resources on project management and professional services automation.
In 1979, the Technical Committee ISO/TC 176 “Quality management and quality assurance” started standardization work in the field of quality management and developed the standard ISO 9000. When deciding how often and how much to report, the complexity, size, rate, scope, risk, and impact of the system should all be taken into account. Additionally, the expectations and needs of different stakeholders should be taken into account. This is because a more complex and large system may require more frequent and detailed reporting, while a faster and wider change may require more frequent and detailed reporting due to more changes needing to be recorded.
It provides status and cross-references actual Technical Data Package (TDP) information that is stored digitally in data repositories. The user then works on the needed file and checks in the changes back to the repository.They can synchronize their local copy to stay updated with the changes made by other team members. With the help of archiving or save feature, it is possible to roll back to the previous version in case of issues. When two or more tasks are happening at the same time, it is known as concurrent operation.
My Accounting Course is a world-class educational resource developed by experts to simplify accounting, finance, & investment analysis topics, so students and professionals can learn and propel their careers. New international agreements and multilateral controls to prevent abuses were enforced as a way to prevent a similar calamity. In this regard, it is common to see groups that want to keep to status quo while others fight against it. Wars, social movements and radical economic policies generally change the status quo. Figure 6.5-1 provides a typical flow diagram for the Configuration Management Process and identifies typical inputs, outputs, and activities to consider in addressing CM. The information that is loaded into CSA is considered “metadata,” that is, information about the data.
- In many cases, without CM, the documentation exists but is not consistent with the item itself.
- Likewise, the purpose of the report may vary depending on the stage of the project, the type of change, and the impact of the configuration status.
- Code can be mysterious to maintenance programmers who must maintain the system for years after the original system was written and the original programmers have moved on to other jobs [Graham et al. 2000].
- In 1979, the Technical Committee ISO/TC 176 “Quality management and quality assurance” started standardization work in the field of quality management and developed the standard ISO 9000.
The first step establishes a robust and well-disciplined internal NASA Configuration Control Board (CCB) system, which is chaired by someone with program/project change authority. CCB members represent the stakeholders with authority to commit the team they represent. The second step creates configuration change management surveillance of the contractor’s activity. The CM office advises the NASA program or project manager to achieve a balanced configuration change management implementation that suits the unique program/project situation.
See Figure 6.5-4 for an example of a typical configuration change management control process. The configuration management (CM) process
provides the framework for the identification, control, status accounting,
roles and responsibilities, and standards and procedures for developing and
implementing the change control process. NASA has four baselines, each of which defines a distinct phase in the evolution of a product design. The baseline identifies an agreed-to description of attributes of a CI at a point in time and provides a known configuration to which changes are addressed. Baselines are established by agreeing to (and documenting) the stated definition of a CI’s attributes.
Key practices, as defined by Cook and Visconti , are listed in Table 7.3. David Tufflye, a consultant who specializes in producing high-quality documentation to a predefined standard, says that consistent, accurate project documentation is known to be a major factor contributing to information systems quality. SC2 developed ISO 9001 on requirements for quality management systems, ISO 9004 as guidance to achieve sustained success, ISO as guidance on quality plans, ISO as guidance on quality management in projects and ISO as guidance on configuration management. Before you decide on a reporting format, you need to know who will use the report and what they need to know.