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]
1994 Reports
Educational Materials
CMU/SEI-94-EM-010,
ADA278536
Lecture Notes on Requirements Elicitation
Raghavan, S.; Zelesnik, G.; & Ford, G.
Requirements elicitation is the first of the four steps in software requirements engineering (the others being analysis, specification, and validation). Software engineers use several elicitation techniques. To facilitate teaching these techniques, materials are provided to support an introductory lecture and four lectures on specific techniques: joint application design, brainstorming, interviewing, and the PIECES framework. A role-playing exercise is provided that allows students to experience each of the techniques. Information for instructors includes educational objectives, pedagogical considerations, additional exercises, and a bibliography.
http://www.sei.cmu.edu/publications/documents/ems/94.em.010.html
CMU/SEI-94-EM-011,
ADA286083
Rate Monotonic Analysis for Real-Time Systems: Instructor's Guide
Ravenel, R. & Obenza, R.
This educational materials package has been developed for instructors of software engineering and, more specifically, real-time systems. This package will help instructors teach rate monotonic analysis (RMA) to graduate and undergraduate software, computer, and electrical engineering students. The package can also be used to teach RMA to continuing education students. The presentation materials and exercises included have been used by Ruth Ravenel in both graduate and undergraduate courses.
These educational materials are intended to be used in conjunction with the videotape, An Introduction to Rate Monotonic Analysis, from SEI Technology Series. (For instructors who have not already obtained the videotape from the SEI, an order form is included in this package.)
http://www.sei.cmu.edu/publications/documents/ems/94.em.011.html
Handbooks
CMU/SEI-94-HB-005,
ADA296 788
Description of the Systems Engineering Capability Maturity Model® Appraisal Method, Version 1.0, A
The purpose of this document is to summarize the major elements of the Systems Engineering Capability Maturity Model® (SE-CMM®) appraisal method (SAM). (SAM) is a method for using the SE-CMM to benchmark, or otherwise appraise, the process capability of an organization's or enterprise's systems engineering function. The SE-CMM itself is described in SECMM-94-04/CMM-SEI-94-HB-04 [SECMM]. This document describes each step of an SE-CMM appraisal and provides guidance for the preparation and conduct of an appraisal. It also contains background and context information about the appraisal method.
http://www.sei.cmu.edu/publications/documents/94.reports/94.hb.005.html
CMU/SEI-94-HB-002,
ADA286082
Software Capability Evaluation (SCE) Version 2.0 Team Members' Guide
Software Capability Evaluation (SCE) is a method for independently evaluating the software process of an organization to gain insight into its software development capability. The method is defined in the report "Software Capability Evaluation Version 2.0 Method Description."
This document is intended for use by members of teams that will be conducting an SCE. The guide provides detailed step-by-step instructions and heuristic information to assist an SCE team in preparing for and conducting an evaluation.
CMU/SEI-94-HB-001,
ADA285595
Software Process Framework for the SEI Capability Maturity Model,® A
Olson, T.; Reizer, N; & Over, J.
The Software Process Framework (SPF) is a document that provides information contained in the Software Engineering Institute's Capability Maturity Model® (CMM®) for Software V. 1. 1 in a format suitable for process definition and improvement. The SPF allows users to determine if their organization's software process documentation is consistent with the recommendations made by the CMM. When organizational software process documentation is found to be inconsistent with the CMM, the SPF provides the ability to make informed decisions regarding the applicability of specific CMM recommendations.
http://www.sei.cmu.edu/publications/documents/94.reports/94.hb.001.html
CMU/SEI-94-HB-004,
ADA293345
Systems Engineering Capability Maturity Model,® Version 1.0, A
Bate, R.; Garcia, S.; Armitage, J.; Cusick, K.; Jones, R.; Kuhn, D.; Minnich, I.;
Pierson, H.; Powell, T.; & Reichner, A.
The Systems Engineering Capability Maturity Model® (SE-CMM®) describes the essential elements of an organization's systems engineering process that must exist to ensure good systems engineering. It does not specify a particular process of sequence. In addition, the SE-CMM provides a reference for comparing actual systems engineering practices against these essential elements. The SE-CMM Model Description provides an overall description of the principles and architecture upon which the SE-CMM is based, an executive overview of the model, suggestions for appropriate use of the model, the practices included in the model, and a description of the attributes of the model. It also includes the requirements used to develop the model.
http://www.sei.cmu.edu/publications/documents/94.reports/94.hb.004.html
Special Reports
CMU/SEI-94-SR-001,
ADA285070
Introduction to Team Risk Management (Version 1.0), An
Higuera, R.; Gluch, D.; Dorofee, A.; Murphy, L.; Walker, A.; & Williams, C.
(Version 1.0) Team Risk Management defines the organizational structure and operational activities for managing risks throughout all phases of the life-cycle of a software-dependent development program such that all individuals within the organizations, groups, departments, and agencies directly involved in the program are participating team members. Through the adoption of team risk management, the government and contractor are provided with processes, methods, and tools that enable both organizations, individually and jointly, to be increasingly anticipatory in decision-making processes. This report introduces the team risk management approach for managing risks within a software-dependent development program.
http://www.sei.cmu.edu/publications/documents/94.reports/94.sr.001.html
CMU/SEI-94-SR-007,
ADA285073
Maturity Questionnaire
Zubrow, D.; Hayes, W.; Siegel, J.; & Goldenson, D.
This package contains a copy of the software process maturity questionnaire. It is intended for those interested in performing and learning about software process appraisals. This version differs in several important ways from its predecessor, A Method for Assessing the Software Capability of Contractors (CMU/SEI-87-TR-023). The most important difference is that this questionnaire is not an appraisal method itself; rather, it is one component that is uses in different appraisal methods.
http://www.sei.cmu.edu/publications/documents/94.reports/94.sr.007.html
CMU/SEI-94-SR-006,
ADA283367
Second Dependable Software Technology Exchange
Weinstock, C. & Heimerdinger, W.
On March 24 and 25, 1994, the Open Attribute Engineering Project hosted the Second Dependable Software Technology Exchange. The exchange, sponsored by the Air Force Phillips Laboratories, the Office of Naval Research, and the Air Force Space and Missile Systems Center, brought together researchers and system developers, providing an opportunity for the researchers to learn the needs of the developers and for the developers to learn about techniques being investigated by the researchers. This report summarizes what transpired at the meeting.
http://www.sei.cmu.edu/publications/documents/94.reports/94.sr.006.html
CMU/SEI-94-SR-009,
ADA286506
Software Acquisition: A Comparison of DoD and Commercial Practices
Ferguson, J. & DeRiso, M.
This paper will compare best commercial practice with the current Department of Defense (DoD) processes for acquiring software and to recommend some steps that can be taken to streamline DoD software acquisitions to minimize overall life-cycle costs.
http://www.sei.cmu.edu/publications/documents/94.reports/94.sr.009.html
CMU/SEI-94-SR-003,
ADA2800915
Software Cost and Schedule Estimating: A Process Improvement Initiative
Park, R.; Goethert, W.; & Webb, J.
This report describes efforts that have been initiated by the Software Engineering Institute to improve the practice of software cost and schedule estimating. These efforts involve support and participation from both industry and government. They are motivated by the capability maturity model, which identified the key roles estimating and cost management play in establishing repeatable software processes. Products from the initiative will include templates, criteria, and guidelines for establishing defined estimating processes, training materials, and examples for teaching good estimating practice, and evaluations of the abilities of contemporary cost models to meet today's estimating needs.
http://www.sei.cmu.edu/publications/documents/94.reports/94.sr.003.html
CMU/SEI-94-SR-005,
ADA283987
Team Risk Management: A New Model for Customer-Supplier Relationships
Higuera, R.; Dorofee, A.; Walker, J.; & Williams, R.
This report will familiarize you with the concepts of Team Risk management by providing a description of the overall process that engages both the customer and supplier in a cooperative framework using explicit methods to manage project risks.
http://www.sei.cmu.edu/publications/documents/94.reports/94.sr.005.html
Technical Reports
Technical Reports
CMU/SEI-94-TR-009,
ADA286093
Artificial Intelligence (AI) and ADA: Integrating AI with Mainstream Software Engineering
Diaz-Herrera, J.
In this report we discuss in detail pragmatic problems posed by the integration of AI with conventional software engineering, and within the framework of current ADA technology. A major objective of this work has been to begin to bridge the gap between the ADA and AI software cultures. The report summarizes survey results from the Association for Computing Machinery (ACM) Special Interest Group for ADA (SIGADA) AI Working Group (AIWG), highlighting lessons learned and sample applications. An interesting observation is that a large percentage of AI code is procedural by nature and that better productivity rates are achieved by using ADA; also, efficiency is much better when compared to traditional AI languages. Although we show favorable results on the use of ADA technology for the implementation of AI software, a total integration remains difficult at the conceptual level. There are some impediments to a completely satisfactory solution, but only a few restrictions are more intrinsically related to the current ADA standard (ADA83); these, however, are being dealt with in the next revision known as ADA9X.
http://www.sei.cmu.edu/publications/documents/94.reports/94.tr.009.html
CMU/SEI-94-TR-013,
ADA283848
Benefits of CMM-Based Software Process Improvement: Initial Results
Herbsleb, J.; Carleton, A.; Rozum, J.; Siegel, J.; & Zubrow, D.
Data from 13 organizations were collected and analyzed to obtain information on the results of CMM-based software process improvement efforts. We report the cost and business value of improvement efforts, as well as the yearly improvement in productivity, early defect direction, time to market, and post-release defect reports. Improvement efforts and results in five organizations are reported in more depth in case studies. In addition, technical issues that we confronted as we tried to measure the results of software process improvement are discussed. We end with conclusions about the results of SPI efforts.
http://www.sei.cmu.edu/publications/documents/94.reports/94.tr.013.html
CMU/SEI-94-TR-015,
ADA311066
Beyond Objects: A Software Design Paradigm Based on Process Control
Shaw, M.
A standard demonstration problem in object-oriented programming is the design of an automobile cruise control. This design exercise demonstrates object-oriented techniques well, but it does not ask whether the object-oriented paradigm is the best one for the task. Here, we examine the alternative view that cruise control is essentially a control problem. We present a new software organization paradigm motivated by process control loops. The control view leads us to an architecture that is dominated by analysis of a classical feedback loop rather than by the identification of discrete stateful components to treat as objects. The change in architectural model calls attention to important questions about the cruise control task that aren't addressed in an object-oriented design.
http://www.sei.cmu.edu/publications/documents/94.reports/94.tr.015.html
CMU/SEI-94-TR-023,
ADA292215
Characteristics of Higher Level Languages for Software Architecture
Shaw, M. & Garlan, D.
As the size and complexity of software systems increases, the design and specification of overall system structure- or software architecture-emerges as a central concern. Architectural issues include the gross organization of the system, protocols for communication and data access, assignment of functionality to design elements, and selection among design alternatives.
Currently, system designers have at their disposal two primary ways of defining software architecture: they can use the modularization facilities of existing programming languages and module inter connection languages; or they can describe their designs using informal diagrams and idiomatic phrases (such as "client-server organization").
In this paper, we explain why neither alternative is adequate. We consider the nature of architectural description as it is performed informally by systems designers. Then we show that regularities in these descriptions can form the basis for architectural description languages. Next, we identify specific properties that such languages should have. Finally, we illustrate how current notations fail to satisfy those properties.
http://www.sei.cmu.edu/publications/documents/94.reports/94.tr.023.html
CMU/SEI-94-TR-012,
ADA290697
Comparison of ISO 9001 and the Capability Maturity Model® for Software, A
Paulk, M.
The Capability Maturity Model® for Software (CMM®), developed by the Software Engineering Institute, and the ISO 9000 series of standards, developed by the International Standards Organization, share a common concern with quality and process management. The two are driven by similar concerns and intuitively correlated. The purpose of this report is to contrast the CMM and ISO 9001, showing both their differences and their similarities. The results of the analysis indicate that, although an ISO 9001-compliant organization would not necessarily satisfy all of the level 2 key process areas, it would satisfy most of the level 2 goals and many level 3 goals. Because there are practices in the CMM that are not addressed in ISO 9000, it is possible for a level 1 organization to receive 9001 registration; similarly, there are areas addressed by ISO 9001 that are not addressed in the CMM. A level 3 organization would have little difficulty in obtaining ISO 9001 certification, and a level 2 organization would have significant advantages in obtaining certification.
http://www.sei.cmu.edu/publications/documents/94.reports/94.tr.012.html
CMU/SEI-94-TR-014,
ADA284922
Construct for Describing Software Development Risks, A
Gluch, D.
This report establishes a representation of software risk wherein the risks associated with software-dependent development programs are defined as distinct, manageable risk entities. The risk entities and their descriptive statements of risk are based upon a Condition-Transition-Consequence (CTC) construct. The CTC construct arises out of a systems representation, where time and value are identified as fundamental to the concept of risk. The CTC construct is also shown to provide a common representation for both program risks and program tasks and to fit into a heuristic framework for identifying risks within software-dependent development programs. Examples of risks are used to demonstrate that the approach facilitates the management of risk as an integral part of routine program management.
http://www.sei.cmu.edu/publications/documents/94.reports/94.tr.014.html
CMU/SEI-94-TR-016,
ADA296801
DoD Software Measurement Pilot: Applying the SEI Core Measures, A
Rozum, J. & Florac, W.
A pilot effort was initiated by the U.S. Department of Defense (DoD) and led by the Defense Information Systems Agency (DISA) to assess the issues and effort involved in implementing a software measurement program across multiple sites and projects. The pilot was conducted involving multiple DoD organizations and projects from varying application domains. The objectives were to assess the ability of an organization to assess and use the core measures, determine the appropriate analysis and reporting of the measurement information at an organization and corporate level, determine the applicability of common definitions of the SEI core software measures, evaluate the effectiveness of the SEI core measure checklists for development and maintenance, and develop metrics program guidelines for DoD implementation. This technical report discusses the observations and lessons learned from the pilot effort and makes recommendations regarding software measurement implementation across a large organization.
http://www.sei.cmu.edu/publications/documents/94.reports/94.tr.016.html
CMU/SEI-94-TR-020,
ADA293020
Experience with a Course on Architectures for Software Systems, Part II: Educational Materials
Shaw, M.; Garlan, D.; & Gaimes, J.
This report contains the materials used by the instructors to teach the course CS 15-775: Architectures for Software Systems in the Spring of 1994 in the School of Computer Science at Carnegie Mellon University. The materials include the lecture slides, questions (with answers) on readings, and homework assignments (with sample solutions.)
http://www.sei.cmu.edu/publications/documents/94.reports/94.tr.020.html
CMU/SEI-94-TR-003,
ADA28765
Exploring Hypermedia Information Services for Disseminating Software Engineering Information
Hefley, W.
This report describes the accomplishments of a pilot hypermedia information service embodying the conceptual definition of a pilot information base developed by the Software Engineering Institute (SEI) in support of the Advanced Research Projects Agency (ARPA) Software and Intelligent Systems Technology Office (SISTO). This pilot effort was conducted in support of the Technology Cost-Benefit Analysis tasks within TO&P 2-151, Software Engineering Technology Transition for Director, Defense Research and Engineering (DDR&E) and ARPA. This report also describes the intended uses and user populations of the proposed information base, design issues that influenced the structure and contents of the information base, a proposed information model consisting of information content and linkages, the pilot information base including the technology selected for the initial pilot effort and the pilot capability, lessons learned from the pilot effort, and future plans relating to the information base efforts. Key to these pilot efforts was the development of a set of proposed information structures for an information base on software engineering. These hypermedia-based information structures can be presented across the Internet and displayed on local workstations using client/server technologies, such as World Wide Web (WWW) and NCSA Mosaic (produced by the National Center for Supercomputing Applications).
This work to date has accomplished four goals. First, the objectives of the pilot effort have been met. An information base containing software engineering information that provides value to ARPA program managers has been demonstrated, and a work plan has been generated to expand from the pilot to an operational system. Second, the SEI has demonstrated a capability for effectively using the WWW, which is certain to be a critical part of the information highway for years to come. Third, techniques to enhance developers' productivity have been identified and demonstrated. Preparation of online information can be aided by templates. Delivery of online information can be enhanced through study of actual users' navigational and usage patterns. Fourth, the SEI has established a "magnetic platform" as the facilities demonstrable at the SEI can be used as a starting point for developing new technology transition capabilities.
http://www.sei.cmu.edu/publications/documents/94.reports/94.tr.003.html
CMU/SEI-94-TR-004,
ADA278596
Interim Profile Development and Trial of a Method to Rapidly Measure Software Engineering Maturity Status
Whitney, R.; Nawrocki, E.; Hayes, W.; & Siegel, J.
Development of an Instant Profile (IP) method was driven by a business need to rapidly measure an organization's software engineering process maturity between organizational software process assessments (SPAs). This document provides information about the process used to develop the method and a description of the method to software engineering process group (SEPG) members and practitioners responsible for diagnosing software process maturity. This document also addresses the next steps in the further development and use of the instant profile method.
http://www.sei.cmu.edu/publications/documents/94.reports/94.tr.004.html
CMU/SEI-94-TR-021,
ADA288963
Introduction to Software Architecture, An
Garlan, D. & Shaw, M.
As the size of software systems increases, the algorithms and data structures of the computation no longer constitute the major design problems. When systems are constructed from many components, the organization of the overall system-the software architecture-presents a new set of design problems. This level of design has been addressed in a number of ways, including informal diagrams and descriptive terms, module interconnection languages, templates, and frameworks for systems that serve the needs of specific domains, and formal models of component integration mechanisms. In this paper, we provide an introduction to the emerging field of software architecture. We begin by considering a number of common architectural styles upon which many systems are currently based, and how different styles can be combined in a single design. Then, we present six case studies to illustrate how architectural representations can improve our understanding of complex software systems. Finally, we survey some of the outstanding problems in the field, and consider a few of the promising research directions.
http://www.sei.cmu.edu/publications/documents/94.reports/94.tr.021.html
CMU/SEI-94-TR-008,
ADA283747
Mapping a Domain Model and Architecture to a Generic Design
Peterson, A. & Stanley, J.
In contrast to the number of reports on domain analysis, little work has been done in describing the utilization of domain analysis results in the development of generic designs for building applications in a domain. This report describes a process for mapping domain information in Feature-Oriented Domain Analysis (FODA) into a generic design for a domain. The design includes supporting code components that conform to the Object Connection Architecture (OCA), a model for structuring software systems. A process for the use of the design in implementing applications is included. The processes and products described herein augment the final phase of domain analysis (or engineering) described in the original FODA report. This report also documents the continuing work of applying FODA to the movement control domain. The design and ADA code examples for the domain used in the document are from prototype software, created in part to test the processes presented.
http://www.sei.cmu.edu/publications/documents/94.reports/94.tr.008.html
CMU/SEI-94-TR-007,
ADA280916
Practical Guide to the Technology and Adoption of Software Process Automation, A
Christie, A.
Process automation provides a means to integrate people in a software development organization with the development process and the tools supporting that development. For many reasons, this new technology has the potential to significantly improve software quality and software development productivity. As yet, however, there is little practical experience in its day-to-day use. The main goal of this report is thus to provide information for organizations that are considering its adoption. For these reasons, the report aims to identify how process automation relates to both process improvement and CASE tools, to review in some detail two of the major commercial process automation products, and to address relevant organizational adoption issues. It is hoped that the report will help bridge the gap between those whose focus is software process improvement and those whose focus is software technology.
http://www.sei.cmu.edu/publications/documents/94.reports/94.tr.007.html
CMU/SEI-94-TR-002,
ADA281026
Procedure Calls Are the Assembly Language of Software Interconnection: Connectors Deserve First-Class Status
Shaw, M.
Software designers compose systems from components written in some programming language. They regularly describe systems using abstract patterns and sophisticated relations among components. However, the configuration tools at their disposal restrict them to composition mechanisms directly supported by the programming language. To remedy this lack of expressiveness, we must elevate the relations among components to first-class entities of the system, entitled to their own specifications and abstractions.
http://www.sei.cmu.edu/publications/documents/94.reports/94.tr.002.html
CMU/SEI-94-TR-024,
ADA302689
Process Tailoring and the Software Capability Maturity Model®
Ginsberg, M. & Quinn, L.
The Software Capability Maturity Model® (SW-CMM®) is serving as the foundation for a major portion of the process improvement being undertaken in the software industry. It is composed of two volumes: the Capability Maturity Model for Software and the Key Practices of the Capability Maturity Model. The key practices of the SW-CMM are expressed in terms that reflect normal practices of organizations that work on large, government contracts. There is, however, a significant population of software-producing and acquiring organizations, operating in different environments, for which the key practices require significant interpretation and/or tailoring, prior to application. This report presents a tailoring framework that identifies process artifacts, tailoring processes, and their relationships to project artifacts, and explores the nature of various kinds of tailoring used in the definition and development of software process descriptions. Techniques appropriate to each type of tailoring are then discussed. The general approach utilizes and builds upon the Software Process Framework, whose purpose is to provide guidance for designing, analyzing, and reviewing software processes for consistency with the SW-CMM.
http://www.sei.cmu.edu/publications/documents/94.reports/94.tr.024.html
CMU/SEI-94-TR-011,
ADA280940
Progress Report on Undergraduate Software Engineering Education, A
Ford, G.
The current status of undergraduate software engineering education in United States universities is summarized, including descriptions of programs at eleven schools. Possible scenarios for the further evolution of undergraduate software engineering programs are described, based on observations of the evolution of computer science and computer engineering programs. Recent and ongoing activities of the Computer Society of the Institute of Electrical and Electronics Engineers (IEEE) and the Association for Computing Machinery (ACM) regarding the establishment of the profession of software engineering are described, including the expected implications for undergraduate software engineering education.
http://www.sei.cmu.edu/publications/documents/94.reports/94.tr.011.html
CMU/SEI-94-TR-026,
ADA303272
Relationships Between the Systems Engineering Capability Maturity Model® and Other Products, Version 1.0
The SE-CMM is a document that describes characteristics, both domain and process-management focused, of systems engineering processes that contribute to successful product development. From the beginning of the effort, users of the SE-CMM have requested information on how SE-CMM practices relate to other products. This document is an initial effort at identifying and characterizing these relationships.
http://www.sei.cmu.edu/publications/documents/94.reports/94.tr.026.html
CMU/SEI-94-TR-017,
ADA289928
Replacing the Message Service Component in an Integration Framework
Zarrella, P. & Brown, A.
In an on-going set of commercial off-the-shelf (COTS) tool integration experiments being conducted by the CASE Environments Project, we have integrated a set of CASE tools using a combination of data integration mechanisms (PCTE Object Management System (QMS) and UNIX file system) and control integration mechanisms (Broadcast Message Server (BMS) of HP SoftBench). One of the key issues addressed in our work is the extent to which the integration of CASE tools can be independent of particular integration framework technology products.
This report describes a task to examine interoperability aspects of the control integration component of the integration framework. The major conclusion from our work is that it is possible to integrate CASE tools using a message-passing approach that is independent of the integration framework product used. This report describes the activities an organization must undertake to integrate CASE tools in order to ensure this interoperation of message-passing integration products. The report also includes a set of lessons learned concerning the experiments we carried out.
http://www.sei.cmu.edu/publications/documents/94.reports/94.tr.017.html
CMU/SEI-94-TR-005,
ADA278635
Software Capability Evaluation (SCE) Version 2.0 Implementation Guide
Software Capability Evaluation (SCE) offers a means to evaluate an organization's software process capability-that is, how well an organization manages the process it used to create software. SCE provides a way to compare an offeror's software capability against a predefined standard. This document is an implementation guide: it is intended as a set of practical information which program managers can use to guide them through the process of using SCE in an acquisition.
http://www.sei.cmu.edu/publications/documents/94.reports/94.tr.005.html
CMU/SEI-94-TR-006,
ADA280943
Software Capability Evaluation Version 2.0 Method Description
This report describes Version 2.0 of the Software Capability Evaluation (SCE) Method, as taught at the Software Engineering Institute (SEI) from fourth quarter 2993. This version of the SCE Method is based on the Capability Maturity Model® defined in Capability Maturity Model for Software, Version 1.1. The document includes an overview of the SCE Method and its evolution, a detailed description of characteristics of the method and their implications for the use of the method. This document provides a new baseline for future evolution of the SCE Method.
http://www.sei.cmu.edu/publications/documents/94.reports/94.tr.006.html
CMU/SEI-94-TR-022,
ADA289912
Software Process Improvement in the NASA Software Engineering Laboratory
McGarry, F.; Pajerski, R.; Page, G.; Waligora, S.; Basili, V.; & Zelkowitz, M.
The Software Engineering Laboratory (SEL) was established in 1976 for the purpose of studying and measuring software processes with the intent of identifying improvements that could be applied to the production of ground support software within the Flight Dynamics Division (FDD) at the National Aeronautics and Space Administration (NASA)/Goddard Space Flight Center (GSFC). The SEL has three member organizations: NASA/GSFC, the University of Maryland, and Computer Sciences Corporation. The concept of process improvement within the SEL focuses on the continual understanding of both process and product as well as goal-driven experimentation and analysis of process change within a production environment.
http://www.sei.cmu.edu/publications/documents/94.reports/94.tr.022.html
CMU/SEI-94-TR-018,
ADA288708
Spinning a Web: Publishing the SEI Software Configuration Management Research on the World Wide Web
Huff, C.
Configuration Management research has been performed by members of the CASE Environments Project over the course of the past five years. This report describes the contents of the configuration management research materials that have been published on the SEI World Wide Web (WWW) Server. Primary Web Structures and methods for accessing information on the Web are described. A summary of the problems and challenges encountered and the Web publishing techniques employed in this process are discussed.
http://www.sei.cmu.edu/publications/documents/94.reports/94.tr.018.html
CMU/SEI-94-TR-010,
ADA283827
Toward Deriving Software Architectures from Quality Attributes
Kazman, R. & Bass, L.
A method for deriving software architectures from a consideration of the non-functional qualities of the system is presented. The method is based on identifying a set of six "unit operations" and using those operations to partition the functionality of the system. These unit operations were derived from the literature and from expert practice. The relationship between the unit operations and a set of eight non-functional qualities is explored. Evidence is provided for the validity of the method by using it to derive six well-known architectures from the areas of user interface software and compiler constructions.
http://www.sei.cmu.edu/publications/documents/94.reports/94.tr.010.html
[2007] [2006] [2005] [2004] [2003] [2002] [2001] [2000] [1999] [1998] [1997] [1996] [1995] [1994] [1993] [1992] [1991] [1990] [1989] [1988] [1987] [1986] [PDF]