Downloads & Free Reading Options - Results

Recently SCRAM (Software Configuration And Management) has been adopted by the applications area of the LHC computing grid project as baseline configuration management and build support infrastructure tool. SCRAM is a software engineering tool, that supports the configuration management and management processes for software development. It resolves the issues of configuration definition, assembly break-down, build, project organization, run-time environment, installation, distribution, deployment, and source code distribution. It was designed with a focus on supporting a distributed, multi-project development work-model. We will describe the underlying technology, and the solutions SCRAM offers to the above software engineering processes, while taking a users view of the system under configuration management.

Recently SCRAM (Software Configuration And Management) has been adopted by the applications area of the LHC computing grid project as baseline configuration management and build support infrastructure tool. SCRAM is a software engineering tool, that supports the configuration management and management processes for software development. It resolves the issues of configuration definition, assembly break-down, build, project organization, run-time environment, installation, distribution, deployment, and source code distribution. It was designed with a focus on supporting a distributed, multi-project development work-model. We will describe the underlying technology, and the solutions SCRAM offers to the above software engineering processes, while taking a users view of the system under configuration management.

Recently SCRAM (Software Configuration And Management) has been adopted by the applications area of the LHC computing grid project as baseline configuration management and build support infrastructure tool. SCRAM is a software engineering tool, that supports the configuration management and management processes for software development. It resolves the issues of configuration definition, assembly break-down, build, project organization, run-time environment, installation, distribution, deployment, and source code distribution. It was designed with a focus on supporting a distributed, multi-project development work-model. We will describe the underlying technology, and the solutions SCRAM offers to the above software engineering processes, while taking a users view of the system under configuration management.

Recently SCRAM (Software Configuration And Management) has been adopted by the applications area of the LHC computing grid project as baseline configuration management and build support infrastructure tool. SCRAM is a software engineering tool, that supports the configuration management and management processes for software development. It resolves the issues of configuration definition, assembly break-down, build, project organization, run-time environment, installation, distribution, deployment, and source code distribution. It was designed with a focus on supporting a distributed, multi-project development work-model. We will describe the underlying technology, and the solutions SCRAM offers to the above software engineering processes, while taking a users view of the system under configuration management.

A comprehensive software control and system configuration management process for flight-crucial digital control systems of advanced aircraft has been developed and refined to insure efficient flight system development and safe flight operations. Because of the highly complex interactions among the hardware, software, and system elements of state-of-the-art digital flight control system designs, a systems-wide approach to configuration control and management has been used. Specific procedures are implemented to govern discrepancy reporting and reconciliation, software and hardware change control, systems verification and validation testing, and formal documentation requirements. An active and knowledgeable configuration control board reviews and approves all flight system configuration modifications and revalidation tests. This flexible process has proved effective during the development and flight testing of several research aircraft and remotely piloted research vehicles with digital flight control systems that ranged from relatively simple to highly complex, integrated mechanizations.

The discipline of software architecture has traditionally been concerned with high-level design. In particular, a variety of architecture description languages have been developed that are used to precisely capture a design. Additionally, analysis tools have been constructed that are used to verify particular properties of a design. However, today's trend towards the development of component-based software seems to suggest a new use of software architecture. Because an architecture captures components and the connections among them, it could potentially be used as an organizing abstraction for many of the activities in the software life cycle. In this paper we present an initial investigation into the feasibility of such use. In particular, we closely examine the role system modeling plays in the fields of configuration management and software deployment, and relate this role to the system modeling capabilities of architecture description languages. The outcome of this investigation is twofold. First, we conclude that, for the specific cases of configuration management and software deployment, the use of software architecture brings opportunities to significantly extend the provided functionality. Second, we present requirements for a number of extensions to typical architecture description languages that are needed to make our approach viable.

Configuration management is defined to be management of change. It has two complementary aspects, provision of information about a changing product and controlling changes to the product. Change needs to be controlled and recorded without excessive interference in the development process. A software product changes whenever any component (compiled unit and the source text from which the compiled unit derived) is changed, or the way in which the components are assembled is changed or any associated item (e.g. requirements, designs, user documents or build files) is changed. A component may be part of more than one product. This paper discusses a basis for a flexible approach to software configuration management. It sets out the aims of software configuration management and outlines the traditional method of achieving these aims. It goes on to describe the underlying features that provide a basis for configuration management in the Flex programming support environment. It describes the practical application of these features in easing some of the traditional problems of configuration management. Configuration management across a set of machines is considered as well as configuration management on a single machine.

Software architecture, configuration management, and configurable distributed systems are three areas of research that until now have evolved separately. Contributions in each field have focused on their respective area of concern. However, as solutions in the three fields tend to center around some notion of a system model, it is worthwhile to investigate their relationship in detail. In particular, the large amount of overlap among the system models developed in each area, combined with the complementary nature of the differences among them, suggests that an approach based on a common system model is viable. In this paper, we illustrate the benefits of using such a unified system model, identify the commonalities and differences among the existing system models, and present some of our initial experiments that we believe will lead to the development of a single system model that is usable in all three fields.

Volume I of this report describes the proposed Runway Configuration Management System (RCMS) operational software for review by the facility personnel. It also serves as an input to RCMS functional specifications for the Traffic Management System (TMS) program. Using interactive computer logic, RCMS helps supervisors select runway configurations which reduce aircraft delays by optimizing throughput capacity in dynamic operational environments. Volume II of this report is the User's Guide to the RCMS. (Author)

This thesis establishes a framework for evaluating automated configuration management tools for use in high assurance software development projects and uses the framework to evaluate eight tools. The evaluation framework identifies a dozen feature areas that affect a high assurance project team's ability to achieve its configuration management goals and evaluates the different methods that existing tools use to implement each feature area. Each implementation method is assigned a risk rating that approximates the relative risk that the method adds to the overall configuration management process. The tools with the lowest total ratings minimize risk to high assurance projects. The results of the evaluation show that although certain tools are less risky to use than other tools for high assurance projects, no tool minimizes risk in all feature areas. Furthermore, none of the existing tools are designed to leverage high assurance environments--i.e. none run on operating systems that have themselves been evaluated as meeting high assurance requirements. Thus, high assurance development projects that want to leverage the benefits of configuration management tools and achieve a sufficiently strong configuration management solution must employ existing tools in a protected environment that specifically addresses the risks created by the tools' implementation methods.

This thesis establishes a framework for evaluating automated configuration management tools for use in high assurance software development projects and uses the framework to evaluate eight tools. The evaluation framework identifies a dozen feature areas that affect a high assurance project team's ability to achieve its configuration management goals and evaluates the different methods that existing tools use to implement each feature area. Each implementation method is assigned a risk rating that approximates the relative risk that the method adds to the overall configuration management process. The tools with the lowest total ratings minimize risk to high assurance projects. The results of the evaluation show that although certain tools are less risky to use than other tools for high assurance projects, no tool minimizes risk in all feature areas. Furthermore, none of the existing tools are designed to leverage high assurance environments--i.e. none run on operating systems that have themselves been evaluated as meeting high assurance requirements. Thus, high assurance development projects that want to leverage the benefits of configuration management tools and achieve a sufficiently strong configuration management solution must employ existing tools in a protected environment that specifically addresses the risks created by the tools' implementation methods.

This thesis establishes a framework for evaluating automated configuration management tools for use in high assurance software development projects and uses the framework to evaluate eight tools. The evaluation framework identifies a dozen feature areas that affect a high assurance project team's ability to achieve its configuration management goals and evaluates the different methods that existing tools use to implement each feature area. Each implementation method is assigned a risk rating that approximates the relative risk that the method adds to the overall configuration management process. The tools with the lowest total ratings minimize risk to high assurance projects. The results of the evaluation show that although certain tools are less risky to use than other tools for high assurance projects, no tool minimizes risk in all feature areas. Furthermore, none of the existing tools are designed to leverage high assurance environments--i.e. none run on operating systems that have themselves been evaluated as meeting high assurance requirements. Thus, high assurance development projects that want to leverage the benefits of configuration management tools and achieve a sufficiently strong configuration management solution must employ existing tools in a protected environment that specifically addresses the risks created by the tools' implementation methods.

When software development is shared between several different sites, or host computers, or even between different development organizations, problems which are not evident in more compact development systems arise. Many of these problems manifest themselves in software configuration management. If software developed on one project is to be reused on another project then software configuration management needs to extend beyond the individual project into a wider area. This paper addresses the problems of software configuration management when sharing software projects and between host development systems, and between projects, using an integrated Programming Support Environment. The discussion assumes the availability of some of the facilities that were proposed for inclusion in the UK CHAPSE (CHILL Ada Programming Support Environment). (Author)

In the past, radios of any type were uniform across the entire United States Marine Corps (USMC) arsenal and were completely interchangeable. Now that they are software defined, each radio can be unique. The configuration management challenge presented by this diversity in the radio inventory motivates the following research questions: 1.How can the USMC maintain the flexibility required to tailor equipment for unique missionswithout introducing interoperability issues? 2.How can the USMC achieve configuration management of software-defined radios to ensurereliable battlefield communications? This thesis reveals an unintended consequence resulting from the development of software-defined radios and explores possible solution concepts. Three solution concepts were developed and analyzed to determine not only how well they answer these two key questions, but also how they might affect existing doctrine, organization, training, materiel, leadership, personnel, facilities, and policy (DOTMLPF-P) of the Marine Corps. Although no single solution concept was selected over the others, this thesis explores the trade space among all three and points out strengths and weaknesses of each, and then goes on to recommend more future work that could be performed to take the exploration to the next level.

In the past, radios of any type were uniform across the entire United States Marine Corps (USMC) arsenal and were completely interchangeable. Now that they are software defined, each radio can be unique. The configuration management challenge presented by this diversity in the radio inventory motivates the following research questions: 1.How can the USMC maintain the flexibility required to tailor equipment for unique missionswithout introducing interoperability issues? 2.How can the USMC achieve configuration management of software-defined radios to ensurereliable battlefield communications? This thesis reveals an unintended consequence resulting from the development of software-defined radios and explores possible solution concepts. Three solution concepts were developed and analyzed to determine not only how well they answer these two key questions, but also how they might affect existing doctrine, organization, training, materiel, leadership, personnel, facilities, and policy (DOTMLPF-P) of the Marine Corps. Although no single solution concept was selected over the others, this thesis explores the trade space among all three and points out strengths and weaknesses of each, and then goes on to recommend more future work that could be performed to take the exploration to the next level.

This report presents a review of the software configuration management (CM) plans developed for the Space Station Training Facility (SSTF) and the Space Station Control Center. The scope of the CM assessed in this report is the Systems Integration and Testing Phase of the Ground Systems development life cycle. This is the period following coding and unit test and preceding delivery to operational use. This report is one of a series from a study of the interfaces among the Ground Systems Development Environment (GSDE), the development systems for the SSTF and the SSCC, and the target systems for SSCC and SSTF. This is the last report in the series. The focus of this report is on the CM plans developed by the contractors for the Mission Systems Contract (MSC) and the Training Systems Contract (TSC). CM requirements are summarized and described in terms of operational software development. The software workflows proposed in the TSC and MSC plans are reviewed in this context, and evaluated against the CM requirements defined in earlier study reports. Recommendations are made to improve the effectiveness of CM while minimizing its impact on the developers.

This report presents a review of the software configuration management (CM) plans developed for the Space Station Training Facility (SSTF) and the Space Station Control Center. The scope of the CM assessed in this report is the Systems Integration and Testing Phase of the Ground Systems development life cycle. This is the period following coding and unit test and preceding delivery to operational use. This report is one of a series from a study of the interfaces among the Ground Systems Development Environment (GSDE), the development systems for the SSTF and the SSCC, and the target systems for SSCC and SSTF. This is the last report in the series. The focus of this report is on the CM plans developed by the contractors for the Mission Systems Contract (MSC) and the Training Systems Contract (TSC). CM requirements are summarized and described in terms of operational software development. The software workflows proposed in the TSC and MSC plans are reviewed in this context, and evaluated against the CM requirements defined in earlier study reports. Recommendations are made to improve the effectiveness of CM while minimizing its impact on the developers.

This report presents a review of the software configuration management (CM) plans developed for the Space Station Training Facility (SSTF) and the Space Station Control Center. The scope of the CM assessed in this report is the Systems Integration and Testing Phase of the Ground Systems development life cycle. This is the period following coding and unit test and preceding delivery to operational use. This report is one of a series from a study of the interfaces among the Ground Systems Development Environment (GSDE), the development systems for the SSTF and the SSCC, and the target systems for SSCC and SSTF. This is the last report in the series. The focus of this report is on the CM plans developed by the contractors for the Mission Systems Contract (MSC) and the Training Systems Contract (TSC). CM requirements are summarized and described in terms of operational software development. The software workflows proposed in the TSC and MSC plans are reviewed in this context, and evaluated against the CM requirements defined in earlier study reports. Recommendations are made to improve the effectiveness of CM while minimizing its impact on the developers.

The growth in cost and importance of software to NASA has caused NASA to address the improvement of software development across the agency. One of the products of this program is a series of guidebooks that define a NASA concept of the assurance processes which are used in software development. The Software Assurance Guidebook, SMAP-GB-A201, issued in September, 1989, provides an overall picture of the concepts and practices of NASA in software assurance. Lower level guidebooks focus on specific activities that fall within the software assurance discipline, and provide more detailed information for the manager and/or practitioner. This is the Software Configuration Management Guidebook which describes software configuration management in a way that is compatible with practices in industry and at NASA Centers. Software configuration management is a key software development process, and is essential for doing software assurance.

Abstract — Traceability in the agricultural production chain enables us to identify the origin and the process by which a product was subjected to its availability to the end consumer. To develop a framework for traceability of the productive grain process, specification and implementation was performed by following the Software Engineering standards, with the management of Software Configuration. This article presents the first phase of this administration, component identification, applied to the development of this framework, as a team, with limited human and financial resources. As a result, the approach has allowed greater control of software components, the assimilation of the importance of team work and greater independence between members of the project. To reduce the development time of new projects, one solution is to establish greater granularity of components to be managed and define a part of the team responsible for the Software Configuration Management

This configuration management plan defines the policies and methods for implementation of configuration management for the IDAMST software. The plan defines the basic functions of configuration management (CM) and the baselines or reference points for development and control of the IDAMST software documents and products. The major impact of configuration management is in the development phase of the program. Since program plans, schedules and contractual requirements for the development phase have not yet been formulated, this plan, of necessity, provides a general approach which will require modification and updating when this information is available. The major functions of configuration management covered by this plan are: Configuration Identification, Configuration Control, Configuration Status Accounting, and Verification.

This configuration management plan defines the policies and methods for implementation of configuration management for the IDAMST software. The plan defines the basic functions of configuration management (CM) and the baselines or reference points for development and control of the IDAMST software documents and products. The major impact of configuration management is in the development phase of the program. Since program plans, schedules and contractual requirements for the development phase have not yet been formulated, this plan, of necessity, provides a general approach which will require modification and updating when this information is available. The major functions of configuration management covered by this plan are: Configuration Identification, Configuration Control, Configuration Status Accounting, and Verification.

This configuration management plan defines the policies and methods for implementation of configuration management for the IDAMST software. The plan defines the basic functions of configuration management (CM) and the baselines or reference points for development and control of the IDAMST software documents and products. The major impact of configuration management is in the development phase of the program. Since program plans, schedules and contractual requirements for the development phase have not yet been formulated, this plan, of necessity, provides a general approach which will require modification and updating when this information is available. The major functions of configuration management covered by this plan are: Configuration Identification, Configuration Control, Configuration Status Accounting, and Verification.

This configuration management plan defines the policies and methods for implementation of configuration management for the IDAMST software. The plan defines the basic functions of configuration management (CM) and the baselines or reference points for development and control of the IDAMST software documents and products. The major impact of configuration management is in the development phase of the program. Since program plans, schedules and contractual requirements for the development phase have not yet been formulated, this plan, of necessity, provides a general approach which will require modification and updating when this information is available. The major functions of configuration management covered by this plan are: Configuration Identification, Configuration Control, Configuration Status Accounting, and Verification.

This configuration management plan defines the policies and methods for implementation of configuration management for the IDAMST software. The plan defines the basic functions of configuration management (CM) and the baselines or reference points for development and control of the IDAMST software documents and products. The major impact of configuration management is in the development phase of the program. Since program plans, schedules and contractual requirements for the development phase have not yet been formulated, this plan, of necessity, provides a general approach which will require modification and updating when this information is available. The major functions of configuration management covered by this plan are: Configuration Identification, Configuration Control, Configuration Status Accounting, and Verification.

This configuration management plan defines the policies and methods for implementation of configuration management for the IDAMST software. The plan defines the basic functions of configuration management (CM) and the baselines or reference points for development and control of the IDAMST software documents and products. The major impact of configuration management is in the development phase of the program. Since program plans, schedules and contractual requirements for the development phase have not yet been formulated, this plan, of necessity, provides a general approach which will require modification and updating when this information is available. The major functions of configuration management covered by this plan are: Configuration Identification, Configuration Control, Configuration Status Accounting, and Verification.

Software configuration management encompasses the disciplines and techniques of initiating, evaluating, and controlling change to software products during and after the development process. It emphasizes the importance of configuration control in managing software production. Configuration management is an integral part of the software development process across all phases of the life cycle. It functions as a controlling discipline, enabling changes to be made to existing documentation and products in such a way as not to destroy the integrity of the software. Since configuration management extends over the life of the product, and since tools, techniques, and standard exist solely aimed at its proper execution, configuration management can stand alone as a module within a graduate curriculum. The module presented here is intended to be an indepth consideration of configuration management, including configuration item identification, change reporting and evaluation change, execution, tool evaluation and use, version control, and management principles related to configuration control.

Software configuration management encompasses the disciplines and techniques of initiating, evaluating, and controlling change to software products during and after the development process. It emphasizes the importance of configuration control in managing software production. Configuration management is an integral part of the software development process across all phases of the life cycle. It functions as a controlling discipline, enabling changes to be made to existing documentation and products in such a way as not to destroy the integrity of the software. Since configuration management extends over the life of the product, and since tools, techniques, and standard exist solely aimed at its proper execution, configuration management can stand alone as a module within a graduate curriculum. The module presented here is intended to be an indepth consideration of configuration management, including configuration item identification, change reporting and evaluation change, execution, tool evaluation and use, version control, and management principles related to configuration control.

Software configuration management encompasses the disciplines and techniques of initiating, evaluating, and controlling change to software products during and after the development process. It emphasizes the importance of configuration control in managing software production. Configuration management is an integral part of the software development process across all phases of the life cycle. It functions as a controlling discipline, enabling changes to be made to existing documentation and products in such a way as not to destroy the integrity of the software. Since configuration management extends over the life of the product, and since tools, techniques, and standard exist solely aimed at its proper execution, configuration management can stand alone as a module within a graduate curriculum. The module presented here is intended to be an indepth consideration of configuration management, including configuration item identification, change reporting and evaluation change, execution, tool evaluation and use, version control, and management principles related to configuration control.

Software configuration management encompasses the disciplines and techniques of initiating, evaluating, and controlling change to software products during and after the development process. It emphasizes the importance of configuration control in managing software production. Configuration management is an integral part of the software development process across all phases of the life cycle. It functions as a controlling discipline, enabling changes to be made to existing documentation and products in such a way as not to destroy the integrity of the software. Since configuration management extends over the life of the product, and since tools, techniques, and standard exist solely aimed at its proper execution, configuration management can stand alone as a module within a graduate curriculum. The module presented here is intended to be an indepth consideration of configuration management, including configuration item identification, change reporting and evaluation change, execution, tool evaluation and use, version control, and management principles related to configuration control.

Software configuration management encompasses the disciplines and techniques of initiating, evaluating, and controlling change to software products during and after the development process. It emphasizes the importance of configuration control in managing software production. Configuration management is an integral part of the software development process across all phases of the life cycle. It functions as a controlling discipline, enabling changes to be made to existing documentation and products in such a way as not to destroy the integrity of the software. Since configuration management extends over the life of the product, and since tools, techniques, and standard exist solely aimed at its proper execution, configuration management can stand alone as a module within a graduate curriculum. The module presented here is intended to be an indepth consideration of configuration management, including configuration item identification, change reporting and evaluation change, execution, tool evaluation and use, version control, and management principles related to configuration control.

Configuration Management research has been performed by members of the CASE Environments Project over the course of the past five years. This report describes the contents of the configuration management research materials that have been published on the SEI World Wide Web (WWW) Server. Primary Web Structures and methods for accessing information on the Web are described. A summary of the problems and challenges encountered and the Web publishing techniques employed in this process are discussed.

Configuration management is defined as the management of change. This paper is about the use of an integrated Programming Support Environment (PSE) in Software Configuration Management. It discusses the current methods of software configuration management, and how the control of change in evolving PSE with an adequately design database and an integrated set of software tools. The discussion is based on the facilities set to be provided in the database and tools of the UK CHAPSE (CHILL Ada Programming Support Environment). (Author)

Configuration management is defined as the management of change. This paper is about the use of an integrated Programming Support Environment (PSE) in Software Configuration Management. It discusses the current methods of software configuration management, and how the control of change in evolving PSE with an adequately design database and an integrated set of software tools. The discussion is based on the facilities set to be provided in the database and tools of the UK CHAPSE (CHILL Ada Programming Support Environment). (Author)

Configuration management is defined as the management of change. This paper is about the use of an integrated Programming Support Environment (PSE) in Software Configuration Management. It discusses the current methods of software configuration management, and how the control of change in evolving PSE with an adequately design database and an integrated set of software tools. The discussion is based on the facilities set to be provided in the database and tools of the UK CHAPSE (CHILL Ada Programming Support Environment). (Author)

This instruction implements Air Force Policy Directive (AFPD) 33-1, Command, Control, Communications, and Computer (C4) Systems. It prescribes the requirements, responsibilities, and procedures for operation, security, and configuration management of the Strategic Automated Command Control System-Data Transmission Subsystem (SACCS-DTS). It applies to all users of the SACCS-DTS Network, either through direct input or interface systems.

The Air Force requires a centralized and cost and effective method for designing and implementing new data processing systems. Similarly, the implementation must also be applied to current data processing systems. The basic premise focuses on the fact that computer hardware prices have steadily decreased over the last fifteen years; however, the cost of software has become more expensive during this same period. With this point in mind, it does not make sense to use a general purpose computer to perform a variety of functions. This is especially true if the hardware is not suited to perform a certain function easily. The software, the most costly part of a data processing system, should not be constrained by the hardware. Additionally, when the same function is performed by several separate organizations, it makes sense to have compatible hardware at these locations. Thus, the same software can be utilized at these locations. Consequently, the standardization of hardware to insure the transportability of software requires a thorough investigation. Standardization and transportability are explored in depth. The focus is on several Department of Defense (DOD) computer systems. The ideas and strategies expressed in this thesis can be applied to any automated function.

This report is one of a series of guidebooks whose purpose is to assist Air Force Program Office Personnel and other USAF acquisition engineers in the acquisition engineering of software for Automatic Test Equipment and Training Simulators. This guidebook provides guidance in the preparation, imposition and enforcement of software configuration management requirements and recommended procedures. (Author)

This thesis establishes a framework for evaluating automated configuration management tools for use in high assurance software development projects and uses the framework to evaluate eight tools. The evaluation framework identifies a dozen feature areas that affect a high assurance project team's ability to achieve its configuration management goals and evaluates the different methods that existing tools use to implement each feature area. Each implementation method is assigned a risk rating that approximates the relative risk that the method adds to the overall configuration management process. The tools with the lowest total ratings minimize risk to high assurance projects. The results of the evaluation show that although certain tools are less risky to use than other tools for high assurance projects, no tool minimizes risk in all feature areas. Furthermore, none of the existing tools are designed to leverage high assurance environments-i.e. none run on operating systems that have themselves been evaluated as meeting high assurance requirements. Thus, high assurance development projects that want to leverage the benefits of configuration management tools and achieve a sufficiently strong configuration management solution must employ existing tools in a protected environment that specifically addresses the risks created by the tools' implementation methods.

This thesis establishes a framework for evaluating automated configuration management tools for use in high assurance software development projects and uses the framework to evaluate eight tools. The evaluation framework identifies a dozen feature areas that affect a high assurance project team's ability to achieve its configuration management goals and evaluates the different methods that existing tools use to implement each feature area. Each implementation method is assigned a risk rating that approximates the relative risk that the method adds to the overall configuration management process. The tools with the lowest total ratings minimize risk to high assurance projects. The results of the evaluation show that although certain tools are less risky to use than other tools for high assurance projects, no tool minimizes risk in all feature areas. Furthermore, none of the existing tools are designed to leverage high assurance environments-i.e. none run on operating systems that have themselves been evaluated as meeting high assurance requirements. Thus, high assurance development projects that want to leverage the benefits of configuration management tools and achieve a sufficiently strong configuration management solution must employ existing tools in a protected environment that specifically addresses the risks created by the tools' implementation methods.

This thesis establishes a framework for evaluating automated configuration management tools for use in high assurance software development projects and uses the framework to evaluate eight tools. The evaluation framework identifies a dozen feature areas that affect a high assurance project team's ability to achieve its configuration management goals and evaluates the different methods that existing tools use to implement each feature area. Each implementation method is assigned a risk rating that approximates the relative risk that the method adds to the overall configuration management process. The tools with the lowest total ratings minimize risk to high assurance projects. The results of the evaluation show that although certain tools are less risky to use than other tools for high assurance projects, no tool minimizes risk in all feature areas. Furthermore, none of the existing tools are designed to leverage high assurance environments-i.e. none run on operating systems that have themselves been evaluated as meeting high assurance requirements. Thus, high assurance development projects that want to leverage the benefits of configuration management tools and achieve a sufficiently strong configuration management solution must employ existing tools in a protected environment that specifically addresses the risks created by the tools' implementation methods.

This thesis establishes a framework for evaluating automated configuration management tools for use in high assurance software development projects and uses the framework to evaluate eight tools. The evaluation framework identifies a dozen feature areas that affect a high assurance project team's ability to achieve its configuration management goals and evaluates the different methods that existing tools use to implement each feature area. Each implementation method is assigned a risk rating that approximates the relative risk that the method adds to the overall configuration management process. The tools with the lowest total ratings minimize risk to high assurance projects. The results of the evaluation show that although certain tools are less risky to use than other tools for high assurance projects, no tool minimizes risk in all feature areas. Furthermore, none of the existing tools are designed to leverage high assurance environments-i.e. none run on operating systems that have themselves been evaluated as meeting high assurance requirements. Thus, high assurance development projects that want to leverage the benefits of configuration management tools and achieve a sufficiently strong configuration management solution must employ existing tools in a protected environment that specifically addresses the risks created by the tools' implementation methods.

This thesis establishes a framework for evaluating automated configuration management tools for use in high assurance software development projects and uses the framework to evaluate eight tools. The evaluation framework identifies a dozen feature areas that affect a high assurance project team's ability to achieve its configuration management goals and evaluates the different methods that existing tools use to implement each feature area. Each implementation method is assigned a risk rating that approximates the relative risk that the method adds to the overall configuration management process. The tools with the lowest total ratings minimize risk to high assurance projects. The results of the evaluation show that although certain tools are less risky to use than other tools for high assurance projects, no tool minimizes risk in all feature areas. Furthermore, none of the existing tools are designed to leverage high assurance environments-i.e. none run on operating systems that have themselves been evaluated as meeting high assurance requirements. Thus, high assurance development projects that want to leverage the benefits of configuration management tools and achieve a sufficiently strong configuration management solution must employ existing tools in a protected environment that specifically addresses the risks created by the tools' implementation methods.

From the beginning of Ogden Air Logistics Center's software engineering division to their current Capability Maturity Model (trademark) (CMM trademark) Level 5 quality practices, the implementation of the software configuration management (SCM) discipline combined with management and engineering practices has been critical to their weapon-system software sustainment activities. The focus of this article is to discuss how SCM adds value to the Ogden Air Logistics Center by establishing and maintaining continuity of the engineering workflow and providing information to help establish a strong SCM function in maturing software organizations. Maintaining a SCM discipline is critical to the center's CMM Level 5 software sustainment activities. Proper implementation of SCM enables them to plan, identify, control, and audit product life cycles. SCM along with management and engineering guide the organization to continuously improve its ability to meet expectations of high quality, low cost, and on-time deliveries. Continuous improvement can be achieved when practitioners are provided with the proper tools and adequate training, and are empowered with a quality process.