Downloads & Free Reading Options - Results

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.

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.

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.

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.

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

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

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 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 is the configuration management Plan for the AdaNet Repository Based Software Engineering (RBSE) contract. This document establishes the requirements and activities needed to ensure that the products developed for the AdaNet RBSE contract are accurately identified, that proposed changes to the product are systematically evaluated and controlled, that the status of all change activity is known at all times, and that the product achieves its functional performance requirements and is accurately documented.

The Guidance and Control Software (GCS) project was the last in a series of software reliability studies conducted at Langley Research Center between 1977 and 1994. The technical results of the GCS project were recorded after the experiment was completed. Some of the support documentation produced as part of the experiment, however, is serving an unexpected role far beyond its original project context. Some of the software used as part of the GCS project was developed to conform to the RTCA/DO-178B software standard, "Software Considerations in Airborne Systems and Equipment Certification," used in the civil aviation industry. That standard requires extensive documentation throughout the software development life cycle, including plans, software requirements, design and source code, verification cases and results, and configuration management and quality control data. The project documentation that includes this information is open for public scrutiny without the legal or safety implications associated with comparable data from an avionics manufacturer. This public availability has afforded an opportunity to use the GCS project documents for DO-178B training. This report provides a brief overview of the GCS project, describes the 4-volume set of documents and the role they are playing in training, and includes configuration management and quality assurance documents from the GCS project. Volume 4 contains six appendices: A. Software Accomplishment Summary for the Guidance and Control Software Project; B. Software Configuration Index for the Guidance and Control Software Project; C. Configuration Management Records for the Guidance and Control Software Project; D. Software Quality Assurance Records for the Guidance and Control Software Project; E. Problem Report for the Pluto Implementation of the Guidance and Control Software Project; and F. Support Documentation Change Reports for the Guidance and Control Software Project.

A set of functional requirements for software configuration management (CM) and metrics reporting for Space Station Freedom ground systems software are described. 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 Space Station Training Facility (SSTF) and the Space Station Control Center (SSCC), and the target systems for SSCC and SSTF. The focus is on the CM of the software following delivery to NASA and on the software metrics that relate to the quality and maintainability of the delivered software. The CM and metrics requirements address specific problems that occur in large-scale software development. Mechanisms to assist in the continuing improvement of mission operations software development are described.

A set of functional requirements for software configuration management (CM) and metrics reporting for Space Station Freedom ground systems software are described. 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 Space Station Training Facility (SSTF) and the Space Station Control Center (SSCC), and the target systems for SSCC and SSTF. The focus is on the CM of the software following delivery to NASA and on the software metrics that relate to the quality and maintainability of the delivered software. The CM and metrics requirements address specific problems that occur in large-scale software development. Mechanisms to assist in the continuing improvement of mission operations software development are described.

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.

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.

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.

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.

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.

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.

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

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

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

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

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

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.

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.

The Software Design Document of UUIS describes the prototype design details of the system architecture, database layer, deployment and configuration details as well as test cases produced while working the design and implementation of the prototype. The requirements specification of UUIS are detailed in arXiv:1005.0783.

The Software Design Document of UUIS describes the prototype design details of the system architecture, database layer, deployment and configuration details as well as test cases produced while working the design and implementation of the prototype. The requirements specification of UUIS are detailed in arXiv:1005.0783.

The Software Design Document of UUIS describes the prototype design details of the system architecture, database layer, deployment and configuration details as well as test cases produced while working the design and implementation of the prototype. The requirements specification of UUIS are detailed in arXiv:1005.0783.

The Software Design Document of UUIS describes the prototype design details of the system architecture, database layer, deployment and configuration details as well as test cases produced while working the design and implementation of the prototype. The requirements specification of UUIS are detailed in arXiv:1005.0783.

The Software Design Document of UUIS describes the prototype design details of the system architecture, database layer, deployment and configuration details as well as test cases produced while working the design and implementation of the prototype. The requirements specification of UUIS are detailed in arXiv:1005.0783.

The Software Design Document of UUIS describes the prototype design details of the system architecture, database layer, deployment and configuration details as well as test cases produced while working the design and implementation of the prototype. The requirements specification of UUIS are detailed in arXiv:1005.0783.

The Software Design Document of UUIS describes the prototype design details of the system architecture, database layer, deployment and configuration details as well as test cases produced while working the design and implementation of the prototype. The requirements specification of UUIS are detailed in arXiv:1005.0783.

The Software Design Document of UUIS describes the prototype design details of the system architecture, database layer, deployment and configuration details as well as test cases produced while working the design and implementation of the prototype. The requirements specification of UUIS are detailed in arXiv:1005.0783.

The Software Design Document of UUIS describes the prototype design details of the system architecture, database layer, deployment and configuration details as well as test cases produced while working the design and implementation of the prototype. The requirements specification of UUIS are detailed in arXiv:1005.0783.

The Software Design Document of UUIS describes the prototype design details of the system architecture, database layer, deployment and configuration details as well as test cases produced while working the design and implementation of the prototype. The requirements specification of UUIS are detailed in arXiv:1005.0783.

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)

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.

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.

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.

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.

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.