Downloads & Free Reading Options - Results

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 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 document describes the software developed as part of the Chicago O'Hare Runway Configuration Management System (CMS). The software is designed as an interactive automated planning aid to assist the O'Hare assistant chief in the consistent selection of efficient runway configurations in order to lower aircraft delays. In addition, CMS serves as an information management system by consolidating various airport data and making them available for the O'Hare facility personnel. Volume I of this document contains the general description of the CMS software plus high level pseudocode describing its logic. Volume II is dedicated to detailed description of the software via low level pseudocode. (Author)

This document describes the software developed as part of the Chicago O'Hare Runway Configuration Management System (CMS). The software is designed as an interactive automated planning aid to assist the O'Hare assistant chief in the consistent selection of efficient runway configurations in order to lower aircraft delays. In addition, CMS serves as an information management system by consolidating various airport data and making them available for the O'Hare facility personnel. Volume I of this document contains the general description of the CMS software plus high level pseudocode describing its logic. Volume II is dedicated to detailed description of the software via low level pseudocode. (Author)

This document describes the software developed as part of the Chicago O'Hare Runway Configuration Management System (CMS). The software is designed as an interactive automated planning aid to assist the O'Hare assistant chief in the consistent selection of efficient runway configurations in order to lower aircraft delays. In addition, CMS serves as an information management system by consolidating various airport data and making them available for the O'Hare facility personnel. Volume I of this document contains the general description of the CMS software plus high level pseudocode describing its logic. Volume II is dedicated to detailed description of the software via low level pseudocode. (Author)

Software Quality Assurance (SQA) is recognized as an essential function needed to monitor the software system development life cycle (SDLC). The framework established for Software Quality Metrics (SQM) provides goal-directed system specifications and the ability to quantitatively assess the quality of the system under development. The Automated Measurement Tool (AMT), which operationalizes the application of SQM, functions as the core of a Decision Support System, providing quantitative measures and various levels of reports. A literature survey of SQA aids enabled the recommendation of a minimum set of tools and techniques to be used by the SQA program for monitoring the SDLC, which has been envisioned as an iterative process controlled by management. Recognizing the functional impact of specific information as the key to objectively monitoring and controlling the software system development, the decision-making model was conceptualized as three subsystems within each phase of the SDLC: scanning (afferent), organizing (intelligence), and decision (efferent). The use of checklists by system developers highlights a prescriptive method of goal-directed development. The thesis provides justification for using SQM by reviewing the need and demonstrating how the concepts can now be used. (Author)

This report is one of a series of guidebooks which provide guidance in the acquisition management and engineering of Airborne Systems software procured under Air Force 800 series regulations. It provides specific guidance in the three basic CM areas: configuration identification, configuration control, and status accounting. (Author)

Contents: A Configuration Management Example; Examples of Software Change Forms; Example of a Software Configuration Management Plan; Typical Revision Control System Session; Presentation Support Viewgraphs; Sample Examinations; Summary of the SEI Workshop on Software Configuration Management; Bibliography on Version Control and Configuration Management.

This paper documents a two-and-a-half year software development project of the Combat Systems Configuration Management Branch of the Combat Systems Department at Naval Surface Warfare Center, Dahlgren Division (NSWCDD), at Dahlgren, Virginia. The author simultaneously managed two AEGIS Configuration Control Engineering Status System (ACCESS) software development projects and pursued a master's degree in Software Engineering Technical Management through the National Technological University sponsored by NSWCDD. The paper describes lessons learned and practical experience gained by the author in managing a software development project to successful completion. The narrative includes methods that worked and ones that did not work. Critical success factors that the author considers most important to satisfactory software development are: (1) structured and documented iterative life cycle development methodology; (2) implementation of software engineering repeatable processes; (3) highly-motivated, technically experienced dedicated team; (4) continuous and substantial customer involvement; (5) self-directed, empowered management style; and (6) experienced and committed project leader.

This paper documents a two-and-a-half year software development project of the Combat Systems Configuration Management Branch of the Combat Systems Department at Naval Surface Warfare Center, Dahlgren Division (NSWCDD), at Dahlgren, Virginia. The author simultaneously managed two AEGIS Configuration Control Engineering Status System (ACCESS) software development projects and pursued a master's degree in Software Engineering Technical Management through the National Technological University sponsored by NSWCDD. The paper describes lessons learned and practical experience gained by the author in managing a software development project to successful completion. The narrative includes methods that worked and ones that did not work. Critical success factors that the author considers most important to satisfactory software development are: (1) structured and documented iterative life cycle development methodology; (2) implementation of software engineering repeatable processes; (3) highly-motivated, technically experienced dedicated team; (4) continuous and substantial customer involvement; (5) self-directed, empowered management style; and (6) experienced and committed project leader.

This document describes the software developed as part of the Chicago O'Hare Runway Configuration Management System (CMS). The software is designed as an interactive automated planning aid to assist the O'Hare assistant chief in the consistent selection of efficient runway configurations in order to lower aircraft delays. In addition, CMS serves as an information management system by consolidating various airport data and making them available for the O'Hare facility personnel. Volume I of this document contains the general description of the CMS software plus high level pseudocodes describing its logic. Volume II is dedicated to detailed description of the software via low level pseudocodes. (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 study investigated the development of a mechanism for use in the evaluation of Software Configuration Management (SCM) tool's. An examination of applicable DoD standards identified the SCM requirements that could be levied on a development contractor, and a literature search revealed the functionality common to various automated tools. These two sets of information were organized into a matrix, and for each requirement that was met, the intersection on the matrix of the requirement and each functionality used to meet that requirement was checked. In addition to the matrix, the mechanism consisted of general information about a given tool and an area to substantiate each requirement identified as being met by the tool. The evaluation mechanism was then used to assess two commercially available SCM tools: Aide-De-Camp and the Product Configuration Management System. The evaluation mechanism prescribes a method for evaluating complex SCM tools and forces the evaluator to gain intimate knowledge of a tool to effectively assess the tool's merits for a given effort. Configuration management, Software engineering, Taxonomy, Life cycles, Computer applications.

This report documents a design effort for an automated system to record and report the configuration status of software for Air Force embedded computer systems. The work included requirements analysis, software design, and data-base design. Because of the flexibility given to program managers in tailoring their reporting requirements and in selecting the data integator, only the requirements of a single AFSC program office were presented in detail. However, the requirements of other offices were considered as well. Current software engineering techniques were used to derive the design. They are highly recommended for use on other software development projects. (Author)

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.

The article proposes a model for the configuration management of open systems. The model aims at validation of configurations against given specifications. An extension of decision graphs is proposed to express specifications. The proposed model can be used by software developers to validate their own configurations across different versions of the components, or to validate configurations that include components by third parties. The model can also be used by end-users to validate compatibility among different configurations of the same application. The proposed model is first discussed in some application scenarios and then formally defined. Moreover, a type discipline is given to formally define validation of a configuration against a system specification

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.