Software Engineering Institute Carnegie Mellon

SEI Documents List

[2007] [2006] [2005] [2004] [2003] [2002] [2001] [2000] [1999] [1998] [1997] [1996] [1995] [1994] [1993] [1992] [1991] [1990] [1989] [1988] [1987] [1986] [PDF]

1992 Reports

Special Reports

CMU/SEI-92-SR-008, ADA264798
Annotated Bibliography on Integration in Software Engineering Environments, An
Brown, A. & Penedo, M.

This paper provides an annotated bibliography on integration in software engineering environments (SEEs). The aim is to provide readers with a source of information that can be used as the basis for more detailed studies in this area.

http://www.sei.cmu.edu/publications/documents/92.reports/92.sr.008.html

CMU/SEI-92-SR-010, ADA2582253
Bibliography of Externally Published Works by the SEI Engineering Techniques Program, A
Brenner, S. & Hart, G.

This bibliography lists works by the members of the Software Engineering Institute (SEI) Engineering Techniques Program that are not published or available from the SEI. The bibliography is organized by type of work (i.e., journal or magazine article, book, or proceedings.) Indices are provided by author and targeted audience.

http://www.sei.cmu.edu/publications/documents/92.reports/92.sr.010.html

CMU/SEI-92-SR-009, ADA257225
Domain-Specific Software Architecture Program, The
Mettala, E. & Graham, M.

There are six independent projects within the DSSA program. Four of these projects are working in specific, military- significant domains. Those domains are Avionics Navigation, Guidance and Flight Director for Helicopters; Command and Control; Distributed Intelligent Control and Management for Vehicle Management; Intelligent Guidance, Navigation and Control for Missiles. In addition, there are two projects working on underlying support technology. Hybrid (discrete and continuous, non-linear) Control and Prototyping Technology.

This report contains brief descriptions from each project and an overview.

http://www.sei.cmu.edu/publications/documents/92.reports/92.sr.009.html

CMU/SEI-92-SR-003, ADA258468
Joint Integrated Avionics Working Group (JIAWG) Object-Oriented Domain Analysis Method (JODA)
Holibaugh, R.

The Joint Integrated Avionics Working Group (JIAWG) Reuse Subcommittee has initiatives in several areas to demonstrate that reuse can effectively support the JIAWG programs, and the creation of reusable assets is an essential element of reuse. Domain analysis is the process that identifies what is reusable, how it can be structured, and how it can be used. This report describes a method for domain analysis that is based on Coad and Yourdon's "Object Oriented Analysis." This method, the JIAWG Object-Oriented Domain Analysis (JODA), includes several enhancements to the method of Coad and Yourdon and produces a domain model to support asset creation and reuse.

http://www.sei.cmu.edu/publications/documents/92.reports/92.sr.003.html

CMU/SEI-92-SR-001, ADA259854
Report on Senior Executive Seminars on Software Issues
Sisti, F. & Sweet, W.

This report expands on the activities executed by the Software Engineering Institute (SEI) associated with raising the software issue awareness of senior executives in the three principal constituent areas of the SEI: senior defense officials, industry executives, and senior academic personnel. In planning for and executing these activities, the SEI has responded to one of the principal aspects of its charter, which is to address the most important software-related issues applicable to the Department of Defense (DoD) and the software industry in the United States.

http://www.sei.cmu.edu/publications/documents/92.reports/92.sr.001.html

CMU/SEI-92-SR-004, ADA258255
Reuse-Based Software Development Methodology, A
Kang, K.; Cohen, S.; Holibaugh, R.; Perry, J.; & Peterson, A.

Software has been reused in applications development ever since programming started. However, the reuse practices have mostly been ad hoc, and the potential benefits of reuse have never been fully realized. Most of the available software development methodologies do not explicitly identify reuse activities. The Application of Reusable Software Components Project of the Software Engineering Institute is developing a reuse-based software development methodology, and the current direction and the progress of the methodology work are discussed in this paper.

The methodology is based on the life cycle model in DoD-STD-2167A with refinement of each phase to identify reuse activities. The reuse activities that are common across the life cycle phases are identified as: 1) studying the problem and available solutions to the problem and developing a reuse plan or strategy, 2) identifying a solution structure for the problem following the reuse plan, 3) reconfiguring the solution structure to improve reuse at the next phase, 4) acquiring, instantiating, and/or modifying existing reusable components, 5) integrating the reused and any newly developed components into the products for the phase, and 6) evaluating the products. These activities are used as the base model for defining the specific activities at each phase of the life cycle.

This methodology focuses more on identification and application of reusable resources than on construction of reusable resources, and some enhancements in the construction aspect might be necessary to make it more complete.

This methodology has never been applied; it will be used in an application redevelopment experiment and then will be improved based on our experience.

http://www.sei.cmu.edu/publications/documents/92.reports/92.sr.004.html

CMU/SEI-92-SR-013, ADA258259
Software Engineering Process Groups: Results of the 1992 SEPG Workshop Event Evaluation and a First Report on SEPG Status
Miller, M. & Goldenson, D.

This report contains a summary of the results from a questionnaire administered to participants in the Software Engineering Process Group (SEPG) Workshop held in Tysons Corner, Virginia, in April of 1992. The purpose of the questionnaire was twofold. (1) to ask the participants for their judgments about the quality of the week-long event, and (2) to begin collecting information comparing the experiences of existing SEPGs. The participants reported a generally high degree of satisfaction with the content and conduct of the event. Although descriptions about SEPG characteristics and activities apply only to the organizations whose representatives attended the workshop, our findings suggest recent and rapid growth in the SEPG community. Of the 169 responding participants, 72 percent stated that their organizations have SEPGs, and over three-quarters of the SEPGs have been established since 1990.

http://www.sei.cmu.edu/publications/documents/92.reports/92.sr.013.html

Technical Reports

CMU/SEI-92-TR-034, ADA260241
Academic Legitimacy of the Software Engineering Discipline
Berry, D.

This report examines the academic substance of software engineering. It identifies the basic research questions and the methods used to solve them. What is learned during this research constitutes the body of knowledge of software engineering. The report then discusses at length what about software makes its production so difficult and makes software engineering so challenging an intellectual discipline.

http://www.sei.cmu.edu/publications/documents/92.reports/92.tr.034.html

CMU/SEI-92-TR-029, ADA258937
ADA Adoption Handbook: A Program Manager's Guide, Version 2.0
Hefley, W.; Foreman, J.; Engle, C.; & Goodenough, J.

the ADA Adoption Handbook provides program managers with information about how best to tap ADA's strengths and manage the transition to fully using this software technology. Although the issues are complex, they are not all unique to ADA. Indeed, many of the issues addressed in this handbook must be addressed when developing any software- intensive system in any programming language. The handbook addresses the advantages and risks in adopting ADA. Significant emphasis has been placed on providing information and suggesting methods that will help program and project managers succeed in using ADA across a broad range of application domains.

The handbook focuses on the following topics: ADA's goals and benefits; program management issues; implications for education and training; software tools with emphasis on compiler validation and quality issues; the state of ADA technology as it related to system design and implementation; and the pending update of the ADA language standard (ADA 9X).

http://www.sei.cmu.edu/publications/documents/92.reports/92.tr.029.html

CMU/SEI-92-TR-001, ADA258325
ADA Validation Tests for Rate Monotonic Scheduling Algorithm
Kohout, K.; Meyer, K.; & Goodenough, J.

This report presents a set of tests for checking whether an ADA runtime system properly supports certain rate monotonic scheduling algorithms, specifically, the basic inheritance and priority ceiling protocols. These tests are intended to be used by vendors and by users to validate implementations of these protocols. The report describes the tests and how they are to be used. The source code is available electronically.

http://www.sei.cmu.edu/publications/documents/92.reports/92.tr.001.html

CMU/SEI-92-TR-031, ADA258459
Analysis of a Software Maintenance System: A CASE Study
Slomer, H. & Christie, A.

To design, implement, and operate a successful software development process, exposure to similar existing systems is invaluable. The objective of this paper is thus to document and analyze an existing, moderate size, software maintenance project. The project, which supports the maintenance of a software environment has, through incremental improvement, become very effective. However, this effectiveness has only been achieved through struggle, compromise, and creativity. The paper documents the evolution of the project, providing insights into how change was managed, and defines and formally models the project as it existed until recently. The project's process is still evolving, and recent changes, while not formally modeled, are also described. The results of this modeling are applied 1) to compare the project's practices from a perspective of the SEI Capability Maturity Model® (CMM®), and 2) to address briefly the issue of process reuse. Comparison to the CMM resulted in an identification of strengths and weaknesses of the project's software process. In the examination of reuse issues, three hypothetical examples of process reuse are examined.

http://www.sei.cmu.edu/publications/documents/92.reports/92.tr.031.html

CMU/SEI-92-TR-010, ADA254176
Analysis of Reservation-Based Dual-Link Networks
Sha, L.; Sathaye, S.; & Strosnider, J.

Next-generation networks are expected to support a wide variety of services. Some services such as video, voice, and plant control traffic have explicit timing requirements on a per-message basis rather than on the average. In this paper, we develop a general model of reservation-based dual-link networks to support real-time communication. We examine the desirable properties of this network and the difficulties in achieving these properties. We then introduce the concept of coherence and develop a theory of coherent dual-link networks. We show that a coherent dual-link network can be analyzed as though it is a centralized system. We then discuss practical considerations in implementing a dual-link network, and implications of this work to address problems observed in the IEEE 802.6 metropolitan area network standard.

http://www.sei.cmu.edu/publications/documents/92.reports/92.tr.010.html

CMU/SEI-92-TR-024, ADA266996
Analysis of SEI Software Process Assessment Results 1987-1991, An
Kitson, D. & Masters, S.

This report focuses on the results of SEI software process assessments conducted over a four year period beginning in 1987. It characterizes the software processes used by software managers and practitioners at the assessed sites and classifies issues identified during the assessments. The basis for the characterization and classification is a software process maturity model developed by the SEI. This report contributes to the existing body of knowledge on the state of practice of software engineering in the U.S. by characterizing the sites from a software process maturity perspective and profiling site software process weaknesses. The data analyzed is drawn from SEI software process assessments of 59 government and industry software sites. This work is an analysis of existing assessment data rather than a designed study. The participating sites were not randomly selected; accordingly, they do not necessarily constitute a statistically valid sampling of the U.S. software industry.

http://www.sei.cmu.edu/publications/documents/92.reports/92.tr.024.html

CMU/SEI-92-TR-003, ADA253351
Analysis Technique for Examining Integration in a Project Support Environment, An
Brown, A. & Feiler, P.

In this paper we describe the use of a Project Support Environment (PSE) services reference model as an analysis technique that helps in describing, understanding, and comparing aspects of integration in a PSE. The model is briefly described, before being used as the basis for discussing a number of issues with regard to PSE integration. A major focus of this paper is a discussion of the interfaces of interest in a PSE-interfaces within a single service, between services, and between services and the PSE end-users.

The paper concludes with a discussion of possible interpretations and developments of the model to suit different user requirements.

http://www.sei.cmu.edu/publications/documents/92.reports/92.tr.003.html

CMU/SEI-92-TR-013, ADA258466
Classification and Bibliography of Software Prototyping, A
Wood, D. & Kang, K.

Prototyping, the creation and enaction of models based on operational scenarios, has been advocated as a useful software engineering paradigm because it lends itself to intense interaction between customers, users, and developers, resulting in early validation of specifications and designs. An extensive and widespread interest in software prototyping in recent years has resulted in a daunting amount of literature and dozens of proposed methods and tools. As with any immature and growing technology, the expanding literature and approaches have resulted in correspondingly expansive and confusing terminology. This report presents an overview of technology and literature relating to the creation and use of software system prototypes. In addition to an annotated bibliography of recent prototyping literature, a technology framework, taxonomy, and series of classifications are provided. The intent of this report is to provide a basic road map through the available literature and technology.

http://www.sei.cmu.edu/publications/documents/92.reports/92.tr.013.html

CMU/SEI-92-TR-023, ADA258254
Concept Study for a National Software Engineering Database, A
Van Verth, P.

Substantial segments of the software engineering community perceive a need for high-quality software engineering data at a national level. A national software engineering database has been proposed as one way to satisfy this need. But is such a database feasible and can it really satisfy these needs?

This report provides information obtained from an informal survey of members of the software engineering community about a national database. The survey served as a means of getting a sense of the expectations that are to be met by building a national database, and provided the opportunity to learn from the experiences of those surveyed about data collection and use. The report summarizes this material in a manner that is informative and expository rather than prescriptive.

http://www.sei.cmu.edu/publications/documents/92.reports/92.tr.023.html

CMU/SEI-92-TR-002, ADA253324
Conceptual Basis for a Project Support Environment Services Model, The
Brown, A. & Feiler, P.

The foundation for a Project Support Environment (PSE) services reference model is presented. This model is to be used as the basis for understanding more about the meaning of integration in a PSE, comparing and contrasting PSE tools and products, and for helping in the identification of PSE interface areas that are candidates for standardization. The model views a PSE as a set of services, distinguishing between services as perceived by PSE end-users, and those provided as mechanisms within the PSE infrastructure. Process constraints on those services are separately identified. The motivation for the view of a PSE is described, followed by a detailed description of the main structure and elements of the model.

http://www.sei.cmu.edu/publications/documents/92.reports/92.tr.002.html

CMU/SEI-92-TR-033, ADA258457
Conceptual Framework for System Fault Tolerance, A
Heimerdinger, W. & Weinstock, C.

A major problem in transitioning fault tolerance practices to the practitioner community is a lack of a common view of what fault tolerance is, and how it can help in the design of reliable computer systems. This document takes a step towards making fault tolerance more understandable by proposing a conceptual framework. The framework provides a consistent vocabulary for fault tolerance concepts, discusses how systems fail, describes commonly used mechanisms for making systems fault tolerant, and provides some rules for developing fault tolerant systems.

http://www.sei.cmu.edu/publications/documents/92.reports/92.tr.033.html

CMU/SEI-92-TR-035, ADA259853
Control Integration through Message Passing
Brown, A.

Understanding tool integration in a Software Development Environment (SDE) is one of the key issues being addressed in current work on providing automated support for large-scale software production. Work has been taking place at both the conceptual level ("What is integration?") and the mechanistic level ("How do we provide integration?"). Many people see the answers to these questions as providing the cornerstone of real progress in the area.

Until recently, existing integration mechanisms have been very rigid in the support for integration that they provide. Users have been offered a fixed level of integration with little flexibility. However, one approach that has been recently implemented employs a control integration paradigm that appears to be flexible, supportive, and adaptable to a wide range of end-user needs. Implementations of this paradigm are based on the notion of "message passing" as the underlying communication mechanism between SDE services.

In this paper we examine the message passing approach to integration in an SDE, look at the general principles of the approach, describe some existing implementations, and discuss the use of such a mechanism as the basis for a more flexible environment that is open to experimentation with different approaches to integration.

http://www.sei.cmu.edu/publications/documents/92.reports/92.tr.035.html

CMU/SEI-92-TR-036, ADA275345
Durra: A Task Description Language User's Manual (Version 2)
Doubleday, D. & Barbacci, M.

This document describes the use of Durra, a task-level application description language, and its associated toolset. The Durra environment supports the development of highly reconfigurable distributed ADA applications. The intended audience for this document is system managers responsible for Durra installation and Durra application developers.

http://www.sei.cmu.edu/publications/documents/92.reports/92.tr.036.html

CMU/SEI-92-TR-017, ADA258221
Experience with a Course on Architectures for Software Systems Part I: Course Description
Garlan, D.; Shaw, M.; Okasaki, C.; Scott, C.; & Swonger, R.

As software systems grow in size and complexity their design problem extends beyond algorithms and data structures to issues of system design. This area receives little or no treatment in existing computer science curricula. Although courses about specific systems are usually available, there is no systematic treatment of the organizations used to assemble components into systems. These issues-the software architecture level of software design-are the subject of a new course that we taught for the first time in spring 1992. In this pair of reports, Part I presents the motivation for the course, the content and structure of the current version, and our plans for improving the next version. Part II consists of teaching materials from the first offering, including assignments and overheads for lectures.

http://www.sei.cmu.edu/publications/documents/92.reports/92.tr.017.html

CMU/SEI-92-TR-015, ADA258852
Guide to CASE Adoption
Stepien Oakes, K.; Smith, D.; & Morris, E.

In an attempt to address the productivity and quality problems afflicting the software industry, many organizations are turning toward computer-aided software engineering (CASE) technology as a potential solution. Unfortunately, the inflated claims of vendors and unreasonable expectations of new users have led to many failed CASE adoption efforts. This guide answers questions organizations may have concerning CASE technology, and provides a strategy for the adoption of CASE tools into an organization.

http://www.sei.cmu.edu/publications/documents/92.reports/92.tr.015.html

CMU/SEI-92-TR-007, ADA253326
Introduction to Software Process Improvement
Humphrey, W.

While software now pervades most facets of modern life, its historical problems have not been solved. This report explains why some of these problems have been so difficult for organizations to address and the actions required to address them. It describes the Software Engineering Institute's (SEI) software process maturity model, how this model can be used to guide software organizations in process improvement, and the various assessment and evaluation methods that use this model. The report concludes with a discussion of improvement experience and some comments on future directions for this work.

http://www.sei.cmu.edu/publications/documents/92.reports/92.tr.007.html

CMU/SEI-92-TR-005, ADA253323
Issues and Techniques of CASE Integration with Configuration
Wallnau, K.

Commercial computer-aided software engineering (CASE) tool technology has emerged as an important component of practical software development environments. Issues of CASE tool integration have received heightened attention in recent years, with various commercial products and technical approaches promising to make inroads into this difficult problem. One aspect of CASE integration that has not been adequately addressed is the integration of CASE tools with configuration management (CM)-including both CM policies and systems. Organizations need to address how to make CASE tools from different vendors work effectively with an organization's CM policies and tools (in effect, integrate CASE with CM) within the context of the rapidly evolving state of commercial integration technology. This report describes key issues of the integration of CASE with CM from a third-party integrator's perspective, i.e., how to approach the integration of CASE and CM in such a way as to not require fundamental changes to the implementation of the tools or CM systems themselves.

http://www.sei.cmu.edu/publications/documents/92.reports/92.tr.005.html

CMU/SEI-92-TR-012, ADA258932
Issues in Requirements Elicitation
Christel, M. & Kang, K.

There are many problems associated with requirements engineering, including problems in defining the system scope, problems in fostering understanding among the different communities affected by the development of a given system, and problems in dealing with the volatile nature of requirements. These problems may lead to poor requirements and the cancellation of system development, or else the development of a system that is later judged unsatisfactory or unacceptable, has high maintenance costs, or undergoes frequent changes. By improving requirements elicitation, the requirements engineering process can be improved, resulting in enhanced system requirements and potentially a much better system.

Requirements engineering can be decomposed into the activities of requirements elicitation, specification, and validation. Most of the requirements techniques and tools today focus on specification, i.e., the representation of the requirements. This report concentrates instead on elicitation concerns, those problems with requirements engineering that are not adequately addressed by specification techniques. An elicitation methodology is proposed to handle these concerns.

This new elicitation methodology strives to incorporate the advantages of existing elicitation techniques while comprehensively addressing the activities performed during requirements elicitation. These activities include fact- finding, requirements gathering, evaluation and rationalization, prioritization, and integration. Taken by themselves, existing elicitation techniques are lacking in one or more of these areas.

http://www.sei.cmu.edu/publications/documents/92.reports/92.tr.012.html

CMU/SEI-92-TR-009, ADA253327
Parallels in Computer-Aided Design Framework and Software Development Environment Efforts
Dart, S.

This paper is an attempt to raise awareness about the similarities between the efforts of the software development environment (SDE) community and the electronic computer-aided design (CAD) framework community. Apparently, SDE and CAD engineers are not aware of what is happening in each other's fields, yet cross-pollenization of efforts would assist progress. Both communities are addressing the same problems of providing configuration management (CM), tool integration, and process management support in their environment. Each community can benefit from the other since both have similar needs and have found, and are finding, similar solutions. It is particularly useful to consider collaborative efforts as both communities are evolving towards standardization.

http://www.sei.cmu.edu/publications/documents/92.reports/92.tr.009.html

CMU/SEI-92-TR-008, ADA254175
Past, Present, and Future of Configuration Management, The
Dart, S.

Automated support for configuration management (CM) is one aspect of software engineering environments that has progressed over the last 20 years. The progress is seen by the burgeoning interest in CM, many technical papers and conferences involving CM, a large number of CM tool vendors, and new software development environments that incorporate CM capabilities. This paper is about future issues affecting solutions to CM problems. To put the future into perspective, it is necessary to discuss the past and present situation for CM. The past evolves around CM systems built in-house and supplemented with manual procedures and policies for executing the CM functions. The present consists of a better understanding of CM, the beginnings of a common vocabulary for CM, existence of many third- party CM tools and environments supporting CM, and recognition that a single CM system does not solve all CM problems and that there is a need for better understanding of CM process support. The future involves technical, process-oriented, political, standardization and managerial challenges. These include the need to provide for new CM requirements, understand the effects of advances in environments, deal with governmental requirements on contractors for using certain CM capabilities, and acquire more management commitment for resources in solving the CM problems of an organization. One way to start addressing these challenges is through the definition of a CM services model that provides a conceptual framework for all CM capabilities. As CM is examined more closely in relation to software engineering, it becomes evident that advances in software technology are needed to aid advances in CM technology.

http://www.sei.cmu.edu/publications/documents/92.reports/92.tr.008.html

CMU/SEI-92-TR-032, ADA264375
Performance and ADA Style for the AN/BSY-2 Submarine Combat System
Altman, N. & Donohoe, P.

The performance of programs prepared with the Verdix ADA Development System (VADS) was measured and analyzed for programmers preparing a large ADA system. Using standard ADA benchmark suites (ACEC, AES and PIWG) and a representative Motorola 68030 target system as a source of data, questions were posed and answered about programming alternatives, based on the measured performance of the compiler. The questions included in the report were extracted from a much larger set selected from an analysis of the BSY-2 Style Guide and augmented with additional questions suggested by SEI experience. The derivation of the questions and the template for the performance analysis sections are presented as appendices.

http://www.sei.cmu.edu/publications/documents/92.reports/92.tr.032.html

CMU/SEI-92-TR-006, ADA258234
Proceedings of the CASE Management Workshop
Huff, C.; Smith, D.; Morris, E.; & Zarrella, P.

The Software Engineering Institute (SEI) Computer-Aided Software Engineering (CASE) Technology Project sponsored a workshop to address a number of key CASE management issues. The workshop was held at the SEI in Pittsburgh, Pennsylvania on June 19-20, 1991. At the workshop, a representative group of SEI affiliates from industry, government, and academia discussed among themselves such management topics as CASE acquisition policy, what CASE tools can and cannot do, CASE and metrics, and CASE tool selection. The results of these discussions are summarized in this report.

http://www.sei.cmu.edu/publications/documents/92.reports/92.tr.006.html

CMU/SEI-92-TR-016, ADA258758
Rationale for SQL ADA Module Language Description (SAMeDL)
Chastek, G.; Graham, M.; & Zelesnik, G.

The SQL ADA Module Description Language, SAMeDL, is a language for the specification of Abstract Interfaces as delineated by the SQL ADA Module Extensions (SAME) methodology. The language is formally defined in the SAMeDL Reference Manual [Chastek]. This document is a companion to the Reference Manual. Whereas the Reference Manual is meant to be precise, the Rationale is meant to be clear.

An explanation of the problem solved by the SAMeDL is given. The creation of a new language is justified and the underlying principles of that language are described. Crucial issues in the language are then explained. These include:

This document is a revision of an earlier technical report, CMU/SEI-91-TR-004. The revision consists of the addition of a reference model of database programming language interfaces to Section 1.3. The reference model gives a context for the survey of ADA SQL interface solutions given in Section 1.3.

http://www.sei.cmu.edu/publications/documents/92.reports/92.tr.016.html

CMU/SEI-92-TR-030, ADA258743
Software Development Risk: Opportunity, Not Problem
Van Scoy, R.

What is risk? What is risk management? What does risk management have to do with software? Noted software expert Tom Gilb says:

If you don't actively attack the risks, they will actively attack you.

- [Gilb, p. d72]

But what does it mean to actively attack risks? We answer these questions by examining the problems that exist in software development today and presenting the SEI Risk Program approach to turning risk into opportunity.

We begin by reviewing the fundamental concepts of risk and elaborating on how these basic concepts apply to the development of large, software-intensive systems. We then develop our strategy for seeing a systematic approach to risk management in software development be routinely practiced.

There are two key activities we are using to implement our strategy. The first is our risk management paradigm. The paradigm defines a set of continuous activities that must be undertaken to resolve technical risk in a systematic and structured way. The second is our risk assessment process for collaborating with clients to identify their technical risks.

We end with our ultimate goal: establishing an effective risk management ethic as standard practice in the software engineering industry.

http://www.sei.cmu.edu/publications/documents/92.reports/92.tr.030.html

CMU/SEI-92-TR-021, ADA258279
Software Effort and Schedule Measurement: A Framework for Counting Staff-Hours and Reporting Schedule Information
Goethert, W.; Bailey, E.; & Busby, M.

This report and the methods in it are outgrowths of work initiated by the Effort and Schedule Subgroup of the Software Metrics Definition Working Group. It contains guidelines and advice from software professionals. It is not a standard, and it should not be viewed as such. Nevertheless, the frameworks and recommendations it presents give a solid basis for constructing and communicating clear definitions for some important measures that can help all of us plan, manage, and improve our software projects and processes.

We hope that the materials we have assembled will give you a solid foundation for making your effort and schedule measures repeatable, internally consistent, and clearly understood by others. We also hope that some of you will take the ideas illustrated in this report and apply them to other measures, for no single set of measures can ever encompass all that we need to know about software products and processes.

http://www.sei.cmu.edu/publications/documents/92.reports/92.tr.021.html

CMU/SEI-92-TR-011, ADA254177
Software Measurement Concepts for Acquisition Program Managers
Rozum, J.

For program managers to effectively manage and control software development, they need to incorporate a measurement process into their decision making and reporting process. Measurement costs money, but it can also save money through early problem detection and objective clarification of critical software development issues. This report provides some basic concepts that program managers can use to help integrate measurement into the process for managing software development. It also provides an initial set of measures to help address common issues in software intensive acquisitions.

When the Software Acquisition Metrics Working Group first met in 1989, only a few reports existed on the subject of how program managers could use software measurement; now, other reports have been written. The goal of this report is not to compete with those reports, but to use them as starting points for expansion. This report should be viewed not as a standard, but as containing guidelines and advice for program officers and managers starting to use software measurement in their own organizations.

http://www.sei.cmu.edu/publications/documents/92.reports/92.tr.011.html

CMU/SEI-92-TR-019, ADA258305
Software Measurement for DoD Systems: Recommendations for Initial Core Measures
Carleton, A.; Park, R.; Goethert, B.; Florac, A.; Bailey, E.; & Pfleeger, S.

This report presents our recommendations for a basic set of software measures that Department of Defense (DoD) organizations can use to help plan and manage the acquisition, development, and support of software systems. These recommendations are based on work that was initiated by the Software Metrics Definition Working Group and subsequently extended by the SEI to support the DoD Software Action Plan. The central theme is the use of checklists to create and record structured measurement descriptions and reporting specifications. These checklists provide a mechanism for obtaining consistent measures from project to project and for communicating unambiguous measurement results.

http://www.sei.cmu.edu/publications/documents/92.reports/92.tr.019.html

CMU/SEI-92-TR-025, ADA257238
Software Measures and the Capability Maturity Model®
Baumert, J. & McWhinney, M.

This document describes a set of software measures that are compatible with the measurement practices described in the Capability Maturity Model® for Software. These measures, in the form of software indicators, cover thirteen different categories that include progress, effort, cost, and quality. Each indicator category contains example figures which illustrate behavior that may occur on a project. The text provides users with tips on how to use these figures or similar ones on their projects. Project software managers and software engineering process groups can use these indicators during the software development life cycle to gain insight into the software development process and software process improvement activities. The indicators chosen have been successfully used on projects in the software industry.

http://www.sei.cmu.edu/publications/documents/92.reports/92.tr.025.html

CMU/SEI-92-TR-022, ADA258556
Software Quality Measurement: A Framework for Counting Problems and Defects
Florac, W.

This report presents mechanisms for describing and specifying two software measures-software problems and defects-used to understand and predict software product quality and software process efficacy. We propose a framework that integrates and gives structure to the discovery, reporting, and measurement of software problems and defects found by the primary problem and defect finding activities. Based on the framework, we identify and organize measurable attributes common to these activities. We show how to use the attributes with checklists and supporting forms to communicate the definitions and specifications for problem and defect measurements. We illustrate how the checklist and supporting forms can be used to reduce the misunderstanding of measurement results and can be applied to address the information needs of different users.

http://www.sei.cmu.edu/publications/documents/92.reports/92.tr.022.html

CMU/SEI-92-TR-004, ADA258465
Software Process Development and Enactment: Concepts and Definitions
Feiler, P. & Humphrey, W.

The scientific treatment of the software process is relatively new and, as with any new field, the initial terminology is often confusing. When terms can have a diversity of meanings, technical communication is more difficult and technological progress is constrained. This paper defines a core set of concepts about the software process. These concepts are intended to facilitate communications and to provide a framework for further definitions. The definitions focus on essential concepts; however, they do not represent a comprehensive glossary of common software process terms. Following an initial overview, this paper outlines the basic process concepts which underlie the definitions. The definitions are then grouped in four sets: a framework for process definition, an engineering of process, an enactment of process, and process properties. This is followed by illustrations of the use of these concepts in several domains. The paper concludes with some observations on the definition process.

http://www.sei.cmu.edu/publications/documents/92.reports/92.tr.004.html

CMU/SEI-92-TR-020, ADA258304
Software Size Measurement: A Framework for Counting Source Statements
Park, R.

This report presents guidelines for defining, recording, and reporting two frequently used measures of software size- physical source lines and logical source statements. We propose a general framework for constructing size definitions and use it to derive operational methods for reducing misunderstandings in measurement results. We show how the methods can be applied to address the information needs of different users while maintaining a common definition of software size.

http://www.sei.cmu.edu/publications/documents/92.reports/92.tr.020.html

[2007] [2006] [2005] [2004] [2003] [2002] [2001] [2000] [1999] [1998] [1997] [1996] [1995] [1994] [1993] [1992] [1991] [1990] [1989] [1988] [1987] [1986] [PDF]