Back to FAQ

Ada Reports & Papers
(Part 8)

[Part 1] [Part 2] [Part 3] [Part 4] [Part 5] [Part 6] [Part 7] [Part 8] [Part 9]


Ada 9X Project Report, Ada 9X Requirements

Abstract: This document specifies needs that are considered to be the appropriate focus of the Ada 9X revision effort and identifies revision requirements that are to be addressed by the Mapping/Revision Team. The requirements as stated in this document are intended to enhance Ada's usability and strengthen its position in the marketplace.

Author: Anderson, Christine M.; et al.

Publisher: Office of the Undersecretary of Defense for Acquisition

Sponsoring Organization: Ada Joint Program Office

Producing Organization: Ada 9X Project Office

Publication Date: 12/90


Draft Ada 9X Project Report - Ada 9X Requirements Rationale

Abstract: This document, edition April 1991, shows how each Revision Request (RR) and Ada commentary (AI) is related to the requirements given in the Ada 9X Requirements document [8]. The association is given in three ways: in order by requirement number, in order by RR and AI number, and in order by keywords appearing in the title of an AI or RR. This document also discusses some alternatives that were considered during the requirements definition phase and in some cases amplifies the discussion presented in the requirements document itself. In developing these comments on the requirements, the authors were helped by comments on the requirements document that were submitted by members of the canvass group established for voting on the proposed revision to the standard.

Author: Ada 9x Project Office

Publisher: Software Engineering Institute, Carnegie Mellon University

Sponsoring Organization: Ada Joint Program Office

Producing Organization: Ada 9X Project Office

Publication Date: 4/91


Ada 9X Requirements Rationale

Abstract: This document, edition May 1991, shows how each Revision Request (RR) and Ada commentary (AI) is related to the requirements given in the Ada 9X Requirements document. The association is given in three ways: in order by requirement number, in order by RR and AI number, and in order by keywords appearing in the title of an AI or RR. This document also discusses some alternatives that were considered during the requirements definition phase and in some cases amplifies the discussion presented in the requirements document itself. In developing these comments on the requirements, the authors were helped by comments on the requirements document that were submitted by members of the canvass group established for voting on the proposed revision to the standard.

Author: Goodenough, J.B, et. al.

Publisher: Carnegie Mellon University

Sponsoring Organization: ADA 9x Project Office

Publication Date: 5/91


Ada 9X Project Report (Draft), Ada 9X Mapping Document, Volume I, Mapping Rationale

Abstract: Volume I, the Mapping Rationale, addresses why specific language changes are being recommended for satisfying Ada 9X Requirements (See Ada 9X Requirements, DoD, December 1990). This release of the Mapping Document (March 1992) revises the Specialized Needs Annexes (including additional rationale) and provides an update to the rationale. Furthermore, this edition has been revised to reflect both public comments received on the previous version and the changes to the core language as described in Volume II, the Mapping Specification (December 1991). Volume I now contains the section-by-section rationale for Chapters 1 through 14 of the Mapping Specification (Appendix S) and an analysis of Ada 9X upward compatibility/consistency (Appendix U).

Author: Carlson, W. et. al.

Publisher: Intermetrics, Inc.

Sponsoring Organization: Ada 9x Project Office

Producing Organization: Ada 9x Mapping/Revision Team, Intermetrics, Inc.

Publication Date: 3/92


Ada 9X Project Report (Draft), Ada 9X Mapping Document, Volume I, Mapping Rationale

Abstract: Volume I, the Mapping Rationale, provides a discussion of why specific language changes are being recommended for satisfying Ada 9X Requirements. Still in draft form, it represents a snapshot of work-in-progress. Furthermore, it offers a distinct trend of reduction of the overall scope of the revision between the March 1991 release and this one.

Author: Carlson, W. et.al.

Publisher: Intermetrics, Inc.

Sponsoring Organization: Ada 9X Project Office

Producing Organization: Ada 9x Mapping/Revision Team, Intermetrics, Inc.

Publication Date: 8/91


Ada 9X Project Report (Draft), Ada 9X Mapping Document, Volume II, Mapping Specification (abridged) Annexes

Abstract: This document contains six annexes in reference to the March 1992 versions of Volumes I and II of the Ada 9X Mapping Document. The annexes, once contained in the Specialized Needs Annex, now appear as six individualized annexes in this document. The six individualized annexes are: Systems Programming, Real-Time Systems, Distributed Systems, Information Systems, Saftey and Security, and Numerics. In addition to presenting information on these topics, the document offers the rationale for them.

Author: Carlson, W. et. al.

Publisher: Intermetrics, Inc.

Sponsoring Organization: Ada 9x Project Office

Producing Organization: Intermetrics, Inc.

Publication Date: 3/92


Ada 9X Project Report (Draft), Ada 9X Mapping Document, Volume II, Mapping Specification

Abstract: Volume II of the Ada 9x Mapping Document, the Mapping Specification, provides a detailed description of the key language changes that are being recommended, along with a traceability index between proposed changes and requirements. It reflects comments based on the August 1991 version and has been refined to facilitate usability by application developers and implementability by compiler vendors.

Author: Carlson, W. et.al.

Publisher: Intermetrics, Inc.

Sponsoring Organization: Ada 9x Project Office

Producing Organization: Intermetrics, Inc.

Publication Date: 12/91


Ada 9X Project Report (Draft), Ada 9X Mapping Document, Volume II, Mapping Specification

Abstract: Volume II of the Ada 9x Mapping Document, the Mapping Specification, provides a detailed description of the key language changes that are being recommended, along with a traceability index between proposed changes and requirements. Still in draft form, it represents a snapshot of work-in-progress.

Author: Carlson, W.

Publisher: Intermetrics, Inc.

Sponsoring Organization: ADA 9X Project Office

Producing Organization: Intermetrics, Inc.

Publication Date: 8/91


Ada 9X Project Plan, Version 2

Abstract: The purpose of the Ada 9X Project Plan is to provide a detailed and organized approach to the ANSI/MIL-STD-1815A revision process. In addition to an overview of the approach to the revision process, it provides the management structure for the Project and identifies specific tasks for various groups and organizations in support of the Project. It also presents a description of the deliverables resulting from the Project, a work breakdown structure that delineates all of the activities to be accomplished, and a master schedule.

Author: Anderson, C.M.

Publisher: Office of the Under Secretary of Defense for Acquisition

Sponsoring Organization: AJPO - Ada Joint Program Office

Publication Date: 2/90


Ada 9X Project Report, Transition Plan

Abstract: The purpose of this document is to specify a plan for transitioning to Ada 9X (ANSI/MIL-STD-1815B). This plan describes activities to be implemented by the Ada 9X Project Office and the Ada Joint Program Office, as well as transition guidelines for consideration by policymakers. The overall goal is to expedite the realization of Ada 9CX benefits, while minimizing disruption to the Ada infrastructure (e.g., programs, programmers, tools, vendors, training, educators, etc.)

Author: Anderson, C.M.

Publisher: Office of the Under Secretary of Defense for Acquisition

Producing Organization: Ada 9X Project Office

Publication Date: 5/92


Ada 9X Project Report, User/Implementer Report, AETECH/RR Software, Ada 9x Experiences in Information Systems Applications on the i386 Architecture

Abstract: This report offers a Manager's Report, User's Report, and Implementers Report regarding Ada 9X experiences in information systems applications on the i386 architecture. It also presents 15 appendices: Hierarchical Libraries, Primitive Visibility, General Access Types, Interface Pragmas, Generics, Object-Oriented Programming Features, Protected Records, Test Programs, Size and Compile Times, Primitive Visibility, Analysis of Relative Importance, Modification of X-Windows Binding, X-Windows Binding with Pragma IMPORT, X-Windows Toolkit Proof of Fitness, and Athena Extension.

Publisher: Office of the Under Secretary of Defense for Acquisition

Sponsoring Organization: Ada 9X Project Office

Producing Organization: RR Software

Publication Date: 10/92


Ada Compatibility Guide, Version 6.0

Abstract: This guide is aimed at projects currently writing or intending to write Ada applications where enhancement or maintenance is required beyond 1997. Its purpose is to alert such projects to any upward incompatibles between Ada 83 and Ada 95 so that Ada 83 software can be written while avoiding these incompatibilities long before transitioning to Ada 95 is required. A set of guidelines is included for avoiding all but the obscure incompatibilities. The guide describes each of the upward incompatibilities in terms of the language change, a rationale for the change, a description and example of the incompatibility, an indication of how it can be avoided in existing Ada 83 programs, and the possibility of its automatic detection and removal. Many of the proposed incompatibilities will not occur in normal programs--the Ada 83 semantics being known only to the most erudite Ada programmers--so each incompatibility is classified according to how likely a normal Ada 83 program of a reasonable size would contain an occurence of the incompatibility. Incompatibilities are also classified according to whether they cause illegalities at compile-time or different semantics at run-time. This version of the guide corresponds to the International Standard version of the language, published in early 1995.

Author: Taylor, B.

Publisher: Transition Technology Limited

Sponsoring Organization: MoD (PE), CIS (Eng) 31a

Publication Date: 1/95


Ada 9X Compatibility Guide, Version 5.0

Abstract: This guide is aimed at projects currently writing or intending to write Ada applications where enhancement or maintenance is required beyond 1997. Its purpose is to alert such projects to any upward incompatibles between Ada 83 and Ada 95 so that Ada 83 software can be written while avoiding these incompatibilities long before transitioning to Ada 95 is required. A set of guidelines is included for avoiding all but the obscure incompatibilities. The guide describes each of the upward incompatibilities in terms of the language change, a rationale for the change, a description and example of the incompatibility, an indication of how it can be avoided in existing Ada 83 programs, and the possibility of its automatic detection and removal. Many of the proposed incompatibilities will not occur in normal programs--the Ada 83 semantics being known only to the most erudite Ada programmers--so each incompatibility is classified according to how likely a normal Ada 83 program of a reasonable size would contain an occurence of the incompatibility. Incompatibilities are also classified according to whether they cause illegalities at compile-time or different semantics at run-time. This fifth version of the guide has been produced as a result of changes to the proposed language, as specified in the Draft International Standard (Version 5.) of the Ada 9X Refence Manual, for which balloting by members of ISO/IEC JTC1 is about to start. Given the interim nature of the language definition, the list of incompatibilities is necessairly provisional.

Author: Taylor, B.

Publisher: Transition Technology Limited

Sponsoring Organization: MoD (PE), CIS (Eng) 31a

Publication Date: 6/94


Ada 9X Compatibility Guide, Version 4.1

Abstract: This guide is aimed at projects currently writing or intending to write Ada applications where enhancement or maintenance is required beyond 1997. Its purpose is to alert such projects to any upward incompatibles between Ada 83 and Ada 95 so that Ada 83 software can be written while avoiding these incompatibilities long before transitioning to Ada 95 is required. A set of guidelines is included for avoiding all but the obscure incompatibilities. The guide describes each of the upward incompatibilities in terms of the language change, a rationale for the change, a description and example of the incompatibility, an indication of how it can be avoided in existing Ada 83 programs, and the possibility of its automatic detection and removal. Many of the proposed incompatibilities will not occur in normal programs--the Ada 83 semantics being known only to the most erudite Ada programmers--so each incompatibility is classified according to how likely a normal Ada 83 program of a reasonable size would contain an occurence of the incompatibility. Incompatibilities are also classified according to whether they cause illegalities at compile-time or different semantics at run-time. This fourth version of the guide has been produced as a result of changes to the proposed language, as specified in Version 4.0 of the Ada 9X Reference Manual, which has been registered with ISO/IEC JTC1/SC22 as a Committee Draft. Further changes to the language should be expected before JCT1 balloting begins in May 1994. Given the interim nature of the language definition, the list of incompatibilities is necessarily provisional.

Author: Taylor, B.

Publisher: Transition Technology Limited

Sponsoring Organization: MoD (PE), CIS (Eng) 31a

Publication Date: 2/94


Ada 9X Compatibility Guide, Version 2.0

Abstract: This guide is aimed at projects currently writing or intending to write Ada applications where enhancement or maintenance is required beyond 1997. Its purpose is to alert such projects to any upward incompatibles between Ada 83 and Ada 95 so that Ada 83 software can be written while avoiding these incompatibilities long before transitioning to Ada 95 is required. A set of guidelines is included for avoiding all but the obscure incompatibilities. The guide describes each of the upward incompatibilities in terms of the language change, a rationale for the change, a description and example of the incompatibility, an indication of how it can be avoided in existing Ada 83 programs, and the possibility of its automatic detection and removal. Many of the proposed incompatibilities will not occur in normal programs--the Ada 83 semantics being known only to the most erudite Ada programmers--so each incompatibility is classified according to how likely a normal Ada 83 program of a reasonable size would contain an occurence of the incompatibility. Incompatibilities are also classified according to whether they cause illegalities at compile-time or different semantics at run-time. This second version of the guide has been produced as a result of changes to the proposed language, as specified in Version 2.0 of the Ada 9X Reference Manuals. Given the interim nature of the language definition, the list of incompatibilities is necessarily provisional.

Author: Taylor, B.

Publisher: Transition Technology Limited

Sponsoring Organization: MoD (PE), CIS (Eng) 31a

Publication Date: 5/93


Ada 9x Compatibility Guide, Version 1.0

Abstract: This guide is aimed at projects currently writing or intending to write Ada applications where enhancement or maintenance is required after February 1998. Its purpose is to alert such projects to any upward incompatibles between Ada 83 and Ada 9X so that Ada 83 software can be written while avoiding these incompatibilities long before transitioning to Ada 9X is required. The guide describes each of the 32 upward incompatibilities in terms of the language change, a rationale for the change, a description and example of the incompatibility, an indication of how it can be avoided in existing Ada 83 programs, and the possibility of its automatic detection and removal. Many of the proposed incompatibilities will not occur in normal programs--the Ada 83 semantics being known only to the most erudite Ada programmers--so each incompatibility is classified according to how likely a normal Ada 83 program of a reasonable size would contain an occurence of the incompatibility. Incompatibilities are also classified according to whether they cause illegalities at compile-time or different semantics at run-time. Given that the revised reference manual is not due for publication until September 1993 and a new standard will not be in place until November 1993, the list of incompatibilities is necessarily provisional.

Author: Taylor, B.

Publisher: Transition Technology Limited

Sponsoring Organization: MoD (PE), CIS (Eng) 31a

Publication Date: 11/92


Introducing Ada 95

Abstract: This document introduces Ada 9X, the revised standard that increases the flexibility of Ada thus making it applicable to wider domains while retaining the inherent reliability for which Ada has become noted. The enhancements to Ada (such as Object Oriented Programming, Hierarchical Libraries, and Protected Objects) make Ada 9X an outstanding language. In addition to discussing the rationale for the revision to Ada, this document offers the following: it gives the background to the development process, including the capture of the requirements from the existing and future user community; it introduces the highlights of the language in a tutorial style; it gives an overview of the whole language, showing how the new facilities fit into the overall framework; and it addresses the issue of upward compatibility with Ada 83 and shows that for normal programs the goal of compatibility has been achieved. This document will be of special value to program managers, team leaders, and all software professionals with concern for the organized development of software.

Author: Barnes, J.

Publisher: Intermetrics, Inc.

Sponsoring Organization: Ada 9X Project Office

Publication Date: 1/95


Ada Dual-Use Program Plan

Abstract: This document presents the DoD's Ada Dual-Use Program Plan, which is under the management of DISA. It describes a five-year projection and a two-year task level plan, as well as discusses background on the Plan and its purpose. It details the strategic approach that will guide the DoD, DISA, and the AJPO and outlines the dual-use strategy. It also describes the tactical approach that the three agencies will follow to increase the usage of Ada, delineating five major thrusts. It also highlights the management approach, provides an integrated program schedule, and contains the Ada-Dual Use Task Summary, which relate to increasing Ada usage.

Author: Defense Information Systems Agency Center for Information Management

Publisher: DISA - Defense Information Systems Agency, Center for information Management

Producing Organization: DISA

Publication Date: 5/94


Application of Software Metrics to Object-Based, Re-engineered Code Implemented in Ada

Abstract: This thesis from University of Idaho focuses on measuring the growing complexity of industrial strength software systems over their life cycle and on the impact on complexity of when re-engineering the software using object-oriented technologies implemented in the Ada programming language. This thesis analyzes issues surrounding the software product life cycle. It evaluates the impact of regular maintenance on the system. It investigates the effects of re-engineering. More specifically, this thesis provides evidence that shows complexity increases with functionality, and maintainability increases with re-engineering. The impact of using object-based software development practices during re-engineering and the subsequent implementation in the Ada program language is probed using software metrics.

Author: Welker, K.D.

Publisher: College of Graduate Studies, University of Idaho

Publication Date: 4/94


Policy Issues Concerning Implementing the Ada Mandate Within the Department of Defense (Draft)

Abstract: This report is a preliminary version of a report dealing with Ada policies of the DoD. Its purpose is to provide a reasoned, objective analysis of the important policy issues connected with the use of Ada as the standard DoD programming language. It is intended to provide useful background and principles for formulating DoD waiver policy; it does not make specific policy recommendations. Instead, it defines and discusses the critical issues, suggests where the weight of the current evidence lies in resolving the issues, and recommends further actions necessary to come to a suitable final resolution. The authors provide a letter that qualifies that while the report should give a good approximation of the substantive content of the final report, it does need considerable additional editorial work.

Author: Emery, J. and M. McCaffrey

Publisher: NPS - Naval Postgraduate School, Monterey, CA 93943

Publication Date: 5/91


Advanced Tactical Surveillance (ATS) Lines of Code Estimate (a technical memorandum)

Abstract: The purpose of this technical memorandum is to provide a preliminary estimate and rationale for the Ada Source Lines of Code (SLOC) and database size necessary to build the Advanced Tactical Surveillance (ATS) System. This Ada SLOC will be used by NAVAIR with models to estimate a cost and schedule for developing the ATS System Software.

Publisher: NADC - Naval Air Development Center, Warminster, PA 18974

Reference Number: 703TM 89-ATS-001

Producing Organization: NADC - Naval Air Development Center

Publication Date: 7/89


An Assessment of the Programming Language CORAL 66 Against the U.S. Department of Defense Tinman Requirements

Abstract: Section 1 of this document gives an overall assessment of CORAL 66 against the Tinman and attempts to put CORAL in historical perspective. Section 2 then evaluates CORAL against each Tinman requirement in turn. This section is structured in the same lines as the Tinman document, with evaluations against both major and minor requirements. An attempt has been made to allow each section and subsection to stand on its own for reference purposes. Some duplication of information is therefore inevitable. The third section provides a graphical summary: it obviously represents a very coarse measure.

Publisher: Software Sciences Ltd.

Reference Number: Software Sciences #: F656

Publication Date: 11/76


DoD Requirements for Ada Language Integrated Computer Environments: Preliminary Stoneman

Abstract: This document specifies the requirements for an Ada Programming Support Environment (APSE). It provides criteria for assessment and evaluation of APSE designs, and offers guidance for APSE designers and implementers.

Publisher: DoD

Publication Date: 11/79


ADA Technical Workshop (Naval Computer and Telecommunications Command)

Abstract: This document presents materials, such as presentations and summations of activities, from a 1991 workshop conducted for NARDAC personnel. The goal of the workshop was to position the activities in the COMNAVCOMTELCOM claimancy as primary sources of quality software written in the Ada programming language. Its objectives are as follows: support Open Systems objectives in the effective implementation of Ada in the NCTC claimancy; effectively incorporate the power of Ada in the implementation strategy; develop a methodology for implementing Ada that has the support of and is understood by the NCTC claimancy; communicate sources of help, training, and NCTC Ada programming standards; identify reuse methods and develop a plan for implementing within the claimancy; identify and prioritize enhancements to AdaSAGE, which has the support of the participating services; and share lessons learned from previous Ada developments within the claimancy.

Publisher: NCTC - U.S. Naval Computer and Telecommunications Command, 4401 Massachusetts Avenue, Washington, DC 20394

Producing Organization: NCTC - Naval Computer and Telecommunications Command

Publication Date: 4/91


Learning Tree International Course Materials, Ada 95 Object-Oriented Programming: Hands-On Introduction

Abstract: This document provides, in addition to marketing materials re: Learning Tree International, a Course Notes packet covering Ada 95 Object-Oriented Programming: Hands-On Introduction. The objectives of this particular course are: understanding Ada95's style and constructs through practice; learning how to design and implement object-oriented software systems in Ada 95; becoming familiar with Ada terminology, the Ada 95 Language Reference Manual (LRM), and Ada 95; and appreciating Ada 95's role in modern software engineering practice. The course prerequisities are experience with a high-level, block structured language, including subroutines, arrays, records, and pointers.

Author: Appelbe, W.

Publisher: Learning Tree International, Inc.

Publication Date: 1/95


Ada Validation Facility Operating Procedures and Guidelines

Abstract: This document describes step-by-step procedures of a validation that proceeds without problem. Because mistakes do happen, it also lists each anticipated problem and describes an acceptable solution to that problem.

Publisher: Ada Validation Facility, Aeronautical Systems Center, Wright-Patterson AFB, OH

Publication Date: 10/92


Electronic Combat Model Reengineering

Abstract: This monograph presents the Improved Many-on-Many (IMOM) reengineering project as a means to provide lessons for both government and commercial software developers and decision makers. The lessons include: the importance of software architecture in achieving significant software-related benefits; the application of object-oriented methods, in the context of a disciplined software engineering process, as a means toward major gains in reuse, productivity, and maintainability, and the value of Ada in obtaining maximum payoffs from an investment in software engineering practices.

Publisher: Ada Information Clearinghouse

Reference Number: AJPO-MON-95-01

Producing Organization: Idaho National Engineering laboratory

Publication Date: 3/95


Ada 95, The New Object-Oriented Standard

Abstract: This magazine article discusses the process of revising Ada so that it could not only meet a narrower definition of Object Oriented Programming (OOP) through support for inheritance, dynamic binding, and polymorphism, but also "raise the ante" through better support for programming by extension, etc. The article goes on to discuss the various features, that is, child packages, inheritance, dynamic binding, and abstract classes. It also details compilers as resources.

Author: Riehle, R.

Publisher: AdaWorks

Publication Date: 5/95


ADA Technical Workshop

Abstract: This guide was developed to provide implementation procedures for the Department of the Navy Data Administration Program outlined in SECNAVINST 5230.xx. It will assist information resource management professionals in the effective application of available technology to satisfy the ever increasing information requirements of their organizations.

Publisher: NCTC - Naval Computer & Telecommuncations Command

Sponsoring Organization: Dept. of the Navy Data Admin. Program

Publication Date: 1/91


Framework Definition and Rationale

Abstract: The PCIS Programme has been established by the NATO Special Working Group on Ada Programming Support Environments. PCIS is to identify a software engineering environment framework responding to the requirements of IRAC, based on PCTE and other available standards. This document defines the PCIS framework service areas. The document presents concepts and rationale for each area, and it includes initial design material. Keywords: Software Engineering framework, PCTE, Object-Orientation, Fine-Grained Information, Life-Cycle Process, Tool Coordination.

Author: PCIS Architecture

Publisher: PCIS Architecture and Assessment Team

Sponsoring Organization: NATO Special Working Group on Ada Programming Support Environments

Producing Organization: PCIS

Publication Date: 12/93


Software Engineering Symposium, 1993 held at Pittsburgh, PA on August 23-26, 1993

Abstract: This document presents material related to Process Improvement, Technology, and Standards & Policy; the many headings present a wide array of subjects--all as covered in presentations at the 1993 Symposium.

Publisher: The Business of Software Engineering

Publication Date: 8/93


Introducing Ada 9x, Ada 9x Project Report

Abstract: This document contains four chapters. Chapter 1 gives the background to the development process including the capture of the requirements from the existing and future user community. Chapter 2 introduces the highlights of the language, especially the three topics Objected Oriented Programming, Hierarchical Libraries, and Protected Objects. It is in a tutorial style. Chapter 3 gives an overview of the whole language showing how the new facilities fit into the overall framework. Finally, Chapter 4 addresses the issue of upward compatibility with Ada 83 and shows that for normal programs the goal of compatibility has been achieved. This document will be of special value to program managers, team leaders, and all software professionals with concern for the organized development of software.

Author: Barnes, J.

Publisher: Intermetrics, Inc.

Sponsoring Organization: Ada 9X Project Office

Producing Organization: Intermetrics, Inc.

Publication Date: 8/93


Ada Quality and Style: Guidelines for Professional Programmers

Abstract: This book is intended to help the computer professional produce better Ada programs. It presents a set of specific guidelines for using the powerful features of Ada in a disciplined manner. Each guideline consists of a concise statement of the principles that should be followed, and a rationale explaining why following the guideline is important. In most cases, an example of the use of the guideline is provided, and in some cases a further example is included showing the consequences of violating the guideline. Possible exceptions to the application of the guideline are explicitly noted, and further explanatory notes, including notes on how the guideline could be automated by a tool, are provided where appropriate. Many of the guidelines are specific enough to be adopted as corporate or project programming standards.

Author: Johnson, Kent, Elisa Simmons, and Fred Stluka

Publisher: SPC - Software Productivity Consortium, Inc., SPC Building, 2214 Rock Hill Road, Herndon, VA 22070-4005

Reference Number: SPC-91061-N

Producing Organization: SPC - Software Productivity Consortium

Publication Date: 1/91


Overview of Megaprogramming Course: Lectures and Exercises

Abstract: This document provides material covering the lectures and workbook exercises for a megaprogramming course. It covers software development, concepts of megaprogamming, application engineering, domain engineering, and a test and survey.

Publisher: Software Productivity Consortium Services Corporation

Reference Number: SPC-93028-CMC

Publication Date: 2/94


Framework for Certification of Reusable Software Components (Version 1.0)

Abstract: This document provides a framework for reusable software component certification. Specifically, the certification process presented in this document describes, at a high level, what is required to certify many types of software development life-cycle products (e.g., requirements, designs, code). It is one approach among several under development with the Department of Defense and private industry. It is written primarily for a technical management audience interested in populating reusable software component libraries with high-quality products of the entire software development life-cycle. Readers should be familiar with software development concepts and techniques.

Author: Merritt, S. (POC)

Publisher: SofTech, Inc.

Reference Number: 1222-04-210/31A-2

Publication Date: 2/93


JAC/EG Technical Review

Abstract: This document provides materials relevant to a Technical Review held on 2-4 May 1989. It covers Process Program, Methods Program, Systems Program, Ada and STARS Support, and Technology Transition.

Publisher: SEI - Software Engineering Institute, Carnegie Mellon University, Pittsburgh, PA 15213

Sponsoring Organization: U.S. Department of Defense

Producing Organization: SEI - Software Engineering Institute

Publication Date: 5/89


Practical Software Management -- A Guide to Objective Program Insight

Abstract: This guide is intended to provide a basic introduction to software measurement for DoD program managers and the technical staff responsible for implementing a software program. It is organized into three parts: 1) The Management Summary (provides an overview of the basic principles and approach contained in Practical Software Measurement); 2) The Implementation Guide (describes a basic measurement process that can be applied to any program -- in particular, it focuses on providing the DoD program manager with visibility into an ongoing program; this document provides recommendations for implementing a measurement program as described in MIL-STD-498); and 3) The Case Study (illustrates many of the key points made in the Implementation Guide; the case study provides a complete example of software measurement as applied to a typical DoD program).

Publisher: Joint Logistics Commanders

Publication Date: 6/95


Software Education Workshop

Publisher: Defense Logistics Agency

Publication Date: 2/95


Affiliates Symposium held in Pittsburgh, PA on May 2-4, 1989

Abstract: This document provides materials from the 1989 Affiliates Symposium, including that from the 23 Symposium Sessions.

Publisher: SEI - Software Engineering Institute, Carnegie Mellon University, Pittsburgh, PA 15213

Sponsoring Organization: U.S. Department of Defense

Producing Organization: SEI - Software Engineering Institute, Carnegie Mellon University

Publication Date: 5/89


Software Reuse Executive Primer

Abstract: This document provides a simple and understandable overview of software reuse. It presents the issues and benefits involved in transitioning to reuse-based software acquisition, development, and maintenance processes, and answers frequently asked questions about software reuse. Technical and organizational issues are discussed along with successful reuse management techniques.

Publisher: DOD Software Reuse Initiative, Program Management Office

Publication Date: 5/95


Assessing the Impact of Implementation of the Ada Programming Language at Naval Regional Data Automation Centers

Abstract: This study assesses Naval Regional Data Automation Centers' (NARDACS) environments to determine the impact of converting to the Ada programming language for software development. The assessment is supported by data collected from current and planned programming projects and from interviews with key software managers at the various NARDACS. From this data, several barriers to a successful implementation became apparent. Possible solutions to the barriers are discussed and recommendations to ease the execution of a transition plan are presented.

Author: Knight, LCDR R.L.

Publisher: Naval Postgraduate School

Publication Date: 12/90


Tools for Storage and Retrieval of Ada Software Components in a Software Base

Abstract: One problem facing the Computer Aided Prototyping System (CAPS) project at the Naval Postgraduate School is the lack of a large repository of existing reliable software components to draw upon for the creation of new prototype designs. The primary goal of this thesis is to solve this problem by creating a tool that accepts an Ada Package Specification as input and automatically generates its corresponding Prototype System Description Language (PSDL) specification. The Ada package along with its PSDL specification may then be stored directly into the CAPS software base. The result of this thesis is a translator that examines each declaration contained in an Ada Package Specification and creates a corresponding PSDL specification. This tool allows the CAPS software base to be populated much faster utilizing existing DoD Ada software libraries such as CAMP, ASSET, RAPID, and CRSS. This tool has demonstrated its effectiveness by translating several complex components of the Common Ada Missile Packages into PSDL specifications.

Author: Eagle, C.S.

Publisher: Naval Postgraduate School

Publication Date: 3/95


The Design and Implementation of a Reusable Component Library and a Retrieval/Integration System

Abstract: This thesis describes a tool to enhance the practice of software reuse within the Computer Aided Prototyping System (CAPS). A software base interface provides prototype designers with the means to retrieve components and integrate them into new applications. Reusable components are retrieved from the software base using a formal specification as the search key or through a browser. The specification language used is the Prototype System Description Language (PSDL). The software base stores the reusable components in an object oriented database management system (ONTOS) with an appropriate PSDL specification. Following a query conducted by the PSDL specification, chosen retrieved components are transformed and integrated to the system under development. All software procedures, including the storage, retrieval, and integration of the components, are conducted through a graphical user interface that is designed to demonstrate and manipulate available software base operations.

Author: Ozdemir, D.

Publisher: Naval Postgraduate School

Publication Date: 12/92


Developing Portable User Interfaces for Ada Command Control Software

Abstract: DoD mandated use of Ada for embedded systems includes Combat and Control Systems such as shipboard Combat Direction System (CDS). A Low Cost CDS (LCCDS) that will use commercial workstation platforms will require interfacing Ada real-time programs with a portable windowing environment such as X Windows. This thesis explores several methods for building X Windows user interface for Ada C 2 programs and provides a step-by-step approach to user interface design for future CDS developers.

Author: Hsiung Sun, C.

Publisher: Naval Postgraduate School

Publication Date: 6/90


Design and Implementation of an Expert User Interface for the Computer Aided Prototyping System

Abstract: This thesis builds on previous work done in the development of the Computer Aided Prototyping System (CAPS) and the Prototype System Description Language (PSDL). The increases in the size and complexity of software projects have caused system designers to reevaluate traditional software engineering methodologies. Rapid prototyping is a method that allows the validation of system requirements and design early in the development cycle. The need for this type of tool is particularly critical in the development of real-time embedded systems. CAPS is one such system. CAPS is a complex system that consists of many individual software tools. An expert user interface that guides the software designers through the development and execution of a prototype is described in this thesis.

Author: Raum, H.G.

Publisher: Naval Postgraduate School

Publication Date: 12/88


Version and Variation Control of a Design Database for a Computer Aided Prototyping System

Abstract: The Computer Aided Protoyping System (CAPS) was created for rapidly prototyping real-time systems to determine early in the software development life cycle whether system requirements can be met. The CAPS consists of several software tools that automatically generate an executable Ada model of the proposed system. This thesis describes the development of a Design Database (DDB) for the CAPS. The DDB is an engineering database that contains all information related to a software prototype design. The DDB enhances the CAPS environment and the prototyping model by providing to the designer the capability to store, retrieve, view, and control variation and versioning of the prototype components. This thesis describes the design, test, and implementation of a tree structure variation and version method for supporting CAPS.

Author: O'Loughlin, M.D.

Publisher: Naval Postgraduate School

Publication Date: 6/92


Ada as a Foundation Programming Language

Abstract: This brief article offers a bar graph and listings relevant to the colleges and universities known to have adopted Ada as their foundation language.

Author: Feldman, M.B

Publication Date: 2/95


Ada/POSIX Real-Time Bindings Quarterly Technical Report

Abstract: This report describes the activities and results of the POSIX/Ada Real-Time (PART) Project for the period 29 October 1994 through 28 January 1995. These activities include the testing and improvement of the GNARL Ada 9X tasking implementation, including the addition of new features and performance improvements. It also includes the production of a new draft of the proposed POSIX 1003.5b standard, which is an Ada binding for the POSIX Realtime and Threads extensions.

Author: Baker, T. and T. Giering

Publisher: Telos Systems Group

Sponsoring Organization: HQ U.S. Army CECOM, Software Engineering Directorate

Publication Date: 1/95


Ada/POSIX Real-Time Bindings Quarterly Technical Report

Abstract: This report describes the activities and results of the POSIX/Ada Real-Time (PART) Project for the period 27 July through 28 October 1994. These activities include the implementation and testing of several Ada 9X tasking features, and the production of a new draft of the proposed POSIX 1003.5b standard, which is an Ada binding for the POSIX Realtime and Threads extensions.

Author: Baker, T. and T. Giering

Publisher: Telos Systems Group

Sponsoring Organization: HQ U.S. Army CECOM, Software Engineering Directorate

Publication Date: 10/94


Implementing Ada 9X Features Using POSIX Threads: Design Issues

Abstract: The draft standard POSIX Threads Extension provides an application program interface to operating system services supporting the creation and execution of multiple threads of control within a single process. Where Ada is implemented over an operating system that supports POSIX-like thread services, there are good reasons to implement the Ada tasks as POSIX threads. This paper explores some of the design issues involved in implementing Ada 9X tasking constructs on a system supporting POSIX threads. It also points out some features of the threads interface that make it less than optimal for the implementation of Ada 9X tasking.

Author: Baker, T.P., E.W. Giering, and F. Mueller

Publisher: Association for Computing Machinery, Inc.

Publication Date: 1/93


Serial I/O and Interrupt Support for a POSIX Threads Kernel

Abstract: Pthreads (POSIX threads) is a draft IEEE standard interface for operating system services to support multiple threads of control within a single process. This report describes the design and implementation of extensions made to an existing Pthreads implementation on a bare Sun SPARCengine 1E, to support the Gnu Ada Runtime Library (GNARL). It shows how much better performance can be achieved by a standalone Pthreads library-based tasking implementation as compared to a user-level Pthreads library-based implementation. It also shows how a standalone Pthreads implementation can provide more predictable execution timing.

Author: Goyal, A.

Publisher: Florida State University College of Arts and Sciences

Publication Date: 1/94


POSIX Ada Real-Time Bindings: Description of Work in Progress

Abstract: Ada bindings are being developed for the proposed POSIX Realtime Extension and Threads Extension. POSIX is a standard application program interface to operating system services. The Threads Extension is of particular interest for Ada implementors and users since it provides services that overlap significantly with Ada tasks. Work in progress on the implementation of Ada tasks over POSIX threads is beginning to shed light on the problem of producing an Ada binding for the POSIX Threads Extension.

Author: Baker, T.P. and E.W. Giering III

Publisher: The Association for Computing Machinery, Inc.

Publication Date: 1/90


The Gnu Ada Runtime Library (GNARL): Design and Implementation

Abstract: The Gnu Ada Runtime Library (GNARL) is an implementation of Ada 9X tasking. It is designed to support the Gnu-NYU Ada Translator (GNAT) and is part of the GNAT distribution. This report describes the design of the interface that GNARL presents to compiler-generated code, some of the alternatives considered, and the motivation for choosing the current design. It also discusses the GNARL implementation, how it is intended to be layered over the services of an off-the-shelf commercial operating system, and the expected compiler translation of various Ada 9X tasking constructs.

Author: Baker, T.P. and E.W. Giering, III

Publisher: The Association for Computing Machinery

Publication Date: 1/94


Gnu Low-Level Interface (GNULLI) Definition

Abstract: This document describes the interface between the Gnu Ada Runtime Library (GNARL) and a lower-level of support services, which are provided by an operating system or run-time kernel. (A separate document defines the interface between the GNARL and compiler-generated code.)

Author: Baker, T.P. and E.W. Giering III

Publisher: Florida State University

Publication Date: 6/93


[Not A] Standards Project, Information Technology--POSIX Ada Language Interfaces--LATEX Macro Usage

Abstract: This document explains how to use the macros defined in the psxcbln LATEX syle file, which is intended for producing Ada language bindings for IEEE POSIX standards.

Author: Baker, T.

Publisher: Florida State University

Publication Date: 11/93


GNARL Low-Level Interface Definition, ANNEX: Condition Variables

Abstract: This document is part of the interface between the Gnu Ada Runtime Library (GNARL) and a lower-level of support services, called the GNU Low-Level Interface (GNULLI) description. This document describes an alternate interface for the suspension of low-level tasks, based on condition variables.

Author: Baker, T.P. and E.W. Giering III

Publisher: Florida State University

Publication Date: 1/93


PART/GNARL Interface Definition

Abstract: This document describes the interface between the code generated by the Gnu NYU Ada Translator (GNAT) and the tasking support portion of the Gnu Ada Runtime Library (GNARL)--the GNARL Interface (GNARLI, for short). The purpose of this document is to serve as a contract between the developers of an Ada compiler (GNAT) and the portion of an Ada runtime system (RTS) that supports tasking (the TRTS, for short.)

Author: Giering, E.W.

Publisher: Florida State University

Publication Date: 7/94


POSIX Threads Catalog of Portability Issues

Abstract: This document collects and classifies the explicit and implicit implementation dependences that are present in the proposed POSIX Threads Extension, P1003.1c (originally named P1003.4a). Dependences that are carried over from IEEE-STD 1003.1-1990 and IEEE-STD 1003.1b-1993 are not discussed. Only semantic issues at the interface level are discussed. Consequently, the analysis of the many valid implementation approaches is considered out of scope for this report. The focus is on issues that affect application developers; some discussion on language bindings and system software development is also presented. It is argued that too many such implementation dependences exist for the standard to be useful for demanding applications. Since P1003.1c was still in a draft form at the time of completing this report, the writers were hopeful their findings would help improve the standard before its final approval.

Author: Pazy, O.

Publisher: Telos Systems Group

Sponsoring Organization: HQ U.S. Army CECOM, Software Engineering Directorate

Producing Organization: Florida State University

Publication Date: 8/94


Tools for Static Analysis of Ada Source Code

Abstract: This paper surveys static analysis tools for Ada source code. These tools analyze Ada source code without executing it. The tools help users understand code and may produce outputs for other tools. This survey helps people who want to extract information from Ada source code. People contemplating static analysis may not know what tools are locally available or how to answer analysis questions with them. They may desire guidance on analysis strategies and specific tools. A comprehensive survey is not necessary, but information about locally available tools is. This survey is an expansion of an internal tools survey that filled this need at the Consortium. The purpose of the present survey is to make Consortium personnel aware of locally available static analysis tools. While intended for use at the Consortium, this survey should be helpful to others. The reader is assumed to have a passing familiarity with programming, Ada, Descriptive Intermediate Attributed Notation for Ada (DIANA), and Ada compilation methods.

Author: Arnold, R.S.

Publisher: Software Productivity Consortium, Inc.

Reference Number: ADA-STATIC-TOOLS-SURVEY-90015-N

Publication Date: 6/90


An Approach for Constructing Reusable Software Components in Ada

Abstract: This paper is aimed at helping the reader gain a clearer understanding of the concept of reuse and its implications. It explores the topic of software reuse at a programming level, focusing on how reuse can be achieved in the Ada programming language. It is aimed at people working at the detailed design level, designing units that will be implemented in Ada and that may have reuse potential. The paper primarily discusses code reuse, but in order to achieve effective code reuse, reuse must be considered during detailed design. In fact, the earlier software reuse is considered during the design process, the greater the potential for savings. Thus, the paper presents a detailed discussion of the tradeoffs a designer must consider early on during the design of a component. This analysis is centered around a conceptual model on what a reusable component actually is. This model is a very appropriate way of thinking about reusable components during all stages of development, whether the goal is designing new components or applying available ones.

Author: Edwards, S.

Publisher: IDA - Institute for Defense Analyses, 1801 N. Beauregard Street, Alexandria, VA 22311

Reference Number: IDA Paper P2378

Sponsoring Organization: SDIO - Strategic Defense Initiative Organization

Producing Organization: IDA - Institute for Defense Analyses

Publication Date: 8/90


Proceedings: Ada Reuse and Metrics Workshop

Abstract: This document offers materials relevant to the Ada Reuse and Metrics Workshop, held on June 20, 1989. Covered topics include: AIRMICS Reuse Project, Metrics, Fault Tolerance, Incentives, Cost/Benefit Modeling, Reuse Guidelines, DoD Stds. Harmonization, and Tool Assessment.

Sponsoring Organization: U.S. Army Institute for Research in Management Information, Communications, and Computer Science

Producing Organization: Martin Marietta Energy Systems, Inc.

Publication Date: 7/89


Kernel User's Manual, Version 1.0

Abstract: This manual describes the models underlying the Kernel and its concept of operations, presents the primitives available to the application program, and provides a number of abstractions that may readily be built on top of Kernel primitives. The Kernel is a body of code that implements real-time facilities that can be invoked by applications written in Ada for execution on a distributed target. The requirements for the Kernel, both behavior and performance, are provided in the Kernel Facilities Definition, and its design will be provided in the forthcoming Kernel Architecture Model. The Kernel was built at the Software Engineering Institute by the Distributed Ada Real-Time Kernel (DARK) Project. This manual provides the information needed by a programmer to understand and use Version 1.0 of the Kernel to support a distributed application. The host system is the MicroVax II (under MicroVMS 4.2). The Kernel is implemented in Ada using the TeleSoft Telegen2 Compiler, Release 3.22, and MC68020 assembler. The target system is a netwok of distributed MC68020 processors and peripherals.

Author: Bamberger, J. et. al.

Publisher: SEI - Software Engineering Institute, Carnegie Mellon University, Pittsburgh, PA 15213

Sponsoring Organization: U.S. Department of Defense

Producing Organization: SEI - Software Engineering Institute, Carnegie Mellon University

Publication Date: 2/89


Mode Change Protocols for Priority-Driven Preemptive Scheduling

Abstract: In many real-time applications, the set of tasks in the system as well as the characteristics of the tasks change during system execution. Specifically, the system moves from one mode of execution to another as its mission progresses. A mode change is characterized by the deletion of some tasks, addition of new tasks, or changes in the parameters of certain tasks, e.g., increasing the sampling rate to obtain a more accurate result. This paper discusses a protocol for systematically accomplishing mode change in the context of a priority-driven preemptive scheduling environment.

Author: Sha, L, et. al.

Publisher: SEI - Software Engineering Institute, Carnegie Mellon University, Pittsburgh, PA 15213

Reference Number: CMU/SEI-88-TR-34; ESD-TR-88-035

Sponsoring Organization: U.S. Department of Defense

Producing Organization: SEI - Software Engineering Institute

Publication Date: 11/88


Meeting of the Software Executive Officials

Abstract: The document provides materials relevant to the meeting of the software executive officials on 18 July 1991. Covered topics include: AJPO issues, evaluation and validation working group report, Ada Board recommendations, work breakdown structure for software, standard for counting lines of Ada code, and Ada 9X transition plan.

Author: Solomond, J.P.

Producing Organization: AJPO

Publication Date: 7/91


Technical Report: Work Breakdown Structure Elements for Software, MIL-HDBK-171

Abstract: This handbook provides a framework for identifying and extending Work Breakdown Structure elements related to software when implementing DoD acquisition policy and MIL-STD-881B. This framework provides guidance to Industry and Government to better monitor, track, analyze, and estimate the cost of developing and supporting defense system software. The handbook shows how an acquisition can be planned and how contractor/developer software management information can be tailored to the specific requirements of the acquisition. This technical report describes the contents of the draft handbook.

Publisher: US Army CECOM, Center for Software Engineering

Reference Number: MIL-HDBK-171 (DRAFT)

Producing Organization: AJPO - Ada Joint Program Office

Publication Date: 7/92


Test Case Study: Estimating the Cost of Ada Software Development

Abstract: The objectives of this report are centered around the major issues regarding Ada software development cost estimation. To assist the cost analyst in arriving at reasonable Ada cost estimates, this report will focus on the following objectives: determine if software cost models that are non-Ada-specific can be successfully used to estimate the cost of Ada development; provide a comprehensive review of selected cost models with regard to Ada-specific cost drivers and issues discussed in literature; evaluate model performance in light of the language considerations of the models to determine any correlation; and identify which models provide reasonable results when used to estimate Ada development cost. An essential part of the research is a test case study in which selected cost models were applied to a database of eight completed Ada projects. This information was used to derive inputs for each model. Emphasis was placed on providing a consistent set of information for each model. In addition, models were applied using nominal (average) values for input ratings while providing actual project values for model inputs that have no associated average value. Model performance was evaluated based on a comparison of each model's projected schedule and effort to the actual resources expended by the software developer for each project. The results of the test case study are the basis for recommending a preferred approach to estimating Ada software costs. Detailed descriptions of the test case study, results, and conclusions are included in this report.

Publisher: IITRI - IIT Research Institute, 4600 Forbes Boulevard, Lanham, MD 20706-4324

Sponsoring Organization: AJPO - Ada Joint Program Office; US Air Force Cost Center; and US Army Cost and Economic Analysis Ce

Producing Organization: IITRI - IIT Research Institute

Publication Date: 4/89


Ada Graphics Driver Software Package for the DY-4 777 Graphics Controller Board

Abstract: This report describes a comprehensive Ada graphics driver software package developed to control a Model 777 graphics controller board manufactured by DY-4 Systems, Inc. This Ada package was developed as the initial graphics driver software for The Combined Arms Weapon System (TACAWS) technical demonstration system. The 777 board was later replaced in the TACAWS gunner station computer development by a greatly enhanced Model 770 graphics board combined with a Model 674 frame grabber board, both from DY-4 Systems. However, many existing and developmental systems use the Model 777 board and can use the Ada package contained in this report. The author also developed a more comprehensive Ada graphics package to accommodate the 770/674 boards' enhanced features. The 770 Ada package is contained in another report.

Author: Reed, D.T.

Publisher: U.S. Army Missile Command, Redstone Arsenal, AL 35898

Reference Number: TR-RD-GC-95-2

Publication Date: 3/95


Incorporating Software Reuse Sources of Support

Abstract: This pamphlet contains the Reuse Advocate Support Matrix for Software Reuse, a matrix designed to provide information on sources of support to reuse advocates who are attempting to incorporate software reuse into their organizations.

Producing Organization: Reuse Acquisition Action Team (RAAT)

Publication Date: 4/95


Reusing Software: Issues and Research Directions

Abstract: This paper discusses the implications of reuse on software production, with an emphasis on the technical challenges. Software reuse includes reusing both the products of previous software projects and the processes deployed to produce them, leading to a wide spectrum of reuse approaches, from the building blocks (reusing products) approach to the generative or reusable processor (reusing process). This paper discusses the implications of such approaches on the organization, control, and method of software development and discusses proposed models for their economic analysis. Software reuse benefits from methodologies and tools to: 1) build more readibly usable software; and 2) locate, evaluate, and tailor reusable software, the last being critical for the building blocks approach. Both sets are discussed in this paper, with a focus on application generators and OO development as they relate to retrieval techniques for software components and component composition (or bottom-up design). The paper also discusses transformational systems. It concludes by highlighting areas that the authors believe are worthy of further investigation. Key Words: Software reuse, managerial aspects of software reuse, software resuse measurements, building reusable components, OO software development, software component retrieval, adapting reusable components.

Author: Mili, H., F. Mili, and A. Mili

Publisher: IEEE Transactions on Software Engineering

Publication Date: 6/95


Concept of Operations for Interoperating Reuse Libraries (Draft 3.2)

Abstract: This document provides a context for standardization efforts for a network of interoperating reuse libraries (NIRL) and a framework to discuss current standards. The existence of NIRLs creates a marketplace operating under common agreements to provide software reuse products and services to customers throughout the software community. This document describes the concepts necessary and appropriate for NIRLs. Appendices describe NIRLs currently in practice, operational scenarios for the proposed NIRLs, and changes necessary to evolve the current NIRLs into the proposed NIRLs.

Publisher: IEEE, Inc.

Reference Number: P1430

Producing Organization: Technical Committee 6: System Architecture of Reuse Library

Publication Date: 5/95


Asset Certification Framework, Baseline Concept

Abstract: This document provides information regarding TC4 overview and motivation, the concept for an asset certfication framework, a standard framework for certification policies, and a certification data model.

Producing Organization: Reuse Library Interoperability Group (RIG)

Publication Date: 5/95


Guide for Information Technology--Software Reuse--Asset Certification Framework

Abstract: This document describes an Asset Certification Framework for defining the asset certification techniques of a reuse library.

Publisher: IEEE, Inc.

Reference Number: P1420.1

Producing Organization: Reuse Library Interoperability Group

Publication Date: 5/95


Information Technology--Software Packages--Quality Requirements and Testing

Abstract: This document presents an International Standard that is applicable to software packages, such as text processors, spreadsheets, database programs, graphics packages, etc. It establishes quality requirements for software packages and gives instructions on how to test a software package against these requirements.

Publisher: ISO/IEC

Reference Number: ISO/IEC 12119:1994(E)

Publication Date: 1/94


Adopting a Policy of Reuse

Abstract: This article describes how considerations for a variety of technical, managerial, economic, social, and legal factors can be woven into the process of adopting reuse. It offers success stories and methodology for starting a program.

Author: Davis, T.

Publisher: IEEE Spectrum

Publication Date: 6/94


Reuse in Practice: Three Case Studies

Abstract: This article offers a snapshot of industrial practice in software reuse from three projects; it looks at object technology as it relates to reuse and offers a perspective on how companies, both in the United States and overseas, are managing to apply modern software-engineering principles to real-life applications. Specifically, it looks at reuse in real-time shipboard applications (the Swedish company CelsiusTech), reuse in a banking system (First National Bank of Chicago), and reuse in a business enterprise database application (AMBAC Indemnity Corporation).

Author: Goldberg, M.

Publisher: The Rational Watch, Rational Software Corporation

Publication Date: 1/95


Sixteen Questions about Software Reuse

Abstract: This article answers 16 questions that, in the authors' experience, are commonly asked about reuse. It relied on survey data collected recently from organizations in the United States and Europe.

Author: Fox, C.J., and W.B. Frakes

Publisher: Communications of the ACM

Publication Date: 6/95


Strategy First, Reuse Benefits Later

Abstract: This article discusses the important role of an effective reuse strategy in building a clear understanding of goals and business priorities. It offers that careful consideration of the elements of such a strategy--the people, process, and technologies, as well as their interactions, will yield better results than an approach based on one element alone.

Author: Adamczyk, J.P.

Publisher: Client/Server Computing

Publication Date: 6/95


Software Reuse Success Stories

Abstract: This document presents a set of software reuse success stories that can be used in various forums by different presenters to show the advantages to be gained from software reuse across a range of projects. Specifically, it looks at five projects: AFATDS (Advanced Field Artillery Tactical Data System); RNTDS (Restructured Naval Tactical Data System); TCIM (Tactical Communications Interface); UARS (Upper Atmosphere Research Satellite); and UNAS (Universal Network Architecture Services)--projects that used languages such as Ada, CMS-2, C, and C++. The document covers their asset creation and management, goals, lessons learned, and more.

Publisher: Department of Defense

Publication Date: 9/93


Domain Analysis Concepts and Research Directions

Abstract: This document is actually Part One (Introduction and Overview) of a larger work. This introduction investigates a context for domain analysis, defines analysis concepts, discusses principles and assumptions, and queries into the state of the art in domain engineering.

Author: Arango, G. and R. Prieto-Diaz

Publisher: IEEE, Inc.

Publication Date: 3/91


Criteria for Comparing Reuse-Oriented Domain Analysis Approaches

Abstract: This paper presents criteria for comparing and contrasting domain analysis approaches. The criteria were derived by studying five approaches that seem representative. The criteria attempt to provide a common conceptual ground for comparing and contrasting different ways to undertake domain analysis. The criteria are studied in terms of external factors that determine how and why an organization should use domain analysis. The criteria are first presented independent of any approach. They are then applied to the five approaches, to illustrate characteristics the approaches possess, and to show what some of the approaches' merits are. The paper concludes with some thoughts on the implications of the criteria for the future of domain analysis, considering in particular the likelihood of a single, unified approach emerging.

Author: Prieto-Diaz, R. amd S. Wartik

Publisher: Software Productivity Consortium, Inc.

Publication Date: 1/91


Using a Conceptual Framework for Reuse Processes as a Basis for Reuse Adoption and Planning

Abstract: This article provides an overview of the STARS Conceptual Framework for Reuse Processes (CFRP) and describes the experiences of several organizations that have applied it.

Author: Collins, P., et. al.

Publication Date: 12/93


What is an Organon?--Part I

Abstract: This document is an informal paper in which the author explains his coinage of the word "organon" as "a term for a new kind of information system/virtual community/organizational form that [he] envisioned emerging out of the confluence of work in reuse with certain key technologies and management innovations."

Author: Simos, M.A.

Producing Organization: Organon Motives

Publication Date: 1/94


The ODM-ISHADS, Being The Full and Complete History of ODM's Visit to Earth

Abstract: In this domain analysis doggerel, rather than in a paper, the author rhymes and reasons out the ten disciplines of Organization Domain Modeling (ODM) in a lengthy, sometimes amusing, poem.

Author: SIMOS, M.A.

Producing Organization: Organon Motives

Publication Date: 1/93


Case Studies (Advanced Field Artillery Tactical Data System [AFATDS], Restructured Naval Tactical Data System [RNTDS], TRW's Universal Network Architecture Services [UNAS], AAS, UARS, Tactical Communications Interface Module [TCIM], JOPES)

Abstract: This draft document combines several case studies covering context information, reuse planning, asset creation, asset management, asset utilization, and reuse findings and issues.

Publication Date: 4/93


Cost Models for Future Software Life Cycle Processes: COCOMO 2.0

Abstract: This paper summarizes research in deriving a baseline COCOMO 2.0 model tailored to the new forms of software development, including rationales for the model decisions. The major new modeling capabilities of COCOMO 2.0 are as follows: a tailorable family of software sizing models, involving Object Points, Function Points, and Source Lines of Code; nonlinear models for software reuse and reengineering; an exponent-driver approach for modeling relative software diseconomies of scale; and several additions, deletions, and updates to previous COCOMO effort-multiplier cost drivers. This model is serving as a framework for an extensive current data collection and analysis effort to further refine and calibrate the model's estimation capabilities.

Author: Boehm, B. et. al.

Publication Date: 10/94


The Economics of Software Reuse

Abstract: This paper describes cost models that have been developed to measure overall cost/benefits and the economic impact of reuse on software cost and productivity. It recommends a modeling framework that can be used to quantify the impact of reuse on software costs and productivity.

Author: Reifer, D.J.

Publisher: Reifer Consultants, Inc.

Sponsoring Organization: International Society of Parametric Analysis

Publication Date: 3/91


American Programmer, Topics on Reuse

Abstract: This issue of American Programmer offers seven articles on reuse, including a case study of MCI. While there is some discussion of the technological aspects of reuse, most of the authors focused on cultural issues, management issues, and the practical activities required to put reuse into practice. Article titles are as follows: Software Reuse--The Next Silver Bullet?; Issues and Experience in Software Reuse; Nontechnical Barriers to Software Reuse; The Story of MCI; Design for Reuse is for Real; Can You Beat the Reuse Achievements of a Decade Ago?; and Facilitating Reuse Using Object Technology.

Author: Binder, R.V., et. al.

Publisher: American Programmer

Publication Date: 8/93


CrossTalk, The Journal of Defense Software Engineering

Abstract: This document contains the entire 9/94 issue of CrossTalk, with the following articles: DoD Policy on the Future of MILSPEC; DoD Policy of Software Maturity Critieria for OT&E; Is Your Program's Software Ready for OT&E; The Impact of Evolving the Capability Maturity Model to Version 1.1; Achieving Higher SEI Levels; Ada 9X Project Report to the Public; Marching Toward a Software Reuse Future; and Building a Phased, Structured Approach to Reengineering Legacy Software Systems. The article on reuse covers the Software Engineering Directorate, Fire Support Software Engineering (SED, FSSE) past methods, current and future trends, as well as practical experiences in institutionalizing a formal reuse program supported with minimal funding.

Publisher: Department of Defense

Publication Date: 9/94


Reuse '94 Turorial, An Introduction to Software Reuse

Abstract: This document offers a tutorial on software reuse and covers the following items: introduction to reuse; issues in achieving reuse; making software reusable; reuse libraries; practicing reuse; and ongoing work.

Author: Braun, C.L.

Publisher: GTE Federal Systems Division

Publication Date: 8/94


Library-Related Legal Issues, 3rd Annual Reuse Education and Training Workshop

Abstract: This document covers materials from a workshop that introduced legal issues pertaining to reuse libraries and showed the connection of legal issues with library business issues. It addressed library interactions with customers (suppliers of components, users of components, and other libraries), addressed concerns and responsibilities of each party, and illustrated resulting library actions by using samples of clauses from agreements and library policies and procedures.

Author: Bowes, R. and T.R. Huber

Publisher: DSD Laboratories, Inc, Software Reuse Division

Publication Date: 8/94


DoD Software Reuse Initiative, Director Charter

Abstract: This document is a charter delineating the responsibilities, authorities, and relationships of the Director, DoD Software Reuse Initiative.

Publication Date: 6/94


DoD Software Reuse Initiative Quarterly Report

Abstract: This quarterly report covers the period 1 October 1992 - 31 December 1992, providing the status of the DoD Software Reuse Intitiative to the Director of Defense Information (DDI) and the Director, Defense Research & Engineering (DDR&E). Accomplishments, problem areas/issues, and required actions are also included.

Publication Date: 1/93


Software Technology for Adaptable, Reliable Systems (STARS) Program

Abstract: This document contains the Domain Analysis Process building block. Domain analysis is defined as the process by which information used in developing software systems is identified, captured, and organized with the purpose of making it reusable. The objective of the process model is to convert the ad-hoc nature of domain analysis into a repeatable procedure with well-defined, tangible outputs.

Sponsoring Organization: Electronic Systems Division, USAF

Producing Organization: IBM Federal Sector Division

Publication Date: 7/91


Software Reuse--History, Plans, and Progress

Abstract: This document is a briefing that provides a history of the objectives and activities of the SRI since its conception in 1991; it also highlights achievements to date with a focus on past and current issues, as well as discusses where the initiative is going and how DIS CIM will engineer that evolution.

Publication Date: 5/94


DoD Virtual Reuse Library Interoperation Strategic Plan, Draft

Abstract: This document presents a strategy and five-year plan for developing an interoperable reuse library capability for Department of Defense (DoD) users. This Plan identifies the strategies, tactics, tasks, and resources needed to incrementally develop and demonstrate those capabilities users need to share reusable assets in a seemingly seamless manner across those heterogeneous reuse libraries that make up the DoD Virtual Reuse Library. This plan is scoped to be compatible with the DoD Software Reuse Intitiative Virtual Library Operational Concept Document.

Producing Organization: Department of Defense

Publication Date: 11/93


Legal/Acquisition Issues: A Technical Report (Final Draft)

Abstract: This document proposes solutions to overcome specific legal and acquisition issues that are barriers to the Department of Defense (DoD) Vision and Strategy for Software Reuse. To achieve this purpose, this technical report does the following: identifies potential legal/acquisition inhibitors to software reuse; identifies DoD procedures that may be modified; and recommends alternative solutions to alleviate the inhibitors and promote successful reuse. It supports DoD Acquisition Executives, PEOs, PMs, OSD staff, and DISA staff responsible for planning and implementing software reuse. It is written specifically in support of DISA/Center for Information Management Reuse program. It is not intended to be an intellectual property law reference; however, it should offer alternative solutions for evaluation by Government contracting staff, Government program management, and Government Contractors.

Author: Wright, E. et. al.

Sponsoring Organization: DoD Center for Software Reuse Operations

Producing Organization: SofTech, Inc.

Publication Date: 2/93


Software Reuse on the Army SBIS Program

Abstract: This article gives an overview of the reuse strategy for the Army Sustaining Base Information Services (SBIS) program. It describes the SBIS reuse strategy and discusses the motivation and rationale behind it, as well as its two-phase approach for implementation. It also outlines the roles of responsible parties and describes the accomplishments of SBIS reuse over the past year, as well as explains how SBIS reuse strategy provides a comprehensive and achievable framework to meet its current goals, including steps taken to help developers find, retrieve, and incorporate reusable assets into SBIS applications.

Author: Poulin, J.S.

Publisher: CrossTalk

Publication Date: 7/95


The Internet, Where's It All Going?

Abstract: This article presents an interview with three key players, Vinton Cerf, Bill Joy, and Tim Berners-Lee, in the development of the Internet; it offers their predictions for its future.

Publisher: InformationWeek

Publication Date: 7/95


A Clearinghouse for Software Reuse: Lessons Learned from the RAPID/DSRS

Abstract: This document discusses the concepts and motivations behind clearinghouses for software reuse. At first it approaches the subject in more general terms, such as discussing the activities necessary for any clearinghouse. The report goes on to look at in particular the Defense Software Repository Service (DSRS) and how its design and implementation is based on a pilot operation initiated by the Army's Reusable Ada Product for Information System Development (RAPID). After investigating RAPIDs history, organization, and activities, the report goes on to discuss DSRS's role in creating a DoD-wide Reuse Program as well as the lessons learned from past clearinghouse practices.

Author: Bui, T.X., et. al.

Publisher: Naval Postgraduate School

Publication Date: 10/92


Software Reuse Business Model, Product Description

Abstract: This document briefly discusses the Software Reuse Business Model, a tool to assist DoD acquisition professionals in determining the best approach for incorporating software reuse practices into DoD weapons, command and control, administrative, and other software intensive system acquisitions. This pamphlet details the reuse-driven acquisition process, the user perspective, the domain perspective, the program perspective, and reuse business strategies.

Publisher: Department of Defense

Sponsoring Organization: DoD Software Reuse Initiative

Producing Organization: Army Space & Strategic Defense Command, Quality Research, DSD La

Publication Date: 10/94


Software Reuse in NATO

Abstract: This document outlines the NATO environment, the procurement and management of NATO information systems, and application of reuse in the NATO environment, as well as issues of concern and aims as they relate to reuse.

Author: Syms, T.

Publisher: NATO Communications and Information Systems Agency (NACISA)

Publication Date: 12/94


A System Dynamics Based Study of Software Reuse Economics

Abstract: This document is a thesis that studies the economics of software reuse using a system dynamics computer model, the Dynamica Reuse Model, which simulates the activities of a software development organization engaged in organization-wide, systematic software reuse. Long-term relationships between reuse rate, productivity, and unit cost are studied by varying consumption cost, production cost, employee turnover rate, and reusable component retirement age. Results suggest long-term steady state relationships may be different from short-term dynamic state relationships. After validation and customization the Dynamica Reuse Model can be used to support an organization's cost and schedule software tools. Increasing understanding of the software development process in order to make knowledgeable rather than intuitive predictions about organizational variables related to reuse such as reuse rate, productivity, and unit cost, enable the model to serve as a management support tool for the complex and costly process of software development.

Author: Gallup, P.J.

Publisher: Naval Postgraduate School

Publication Date: 6/94


Software Reuse Technology, A Tutorial

Abstract: This tutorial offers a presentation of reuse methods developed and used by SEI and other organizations, discusses a life-cycle process for reuse that is illustrative, not prescriptive, and presents products of reuse development as well as specific tools and classes of tools to support reuse methods.

Publisher: Software Engineering Institute, Carnegie Mellon University

Sponsoring Organization: U.S. Department of Defense

Producing Organization: Software Engineering Institute

Publication Date: 9/90


Introducing Software Reuse

Abstract: This document presents material from a seminar whose purpose was as follows: to discuss reuse--its importance and its impact on business practices; to provide a framework for making reuse happen in your firm; to focus on parametric and business case issues associated with reuse; to identify early experiences with reuse and discuss the lessons learned; and to stimulate you to exploit this promising technology in low-risk ways.

Sponsoring Organization: Tri-Ada '93

Producing Organization: Reifer Consultants, Inc.

Publication Date: 9/93


Software Reuse Videos

Abstract: This document provides brief descriptions of available videos and software programs available on reuse.

Producing Organization: SIGAda Reuse Working Group, Reuse Acquisition Action Team

Publication Date: 6/94


Software Reuse Acquisitions Scenarios, A Discussion Paper

Abstract: This report provides an effective set of reuse acquisition strategies that will benefit both government and industry, and an outline for the development of additional scenarios that may respond more effectively to individual needs.

Producing Organization: RAAT

Publication Date: 3/94


Reuse '94 Tutorial, New Directions in Software Reuse

Abstract: This document provides material from a tutorial on new directions in software reuse. It offers a reuse research "framework" and discusses domain-specific reuse in terms of the rationale and basic concepts behind it, a project case history, the ARPA DSSA program, and a domain model/architecture representation. It also discusses an architecture-based life-cycle process, managerial challenges, and some suggestions on establishing a corporate reuse program.

Author: Braun, C.L.

Publisher: GTE Federal Systems Division

Publication Date: 8/94


A Collection of Software Reuse Reference Materials from the SIGAda Reuse Working Group

Abstract: This document is actually a folder that has collected a number of items related to reuse: A report on Software Reuse Success Stories illustrating the benefits of systematic software reuse, a flyer describing the Reuse Acquisition Action Team, a checklist on Contract Considerations for Reuse, a listing of Software World-Wide Web Servers and directions on how to use the list servers, contact sheets for further information, a pamphlet on the DoD Software Reuse Vision and Strategy, a pamplet on the Software Reuse Business Model, and a listing of Software Reuse Videos.

Sponsoring Organization: ACM Sig Ada

Producing Organization: Army Reuse Center

Publication Date: 4/95


Utilization of Reuse for Software Development

Abstract: This document describes the process involved in the development, testing, and deliverance of Version 4.0 under a very tight schedule. It relates decisions involving AdaSage, reuse candidate items, establishing metrics, and selection of other development tools. It also discusses risk assessment and reuse management re: concerns and goals. It also offers an overview of AdaSage's advantages and shortfalls as a tool and presents a discussion on lessons learned.

Author: Canal, K.L and Capt. M.J. Foley

Producing Organization: Marine Corps

Publication Date: 2/94


Reuse-Driven Software Processes Guidebook, Version 02.00.03

Abstract: This guidebook defines Synthesis, a sound approach for effective, family-oriented software development. It serves as a detailed guide to the practice of Synthesis and helps the reader to begin to practice it. The scope of this guidebook includes all activities and work products related to production of software and support of the needs and objectives of a business-area organization and its customers. Detailed descriptions of particular methods are generally outside the scope of this guidebook; such descriptions are available in other Consortium publications that are referenced, where appropriate, throughout this guidebook. Audience for this guidebook includes business-area managers, project managers, and engineers of all disciplines who work together to accomplish the objectives of a business-area organization.

Author: Burkhard, N. et. al.

Sponsoring Organization: VA Center of Excellence for Software Reuse and Tech Transfer

Producing Organization: Software Productivity Consortium Services Corporation

Publication Date: 11/93


Software Reuse

Abstract: This document outlines its purpose as the following: to identify the principal issues surrounding the army's ability to establish software reuse as a significant dimension of its future business; and to unify team Fort Monmouth in its pursuit of its resolution.

Author: Turner, D.J.

Producing Organization: U.S. Army CECOM RDEC

Publication Date: 6/94


Air Force Software Reuse Implementation Plan

Abstract: This plan outlines tasks and actions required to assure software reuse becomes integral to the process of acquiring, designing, and upgrading Air Force systems. In doing so, it provides the vision, strategy, tasks, and milestones for the Air Force software reuse program. The plan identifies tasks and actions that promote reuse for all software development activities and take advantage of reuse opportunities as an alternative to developing new software. The plan applies to all Air Force MAJCOMS, FOA, and HG USAF elements. It addresses software for all Air Force systems and equipment, including, but not limited to, weapons, command and control, intelligence, and management information systems.

Publisher: Department of the Air Force

Producing Organization: Air Force Software Management Division

Publication Date: 9/92


CIM Reuse Program: Design/Coding Guidelines for Reusable Ada Software

Abstract: This document is a revision of the RAPID Center Standards for Reusable Software, 3451-4-012/6.4. It was intended for the use of the DoD Software Warehouse staff to evaluate for quality and completeness, the code, format, syle, and documentation of reusable software components (RSCs) submitted to the DoD Software Warehouse. It presents a comprehensive set of standards and guidelines (collectively called "conventions") for Ada software development, with emphasis on the issues related to software reuse and the operation of the DoD Software Warehouse. Also included is a set of documentation conventions specifically for reusable software. While the presentation is oriented toward Software Warehouse staff, software developers are encouraged to use the document as a reference, particularly the documentation standards in Section 4.

Sponsoring Organization: DoD CIM Reuse Program

Producing Organization: SofTech, Inc.

Publication Date: 1/90


Software Reuse Implentation Guide, Draft

Abstract: This Guide provides the Department of the Navy's Program Executive Officers, Direct Reporting Program Managers, Program Managers, and their staffs guidance on the adoption of software reuse technology. It complements the Department of the Navy Software Reuse Implementation Plan, which describes the responsibilities and plan of action to integrate software reuse into the software development life cycle. This Guide presents the context in which the plan will be implemented, including motivation, background, and definitions.

Publisher: Department of the Navy

Producing Organization: Naval Information Systems Management Center

Publication Date: 3/94


Army Software Reuse Implementation Plan

Abstract: This document provides detailed information necessary for successful implementation of the Army Strategic Software Reuse Plan (ASSRP), which was approved by the Secretary of the Army and provided to the Defense Appropriations Committee in September 1992, in response to Congressional tasking. The scope of this plan is consistent with the ASSRP. It encompasses and further details the ten strategic elements of Software Reuse on which the ASSRP is based, and describes a shift in the way the Army develops software. This shift, or paradigm, will be used to transition existing software developments, where appropriate, and to fully support future Army software developments.

Publication Date: 10/93


Reuse Adoption Guidebook, Version 01.00.03

Abstract: This guidebook is geared for use by organizations to assist them in improving their competitiveness through the adoption and institutionalization of software reuse technology. It identifies how to develop and implement a reuse program so as to take advantage of existing reuse opportunities. It also assists the reader in determining if reuse technology is appropriate to his/her business and organizational circumstances. It prescribes a reuse adoption process and attempts to assist the end user in identifying both near- and long-term needs and actions. The process provides guidance for developing a plan that will put the technology into practice, as well as shows the reader how to address critical institutional barriers, risks, and planning areas to make a reuse effort successful.

Sponsoring Organization: VA Center of Excellence for Software Reuse and Technology Transfer

Producing Organization: Software Productivity Consortium Services Corporation

Publication Date: 11/92


Command Center Domain Model Description, Central Archive for Reusable Defense Software (CARDS), Informal Technical Report

Abstract: This document describes a version of the CARDS (Central Archive for Reusable Defense Software) library model created during Phase 2 of the CARDS Program. This release replaces earlier versions of the document. Its purposes are as follows: to provide the reader with an understanding of what CARDS library models represent and how they are related to domain analysis; to describe how the v2.0 library model is related to the PRISM project; to describe the v2.0 library model; and to describe CARDS plans for the evolution of the library model through the various phases of the PRISM (Portable Reusable Integrated Software Modules) Program.

Author: Baker, C., P. Kogut, and C. Smotherman

Sponsoring Organization: Electronic Systems Center, USAF

Producing Organization: Paramax Systems Corporation

Publication Date: 11/92


Reuse Bibilography

Abstract: This document is a draft that has many handwritten editorial comments. It provides listings of available reports on reuse, as of 1991.

Author: Hess, J.

Publisher: Center for Software Engineering, Quality Support

Publication Date: 9/91


Guidelines for Submissions to Reuse Documents Database (Draft)

Abstract: This document provides information on the reuse document database developed to support the DoD Software Reuse Vision and Strategy. It provides the specific information required for the database, several detailed examples of forms for submittal to the database, and a blank form for submitting information.

Publication Date: 6/93


Data Model for Working Groups

Abstract: This document provides a data model of Applied Expertise's (AE's) internal databases for tracking working groups and related items. This model serves as an input for the building of a relational database at DISA-CIM. The document also provides a draft Entity-Relationship Diagram (ERD) of AE's FileMaker (flat file) databases, modified to support a relational design.

Author: Nassau, D.

Producing Organization: Applied Expertise, Inc.

Publication Date: 1/93


Reuse Document Database

Abstract: This brief document provides background material on the Reuse Document Database, including status, points of contact, and current actions.

Author: Dobbs, V.S., H.F. Joiner, and S.H. Levine

Producing Organization: RAAT

Publication Date: 7/93


ISEC Portability Guidelines

Abstract: This document discusses the issues and tradeoffs that must be made in writing a portable Ada program. The discussions center on three aspects of portability: source modification, program behavior, and safety (compile-time versus execution-time, discovery of implementation differences). The first chapter discusses what portability is, and what is involved in writing a portable Ada program. Each of the remaining chapters discusses portability of the features in the corresponding chapter in the Ada Language Reference Manual [Ada83].

Sponsoring Organization: U.S. Army Information Systems Engineering Command

Producing Organization: SofTech, Inc.

Publication Date: 12/85


Generic Architecture Study

Abstract: This report explores the use of generic architectures as an approach to the development of reusable software in Ada. It focuses specifically on their applicability to the development of Army command and control systems. In that respect it is a further extension of work performed by SofTech on generic architectures for the RAPID program of the Army Information Systems Engineering Command and for the RAPIER system of the Air Force Space Command. The report also gives special attention to the use of the Ada programming language in the development of generic architectures. The report examines the concepts of a generic architecture as well as the requirements of Army command and control systems. It then illustrates the application of the concepts through a "strawman" generic architecture for command and control. The final chapter discusses the activities and issues of importance in the demonstration and validation of this approach to reusable software.

Author: Quanrud, R.B.

Sponsoring Organization: U.S. Army CECOM

Producing Organization: SofTech, Inc.

Publication Date: 1/88


Defense Software Repository System (DSRS) System Security Plan (Working Paper)

Abstract: This document covers the security plan for the Defense Software Repository System (DRSR) Version 5.0, the responsibity for which lies with DISA. The plan specifies system identification, sensitivity of information processed, and system security measures.

Publisher: Defense Information Systems Agency

Publication Date: 3/94


ASSET/CARDS/DSRS Software Reuse Libraries Interoperability Security Document

Abstract: This document focuses on the libraries, respositories, and mechanisms that will provide the Department of Defense with the secure distribution channels it needs to make assets readily available. The intention of this document is to develop a coordinated technical approach to meet the DoD security requirements for an interoperable asset distribution system. Additionally, this document outlines an architecture designed to accomodate the technical recommendations of international, national, and industry standardization groups that are currently working on the protection of national security and proprietary information in heterogeneous distributed systems.

Author: Perry, J.

Publication Date: 8/93


DoD Software Reuse Security Policy Recommendations

Abstract: This document addresses the security concerns of the new reuse capability and includes policy suggestions that will reduce any threats to manageable levels. These recommendations apply to the scenario described in the DoD Software Reuse Initiative Vision and Strategy, detailing the threat and the response to the threat unique to this environment. This is not meant to be a policy document covering the full range of policy decisions that need to be made in a reuse security policy; rather, it is intended to suggest policy in specific areas of security.

Author: Debreceny, S., T.A. Longstaff, and K.S. Nichols

Publisher: Software Engineering Insitute, Carnegie Mellon University

Publication Date: 7/93


Guidelines for Writing Trusted Facility Manuals

Abstract: This manual provides a set of good practices related to the documentation of trusted facility management functions of systems employed for processing classified and other sensitive information. It describes how to configure and install a specific secure system, operate the system in a secure manner, and make effective use of the system privileges and protection mechanisms to control access to administrative functions and databases.

Publisher: National Computer Security Center

Reference Number: NCSC-TG-016 Library No. S239,639, Version 1

Publication Date: 10/92


DSRS Trusted Facility Manual

Abstract: This document provides information on how to configure, install, operate, and use system privileges. It also has descriptions of protection mechanisms to control access to administrative functions and databases, and tells how to avoid errors that would compromise the Defense Software Repository System (DSRS) Trusted Computing Base (TCB) and user security.

Author: Perry, J., et. al.

Publisher: SofTech, Inc.

Publication Date: 8/93


DSRS Security Posture

Abstract: This document is a posture statement for DSRS Version 3.5, which operates on VAX/VMS Version 5.4. It is written to provide the following: an identification of the potential threats to the DSRS, a description of the actions taken to reduce and remove each threat, and a description of other current efforts related to the security of the DSRS.

Author: Coker, G., et. al.

Publisher: SofTech., Inc.

Reference Number: Doc # 1222-04-210/50; Contract #: 62K-RF029C

Publication Date: 1/92


DoD Software Reuse Initiative Technology Roadmap, Version 1.0

Abstract: This document initializes a DoD software reuse investment strategy and identifies both a reuse-oriented process and product technologies. A subset of these technologies is proposed for investment in order to expedite their maturation and broad utilization. Transition of technologies into the software reuse community is recognized as a major concern, but technology transfer investment is not the focus of this document. Certainly the progress of the emerging technologies will need to be tracked; technologies with maturation rates currently assessed to be acceptable may cease to evolve as well, and those technologies in which the DoD invests to accelerate their maturation rate may also require reevaluation. This document contains an analysis of the set of capabilities that are needed to develop a software reuse infrastructure that can support and sustain the implementation of software reuse by means of technologies and tools. The document also addresses the technical dependencies associated with the reuse of both knowledge and other artifacts that facilitate the broad adoption of software reuse. This document's purposes are as follows: identify those technologies that are critical in implementing software reuse within DoD; assess the current and projected maturation of the critical technologies; and recommend investment in specific critical technologies to accelerate their maturation sufficiently to support the DoD software reuse goals in a timely manner.

Publisher: Department of Defense

Publication Date: 10/93


DSRS Risk Mitigation Statement

Abstract: The purpose of this document is to make the Designated Approving Authority (DAA) aware of those security weaknesses identified during NSA's Information Systems Security (INFOSEC) Assessment, Information Systems Security Officer (ISSO) risk management reviews, testing, or certification activities. Additionally, the document will outline the countermeasure(s) employed to mediate each weakness.

Producing Organization: DISO/JIEO/CIM

Publication Date: 3/94


Information Systems Security Assessment of the Defense Software Repository System (DSRS) at the Center for Software Reuse Operations

Abstract: This document presents a report on the Information Systems Security (INFOSEC) assessment that the Information Systems Security Organization (ISSO) conducted on the Defense Software Repository System (DSRS). Major recommendations to improve the INFOSEC posture of the automated information system are: a) develop an overall Security Policy; b) assign a full-time Security Administrator; and c) implement audit trails and audit procedures.

Publisher: The Information Systems Security Organization, NSA

Publication Date: 8/92


Juncture of Education and Training Working Group (JETWG)

Abstract: This brief document outlines the accomplishments and goals of the Juncture of Education and Training Working Group as of July 1994.

Author: Facemire, J.

Publication Date: 7/94


ASSET, CARDS, DSRS Interoperability Status

Abstract: This brief document outlines the interoperability status of ASSET/CARDS/DSRS, and gives an activity graphic for the months of June and May, 1994 (a very general graphic.)

Author: Perry, J.

Publisher: Defense Information Systems Agency

Publication Date: 7/94


Department of Defense Software Reuse Initiative Technology Roadmap, Version 2.0 (Volume 2: Implementation Plan) (Draft)

Abstract: The overall objective of this plan is to accelerate the development of technologies critical to software reuse in order to enable DoD to achieve the potential benefits of reuse in a timely manner. The plan is divided into nine sub-plans, eight of which correspond to the eight recommended technology thrusts in Volume 1, Section 4 of this Roadmap; the ninth is a plan for continued monitoring of the status and evolution of reuse technologies.

Publisher: Department of Defense

Publication Date: 8/94


CARDS Organizational Analysis for Reuse

Abstract: This document presents an outline of CARDS re: its Organizational Analysis for Reuse (COAR). After presenting some information about the organizational challenges to reuse adoption, it discusses COAR as a model for meeting those challenges. It also outlines methods for mitigating risk. Finally, it presents an overview of COAR, with its goals, scheduling, results, benefits, and organizational commitment.

Author: Weisman, D.

Publication Date: 7/94


DoD Software Reuse Initiative (SRI) Progress Report

Abstract: This document provides a progress report on the Software Reuse Business Model (SRBM), Risk Assessment and Mitigation Procedure (RAMP), Component Evaluation Procedure (CEP), and Missile Defense Identification (MDDI), as of October 26, 1994.

Author: Green, C. Ronald, Dr.

Producing Organization: U.S. Army Space and Strategic Defense Command

Publication Date: 10/94


DoD Software Reuse Initiative (SRI) Progress Report

Abstract: This document provides a progress report, as of 9/94, on the Software Reuse Business Model, covering schedule, accomplishments, status, a look ahead, and issues.

Author: Green, C. Ronald Dr.

Producing Organization: U.S. Army Space and Strategic Defense Command

Publication Date: 9/94


Army Common Operating Environment (ACOE) Where We Are and Where We're Going

Abstract: This document provides an outline of COE, including its purpose, objectives, strategies, operating environment, hardware configurations, benefits, and more.

Author: Project Manager, Common Hardware Software

Publication Date: 1/94


CRYSTALLIZE Software Reuse Facility

Abstract: This document discusses the CRYSTALLIZE software reuse facility, which develops, advertises, supports, and distributes Government-owned 'C' and 'C++' software to application developers within the intelligence community. The uniqueness of CRYSTALLIZE lies in the fact that it has a horizontal domain, that is, the software can be used in a broad range of intelligence gathering and processing applications. The document discusses the two ways CRYSTALLIZE helps reduce development and support, the reasons behind its success, and its take on expansion.

Author: Matuschek, G.

Publication Date: 1/94


SRI Program Review, Reuse Technical Working Group, Management Issues Working Group

Abstract: This document outlines the accountability, mission, membership, meetings, working broad issues of the Reuse Technical Working Group and the Management Issues Working Group.

Author: Rosson, D.

Publisher: Defense Information Systems Agency

Publication Date: 7/94


Informal Technical Report for the Software Technology for Adaptable, Reliable Systems (STARS)

Abstract: This paper documents the Central Archive for Reusable Defense Software (CARDS) sponsored Software Reuse Legal Issues Workshop, held in Arlington, VA, 22-25 March 1993. The workshop addressed concerns in the software reuse community regarding perceived legal impediments in establishing and operating a software reuse library. Participating lawyers analyzed and provided answers to posed questions pertaining to liability, contracting, library, supplier, and subscriber. In addition to the specific questions posed, library liability and agreements to reduce those liabilities were discussed as a general topic. These proceeedings are intended for use by managers responsible for formulating or implementing plans of operations for software reuse libraries. It provides an overview of some of the problem elements that must be taken into account and is intended to promote discusssion.

Author: Unknown

Sponsoring Organization: Electronic Systems Center, USAF

Producing Organization: DSD Laboratories, Inc, under contract to Paramax Systems Corp.

Publication Date: 4/93


A Compositional Model for Software Reuse

Abstract: Emerald, a strongly-typed object-oriented language designed for programming distributed applications, provides abstract typing, type conformity, and complete separation of typing from implementation. While Emerald supports type inheritance, it does not support behavior sharing among objects for simplifying distribution. In order to increase Emerald's utility in general-purpose programming, some support for software reuse is needed. Research by the authors has revealed that inheritance-based techniques commonly used in other object-oriented systems for obtaining reuse are inappropriate for Emerald. As an alternative to traditional inheritance, a compositional model, where objects are composed from simpler entities, is proposed, outlined, and analyzed in this report.

Author: Levy, H. and Rajendra Raj

Publisher: University of Washington

Reference Number: UWash-CSE-89-01-004

Publication Date: 3/89


Composition and Reuse in Object-Oriented Languages

Abstract: Significant improvements in software productivity are expected with the development of reusable software using the object-oriented paradigm. Object-oriented languages have several features that directly or indirectly help in software reusability. Their primary abstraction mechanism, the object, typically is a self-contained entity with two major facets: an interface that specifies how other objects may interact with it, and an implementation that consists of data and operations. In traditional object-oriented languages, both object interfaces and implementations are described by the class concept, and new classes are created as extensions of existing classes using the inheritance concept. Some object-oriented languages have also formalized the notion of object substitution based on interface conformance of objects. While classes, inheritance, and conformance support software reuse, this dissertation shows that inadequate definitions and inappropriate interaction of these concepts restricts reuse. Our thesis is that software reuse is improved by (a) dissociating object interfaces and implementations, and (b) separating the concerns of linguistic and environmental factors governing reuse. In our solution, objects are reused via the compatibility of their interfaces, and object implementations are reused via composition, a scheme in which simpler components are combined to form larger components. The language and environment complement each other's support for software reuse. The major contributions of this dissertation include a qualitative analysis of object-oriented reuse paradigms, an attempt to quantify object-oriented reuse, and the design and development of the compositional model for software reuse.

Author: Raj, R.

Publisher: University of Washington, Seattle

Reference Number: UWash-91-03-06

Publication Date: 3/91


Automated Acquisition and Refinement of Reusable Software Design Components

Abstract: The importance of reusing software components in new software developments has long been recognized. A reason for the current low level of software reuse stems from the difficulties of obtaining appropriate components for populating a reuse library. [pp] This thesis presents a framework for a hybrid software design environment that supports the reuse of design schemas and cases. At the heart of this framework is a knowledge-based approach for automating the acquisition and refinement of software components for its reuse library. A prototype system, CAReT, has been implemented to demonstrate the viability of the approach. CAReT is based on a bottom-up, case-based approach to domain analysis, where design cases for existing systems within an application domain are examined to determine common pattern of operations and objects. The correspondences between features are established using domain knowledge, where available. Otherwise the correspondence identification is decided by using a similarity metric to compute the degree of closeness between features. The common features are then abstracted. This same mechanism for determining correspondence underlies CAReT's analogy-based retriever, which retrieves software components that satisfy a reuser's query.

Author: Lee, H.

Publisher: Univeristy of Illinois at Urbana-Champaign, Urbana, IL

Publication Date: 5/92


Integrating 001 Tools Support into the Feature-Oriented Domain Analysis Methodology

Abstract: This report addresses the need for additional tool support for the Feature-Oriented Domain Analysis (FODA) methodology, developed at the Software Engineering Institute (SEI). Previous FODA studies relied on multiple tools to represent the components of a domain model. This report discusses the ability to represent an analyzed domain within the confines of a single support tool. This discussion was based on the transformation of a recently completed domain analysis from a multi-tool, multi-view representation into a single tool which represents the multiple views of a FODA domain model. This report also describes the potential for prototyping of systems using the FODA domain analysis products and the supporting tool.

Author: Krut, R. W.

Publisher: Software Engineering Institute, Pittsburgh, PA

Reference Number: SEI-93-TR-011

Publication Date: 7/93


Reengineering: An Engineering Problem

Abstract: This paper discusses a plan that addresses how the Software Engineering Institute (SEI) may assist the Department of Defense (DoD) in reengineering its large software-intensive systems. This plan is based on a view of reengineering as an engineering problem to improve the cost-effective evolution of large software-intensive systems. This view of reengineering, which takes the whole software engineering process into account, fosters a growth path by leveraging promising emerging software engineering technologies. Reengineering also builds on the industry's improvement in its ability to manage the software engineering process, an accomplishment of SEI work in the Capability Maturity Model (CMM) and its key process areas.

Author: Feiler, P.

Publisher: Software Engineering Insitute, Pittsburgh, PA

Reference Number: SEI-93-SR-005

Publication Date: 7/93


A Reuse-Based Software Development Methodology

Abstract: 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. [pp] 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: l) 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. [pp] 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. [pp] This methodology has never been applied; it will be used in an application redevelopment experiment and then will be improved based on our experience.

Author: Peterson, S and J. Perry; R. Holibaugh; S. Cohen; K. Kang

Publisher: Software Engineering Institute, Pittsburgh, PA

Reference Number: SEI-92-SR-04

Publication Date: 5/92


Joint Integrated Avionics Working Group (JIAWG) Object-Oriented Domain Analysis Methods (JODA)

Abstract: 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.

Author: Holibaugh, R.

Publisher: Software Engineering Institute, Pittsburgh, PA

Reference Number: SEI-92-SR-003

Publication Date: 11/92


Application of Feature-Oriented Domain Analysis to the Army Movement Control Domain

Abstract: This report documents an analysis of the army movement control domain performed by the Software Engineering Institute (SEI) and a team of movement control experts from the Army. This report includes common terminology and requirements extracted from Army doctrine, experts in the field, and movement control systems. The report also describes the potential for prototyping of systems using domain analysis products and the tool support needed.

Author: Krut, R. and A. Peterson; J. Stanley; S. Cohen

Publisher: Software Engineering Institute, Pittsburgh, PA

Reference Number: SEI-91-TR-028

Publication Date: 6/92


A Context Analysis of the Movement Control Domain for the Army Tactical Command and Control System (ATCCS)

Abstract: This report describes the results of the first phase of a domain analysis performed by the SEI's Domain Analysis Project. The report establishes the context and scope of the movement control domain within command and control (C2) systems and in particular, ATCCS. It discusses the purpose of a domain analysis and presents an overview of the method being used to perform the analysis. The report describes both the Army's use of ATCCS in achieving the Army mission and the ATCCS software development strategy. A brief description of Army C2systems lays a foundation for defining movement control and its context in the ATCCS structure. Within this context, the report identifies the key areas within movement control that will be explored during the remainder of the domain analysis. The report also describes the approach for performing the analysis and includes appendices providing additional information about ATCCS, relevant terms, and acronyms.

Author: Cohen, S. and A. Peterson

Publisher: Software Engineering Institute, Pittsburgh, PA

Reference Number: SEI-91-SR-3

Publication Date: 3/91


STARS/Users Workshop: Final Report - Issues for Discussion Groups

Abstract: The STARS (Software Technology for Adaptable, Reliable Systems) Program is focused on providing the DoD software community with a software engineering environment, repository technology, and process models. This STARS Workshop was targeted toward increasing the communication between the STARS Program and the builders of software-dependent systems. This was the first of many public discussion hosted by the STARS Program. This workshop was hosted by the SEI.

Author: Bamberger, J.

Publisher: Software Engineering Insitute, Pittsburgh, PA

Reference Number: SEI-90-TR-32

Publication Date: 9/90


Proceedings of Reuse in Practise Workshop

Abstract: This document is the result of a workshop held in Pittsburgh, PA, 11-13 July 1989. The objective of the workshop was to assess the state of the practise of software reuse. Software reuse practise was evaluated in the following areas: domain analysis, implmentation, software environment support, and management. However, due to the workshop program committee's objective to produce results that were detailed enough to have impact, other software reues topics were not included.

Author: Baldo, J.

Publisher: Software Engineering Institute, Pittsburgh, PA

Reference Number: SEI-90-PROC-REUSE

Publication Date: 4/90


Perspective on Software Reuse

Abstract: This report presents a perspective on software reuse in the context of "ideal" software development capabilities. Software reuse is viewed as a means of achieving-or at least approximating--the idea capabilities. A generic application and development model is proposed for unifying various types of software reuse. The model can be initially formulated as a project family architecture and produced from a domain features analysis. The approach presented in this report is intended to lead to a reuse strategy and methodology for software development.

Author: Perry, J.

Publisher: Software Engineering Institute, Pittsburgh, PA

Reference Number: SEI-88-TR-22

Publication Date: 9/88


Phase 1 Testbed Description: Requirements and Selection Guidelines

Abstract: The Application of Reusable Software Components Project has constructed a reuse testbed for conducting software engineering experiments in software reusability. The hardware and system software of the testbed will provide a distributed computing environment with file-server capability for the storage of reusable components and other artifacts of the development process. The testbed will support a variety of domain-independent and domain-dependent reusable components. The testbed will also support tools that foster reuse. This document contains the requirements and selection criteria for the testbed hardware, software, reusable resources, and an environment. For each of these four testbed resources, the requirements are grouped into five areas: support of experiments, maximization of experience and reusability, applicability to problem domains, acceleration of technology transition, and advancing the state of the practice in reuse.

Author: Perry, J and R. Holibaugh

Publisher: Software Engineering Institute

Reference Number: SEI-88-TR-13

Publication Date: 9/88


A Hypertext Sytem for Integrating Heterogeneous, Autonomous Software

Abstract: Hypertext is a simple concept for organizing information into a graph structure of linked container objects. This paper examines issues involved in applying hypertext concepts to the integration of heterogeneous, autonomous software repositories, and presents a solution called the Distributed Hypertext System (DHT). Based on a hypertext data model and client-server architecture, DHT features powerful modeling capabilities, integration of heterogeneous, pre-existing repositories, update with concurrency control, and full local autonomy.

Author: Noll, J. and W. Scacchi

Publisher: University of California at Irvine, Irvine, CA

Reference Number: UCIrv-94-PROC-ISS-005

Publication Date: 1/94


Economics of Software Reuse Revisited

Abstract: The field of software reuse is attracting increasing attention from academics and practitioners who recognize the economies to be gained from reducing duplication of software development effort. However, development for reuse requires additional costs that are difficult to justify under a single-project management view. Since reuse benefits accrue over time and across a number of projects, project management decision making must shift to a multi-project, long-term view and thus changes management information requirements. In particular, given scarce resources management needs to be able to assess whether software reuse will have the kind of return that warrants the up-front investment in reusability. This paper evaluates and extends the pioneering contributions of other authors in the area of cost-benefit analysis for software reuse. In addition to Incorporating timing and risk inherent in future reuse opportunities, the analysis includes reuse costs and benefits that were not accounted for in previous models.

Author: Ruth A. Malan, Kevin Wentze

Publisher: University of California at Irvine: Dept. of Information & Computer Science

Reference Number: UCIrv-93-PROC-ISS-011

Publication Date: 1/93


Re-BART: Bay Area Roundtable Series on Reuse and Reengineering

Abstract: In spring 1992, Leon J. Osterweil of the University of California, Irvine assembled a "steering committee" in the San Francisco Bay area to plan a series of Bay Area Roundtable (BART) meetings on a software topic of interest to Silicon Valley software developers. This was an attempt to restart the BART sessions after a previous series had wound down. The group agreed upon on reuse and reengineering as a timely topic that would be interesting to a large number of developers in the commercial and government contract software communities. Software productivity improvements are important to all software development organizations and reuse, with it's promise of improvements in productivity, time-to-market, and quality, has been receiving increasing levels of attention. Several companies in the Bay area had started efforts in software reuse as research or development productivity projects. Reengineering was being explored as a way to improve software maintainability and as a way to find reusable software components. The goal of the BART series on reuse and reengineering was to increase understanding of issues and successes in the subject and to build a local community of practitioners knowledgeable in the area of reuse and reengineering. The selected meeting format was a few short presentations or panel discussions with plenty of time for discussion. Martin Griss of Hewlett-Packard Company agreed to assemble an agenda for a series of meetings and to be the kickoff speaker for the first which was planned for August. This paper provides a summary of the 7 meetings to date.

Author: Brodbeck, D. and K. Wentzel

Publisher: University of California at Irvine Computer Science Dept., Irvine, CA

Reference Number: UCLIrv-93-PROC-ISS-08

Publication Date: 8/93


An Approach to Improve the Effectiveness of Software Retrieval

Abstract: This paper introduces an approach for software retrieval based on partial natural language analysis of both queries and descriptions of software components. Retrieval is accomplished by matching the semantic structures associated to both the query and the natural language descriptions of software components in a knowledge base. Semantic structures are automatically created by identification of thematic roles in the user input through the application of syntactic techniques and some heuristics. A courseware development environment to be used in the evaluation of the retrieval system is also introduced. Related work in the area of reuse systems and on the application of natural language processing techniques in information retrieval systems is discussed.

Author: Girardi, M. and B. Ibrahim

Publisher: University of California at Irvine: Dept. of Information & Computer Science

Reference Number: UCIrv-93-PROC-ISS-009

Publication Date: 9/93


Reusable Data Flow Diagrams

Abstract: While the reuse of code and interfaces has been the primary focus in object-oriented system design, the reuse of large scale designs has been ignored. In this paper, we present a method for structured reuse of large scale designs using reusable data flow diagrams. Data flow diagrams may be closely linked to class hierarchies in an object-oriented language. In addition to composing and clustering data flow diagrams, we show how successively more specialized data flow diagrams can be organized into an inheritance hierarchy. We show the use of this technique in the design of an object-oriented scheduling subsystem written in C++ that is part of the Choices object-oriented operating system.

Author: Islam, N. and R. Campbell

Publisher: University of Illinois at Urbana-Champaign: Department of Computer Science

Reference Number: UIUC-CS-92-1770

Publication Date: 12/92


Refactoring Object-Oriented Frameworks

Abstract: This thesis defines a set of program restructuring operations (refactorings) that support the design, evolution and reuse of object-oriented application frameworks. [pp] The focus of the thesis is on automating the refactorings in a way that preserves the behavior of a program. The refactorings are defined to be behavior preserving, provided that their preconditions are met. Most of the refactorings are simple to implement and it is almost trivial to show that they are behavior preserving. However, for a few refactorings. one or more of their preconditions are in generate undecidable. Fortunately, for some cases it can be determined whether these refactorings can be applied safely. [pp] Three of the most complex refactorings are defined in detail: generalizing the inheritance hierarchy, specializing the inheritance hierarchy and using aggregations to model the relationships among classes. These operations are decomposed into more primitive parts, and the power of these operations is discussed from the perspectives of automatability and usefulness in supporting design. [pp] Two design constraints needed in refactoring are class invariants and exclusive components. These constraints are needed to ensure that behavior is preserved across some refactorings. This thesis gives some conservative algorithms for determining whether a program satisfies these constraints, and describes how to use this design information to refactor a program.

Author: Opdyke, W.

Publisher: University of Illinois at Urbana-Champaign: Department of Computer Science

Reference Number: UIUC-CS-92-1759

Publication Date: 6/92


Domain-Based Program Synthesis Using Planning and Derivational Analogy

Abstract: Constructing an automatic program synthesis system, that can accept a high-level description of a problem for an arbitrary domain, and generate code for the problem completely automatically is pragmatically impossible. However, by concentrating on a well-defined domain, it is possible to incorporate sufficient knowledge within a system, so that it can communicate with an end-user at the level of his application, and generate a program automatically from a problem specification. Such knowledge-based systems often employ a catalog of transformational rules that progressively refine an abstract specification into a concrete implementation. A major research issue in such systems is how to increase the efficiency of the systems by controlling the application of rules and avoiding repetitive computations. [pp] In this thesis, we propose a domain-based, integrated framework for program synthesis that emphasizes the reuse of software components and past experience in solving problems. A crucial component of the framework is a concept dictionary that contains a description of domain related components. This forms a basis for communicating with a user in a high-level, application-oriented terms; for constructing generic, problem-solving rules, and for reasoning by analogy. The other components of the framework include a library of reusable subroutines, cliches, and derivation histories of previously solved problems, a layered rulebase, a hierarchical planner, and an analogical reasoner based on Carbonell's derivational analogy paradigm. [pp] The planner uses the rulebase and the library to decompose a given problem in a top-down manner and synthesize a plan for solving it. The layered structure of the rule-base ensures that efficient plans are preferred over inefficient ones, and the changes needed to synthesize programs for a different domain are minimal. The analogical reasoner complements the role of the planner. It uses a set of heuristics to retrieve a problem from the derivation history library that is analogous to a current problem, and replays the derivation of the retrieved problem to synthesize a program for the current problem. A solved problem is stored back into the derivation history library, and may be used to solve a different problem in a future context. [pp] A prototype system, APU, based on the above framework has been implemented for the domain of UNIX programming. We describe a set of experiments designed to test the performance of APU, and provide empirical results demonstrating the feasibility and usefulness of the approach.

Author: Bhansali, S.

Publisher: University of Illinois at Urbana-Champaign: Department of Computer Science

Reference Number: UIUC-CS-91-1701

Publication Date: 5/91


Evaluation and Validation (E&V) Guidebook

Abstract: This document is a product of the Ada Programming Support Environment (APSE) Evaluation and Validation (E&V) Task sponsored by the Ada Joint Program Office. It is one of a pair of companion documents known as the E&V Reference System, consisting of the E&V Reference Manual and the E&V Guidebook. The purpose of the Guidebook is to provide a collection of information to support a variety of users. It should help users to gain an overall understanding of APSE assessment, in particular, the selection of appropriate E&V procedures, the interpretation of test results, and the integration of analyses and results; apply the various E&V procedures and techniques developed under E&V Task sponsorship; and find the primary sources for those E&V procedures and techniques not developed by the E&V Task or not fully explained within the Guidebook (due to space or other constraints). The Reference Manual includes many "pointers" to sections in the Guidebook and other documents that describe E&V techniques.

Author: Clark, Peter G. and Bard S. Crawford

Publisher: E&V Team/DoD

Reference Number: TASC #: TR-5234-4

Sponsoring Organization: WPAFB

Producing Organization: The Analytic Sciences Corporation (TASC)

Publication Date: 2/91


Implementing the DOD-STD-2167 and DOD-STD-2167A Software Organizational Structure in Ada

Abstract: The purpose of this report is to present several different solutions to the problem of compliant implementation of the software organizational elements described by DOD-STD-2167 and 2167A, Defense System Software Development. The intended audience for this report are manages and technical staff members who find themselves with the following responsibilities: 1- they must decide how to organize their design, coding and testing efforts to effectively manage them and effectively present them in design documentation and design and testing reviews; and 2- they must comply with DOD-STD-2167 or 2167A.

Author: ACM-SIGAda, SDSWG Software Organization Subgroup

Publisher: ACM-SIGAda

Publication Date: 3/88


Rationale for the DoD Requirements and Design Criteria for the Common APSE Interface Set (CAIS)

Abstract: The purpose of this document is to provide, for each requirement and design criteria in the RAC, any or all of the following as appropriate: explanations or clarifications of KIT/KITIA intent; exposition of alternatives considered and the reasoning for the requirement or design criterion in the RAC; examples; and identification of known constraints on CAIS specifications and implementations. The structure of this rationale document is identical to that of the RAC document of the same date.

Publisher: KIT/KITIA

Sponsoring Organization: AJPO

Producing Organization: KIT/KITIA

Publication Date: 10/86


Public Review Draft Specification of the Common APSE Interface Set (CAIS)

Abstract: This document includes paper copies of viewgraphs for presentations given at the CAIS Specification Public Review. Topics covered include General Information on the Review, CAIS Background, CAIS Introduction, Introduction to Node Model/Structural Nodes, Introduction to File/Device Nodes, Introduction to Process Nodes, CAIS Node Model/Structural Nodes, CAIS File Nodes, CAIS Process Nodes, CAIS Device Nodes, and CAIS Utilities.

Author: AJPO; KIT/KITIA; CAISWG

Publisher: AJPO; KIT/KITIA; CAISWG

Publication Date: 9/83


The Project Management Experiment

Abstract: This report covers a program management (PM) experiment, one of six experiments that examine different functional areas of Ada programming environments. The PM experiment was designed as part of the Evaluation of Ada Environments Project. This report describes the environment-independent part of the experiment: the activities covering the functional area, the evaluation criteria, and an experiment scenario to be performed on different environments. The experiment, as it stands, has been validated through internal and external review and through application to several environments that support project management.

Author: Feiler, Peter H. and Roger Smeaton

Publisher: CMU-SEI

Reference Number: SEI #: CMU/SEI-88-TR-7; SEI Joint Program Office #: ESD-TR-88-008

Sponsoring Organization: SEI Joint Program Office

Producing Organization: CMU-SEI

Publication Date: 7/88


Annual Technical Report for Ada Embedded Systems Testbed Project

Abstract: The purpose of the Software Engineering Institute's (SEI) Embedded Systems Testbed (AEST) Project is to investigate some of the critical issues in using Ada for real-time embedded applications, particularly the extent and quality of the run-time support facility provided by Ada implementations. The project's objective has been to generate new information about using Ada in real-time embedded systems. This information is in the form of benchmark test results, higher level experiment results, and lessons learned in designing and implementing real-time applications in Ada. This technical report provides an overview of the results produced in the first year of the project (through 30 September 1987). Details of these results are contained in other, referenced technical reports.

Author: Weiderman, Nelson H., et al.

Publisher: CMU-SEI

Reference Number: SEI #: CMU/SEI-87-TR-31; SEI Joint Program Office #: ESD-TR-87-194

Sponsoring Organization: SEI Joint Program Office

Producing Organization: CMU-SEI

Publication Date: 12/87


Object World Conference Notes

Abstract: These proceedings contain paper copies of viewgraphs for presentations given during the course of the trade show. The briefing viewgraphs are arranged by day and time of presentation. Volumes 1, 2 and 3 (Tuesday, Wednesday, and Thursday) contain viewgraphs for the several presentations for each of the following topics: Introduction to Object Technology; Objects in Business; Technology of Objects; Distributed Computing with Objects; Software Developers; Object Technology: The Journey So Far and What Lies Ahead; and Financial Services; OMG: Building the Object Technology Infrastructure; Object Technology: Roadmap for the Future; Transportation; CORBA & COSS Up Close; Town Meeting: Distributed Computing Using Object Technology; and Telecommunications.

Publisher: Object World

Publication Date: 8/95


Proceedings of the Second International Workshop on Software Reusability: Advances in Software Reuse

Abstract: These proceedings contain the best 20 papers of 93 submitted for consideration to the reviewers. Paper titles include "Uniformity and Invariance in Support of Reuse," "Design as Evolution and Reuse," "A Constructive Approach to Reuse of Conceptual Components," "Object-Oriented Module Interconnection Languages," "The Generic Reusable Component: An Approach to Reuse Hierarchical OO Designs," "Polymorphic Components for Monomorphic Languages," "Reuse-in-the-Large: Modeling, Specification, and Management," "LILEANNA: A Parameterized Programming Language," "The REBOOT Environment," "Retrieval of Reusable Components in a Development Information System," "On the Retrieval of Reusable Software Components," "SRSGEN -- A Software Reuse Tool for Large Scale Applications," "Experiences from Application of a faceted Classification Scheme," "The Reuse Capability Model: A Basis for Improving an Organization's Reuse Capability," "Regression Analysis of Reusable Program Components," "Performance Considerations in Object-Oriented Reuse," "A Reuse Metrics and Return on Investment Model," "Enhanced Reuse with Group Decision Support Systems," "People-Oriented Software Reuse: The Very Thought," "Experiences from Software Reuse in Industrial Process Control Applications," and "A Positive Experience with Software Reuse Supported by a Software Bus Framework."

Author: Prieto-Diaz, Ruben and William B. Frakes

Publisher: IEEE Computer Society Press

Reference Number: IEEE Press Order #: 3130

Publication Date: 3/93


Object World Conference Notes

Abstract: These proceedings contain paper copies of viewgraphs for presentations given during the course of the trade show. The briefing viewgraphs are arranged by day and time of presentation. Volumes 1, 2 and 3 (Tuesday, Wednesday, and Thursday) contain viewgraphs for the several presentations for each of the following topics: Introduction to Object Technology; Objects in Business; Technology of Objects; Distributed Computing with Objects; Software Developers; Object Technology: The Journey So Far and What Lies Ahead; and Financial Services; OMG: Building the Object Technology Infrastructure; Object Technology: Roadmap for the Future; Transportation; CORBA & COSS Up Close; Town Meeting: Distributed Computing Using Object Technology; and Telecommunications.

Publisher: Object World

Publication Date: 8/95


Object World Conference Notes

Abstract: These proceedings contain paper copies of viewgraphs for presentations given during the course of the trade show. The briefing viewgraphs are arranged by day and time of presentation. Volumes 1, 2 and 3 (Tuesday, Wednesday, and Thursday) contain viewgraphs for the several presentations for each of the following topics: Introduction to Object Technology; Objects in Business; Technology of Objects; Distributed Computing with Objects; Software Developers; Object Technology: The Journey So Far and What Lies Ahead; and Financial Services; OMG: Building the Object Technology Infrastructure; Object Technology: Roadmap for the Future; Transportation; CORBA & COSS Up Close; Town Meeting: Distributed Computing Using Object Technology; and Telecommunications.

Publisher: Object World

Publication Date: 8/95


Third International Conference Software Reuse: Advances in Software Reusability

Abstract: These proceedings contain over 20 papers submitted for consideration to the reviewers. Paper titles include "Systematic Software Reuse: A Paradigm Shift," "An Assessment of Reuse Technology After Ten Years," "Maximizing Reuse During Reengineering," "Automatic Indexing of Software Artifacts," "Learning the Semantic Similarity of Reusable Software Components," "Reuse of Software Process and Product Through Knowledge-Based Adaptation," "Practical Software Reuse: An Interim Report," "Reuse-Driven Approach for Rapid Telephone Service Creation," "A Prototype Domain Modeling Environment for Reusable Software Architectures," "An Architecture-Driven, Business-Specific, and Component-Based Approach to Software Engineering," "DRACO-PUC: A Technology Assembly for Domain Oriented Software Development," "The Library Scaling Problem and the Limits of Concrete Component Reuse," "Reducing Business and Legal Risks in Software Reuse Libraries," "The Use of Encryption to Ensure the Integrity of Reusable Software Components," "Measuring Software Reusability," "Reuse Level Metrics," "On Tight Performance Specification of Object-Oriented Software Components," "Creating Domain Specific Libraries: A Methodology and Design Guidelines," "Domain Modeling for Reuse," and "The Design of Object-Oriented Software with Domain Architecture Reuse."

Author: Frakes, William B.

Publisher: IEEE Computer Society Press

Reference Number: IEEE Press Order #: 6632-02

Publication Date: 11/94


Reuse '95: Making Reuse Happen -- Factors for Success

Abstract: These proceedings are arranged into three sections, each with several chapters: PLENARY PAPERS [chapters 1- Making Reuse an Engineering Reality at Raytheon, 2- Integrating Software Reuse Into a Specific Software Engineering Course, 3- Incremental Transformation Based On Domain Analysis For Designing Reusable Components, 4- An Analysis of Organizational Success Factors For Software Reuse, 5- Choosing an Organizational Structure for Software Reuse: Case Studies of Seven Organizations], POSTER SESSIONS [chapters 1- US Air Force/Comprehensive Approach to Reusable Defense Software's (CARDS) Technology Transition Program: Reuse Partnerships, 2- A Flexible Approach to Constructing Virtual Reuse Libraries, 3- EFCS: Representing Software Engineering Domains, Systems, and Components, 4- A Quantitative Measure of Reusability, 5- A Short High School Course in Software Engineering Using Ada, 6- Characterizing Object-Oriented Software for Reusability in a Commercial Environment, 7- Software Risk Assessment & Mitigation Procedure (RAMP), 8- Viewpoint Oriented Domain Analysis, 9- Automatic Generation of a Viewpoint Based on Domain Model from Classification of Requirements], and WORKSHOP RESULTS [chapters 1- Megaprogramming in the Software Engineering Curriculum, 2- Reuse Education in DoD Schools, 3- Software Reuse Metrics and Economics, 4- Characteristics of a Good Architecture, 5- A Framework for Reuse Technology Transfer, 6- Value-Added Library Services, 7- Characteristics of a Domain Model, 8- Policies, Laws, and Regulations Affecting Software Reuse in DoD].

Publisher: Reuse '95

Publication Date: 8/95


OOPSLA '95 -- Tenth Annual Conference on Object-Oriented Programming Systems, Languages, and Applications

Abstract: These proceedings contain papers arranged by session: Session 1- Design, Analysis, and Methods ("Extending the Statechart Formalism: Event Scheduling and Disposition," "Object-Oriented State Machines: Subclassing, Composition, Delegation, and Genericity," "Lessons from the Experiences of Leading-Edge Object Technology Projects in Hewlett-Packard"), Session 2- Environments ("The Self-4.0 User Interface: Manifesting a System-Wide Vision of Concreteness, Uniformity, and Flexibility," "Using a Protoype-Based Language for User Interface: The Newton Project's Experience," "Annotating Objects for Transport to Other Worlds"), Session 3- Implementation and Types A ("Type Feedback vs. Concrete Type Inference: A Comparison of Optimization Techniques for Object-Oriented Languages," "Profile-Guided Receiver Class Prediction," "Bidirectional Object Layout for Separate Compilation"), Session 4- Types and Implementation B ("Minimizing Row Displacement Dispatch Tables," "Subtypes vs.Where Clauses: Constraining Parametric Polymorphism," "Sound Polymorphic Type Inference for Objects"), Session 5- Theory and Semantics ("An Algebraic Semantics of Subobjects," "Modular Reasoning in the Presence of Subclassing," "On the Semantic Diversity of Delegation-Based Programming Languages"), Session 6- Language Design ("Subject-Oriented Composition Rules," "How and Why to Encapsulate Class Trees," "A Reflective Model for First Class Dependencies"), and Session 7- Reflective Protocols ("A Metaobject Protocol for C++," "Compiling Away the Meta-Level in Object-Oriented Concurrent Reflective Languages Using Partial Evaluation," "Towards a Methodology for Explicit Composition of Metaobjects").

Publisher: ACM SIGPLAN

Reference Number: SIGPLAN #: SIGPLAN Notices Volume 30, Number 10

Publication Date: 10/95


Department of Defense Software Reuse Initiative Operational Procedures

Abstract: This report addresses the definition and development of processes required for operation of the Software Reuse Initiative. Initial guidelines for the program were established by the Program Manager, Service and Agency Focal Points, and other designated key individuals; it was decided during a planning session that SRI processes were applicable to different parts of the acquisition life-cycle. Processes applied to the areas of Product Life-Cycle; Planning, Budgeting, Tracking, and Reporting; the Coordination Process; and Process Definition & Improvement.The program principles then prioritized the processes and defined the time frame within which it would be reasonable to complete the definition of the process itself. The specifics of each process are the essence of this document. Only completely defined processes are included in this edition; as more processes are defined, they will be included in an update of this document.

Publisher: CACI

Sponsoring Organization: DISA-SRI

Producing Organization: CACI

Publication Date: 8/95


Analysis/Report of Submitted DOD Service and Agency Plans

Abstract: Copies of the Software Reuse Plans were requested from all Services and Agencies involved in the Software Reuse Initiative (SRI). The Department of the Navy (DON) was the only activity that provided plans for analysis. The DON provided the DON Software Reuse Plan and Software Reuse Guide. Analysis of these documents is provided in this report.

Publisher: CACI

Sponsoring Organization: DISA-SRI

Producing Organization: CACI

Publication Date: 9/95


Software Reuse Initiative Reuse Policy Recommendations Document

Abstract: This Reuse Policy Recommendations Document is intended to provide a mechanism for identifying factors that had positive impacts on efforts to transition to software reuse-based processes for engineering, management, and acquisition throughout Government and industry. DOD software reuse policies and plans are reviewed to determine if they have included these factors, and if it is appropriate to include the factors.

Publisher: CACI

Sponsoring Organization: DISA-SRI

Producing Organization: CACI

Publication Date: 9/95


Department of Defense Software Reuse Initiative Organizational Structure and Relationship Report

Abstract: This report addresses management issues associated with providing orderly and logical direction to the Software Reuse Initiative (SRI). The scope of the SRI spans the entire breadth of the DOD. It is intended to cover every Service and Agency and address all of the systems built and maintained by the DOD that are software-intensive: information systems, Command, Control, Communications and Intelligence (C3I) systems, and weapons systems. Formation of the SRI Program Management Office (PMO) was one positive management action taken by the Department of Defense (DOD). Unfortunately the SRI PMO does not have the appropriate support structure to provide the program with the single focus necessary to accomplish its mission. Five major issues resulting from the current organizational structure providing management direction to the SRI are 1- the Reuse Executive Steering Committee (RESC) membership has not been functioning at an appropriate level, 2- the PMO has responsibility for , but not authority over, the SRI, 3- the working groups operate in an ad hoc fashion, 4- the committee structure is too overlapping, 5- the working groups do not address issues identified by SRI stakeholders. This report proposes organizational realignment that is in concert with the March 1994 Report to Congress, "DOD Software Reuse Initiative."

Publisher: CACI

Sponsoring Organization: DISA-SRI

Producing Organization: CACI

Publication Date: 9/95


Department of Defense Software Reuse Initiatvie Operational Management Plan

Abstract: The overall objective of this plan is to define the DOD's tactical approach for facilitating early reuse successes and leveraging them as the foundation for migrating to a reuse-driven, product-line approach throughout the DOD.

Publisher: CACI

Sponsoring Organization: DISA-SRI

Producing Organization: CACI

Publication Date: 9/95


Department of Defense Software Reuse Initiative Strategic Plan for FY96

Abstract: This plans defines an overall DoD Software Reuse Initiative that has a coordinated approach among the Services, Agencies, and SRI Program Management Office (PMO); defines the roles and responsibilities of all stakeholders; provides a process for identifying duplication of effort and gaps in the required infrastructure; and has an incremental strategy for the adoption of systematic reuse. This plan is structured around the following major thrusts: 1- Implement a Product-Line Approach (restructure the way DoD organizations do business by adopting and practicing a product-line approach to systems acquisition, development, and life-cycle support), 2- Develop a Reuse-Based Software Systems Engineering Paradigm (develop and maintain a technical base which enables a reuse-based software and systems engineering paradigm for systems acquisition, development and life-cycle support), 3- Remove Barriers to Reuse (identify and remove the non-technical barriers, such as legal, contractual, economic, and organizational barriers, which inhibit the product-line aproach to acquisition, development,and life-cycle support), 4- Quicken Technology Transfer (develop appropriate partnerships and processes, product, and service solutions for speeding the adoption and institutionalization of reuse), and 5- Make Successes Apparent (publicize reuse successes and provide sufficient information on reuse to promote reuse awareness).

Publisher: CACI

Sponsoring Organization: DISA-SRI

Producing Organization: CACI

Publication Date: 9/95


Object Technology -- The journey so far... and what, perhaps, lies ahead

Abstract: This document contains paper viewgraphs from a presentation on object technology, including a section on software reuse.

Author: Cook, Colin

Publisher: Citicorp

Publication Date: 11/95


Proceedings of the Conference on Ada Applications and Environments

Abstract: These proceedings provide the text of papers presented at the conference. Papers are arranged by topic: Ada Run-Time Models ("Design of an Ada Run-Time System," "An Applications Programmers Guide to Ada Tasking," "A Capability Architecture for Ada," "An Efficient Evaluation Stack for Ada Tasking Programs"), Ada Programming Environments and Tools ("Towards a KAPSE Database,"An Ada Environment for Programming-in-the-Large," "A Methodology for the Design of Ada Transformation Tools in a DIANA Environment"), Applications and the Use of Ada ("On the Use of Text_I/O on Interactive Terminals," "Developing an Ada to CMS-2 Translator," "Ada as a Programming Design Language for a Telematic Service Project"), Methodologies for Ada ("Debugging Ada Tasking Programs," "Four Uses for Derived Types and a Complication," "An Overview of Anna, A Specification Language for Ada," "Function-Level Programming in Ada"), and Distributed Implementations ("A Network Operating System Model for Ada Tasking," "Communication Between Ada Programs," "Four Approaches to Partitioning Ada Programs for Execution on Distributed Targets").

Publisher: IEEE Computer Society Press

Reference Number: ISBN #: 0-8186-0590-1; IEEE Order #: 590

Publication Date: 10/84


Users' Directory of Computer Networks

Abstract: This directory indexes networks on the government agency networks ARPANET, MILNET, NSFNET, SPAN, HEPNET, and ESnet; the user-formed networks CSNET, BITNET, USENET/UUCP, THEnet; descriptions of the commercial public data networks GTE Telenet, TYMNET.

Author: La Quey, Tracy

Publisher: IITRI

Sponsoring Organization: IITRI

Producing Organization: University of Texas at Austin

Publication Date: 7/88


Users' Directory of Computer Networks

Abstract: This directory indexes networks on the government agency networks ARPANET, MILNET, NSFNET, SPAN, HEPNET, and ESnet; the user-formed networks CSNET, BITNET, USENET/UUCP, THEnet; descriptions of the commercial public data networks GTE Telenet, TYMNET.

Author: LaQuey, Tracy

Publisher: IITRI

Sponsoring Organization: IITRI

Producing Organization: University of Texas at Austin

Publication Date: 7/88


Understanding the Implications of Selling Rights in Software to the Defense Department: A Journey Through the Regulatory Maze

Abstract: This article of the Software Licensing Project of the SEI examines problems related to DoD procurement policy as reflected in the DoD acquisition regulations, and ways in which these problem areas might result in unexpected disadvantages to both the government and industry. Issues related to funding of software development, treatment of technical data and documentation, the concept of unlimited rights, the making of derivative works and other modifications of software, and the interface between DoD acquisition policy and intellectual property laws (such as copyright and trade secret law) are discussed. The article serves to catalogue potential problems that might arise under the DoD acquisition regulations.

Author: Samuelson, Pamela

Publisher: CMU-SEI

Reference Number: CMU-SEI #: SEI-86-TM3

Sponsoring Organization: DoD

Producing Organization: CMU-SEI

Publication Date: 3/86


Software and System Warranty Issues and Generic Warranty Clause

Abstract: This report describes how to effectively include software issues into a system warranty. The report includes a generic system warranty clause, with a description of the rationale for each paragraph in the clause. The clause will have to be tailored to the circumstances of the system, and some tailoring considerations are described. There is also a description of the important legal, technical, and administrative concerns that are directly related to the warranty issues. The report describes the need for such a systems warranty, and includes firm recommendations on how to use such a warranty to improve the quality of the delivered system.

Author: Druffel, Larry, et al.

Publisher: CMU-SEI

Reference Number: CMU-SEI #: CMU/SEI-87-TR-4; SEIJPO #: ESD-TR-86-104

Sponsoring Organization: SEI Joint Program Office

Producing Organization: CMU-SEI

Publication Date: 6/87


Proposal for a New "Rights in Software" Clause for Software Acquisitions by the Department of Defense

Abstract: This report recommends three distinct regulatory strategies for addressing difficulties the DoD has been experiencing with respect to legal issues related to software acquisitions. First, the report reiterates the Software Licensing Project's earlier recommendation that the DoD adopt the proposed Federal Acquisition Regulation (FAR) data rights provisions instead of the proposed revisions to the DoD supplement to the FAR (DoD FAR SUPP). In the event that the DoD chooses to adopt a data rights procurement policy different from that found in the data rights provision of the proposed FAR, this report recommends that the DoD adopt a separate "Rights in Software" clause for software acquisitions, rather than continuing the present practice of handling software procurements under the "Rights in Technical Data" clause. Reasons in support of a separate acquisition policy are offered here, as well as a beginning model for the "Rights in Software" clause. In the event that the DoD elects to retain the procurement format found in the DoD FAR SUPP, this report offers several concrete recommendations for changes to those regulations that should result in a procurement policy that more effectively meets the mission needs of the DoD.

Author: Samuelson, Pamela, Kevin Deasy, and Anne C. Martin

Publisher: CMU-SEI

Reference Number: CMU-SEI #: CMU/SEI-86-TR-2; SEIJPO #: ESD-TR-86-203

Sponsoring Organization: SEI Joint Program Office

Producing Organization: CMU-SEI

Publication Date: 9/86


C2MUG Software Catalog

Abstract: This catalog lists the software programs available to units and individuals of the Command and Control Microcomputer Users' Group (C2MUG). These programs have been provided to our software library by various C2MUG users. The catalog is numbered and divided into sections. Suggested uses and users are given for each program.

Publisher: C2MUG

Publication Date: 1/89


Faceted Classification and Reuse Across Domains

Abstract: This paper proposes an approach to facilitate reuse across domains. The approach draws from concepts in domain analysis and faceted classification. The proposal consists of, first, using domain analysis to derive faceted classification schemes of domain specific collections. Then, the next step is to derive a global faceted scheme that relates the domain specific vocabularies. A global scheme allows users to identify and select components from different application domains and, thus, increases their potential for reusability.

Author: Prieto-Diaz, Ruben

Publisher: GTE Laboratories, Inc.

Publication Date: 1/89


Coming to Terms with Terminology for Software Reuse

Abstract: There are problems with the use of many of the terms used in software engineering when applied specifically to reuse. Three terms of particular interest, taxonomy, software, and domain analysis and some problems with their usage are discussed. The specific problems are generalized and several solutions are given, the most important being the introduction of the concept of a reuse process model to provide context and an overall view of the potential areas of discourse in reuse. Several new terms are proposed for future use as well as definitions that are meaningful in the context of software reuse.

Author: Peterson, A. Spencer

Publisher: CMU-SEI

Sponsoring Organization: DoD

Producing Organization: CMU-SEI

Publication Date: 10/89


Department of Defense Software Master Plan

Abstract: This document consists of two volumes, a "Plan of Action" volume and a "Background" volume, and provides a consolidated approach for addressing the challenges presented to the DoD today by the escalating development, utilization, and cost of software in our defense systems. It identifies specific areas for improvement in research, development, test, deployment and maintenance of software in defense systems, including mission critical computer systems, automated information systems, scientific and engineering systems, and weapons systems. it also identifies feasible concrete actions to accomplish these improvements.

Author: Defense Acquisition Board-Acience and Technology Committee-Software Working Group

Publisher: DoD

Publication Date: 2/90


Catalogue of Ada Runtime Implementation Dependencies

Abstract: The main goal of this catalogue is to be the one place where all the areas of the Ada Reference Manual (RM) that permit implementation flexibilities can be found. The Ada Runtime Environmant Working Group (ARTEWG) has analysed the RM and other associated documents, such as the Ada Implementor's Guide, to find those areas where the language definition has left the implementation details up to the Ada compilers that implement them.

Publisher: ACM-SIGAda-ARTEWG

Publication Date: 11/86


Quality Characteristics and Metrics for Reusable Software (Preliminary Report)

Abstract: A report defining a set of quality characteristics of software, providing a summary of software metrics that are useful in measuring quality characteristics for software products. The metrics are useful in assessing the reusability of software products.

Author: W. Salamon and D. Wallace

Publisher: National Institute of Standards & Technology

Reference Number: PB94-203-437

Producing Organization: National Institute of Standards & Technology

Publication Date: 6/94


Reuse Economics Spreadsheet Model User Manual Version 3.00.08

Abstract: A user manual for version 3 of the Reuse Economics Spreadsheet Model tool, that provides automated support for performing economic analyses of various software reuse strategies. The tool is implmented on version 4.0 of the Micorsoftware Excel spreadsheet. You can operate it using either a Macintosh or an IBM PC. It provides both spreadsheet and graphics capabilities.

Publisher: Software Productivity Consortium - SPC

Reference Number: AD-A267-712

Producing Organization: Software Productivity Consortium - SPC

Publication Date: 7/93


Industry Versus DoD: A Comparative Study of Software Reuse

Abstract: Software reuse is a longtime practiced method. The technical issues, such as how to link software repositories and programming for reuse, have been resolved. The problems faced by industry and the DoD are of a non-technical nature and can be catagorized into 3 broad catagories: managerial, economic, and legal. This thesis comapres industry and DoD reuse efforts highlighting common problems and lessons learned, drawing comparisons between IBM, Hewlett-Packard, the Air Force's CARDS, and the RNTDS. Each reuse effort is studied using personal interviews and written descriptions. Problems encountered by private industry and their solutions are analyzed and compared to DoD. Legal issues, the least understood by industry and DoD, are in need further research. Overall, industry is found to be more advanced than the DoD in their understanding of reuse. Furthermore, the DoD might allieviate some of its reuse problems by employing lessons learned in industry.

Author: R. Therriault and K. Van Nederveen

Publisher: Naval Postgraduate School

Reference Number: Ad-A285-708

Producing Organization: Naval Postgraduate School

Publication Date: 9/94


Proceedings of the Workshop on the Next Generation of Case Tools(5th) Held in Utrecht, The Netherlands on June 6-7, 1994

Abstract: The fifth in a serires of workshops that attempt to provide a framework for the academic exchange of ideas and results that advance the state of the are in CASE-related research. Contains the following papers: An Imprecise Querying Mechanism for the Reuse of Conceptual Schema Components; Case Tool Integration: A State of the Art Review; Reverse Engineering in Relational Databases; End User CASE - Specializing Rules in a Secure Environment; and Human Factors and Modern Software Development.

Publisher: Technische Univ. Enshede (Netherlands)

Reference Number: PB95-135208

Producing Organization: Technische Univ. Enshede (Netherlands)

Publication Date: 5/94


Hypermedia Implementation for Reusable Software Component Representation

Abstract: This study investigated software component representation methods. Hypermedia was chosen as the implementation method to represent a collection of reusable software components. The hypermedia implementation organizes knowledge about the component collection into a web of small information chunks called frames. The set of software components was represented using a hybrid classification scheme composed of enumerated and faceted parts. The enumerated part enables the user to progress along a path in a taxonomic tree, narrowing the scope of eligible components. Each leaf node in this tree denotes a class of components, members of which are distinguished by their time and space characteristics. These characteristics, known as forms, are grouped into eleven facets, each comprised of two to four elements. Links between frames establish a means of traversing the information net. Some of these links allow the user to progress directly through the levels of the classification structure. Other links lead from the classification structure frames containing explanatory text for the terms used in the classification. Additional links cross-reference related topics. (JS) Classification; Collection; Computer programs; Frames; Grade structure(Personnel management); Hybrid systems; Nodes; Parts; Reusable equipment; Taxonomy; Trees; Webs(Sheets)

Author: G. Worrall

Publisher: Air Force Institute of Technology - AFIT

Reference Number: AD-A230 497/0/XAB

Producing Organization: Air Force Institute of Technology - AFIT

Publication Date: 12/90


Repository-Based Software Engineering Working Program ManagementPlan

Abstract: Repository-Based Software Engineering Program (RBSE) is a National Aeronautics and Space Administration (NASA) sponsored program dedicated to introducing and supporting common, effective approaches to software engineering practices. The process of conceiving, designing, building, and maintaining software systems by using existing software assets that are stored in a specialized operational reuse library or repository, accessible to system designers, is the foundation of the program. In addition to operating a software repository, RBSE promotes (1) software engineering technology transfer, (2) academic and instructional support of reuse programs, (3) the use of common software engineering standards and practices, (4) software reuse technology research, and (5) interoperability between reuse libraries. This Program Management Plan (PMP) is intended to communicate program goals and objectives, describe major work areas, and define a management report and control process. This process will assist the Program Manager, University of Houston at Clear Lake (UHCL) in tracking work progress and describing major program activities to NASA management. The goal of this PMP is to make managing the RBSE program a relatively easy process that improves the work of all team members. The PMP describes work areas addressed and work efforts being accomplished by the program; however, it is not intended as a complete description of the program. Its focus is on providing management tools and management processes for monitoring, evaluating, and administering the program; and it includes schedules for charting milestones and deliveries of program products. The PMP was developed by soliciting and obtaining guidance from appropriate program participants, analyzing program management guidance, and reviewing related program management documents. *Management planning; *NASA programs; *Project management; *Software engineering; *Software reuse; Computer programming; Technology transfer

Publisher: Applied Expertise, Inc.

Reference Number: N93-28319/0/XAB

Sponsoring Organization: NASA

Producing Organization: Applied Expertise, Inc.

Publication Date: 4/93


Cognitive Issues in Software Reuse

Abstract: Vast resources are invested in the construction of software. Reuse of software offers potential savings in the construction of new software systems. From the perspective of cognitive science, current proposals for software reuse are depicted. This work covers cognitive analysis of programming behavior in addition to the aspects of cognitive behavior related to program comprehension, the motions of knowledge domain, knowledge acquisition, and reconstruction and memory mechanisms. The definition of software reusability, reuse methods, and the software model DRACO are presented and discussed.

Author: E. Coelho

Publisher: Naval Postgraduate School

Reference Number: AD-A159-386

Producing Organization: Naval Postgraduate School

Publication Date: 6/85


A Knowledge and Deduction Based Software Retrieval Tool

Abstract: Two approaches to automated software reuse and retrieval that increase the efficiency of building large software systems are: Describing reusable components on an abstract level with keywords and catching the detailed semantics of functions with formalisms based on mathematical and logical notation. For the former, automated support exists, however, the coarse-grained description is insufficient. The latter supports detailed description, but lacks in general automated support. This paper presents formal foundations of software retrieval and a related system that is able to handle all relevant properties of software components.

Author: S. Meggendorfer and P. Manhart

Publisher: Technische Univ. Muenchen Germany

Reference Number: TIB/A93-02189/HDM

Producing Organization: Technische Univ. Muenchen Germany

Publication Date: 10/91


Working Notes From the 1992 AAAI Workshop on Automating Software Design - Theme: Domain Specific Software Design

Abstract: The goal of the AAAI workshop is to identify different architectural approaches to building domain specific software design systems and to explore issues unique to domain specific software design. Some general issues that cut across the particular software design domain include: Knowledge representation, acquisition and maintenance, specialzed software design techniques, and user interaction and interfaces. Among the papers presented are: CARDS: A Blueprint and Environment for Domain-Specific Software Reuse; Knowledge Modeling for Software Design; Formalizations and Visualization of Domain-Specific Software Architectures; Modeling Software Systems by Domains; Software Design as a Problem Learning Theory; and Model-Based Software Design.

Publisher: NASA

Reference Number: N93-17499

Sponsoring Organization: NASA

Producing Organization: NASA Ames Research Center

Publication Date: 7/92


Report on the Advanced Software Technology Workshop. Held on February 1, 1994

Abstract: On February 1, 1994, the Director of the Computer Systems Laboratory of the National Institute of Standards and Technology (NIST) convened an invitational workshop attended by eleven executives for whom software is critical to business. The purpose of the workshop was to identify advanced software technology requirements for U.S. business and to identify opportunities that NIST might pursue in the area of advanced software technology. This report summarizes the deliberations of the workshop. *Computer software; *Software engineering; *Technology assessment; Computer program reliability; Software reuse; Computer security ; Standards; Businesses; Computer program portability; Computer applications; Requirements

Author: Wallace, D. R. ; Kuhn, D. R. ; Rhodes, T. R.

Publisher: National Institute of Standards & Technology

Reference Number: PB95-136610

Producing Organization: National Institute of Standards & Technology

Publication Date: 8/94


Twenty-Fourth Annual ACM Computer Science Conference Proceedings: Past as Prologue to the Future -- 50 Years of Computing

Abstract: Two tracks were planned and followed during this conference: The History of Computing and The New Strategic Directions in Computer Science. The conference included speakers, technical paper sessions, tutorials, panels and demonstrations. In addition to several speeches and workshop sessions, the text of the following technical papers are included in these proceedings: "Enumerating the Risks of Reengineered Processes," "Mapping a Functional Specification to an Object-Oriented Specification in Software Re-engineering," "Merging Task-Centered UI Design With Complex System Development: A Risky Busines," "Representation of Scientific Hypotheses for Use by the Expert System, Research Assistant: The Setup," "Improving Opening Book Performance Through Modeling of Chess Opponents," "An Architecture for Planning with External Information Points in a Real-Time System," "Matrix Inversion in O(log n) on a Scan-Enhanced Reconfigurable Mesh Computer," "Yet Another Efficient Algorithm for Replacing the Edges of a Minimum Spanning Tree," "The PML-tree: An Efficient Parallel Spatial Index Structure for Spatial Databases," " An Evaluation of a Client-Server Real-Time Database System," "Ternary Relationship Decomposition and Higher Normal Form Structures Derived from Entity Relationship Conceptual Modeling," "A Hybrid Conceptual Clustering System."

Publisher: ACM

Reference Number: ACM ISBN: 0-89791-828-2; ACM Order Number: 404960

Publication Date: 2/96


TRI-Ada Conference Proceedings -- Ada's Role in Global Markets: Solutions for a Changing, Complex World

Abstract: These proceedings are organized by program session and day of presentation: SESSION -- Bindings 1 ("An Ada Binding for ODMG-93," "Interfacing Ada to C -- Solutions to Four Problems," "ADABINDGEN: A Tool to Support the Generation of Ada Bindings to C and C++"); SESSION -- Bindings 2 ("Ada 83/95 Bindings to OSF's Distributed Computing Environment (DCE)," "An Implementation of the DIS Standard in Ada"); SESSION -- Case Studies 1 ("Ada and the Evolution of Software Engineering," "Swiss Post Office Electronic Funds Transfer"); SESSION -- Case Studies 2 ("Cassini," "Reuters"); SESSION -- Novel Uses of Ada ("A Reinforcement Strategy for Least Slack Scheduling Using BPHT," "Refinement of Z Specifications Using Reusable Software Componenets of Ada," "Distributed Simulation in Ada 95"); SESSION -- Real-Time 1 -- Ada 83 Experience ("Real-Time Avionics in Ada 83," "Dataflow Coverage in Boeing 777 Primary Flight Control Center"); SESSION -- Real-Time 2 -- Ada 95 Issues ("Implementing Ada Protected Objects -- Interface Issues and Optimization," "A Software Design Method for Ada 95 Based Concurrent and Real-Time Systems," "A Comparison of Ada 83 and Ada 95 Runtime Performance"); SESSION -- Architecture 1 ("Cost-Effective Satellite Development with Use of an Ada Microprocessor," "Transitioning a Model-Based Software Engineering Architectural Style to Ada 95," "DVM: An Object-Oriented Framework for Building Large Distributed Ada Systems"); SESSION -- Object-Oriented Programming ("Implementing the Model-View-Controller Paradigm in Ada 95," "Ada 95 as Implementation Language for Object-Oriented Design," "A Survey of Object-Oriented Methodologies"); and SESSION -- Distributed Systems ("Performance of a High-Level Parallel Programming Layer Defined on Top of the Ada Tasking Model," "GARLIC: Generic Ada Reusable Library for Interpartition Communication," "The First Embedded Distributed Ada 95 Application").

Publisher: ACM

Reference Number: ISBN: 0-89791-705-7; ACM Order Number: 825950

Publication Date: 11/95


TRI-Ada Tutorial Proceedings -- Ada's Role in Global Markets: Solutions for a Changing, Complex World

Abstract: These tutorial proceedings include slides and some paper text for the following tutorials: "Design of Concurrent Software," "Teaching Programming for Reuse: Generics for Educators," "Conversion of Ada to Ada 95: A Software Re-engineering Approach," "The GNU Ada 95 Booch Components," "CORBA and the Future of Application Development," "Patterns and Paradigms for Using Ada 95," "Advanced Object-Oriented Features and Proramming in Ada 95," "Software Architecture and Iterative Development Process," "Implementing Concurrent Programs in Ada 95," "Teaching Object Programming with Ada 95," "Software Soecification and Design," "O4S (Objects for Systems): Tailoring MIL-STD-498," and "FRESCO -- The Next Generation of GUI's."

Publisher: ACM

Publication Date: 11/95


Proceedings of the Second International Symposium on Ground Data Systems for Space Mission Operations November 16-20, 1992 Pasadena, CA

Abstract: Hosted by the Jet Propulsion Laboratory, the symposium on Ground Data Systems featured such catagories as: future missions and operations, system-level architectures, mission and science planning and sequencing, mission control, operations automation and emerging technologies, data acquisition, navigation, operations support services, and operations management.

Publisher: Jet Propulsion Laboratory - JPL

Reference Number: N94-23832

Producing Organization: Jet Propulsion Laboratory - JPL

Publication Date: 3/93


Proceedings of the 18th Annual Software Engineering Workshop

Abstract: The 18th annual Software Engineering Workshop contains the following papers and presentations: Lessons Learned Applying CASE Methods/Tools to Ada Software Development Projects; Fusing Modeling Techniques to Support Domain Analysis for Reuse Opportunities Identification; Impact of Ada in the Flight Dynamics Division: Excitement and Frustration; Software Quality: Process of People; Software Engineering with Application-Specific Languages; Process Improvement as an Investment: Measuring its Worth; Software Forecasting as it is Really Done: A study of JPL Software Engineering.

Publisher: NASA

Reference Number: N94-36484

Producing Organization: NASA

Publication Date: 12/93


Proceedings of the 16th Annual Software Engineering Workshop

Abstract: Part of the Software Engineering Laboratory (SEL) series this document contains the following papers: A Prototype Software Engineering Environment for Domain Modeling and Reuse; The Successful Introduction of Software Reuse Across an Entity; SEI Process Maturity Model: Use/Misuse; A Study of Large-Scale Software Testing; Cleanroom Process Evolution in the SEL; A Markov Model of Software Usage; Measurement in Practise; and A Model for the Measurement of Cognitive Complexity in Software.

Publisher: NASA

Reference Number: N92-32869

Producing Organization: NASA

Publication Date: 12/91


Proceedings of the 13th Annual Software Engineering Workshop

Abstract: The 13th Annual Software Engineering Workshop, held at the NASA Goddard Space Flight Center, contains the following papers: Evolving Impacts of Ada on a Production Environment; Measuring/Reusing and Maintaining Ada Software; Software Sizing, Cost Estimation and Scheduling; Ada Software Productivity Analysis; Experience With Ada in an Embedded System; A Modernized PDL Approach for Ada Software Development; and A practical Approach to Object Based Requirements Analysis.

Publisher: NASA

Reference Number: N91-10606

Producing Organization: NASA

Publication Date: 11/88


Software Technology for Adaptable, Reliable Systems (STARS) Case Vendor Workshop, held in Seattle on July 23-24, 1991

Abstract: Divided by Business Track Discussion Groups and Technical Track Discussion Groups. Business Track:Vendor Dialog and Participation in STARS, Marketing Strategies & DoD Procurement Policies, Marketing Strategies and Perceived DoD Needs, Open Architecture--Competition or Cooperation?, Respopnse to STARS Goals, Vision, and Strategy. Technical Track: Relevant Standards & STARS Selection Process, Framework Convergence, STARS Role Amidst all the Standards Activities, Standards vs. Tool Development Strategies, CASE Vendors Perspectives on Reuse, STARS Effects on the Development Process, CASE Vendors Perspectives on Process.

Publisher: Dataquest Inc.

Sponsoring Organization: STARS Program

Producing Organization: Boeing Company

Publication Date: 7/91


Automated Interface for Retrieving Reusable Software Components

Abstract: The Computer AIded Prototyping System (CAPS) software base contains software components described by formal specifications written in the Prototype System Description Language (PSDL). The problems addressed are to develop a retrieval mechanism for extracting components that match user-provided PSDL specifications, and the integration of a retrived component into a software prototype.

Author: Dolgoff, Scott J.

Publisher: NPS - Naval Postgraduate School, Monterey, CA 93943

Sponsoring Organization: Naval Postgraduate School

Producing Organization: Computer Science Dept., Naval Postgraduate School

Publication Date: 9/93


Proceedings TRI-Ada '90

Abstract: Organized by 4 tracks. Track 1: Methods/Ada Infrastructure. Sessions: Formal Methods, Ada Bindings, Panel:Ada Interface Technology, Session:Object-Oriented Programming in Ada, Panel: How Much Object-Orientation in Ada, Session: Alternative Computation Models, Design Methods 1, Design Methods 2, Panel:Ada Education in Universities, Reuse Methods. Track 2: Real-Time Programming in Ada/Ada 9X. Session: Tasking Performance, The Ada Tasking Model is Adequate for Real-Time Embedded Applications, Experiences in Ada Real-Time Applications, Ada for Distributed Systems, Ada on Multi-Processor Systems, Resource Allocation and Deadlock Detection, Ada in Safety-Critical and Fault-Tolerant Systems, Ada 9X Requirements, Ada 9X Town Meeting:Getting Ada into the Mainstream in the 1990's. Track 3: Transitioning to Ada/Management Issues. Sessions:Ada in Different Application Domains, Ada Transition I, Ada Transition II, Panel:Status of Ada Then and Now, Acquisition and Contractual Issues, Barriers to Ada Adoption:Have They Changed?, Ada Compiler Evaluation, Compiler Evaluation within DoD, Ada Awareness Issues:In Government, Congress, and Industry, Ada Optimizations - Why the User Should Care. Track 4: Ada in Practice. Sessions:Track 4 Background and Purpose, Integrating Ada with Existing System:the ATACC Experience, Weirton Steel-Ada in Process Control, AFATDS-From Concept Evaluation to Full Scale Development, Bofors 9LV Mk3 System - Developing for Maximum Software, LINX- Ada in an Open Systems Architecture, Command Center Processing and Display System Replacement - CCPDS-R, STANFINS - One Year Later, DIGITAC III Digital Flight Control System, Reuters - Experience with D2000 and Globex.

Sponsoring Organization: Association for Computing Machinery

Publication Date: 12/90


A Brief Comparison Between Ada and Unix C

Abstract: Memo and brief technical memorandum to Pentagon Computer Software and Systems Division re use of UNIX and C instead of Ada.

Author: Habermann, A.N.

Publisher: SEI - Software Engineering Institute, Carnegie Mellon University, Pittsburgh, PA 14213

Reference Number: SEI-85-TM-3

Producing Organization: SEI - Software Enginnering Institute, Carnegie-Mellon University

Publication Date: 6/85


Ada-Based Design Language Guidelines

Abstract: Presents a brief history of Ada-based design languages and a detailed analysis of current issues surrounding the use of ADLs.

Publisher: Software Productivity Solutions Inc.

Sponsoring Organization: Naval Avionics Center

Publication Date: 1/86


Ada/MIL-STD/DSSD Integration Study (Draft) for NAVELEX PME 120-3

Abstract: This study presents an integration strategy for the following pieces of the future NAVELEX software development environment: The Ada language, the Ada Programming Support Environment, Software System Acquisition Military standards, the Data Structured Systems Development method.

Sponsoring Organization: NAVELEX

Producing Organization: PRC Government Information Systems and Ken Orr and Associates

Publication Date: 9/83


Proceedings of the Seventeenth Annual Software Enginering Workshop

Abstract: The workshop provides a forum for software practioners to exchange information on the measurement, utilization, and evaluation of software methods, models, and tools.

Sponsoring Organization: NASA/GSFC

Producing Organization: Software Engineering Laboratory

Publication Date: 12/92


Design Principles for Software Manufacturing Tools

Abstract: A software manufacturing methodology has been developed called Computer Aided Programming, which is based ona functional programming concept called a frame, motivated in turn by the reusable code problem. This document describes the necessary background idea about frames, and the distinction between problem solving and programming.

Author: Bassett, Paul

Publication Date: 10/83


DARPA Software Technology Conference April 28-30, 1992

Abstract: The conference brought together researchers representing nearly all areas of software technology research at DAPA for the purpose of presenting major results, fostering common strategic technical approaches, and increasing opportunities for technology transition.

Sponsoring Organization: DARPA

Producing Organization: DARPA

Publication Date: 4/92


Trial-Use Standard for Ada-Based ATLAS-Level Test Procedure Interface for a Broad-Based Environment for Test (ABBET).

Abstract: Ada packages that specify data types and services for the Ad-based ATLAS-level test procedure interface for a broad-basedenvironment for test(ABBET) are defined. They are to be used to support the development of Ada-based, UUT-directed, signal-oriented test programs. IEEE design data, test requirements/strategies, and test results management in the implementation of automated test systems and test control programs.

Author: Ziegler, J.; et al

Publisher: IEEE - Institute of Electrical and Electronic Engineers, Inc., 345 East 47th Street, New York, NY 10017

Reference Number: IEEE Std 1226.2-1993

Sponsoring Organization: Standards Coordinating Committee 20, Abbreviated Test Language for All Systems (ATLAS)

Producing Organization: Institute of Electrical and Electronics Engineers Inc,

Publication Date: 4/94


Methodology for Software Reliability Prediction

Abstract: Report describes the results of a research and development effort to develop a methodology for predicting and estimating software reliability. A software Reliability Measurement Framework was established which spans the life cycle of a software system and includes the specification, prediction, estimation, and assessment of software reliability. Data from 59 systems, representing over 5 million lines of code, were analyzed and generally applicable observations about software reliability were made. A detailed approach to the collection and analysis of reliability data is also presented.

Author: McCall, J.; et al.

Publisher: RADC - Rome Air Development Center, Griffiss AFB, NY 13441

Reference Number: RADC-TR-87-171 Vol I

Sponsoring Organization: RADC - Rome Air Development Center

Producing Organization: SAIC - Science Applications International Corporation

Publication Date: 11/87


Methodology for Software Reliability Prediction, Volume II

Abstract: The Guidebook provides detailed procedures for the preparation of software reliability predictions and estimations on DOD projects. In developing the Guidebook, 59 software systems were examined and 19 key variables were developed to account for the type of application, development, environment, various software characteristics (such as modularity and complexity), test technique, test effort and test coverage. A methodology was also provided to use these measures to predict software faulty density and software failure rates.

Author: McCall, J.; et al.

Publisher: RADC - Rome Air Development Center, Griffiss AFB, NY 13441

Reference Number: RADC-TR-87-171 Vol II

Sponsoring Organization: RADC - Rome Air Development Center

Producing Organization: SAIC - Science Applications International Corporation

Publication Date: 11/87


A Conceptual Framework for Software Reusability

Abstract: The concept of software reusabilty is similar to data sharability. A piece of software is reusable when it is interpretable, incorporatable and portable. The goal for software reusability is the automatic generation of large software systems utilyzing reusable components. In this paper, the authos outline some of the problems that must be solved to reach this goal and a brief discussion of their approach to solve these problems.

Author: Yeh, Raymond T. and Roussopoulos, Nick

Publication Date: 4/83


Technical Report on the Comparison of DoD-STD-1679A and DoD-STD-2167

Abstract: This technical report presents the results of an in-depth comparison of software development standards DoD-STD 1679 A and DoD-STD-2167 and their associated Data Item Descriptions (DIDs.) The first part of this report is an Executive Summary, which presents key similarities, key differences, and general observations concerning the standards and their DIDs. The second part of the report is a detailed comparison of the standards and their DIDs.

Sponsoring Organization: Joint Logistics Commanders Computer Software Mgt Subgroup

Producing Organization: Logicon

Publication Date: 9/85


Suggestions for Using and Organizing Libraries for Ada Program Development

Abstract: Discusses problems, concepts and approaches relevant to an on-line library system supporting the creation, documentation and maintenance of Ada software systems. The ultimate goal of research in this area is to make Ada programming significantly easier, more reliable, and more cost effective by using previously written Ada Code and previously accumulated programming experience to the maximum possible extent.

Author: Goguen, Joseph A.

Sponsoring Organization: Ada Joint Program Office

Producing Organization: SRI International

Publication Date: 10/83


A Formal Specification and Verification Method for the Prevention of Denial of Service in Ada Services

Abstract: The purpose of this paper is to review the denial-of-service problem and introduce a new formal specification and verification method for the prevention of denial of service. A formal method for establishing the specification-to-code correspondence is used. This enables the authors to verify formally the prevention of denial-of-service in Ada services. To verify the absence of denial of service, a service specification model is introduced. A key component of that model is the separation of the service sharing mechanism from the service sharing policy. The argument is that, in contrast with other properties, the prevention of denial-of-service requires specification of service use, i.e., user agreements which are external constraints on service invocations and which must be obeyed by all service users.

Author: Yu, Che-fn; Virgil D. Gilgor

Publisher: IDA - Institute for Defense Analyses, 1801 N. Beauregard St., Alexandria, VA 22311

Reference Number: IDA Paper P-2120

Sponsoring Organization: Rome Air Development Center, RADC/COTC, Griffis AFB, NY 13441

Publication Date: 3/88


Object Oriented Programming Systems (OOPS) and Frame Representations, an Investigation of Programming Paradigms

Abstract: The project that led to this report was initiated to research object-oriented programming systems (OOPS) and frame representation systems, their significance and applicability, and their implementation in or relationship to Ada. The approach was to first define the terms; them pursue the possibilities of merging OOPS with Ada, which will further elucidate the significant characteristics which make up this programming approach; and, finally, consider some of the merits and demerits of OOPS as a way of addressing the applicability of OOPS to various programming tasks.

Author: Auty, David

Publisher: Softech, Inc., 1300 Hercules Drive, Suite 105, Houston, TX 77058-2747

Reference Number: RICIS Report AI.9; Softech Document HO-003

Sponsoring Organization: NASA

Producing Organization: Research Institute for Computing and Information Systems

Publication Date: 7/88


An Economics Foundation For Software Reuse

Abstract: Software reuse is being heralded as a prime means of increasing productivity of the software development process. Here is an economics model of reuse, which provides a relationship among productivity, the cost of engineering reusable components, the cost of software component reuse, the proportion of software reused in an application, and the number of reuses. The equations presented are derived from the point of view of code reuse, which is what most people mean when they say software reuse.

Author: Gaffney, John E., Jr.

Publisher: SPC - Software Reuse Consortium, SPC Building, 2214 Rock Hill Road, Herndon, VA 22070

Reference Number: SW_REUSE_ECONOM-89040-N

Sponsoring Organization: Software Productivity Consortium

Publication Date: 7/89


A Model for Analysis of Scale Economies and Software Productivity

Abstract: Provides an approach for member companies to quantitatively characterize their current software development practices and relate them to others in their industry. The approach is illustrated with productivity data from member company and other industry sources. The productivity data may be found useful as baselines. The report considers the issue of economies and diseconomies of scale in software development. This is related to the familiar model of software development costs as consisting of fixed costs plus costs that vary with the amount of product developed. The concept explains the observed phenomenon of unit costs that first decrease with larger product size (in KSLOC), the decrease as product size increases beyond the region of the MPSS. The models are applicable to both aerospace and MIS software.

Author: Gaffney, John E., Jr. and Richard Werling

Publisher: SPC _ Software Productivity Consortium, SPC Building, 2214 Rock Hill Road, Herdon, VA 22070

Reference Number: ANALYSIS_PROJECT_DATA-90018-N

Producing Organization: SPC _ Software Productivity Consortium

Publication Date: 8/90


Interim Report on Software Test Tools

Abstract: This report is an interim synopsis of the Software Technology Support Center's (STSC) progress in evaluating software test tools. The lists of tools, capabilities, and assessments in this report will help Air Force organizations identify and select software test tools. Although the material has been reviewed for technical accuracy, no guarantees are made or implied. Product specifications are subject to change without notice. Readers should verify information independently and evaluate the usefulness of the material as it relates to their environment.

Author: Petersen, Gary; Greg Daich; Debbie Dyer; and Shane Atkinson

Publisher: U.S. Air Force, Ogden Air Logistics Center, Hill AFB, Utah

Producing Organization: STSC - Software Technology Support Center

Publication Date: 11/90


Interim Report on Requirements Analysis & Design Tools

Abstract: This report is an interim synopsis of the Software Technology Support Center's (STSC) progress in evaluating requirements analysis and high level design computer aided software engineering (Upper CASE) tools. The assessment strategies and lists of tools in this report will help Air Force Organizations select productive Upper CASE tools. The material has been reviewed for technical accuracy, but no guaranties are made or implied.

Author: Petersen, Gary; James Van Buren; and Susan Nilson

Publisher: U.S. Air Force, Ogden Air Logistics Center, Hill AFB, Utah

Producing Organization: STSC - Software Technology Support Center

Publication Date: 11/90


Interim Report on Software Documentation Tools

Abstract: This report is an interim synopsis of the Software Technology Support Center's (STSC) progress in evaluating software documentation tools. The lists of tools, capabilities, and assessments will help Air Force organizations select documentation tools. The material presented has been reviewed for technical accuracy, but no guaranties are made or implied.

Author: Petersen, Gary; Lynn Satterthwaite; and David Crosby

Publisher: U.S. Air Force, Ogden Air Logistics Center, Hill AFB, Utah

Producing Organization: STSC - Software Technology Support Center

Publication Date: 11/90


IEEE Recommended Practice for Ada as a Program Design Language; ANSI/IEEE Std 990-1987

Abstract: This document provides recommendations reflecting the state of the art and alternate approaches to good practice for characteristics of Program Design Languages (PDLs) based on the syntax and semantics of the Ada Programming Language. This recommended practice addresses the characteristics of an Ada PDL and not the use of an Ada PDL.

Author: Blasewitz, Robert M.; et al.

Publisher: IEEE

Reference Number: IEEE Std 990-1987

Sponsoring Organization: IEEE Computer Society, Technical Committee on Software Engineering

Producing Organization: IEEE

Publication Date: 1/87


IEEE Standard Glossary of Software Engineering Terminology, IEEE Std 610.12-1990

Abstract: This revision and redesignation of IEEE Std 792-1983 identifies terms currently in use in the field of software engineering. Standard definitions for those terms are established.

Author: Radatz, Jane; et al.

Publisher: Institute of Electrical and Electronics Engineers, 345 East 47th Street, New York, NY 10017

Reference Number: !EEE Std 610.12-1990; SH13748

Sponsoring Organization: IEEE Computer Society

Producing Organization: IEEE Computer Dictionary Working Group

Publication Date: 12/90


Standard ECMA-149 Portable Common Tool Environment (PCTE); Abstract Specification, Volume 2

Abstract: Specifies Portable Common Tool Environment (PCTE) in abstract, programming-language-independent terms. It specifies the interfaces supported by any conforming implementation as a set of abstract operation specifications, together with the types of their parameters and results. It is supported by a number of standard bindings, i.e., representations of the interface in standard programming languages.

Publisher: ECMA - European Computer Manufacturers Association

Reference Number: ECMA-149

Producing Organization: ECMA - European Computer Manufacturers Association

Publication Date: 6/93


The Role of Assessment in Software Process Improvement

Abstract: Discusses the role of assessment in improving an organization's software capabilities; specifically, the ability of the organization's projects to consistently meet cost, schedule, and quality objectives. Software process assessments are described from both a conceptual and pragmatic point of view. Underlying concepts of software process, software process management, and software process maturity are discussed. Collectively, these constitute a framework for software process assessment and improvement.

Author: Kitson, David H. and Watts S. Humphrey

Publisher: SEI - Software Engineering Institute, Carnegie Mellon University, Pittsburgh, PA 15213

Reference Number: CMU/SEI-89-TR-3; ESD-TR-89-3

Sponsoring Organization: SEI Joint Program Office, Carnegie Mellon University, Pittsburgh, PA 15213

Producing Organization: SEI - Software Engineering Institute

Publication Date: 12/89


The Durra Application Debugger/Monitor

Abstract: This describes the debugger/monitor, a program that works in conjunction with the Durra runtime software to help the developer locate errors and/or performance bottlenecks in a Durra application.

Author: Doubleday, Dennis L.

Publisher: SEI - Software Engineering Institute, Carnegie Mellon University, Pittsburgh, PA 15213

Reference Number: CMU/SEI-89-TR-32; ESD-TR-89-43

Sponsoring Organization: SEI Joint Program Office, Carnegie Mellon University, Pittsburgh, PA 15213

Producing Organization: SEI - Software Engineering Institute

Publication Date: 9/89


An Object-Oriented Solution Example: A Flight Simulator Electrical System

Abstract: Describes an implementation of a subset of an aircraft flight simulator electrical system. It is a result of work on the Ada Simulator Validation Program (ASVP) carried out by members of the technical staff at the Software Engineering Institute. They developed a paradigm for describing and implementing flight simulator systems in general. The paradigm is a model for implementing systems of objects. The objects are described in a form of design specification called an object diagram. The report was prepared to demonstrate a full implementation of a system: package specifications and bodies. The intent is to provide an example; the code is functional, but there is no assurance of robustness.

Author: Lee, Kenneth J. and Michael S. Rissman

Publisher: SEI - Software Engineering Institute, Carnegie Mellon University, Pittsburgh, PA 15213

Reference Number: CMU/SEI-89-TR-5; ESD-TR-89-5

Sponsoring Organization: SEI Joint Program Office, Carnegie Mellon University, Pittsburgh, PA 15213

Producing Organization: SEI - Software Engineering Institute

Publication Date: 2/89


What a Software Engineer Needs to Know: I. Program Vocabulary

Abstract: Software development, like any complex task, requires a wide variety of knowledge and skills. We examine one particular kind of knowledge. the programming language vocabulary of the programmer, by gathering statistics on large bodies of code in three languages. This data shows that most of the identifiers in programs are either uses of built-in or standard library definitions or highly idiomatic uses of local variables. We interpret this result in light of general results on expertise and language acquisition. We conclude that tools to support the vocabulary component of software development are wanting, ad this part of an engineer's education is at best haphazard, and we recommend ways to improve the situation.

Author: Shaw, Mary; Dario Giuse; and Raj Reddy

Publisher: SEI - Software Engineering Institute, Carnegie Mellon University, Pittsburgh, PA 15213

Reference Number: CMU/SEI-89-TR-30; ESD-TR-89-40

Sponsoring Organization: SEI Joint Program Office, Carnegie Mellon University, Pittsburgh, PA 15213

Producing Organization: SEI - Software Engineering Institute

Publication Date: 8/89


1989 SEI Report on Graduate Software Engineering Education

Abstract: Describes SEI 1989 educational activities, including the 1988 SEI Curriculum Design Workshop. A model curriculum for a professional Master of Software Engineering degree is presented, including detailed descriptions of six core courses. Fifteen university graduate programs in software engineering are surveyed.

Author: Ardis, Mark and Gary Ford

Publisher: SEI - Software Engineering Institute, Carnegie Mellon University, Pittsburgh, PA 15213

Reference Number: CMU/SEI-89-TR-21; ESD-TR-89-29

Sponsoring Organization: SEI Joint Program Office, Carnegie Mellon University, Pittsburgh, PA 15213

Producing Organization: SEI - Software Engineering Institute

Publication Date: 6/89


An Analysis of Input/Output Paradigms for Real-Time Systems

Abstract: The correctness of a real-time system with hard deadline requirements depends both on the logical correctness and on the timing correctness of the system. The principles of rate monotonic scheduling have proven to be very useful in providing a framework for designing, analyzing, and modifying the timing and concurrency aspects of real-time systems. This paper illustrates how to build a mathematical model of the schedulability of a real-time system, taking into consideration such factors as preemption, synchronization, non-pre-emptibility, interrupts, and process idle time. In particular, this paper illustrates how these principles can be applied to input/output interfaces (e.g., to devices of local area networks) to predict the timing behavior of various design alternatives.

Author: Klein, Mark H. and Thomas Ralya

Publisher: SEI - Software Engineering Institute, Carnegie Mellon University, Pittsburgh, PA 15213

Reference Number: CMU/SEI-90-TR-19; ESD-90-TR-220

Sponsoring Organization: SEI Joint Program Office, Carnegie Mellon University, Pittsburgh, PA 15213

Producing Organization: SEI - Software Engineering Institute

Publication Date: 7/90


Feature-Oriented Domain Analysis (FODA) Feasibility Study

Abstract: Successful software reuse requires the systematic discovery and exploitation of commonality across related software systems. By examining related software systems and the underlying theory of the class of systems they represent, domain analysis can provide a generic description of the requirements of that class of systems and a set of approaches for their implementation. This report will establish methods for performing a domain analysis and describe the products of the process. To illustrate the application of domain analysis to a representative class of software systems, this report will provide an analysis of window management system software.

Author: Kang, Kyo C.; et al.

Publisher: SEI - Software Enginering Institute, Carnegie Mellon University, Pittsburgh, PA 15213

Reference Number: CMU/SEI-90-TR-21; ESD-90-TR-222

Sponsoring Organization: SEI Joint Program Office, Carnegie Mellon University, Pittsburgh, PA 15213

Producing Organization: SEI - Software Engineering Institute

Publication Date: 11/90


Transaction-Oriented Configuration Management: A Case Study

Abstract: This report illustrates some of the advances in software configuration management concepts by example of a particular commercial system: the Sun Network Software Environment (NSE). NSE embodies a transaction model of configuration management. In order to demonstrate the capabilities and limitations of the transaction model, NSE is applied to three problem areas for configuration management: adaptation for parallel development and team support, development and maintenance in software families, and development in a distributed and heterogeneous network.

Author: Feiler, Peter and Grace Downey

Publisher: SEI - Software Engineering Institute, Carnegie Mellon University, Pittsburgh, PA 15213

Reference Number: CMU/SEI-90-TR-23; ESD-90-TR-224

Sponsoring Organization: SEI Joint Program Office, Carnegie Mellon University, Pittsburgh, PA 15213

Producing Organization: SEI - Software Engineering Institute

Publication Date: 11/90


Tool Integration and Environment Architectures

Abstract: This paper describes the evolution of environment architectures to support federated CASE integration and outlines the implications of this evolution on the technical issues of CASE tool integration.

Author: Wallnau, Kurt C. and Peter H. Feiler

Publisher: SEI - Software Engineering Institute, Carnegie Mellon University, Pittsburgh, PA 15213

Reference Number: CMU/SEI-91-TR-11; ESD-TR-91-11

Sponsoring Organization: SEI Joint Program Office, Carnegie Mellon University, Pittsburgh, PA 15213

Producing Organization: SEI - Software Engineering Institute

Publication Date: 5/91


Durra: A Task-Level Description Language Reference Manual (Version 2)

Abstract: This document, a revised version of the original reference manual, describes the syntax and semantics of the language and incorporates all the language changes introduced as a result of our experience writing task and application descriptions in Durra. A companion document, Durra: A Task-Level Description Language User's Manual, describes how to use the compiler, runtime environment, and support tools.

Author: Barbacci, Mario R. and Jeanette M. Wing

Publisher: SEI - Software Engineering Institute, Carnegie Mellon University, Pittsburgh, PA 15213

Reference Number: CMU/SEI-89-TR-34; ESD-TR-89-45

Sponsoring Organization: SEI Joint Program Office, Carnegie Mellon University, Pitteburgh, PA 15213

Producing Organization: SEI - Software Engineering Institute

Publication Date: 9/89


Durra: A Task-Level Description Language User's Manual

Abstract: This is the manual for users of the Durra compiler, runtime system, and support tools. Additional documents that describe the syntax and semantics of the language and the runtime environment are cited in the bibliography.

Author: Barbacci, Mario R,; Dennis L. Doubleday; and Charles B. Weinstock

Publisher: SEI - Software Engineering Institute, Carnegie Mellon University, Pittsburgh, PA 15213

Reference Number: CMU/SEI-89-TR-33; ESD-TR-89-44

Sponsoring Organization: SEI Joint Program Office, Carnegie Mellon University, Pittsburgh, PA 15213

Producing Organization: SEI - Software Engineering Institute

Publication Date: 9/89


Development Statistics for the UH-1 FS Ada Feasibility Study

Abstract: The basic goal was to implement an Ada Data Collection and Analysis Program and coordinate the program with the development contractor to fulfill the goals of defining productivity, cost, and quality metrics to support future acquisitions. This paper describes the approach to data collection and analysis, and how techniques were applied to one particular trainer development project, the UH-1 Flight Simulator. The results of the study should be a greater understanding of the software development process, product improved simulators, and associated specifications and contracts.

Publisher: IITRI - IIT Research Institute, 4600 Forbes Boulevard, Lanham, MD 20706-4324

Sponsoring Organization: US Army Material Command, Program Manager for Training Devices (PM TRADE), Orlando, FL 32826

Producing Organization: IITRI

Publication Date: 1/92


Revised Hardware and Software Analysis

Abstract: This updated Hardware/Software Analysis pare is intended to provide the Ada Joint Program Office (AJPO) and the Ada 9X Project Office with a clear and concise overview of the types of hardware and software available for the Ada 9X Review Database project (Section 2.0) and a comparison and recommendation for a development and utilization environment (Section 3.0).

Publisher: IITRI - IIT Research Institute, 4600 Forbes Boulevard, Lanham, MD 20706

Sponsoring Organization: AJPO - Ada Joint Program Office, Ada 9X Project Office, Eglin AFB, FL

Producing Organization: IITRI

Publication Date: 6/89


Review of Ada Guidebooks, Handbooks, and Style Guides

Abstract: The goal of this effort is to develop an evaluation process for Ada guidebooks, handbooks, and style guides. Collectively, these are referenced as Ada guidebooks. They assume a basic knowledge of the Ada language and are intended to give more detailed advice. To satisfy this goal required developing a framework for each type of guidebook to be evaluated and a set of evaluation criteria. One evaluation criterion, completeness, assesses how well a guidebook covers the appropriate framework. The final portion of the study was to assess the feasibility of application-specific guidebooks.

Publisher: IITRI - IIT Research Institute, 4600 Forbes Boulevard, Lanham, MD 20705-4324

Reference Number: MDA903-87-D-0056; IITRi Project No. T06178

Sponsoring Organization: US Army CECOM, Advanced Software Technology, Ft. Monmouth, NJ 07703-5000

Producing Organization: IITRI

Publication Date: 7/90


Report of Mil-STD-1862 Review Committee d.b.a. Nebula Review Committee

Abstract: This report is the result of a joint industry/government examination of MIL-STD-1862 (Nebula). The document highlights the key issues in three areas; management, the Ada language, and instruction set architecture (ISA). While implementation of the NEBULA ISA is not specifically addressed or necessarily under the purview of MIL-STD-1862, implementation considerations are made in this review.

Author: Martin, Edith W., ed.

Publisher: EIA - Electronic Industries Association

Sponsoring Organization: US army and US Air Force

Producing Organization: EIA - Electronic Industries Association

Publication Date: 6/81


Department of Defense In-house RDT&E Activities: Management Analysis Report

Abstract: Each in-house RDTE activity of the Department of Defense is described on one page in this compilation. The data for 1981 are summarized in tables preceding the main text, and charts and tables are provided for each service showing organizational relationships and command chain.

Author: Davidson, Harold F.

Publisher: DoD

Sponsoring Organization: US Army DARCOM,5001 Eisenhower Avenue, Alexandria, VA 22333

Producing Organization: Harold F. Davidson, 9318 Convento Terrace, Fairfax, Va 22031

Publication Date: 10/81


analyzER: A Software Tool for the Analysis ans Verification of Entity-Relationship (E-R) Models

Abstract: WARNING - EXPORT CONTROLLED *** This describes the capabilities and user operation of a software engineering tool which supports the analysis, verification, and documentation of Entity-Relationship (E-R) models. The tool, known as the analyzER, provides numerous outputs of data and messages which support consistency and completeness checking of an E-R model. In addition, certain tabular lists of information provided by the analyzER are appropriate for inclusion in system/software design documentation. AnalyzER is implemented as two Prolog databases. The first contains the predicates (command and queries) and their associated clauses that will manipulate the second, consisting of facts representing the E-R model to be analyzed. Written entirely in Prolog, the analyzER should operate on any host computer system supporting either a Prolog interpreter or compiler.

Author: Vito, Armand A. and Frank S. LaMonica

Publisher: RADC - Rome Air Development Center, Griffiss AFB, NY 13441-5700

Reference Number: RADC-TR-86-206

Sponsoring Organization: RADC - Rome Air Development Center, Griffiss AFB, NY 13441-5700

Producing Organization: RADC - Rome Air Development Center

Publication Date: 12/86


The FSD Ada Style Guide

Abstract: The purpose of this guide is to provide uniform Ada design and coding conventions. The DoD initiated the Ada program to improve software development through standardization. The application of these style conventions will help projects achieve the expected benefits of Ada. It complements the Ada Language Reference Manual, it doesn't replace it. It addresses Ada style not Ada syntax and semantics.

Author: Rymer, John and Tom McKeever

Publisher: IBM Corporation

Producing Organization: IBM Federal Systems Division, Ada Coordinating Group

Publication Date: 9/86


User Manual for NATO SWG on APSE DRB Math Library

Abstract: This manual shows how to use the library and how to invoke its various routines, functions, and operations. Detailed information about handling errors is also provided. It also explains the various algorithms used for the functions, routines, and operations provided by the library. However, no derivations are included in this document.

Publisher: NWC - Naval Weapons Center, Code 3922, China Lake, CA 93555

Producing Organization: NWC - Naval Weapons Center

Publication Date: 8/89


Test and Maintenance Information for NATO SWG on APSE DRB Math Library

Abstract: This document describes the test procedures, test reports, and maintenance procedures for functions, operations, and routines of the Ada Mathematical Library.

Publisher: NWC - Naval Warfare Center, Code 3922, China Lake, CA 93555

Producing Organization: NWC- Naval Warfare Center

Publication Date: 11/89


Specifications for NATO SWG on APSE DRB Math Library

Abstract: This software requirements specification specifies the engineering and qualification requirements for the Ada Mathematical Library, which will be composed of trigonometric (transcendental) functions, vector and matrix operations, and square root routines.

Publisher: NWC - Naval Warfare Center, Code 3922, China Lake, CA 93555

Producing Organization: NWC - Naval Warfare Center

Publication Date: 11/89


Patriot Missile Defense: Software Problem Led to System Failure at Dhahran, Saudi Arabia

Abstract: The Patriot battery at Dhahran failed to track and intercept the Scud missile because of a software problem in the system's weapons control computer. This problem led to an inaccurate tracking calculation that became worse the longer the system operated. At the time of the incident, the battery had been operating continuously for over 100 hours. By then, the inaccuracy was serious enough to cause the system to look in the wrong place for the incoming Scud. The Patriot had never before been used to defend against Scud missiles nor was it expected to operate continuously for long periods of time. Two weeks before the incident, Army officials received Israeli data indicating some loss in accuracy after the system had been running for 8 consecutive hours. Consequently, Army officials modified the software to improve the system's accuracy. However, the modified software did not reach Dhahran until the day after the Scud hit an Army barracks killing 28 soldiers.

Author: Blair, Michael; Sally Obenski; and Paula Bridickas

Publisher: GAO - US General Accounting Office, Washington, DC 20548

Reference Number: GAO/IMTEC-92-26; B-247094

Sponsoring Organization: US Congress, House of Representatives

Producing Organization: GAO - US General Accounting Office

Publication Date: 2/92


Reference Model for Frameworks of Software Engineering Environments (Technical Report ECMA TR/55, 2nd Edition)

Abstract: This document provides a reference model for software engineering environment (SEE) frameworks and describes the role that the framework plays in an entire SEE.

Publisher: NIST - National Institute of Standards and Technology, Gaithersburg, MD 20899

Reference Number: NIST Special Publication 500-201; ECMA TR/55, 2nd ed.

Sponsoring Organization: US Dept. of Commerce

Producing Organization: NIST - National Institute of Standards and Technology

Publication Date: 12/91


Quality Management and Quality Assurance Standards, Part 3: Guidelines for the Application of ISO 9001 to the Development, Supply and Maintenance of Sortware (ISO 9000-3)

Abstract: This part of ISO 9000 sets out guidelines to facilitate the application of ISO 9001 to organizations developing, supplying, and maintaining software. It is intended to provide guidance where a contract between two parties requires the demonstration of a supplier's capability to develop, supply, and maintain software products. It is intended to describe the suggested methods and controls for producing software which meets a purchaser's requirements. This is done primarily by preventing nonconformity at all stages from development through maintenance.

Publisher: ISO - International Organization for Standardization, Case Postale 56, CH-1211, Geneva 20, Switzerland

Reference Number: ISO 9000-3:1991 (E)

Producing Organization: ISO - International Organization for Standardization

Publication Date: 6/91


The State of Software Engineering Practice: A Preliminary Report

Abstract: This is the first in a series of reports to provide periodic updates on the state of software engineering practice in the DoD software community. The SEI has developed, and is refining, a process framework and assessment methodology for characterizing the processes used by software organizations to develop and evolve software products. This report provides a brief overview of the process framework and assessment approach, describes assessment results obtained to date, and discusses implications of the current state of the practice for both customers and suppliers of DoD software.

Author: Humphrey, Watts S.; David H. Kitson; and Tim C. Kasse

Publisher: SEI - Software Engineering Institute, Carnegie Mellon University, Pittsburgh, PA 15213

Reference Number: CMU/SEI-89-TR-1; ESD-TR-89-01

Sponsoring Organization: SEI Joint Program Office, Carnegie Mellon University, Pittsburgh, PA 15213

Producing Organization: SEI - Software Engineering Institute

Publication Date: 2/89


1990 SEI Report on Undergraduate Software Engineering Education

Abstract: Fundamental issues of software engineering education are presented and discussed in the context of undergraduate programs. Included are discussions of the definition of software engineering and its differences from computer science, the need for undergraduate software engineering education, possible accreditation of undergraduate programs, and prospects for professional certification and licensing of software engineers. The objectives and content of an undergraduate program are described, as are strategies for the evolution and implementation of such programs.

Author: Ford, Gary

Publisher: SEI - Software Engineering Institute, Carnegie Mellon University, Pittsburgh, PA 15213

Reference Number: CMU/SEI-90-TR-3; ESD-TR-90-204

Sponsoring Organization: SEI Joint Program Office, Carnegie Mellon University, Pittsburgh, PA 15213

Producing Organization: SEI - Software Engineering Institute

Publication Date: 3/90


Kernel Ada Programming Support Environment (KAPSE) Interface Team: Public Report, Volume I

Abstract: The initial activities of the KAPSE industry-academia interface team are reported. The AJPO-sponsored effort will ensure the interoperability and transportability of tools and data bases among different KAPSE implementations. The effort is the result of a MOA among the three services directing the establishment of an evaluation team, chaired by the Navy, to identify and establish KAPSE interface standards. As with previous Ada-related developments, the widest possible participation is being encouraged to create a broad base of experience and acceptance in industry, academia, and the DoD.

Author: Oberndorf, Patricia A.; et al.

Publisher: NOSC - Naval Ocean Systems Center, San Diego, CA 92152

Reference Number: NOSC TD 509; AD A115 590

Sponsoring Organization: AJPO - Ada Joint Program Office

Producing Organization: NOSC - Naval Ocean Systems Center, San Diego, CA 92152

Publication Date: 4/82


Kernel Ada Programming Support Environment (KAPSE) Interface Team: Public Report, Volume II - Interim Report for 1 April 1982 - 28 October 1982

Abstract: The continuing activities of the KAPSE interface team and its industry/academia auxilary are reported.

Author: Oberndorf, Patricia A.; et al.

Publisher: NOSC - Naval Ocean Systems Center, San Diego, CA 92152

Reference Number: NOSC TD 552; AD A123 136

Sponsoring Organization: AJPO - Ada Joint Program Office

Producing Organization: NOSC - Naval Ocean Systems Center, San Diego, CA 92152

Publication Date: 10/82


A Proposal for Ada International Standardization and Language Maintenance: Technical Proposal in Response to MDA903-84-R-0015

Abstract: ***PROPRIETARY INFORMATION*** Honeywell and Alsys proposal for the ISO standardization of the Ada language and continued language maintenance support.

Publisher: Honeywell, Aerospace and Defense Systems Research Center, 2600 Ridgway Parkway, NE, Minneapolis, MN 55413

Reference Number: MDA903-84-R-0015

Sponsoring Organization: AJPO - Ada Joint Program Office

Producing Organization: Honeywell and Alsys

Publication Date: 11/83


Ada Language Maintenance and International Standardization, Part 1: Directory of Ada Design Documents; Printed Form

Abstract: This document is the printed form of the Directory of Ada Design Documents as of 85 September 10. Ada Design Documents are all the major relevant documents produced during the development and standardization of the Ada language. Such documents include Language Study Notes, Language Issue Reports, and Notes by Distinguished Reviewers. It is designed to support the process of Language Maintenance and International Standardization of Ada by providing fast access to relevant documents concerning a particular topic or rule of the Ada Reference Manual.

Author: Kamrad, J. Michael; et al.

Publisher: Honeywell Systems and Research Center, 2600 Ridgway Parkway, Minneapolis, MN 55413

Reference Number: Item 0002AC of Contract MDA903-84-C-0485

Sponsoring Organization: AJPO - Ada Joint Program Office

Producing Organization: Honeywell and Alsys

Publication Date: 9/85


Ada Language Maintenance and International Standardization, Part 2: Directory of Design Documents; Printed Form Annex

Abstract: This document provides the major characteristics in the Directory of Ada Design Documents, such as: type of document; title; author; date; size (in printed pages); relevant section of the Ada Reference Manual; etc.

Author: Kamrad, J. Michael; et al.

Publisher: Honeywell Systems and Research Center, 2600 Ridgway Parkway, Minneapolis, MN 55413

Reference Number: Item 0002AC of Contract MDA903-84-C-0485

Sponsoring Organization: AJPO - Ada Joint Program Office

Producing Organization: Honeywell and Alsys

Publication Date: 9/85


Ada Training Curriculum: Ada for Software Managers, L201: Teachers' Guide, Volume II

Publisher: Softech, Inc., 460 Totten Pond Road, Waltham, MA 02154

Reference Number: AD-A142 431

Sponsoring Organization: US Army CECOM/CENTAS

Producing Organization: Softech, Inc.

Publication Date: 5/84


[Part 1] [Part 2] [Part 3] [Part 4] [Part 5] [Part 6] [Part 7] [Part 8] [Part 9]

Back to FAQ