Thesis (M.S. in Information Technology Management)--Naval Postgraduate School, March 2004. / Thesis advisor(s): Cynthia Irvine, Tim Levin. Includes bibliographical references (p. 65-66). Also available online.

Thesis (M.S.C.I.T.)--Regis University, Denver, Colo., 2006. / Title from PDF title page (viewed on Aug. 29, 2006). Includes bibliographical references.

Thesis (doctoral)--University of Oulu, 2000. / Includes bibliographical references. Also available on the World Wide Web.

Sixty to eighty per cent of the software life-cycle cost is spent on the software maintenance phase because software maintenance is usually more difficult than original development and legacy systems are generally large and complex. Software reuse has recently been considered as a best solution to enhance the productivity of a software development team and to reduce maintenance costs. In addition, Software Configuration Management (SCM) is a central part of software maintenance as it is associated with changing existing software and is a discipline for controlling these changes. Thus, both software reuse and SCM have been proposed for making a significant improvement in productivity, quality and cost. However, so far these two technologies have been investigated separately. In order for software reuse and SCM to produce effects by synergy, both approaches require to be introduced into a maintenance environment together. Since software reuse and SCM, and software reuse and software maintenance have many similarities in their activities, these disciplines can be integrated within a software maintenance environment. This research has therefore developed an integrated process model for 'Maintenance with Reuse (MwR)', that supports SCM for a reuse library which is actively maintained for use in a software maintenance environment. This thesis addresses an integrated process model called the MwR model and its prototype tool TERRA (Tool for Evolution of a Reusable and Reconfigurable Assets Library) that consist of a configuration management (CM) process, reuse process, maintenance process and administration of a reuse library. The MwR model and TERRA provide reusers and maintainers with many activities of these four processes such as classifying, storing, retrieving, evaluating, and propagating reusable components, including controlling changes to both reusable components and existing systems. The process model of an integrated approach has been developed and validated using Process Weaver. The TERRA tool has been implemented on the WWW so that the prototype can provide portability, traceability, integration with existing tools, and a distributed maintenance environment. The TERRA prototype has been tested and evaluated through a scenario based case study. Several scenarios based on real data have been created and used for the case study so that an organisation can apply the model and tool to its maintenance environment without many problems. The software maintenance community is facing serious problems with legacy systems, such as a ever increasing frequency of changes and backlogs, lack of integrated tools and methods, and lack of software maintenance support environments. The control and management of changes to the software components in a reuse repository are crucial to successful software development and maintenance. If the component is being used in multiple systems effects of uncontrolled change are more critical. However, reuse libraries and servers currently available have not been successful as they do not support further development or maintenance of the reusable components. In addition, most of them are not sophisticated since they have not been linked to a development/maintenance environment. The integrated model of MwR can overcome many problems that exist in software maintenance and reuse through introduction of SCM functionalities into a maintenance environment. Thus, the integration of these common activities will greatly contribute to enhancing the productivity and quality of software, and will additionally lead to reducing the costs and backlogs of changes within a maintenance environment.

Thesis (M.S.)--University of Missouri--Rolla, 2007. / Vita. The entire thesis text is included in file. Title from title screen of thesis/dissertation PDF file (viewed February 4, 2008) Includes bibliographical references (p. 163-165).

No description available.

ITC/USA 2005 Conference Proceedings / The Forty-First Annual International Telemetering Conference and Technical Exhibition / October 24-27, 2005 / Riviera Hotel & Convention Center, Las Vegas, Nevada / Creating a generic, multi-vendor data exchange system for transmitting telemetry configurations between various systems is a daunting task. To date many different systems have been proposed including relational databases (RDBMS), TMATS, and several different XML schemas. Although many of these systems have been implemented, a complete, flexible solution has not been developed. This paper describes an implementation that is currently in use for exporting and importing a complete telemetry system via XML. Using this system, an engineer can import an entire telemetry configuration, a partial telemetry configuration, or even just a single measurement (parameter). As a result, the gap between user database systems and the airborne instrumentation vendor’s configuration software (IVCS) is seamlessly bridged. This provides many benefits including: the ability to rapidly change configurations, data entry error avoidance, version control, the protection of sensitive information, and configuration reusability. This system allows for the configuration of all aspects of the telemetry setup including data acquisition hardware, transmitters, ground stations, and recorders. In addition, the recorder settings and the definition of the data that are to be recorded are coupled and linked to the rest of the telemetry configuration, which facilitates future data recovery.

ITC/USA 2008 Conference Proceedings / The Forty-Fourth Annual International Telemetering Conference and Technical Exhibition / October 27-30, 2008 / Town and Country Resort & Convention Center, San Diego, California / This paper presents the Flight Test Instrumentation Manager Software application internally developed and used inside the Eurocopter Flight Test department. This fully integrated and user friendly tool covers the all management requirement for entire life cycle of the flight test instrumentation equipment and configuration, tracking all the main events: order, calibration, configuration, service and repair, final disposal. FTIManager serves as a central hub between the instrumentation team and the post processing and analysis teams.

Model checking is an existing approach for automatic reasoning. The model checker is an important tool and has been applied to software engineering for system verification. As an extension of model checking, model update is a new concept and has been defined and developed in this dissertation. A model updater is employed as an automatic system modification tool for software verification. The combination of model checking and model update completes the task of automatic system verification. In this dissertation, a comprehensive theoretical foundation and prototype implementation for CTL model update are developed. First, five primitive updates which capture the basic atomic operations in a CTL Kripke model are identified and formalized. Next, the minimal change criteria for CTL model update based on these primitive operations are defined. Then, updating an original model to a new model satisfying CTL semantics based on previous primitive updates and minimal change rules is characterized. The related complexity of CTL model update is also analyzed. Following this research, formal algorithms in the form of pseudo code to be used as the guidance for future implementation are designed. Then, a prototype CTL model updater is implemented. This prototype CTL model updater is a stand alone utility and contains both model checking and update functions. The prototype is then applied to three well known models and has successfully been tested. During the implementation, as a byproduct, the approach for extracting a complete Kripke model from NuSMV is described. Also, during the implementation, an up-date model explosion problem is discovered and further minimal change rules based on the original minimal change rules are proposed which significantly reduce the number of minimally updated models. The corresponding theory is formalized and the complexity for solving the update model explosion problem is analyzed. / Doctor of Philosophy (Ph.D.)

<p> </p><p>Nowadays, as the use of computers is rapidly spreading to our life, software is getting more and more complex and large in computer systems. Therefore, the software configuration management (SCM) is playing an increasingly important role in the software development process. One of its significant activities is change management, which has an outstanding role in dealing with the continued and concurrent change requirements during the system development and use.</p><p>In this report, we describe some basic activities of SCM, overview some representative SCM CASE tools with emphasizing on change management and analyze a possibility of integration of SCM version management tool (e.g., Subversion) and error management tool (e.g., Bugzialla) in order to provide an integrated software configuration management and change management. Moreover, a set of exercises based on RCS are developed, which illustrate some SCM simple activities and their modification to facilitate version management and change management.</p><p> </p>