Back to FAQ

Ada Reports & Papers
(Part 7)

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

Software Technology for Adaptable, Reliable Systems (STARS)

Reference Number: AD-A284 373/8/XAB

Producing Organization: Unisys Corp., Reston, VA. Reston Tech. Center.

Publication Date: 3/94

Model Contracts/Agreements. Comprehensive Approach to Reusable Defense Software (CARDS)

Reference Number: AD-A284 403/3/XAB

Producing Organization: Unisys Corp., Reston, VA. Reston Tech. Center.

Publication Date: 3/94

Library Operations Policies and Procedures, Volume 2. Central Archive for Reusable Defense Software (CARDS)

Author: Cortes, R. ; Quick, M.

Reference Number: AD-A284 431/4/XAB

Producing Organization: Unisys Corp., Reston, VA. Reston Tech. Center.

Publication Date: 2/94

Library Capability Demonstration. Comprehensive Approach to Reusable Defense Software (CARDS)

Author: Petro, J. L.

Reference Number: AD-A284 444/7/XAB

Producing Organization: Unisys Corp., Reston, VA. Reston Tech. Center.

Publication Date: 7/94

Direction Level Handbook. Comprehensive Approach to Reusable Defense Software (CARDS)

Author: Delgado, L. ; Bowes, R. J. ; Huber, T. R. ; Saisi, R. O.

Reference Number: AD-A284 532/9/XAB

Producing Organization: Unisys Corp., Reston, VA. Reston Tech. Center.

Publication Date: 3/94

Component Provider's and Tool Developer's Handbook. Central Archive for Reusable Defense Software (CARDS)

Author: Nilson, R. ; Kogut, P.

Reference Number: AD-A284 566/7/XAB

Producing Organization: Unisys Corp., Reston, VA. Reston Tech. Center.

Publication Date: 3/94

Library Capability Demonstration. Central Archive for Reusable Defense Software (CARDS)

Author: Nichols, D.

Reference Number: AD-A284 569/1/XAB

Producing Organization: Unisys Corp., Reston, VA. Reston Tech. Center.

Publication Date: 3/94

Library Capability Demonstration. Central Archive for Reusable Defense Software (CARDS)

Author: Humphrey, G. ; Massey, B.

Reference Number: AD-A284 572/5/XAB

Producing Organization: Unisys Corp., Reston, VA. Reston Tech. Center.

Publication Date: 1/94

Metrics Concept Report. Central Archive for Reusable Defense Software (CARDS)

Author: Berns, A.

Reference Number: AD-A284 573/3/XAB

Producing Organization: Unisys Corp., Reston, VA. Reston Tech. Center.

Publication Date: 3/94

Library Capability Demonstration. Central Archive for Reusable Defense Software (CARDS)

Author: Petro, J.

Reference Number: AD-A284 574/1/XAB

Producing Organization: Unisys Corp., Reston, VA. Reston Tech. Center.

Publication Date: 1/94

Command Center Component Supported Component Report. Central Archive for Reusable Defense Software (CARDS)

Abstract: A software reuse library is only useful if the assets within the library can be quickly and easily located, evaluated, and the characteristics of the assets be easily understood. This Command Center Supported Components Report provides a set of guidelines, initially developed for Command Center Libraries, to assist domain engineers and/or the qualification team in charge of the library in providing information on domain-specific qualified library assets. These guidelines consist of one page templates describing a component from a high level viewpoint, i,e,. glossies, and a multi-page template describing a component in greater technical detail, i.e., technical brief. Two examples of a glossy and technical brief are provided in the appendix. *Libraries; *Software engineering; *Templates; Archives; Management training; Computer aided instruction; Documents

Author: Estep, J. ; Haines, K.

Publisher: Unisys Corp.

Reference Number: AD-A284 575/8/XAB

Sponsoring Organization: Dept. of the Air Force - STARS

Producing Organization: Unisys Corp.

Publication Date: 2/94

Software Technology for Adaptable, Reliable Systems (STARS). Software Architecture Seminar Report: Central Archive for

Author: Facemire, H. J. ; Petracca, A. ; Riesbeck, S.

Reference Number: AD-A284 668/1/XAB

Producing Organization: Unisys Corp., Reston, VA.

Publication Date: 1/94

Software Technology for Adaptable, Reliable Systems (STARS) Program

Reference Number: AD-A284 770/5/XAB

Producing Organization: Loral Federal Systems, Gaithersburg, MD.

Publication Date: 7/94

Industry Versus DoD

Author: Therriault, R. W. ; Van Nederveen, K. E.

Reference Number: AD-A285 708/4/XAB

Producing Organization: Naval Postgraduate School, Monterey, CA.

Publication Date: 9/94

Software Reuse and Reusable Software Libraries. (Latest citations from the INSPEC Database) April 88 - Present

Abstract: The bibliography contains citations concerning enhanced software development productivity and longevity through reuse of software modules. The citations explore software structure and archiving in libraries to promote reusability. Software tools and specifications are presented to maximize the potential of reuse. (Contains 250 citations and includes a subject term index and title list.) *Bibliographies; *Subroutine libraries; Computer systems programs; Productivity

Publisher: NERAC, Inc.

Reference Number: PB95-852869/XAB

Sponsoring Organization: NTIS

Producing Organization: NERAC, Inc.

Publication Date: 10/94

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

Author: Theodoulidis, B.

Reference Number: PB95-135208/XAB

Publication Date: 5/94

Domain Analysis of the Alarm Surveillance Domain. Version 1.0. Conducted as Part of the Domain Analysis Case Study

Abstract: The Domain Analysis Case Study was created to examine the potential use of domain analysis methods in supporting software reuse. To this end, the Domain Analysis Case Study has investigated the use of a particular domain analysis method, called the Feature Oriented Domain Analysis (FODA) method. This report describes the results of the application of the second phase of the FODA method--the domain modeling phase--to the alarm surveillance domain. During this phase, a domain model of alarm surveillance systems was created. This model captured commonalities and variabilities of the alarm surveillance domain with respect to the features of systems in the domain, the functions system perform, and the underlying structure of data used by systems. The domain model is intended to be reused to derive functional requirements for new software systems in this domain. *Software reuse; *Communications networks; *Management; Fault detection; Information systems; Models; Domain analysis; Alarm surveillance; FODA(Feature Oriented Domain Analysis)

Author: Dabrowski, C. ; Watkins, J.

Publisher: National Institute of Standards & Technology ( NIST)

Reference Number: PB95-136339/XAB

Producing Organization: National Institute of Standards & Technology ( NIST)

Publication Date: 9/94

Reuseable Objects Software Environment (ROSE) Software Reuse Workshop

Abstract: The Reusable Objects Software Environment (ROSE) is a common, consistent, consolidated implementation of software functionality using modern object oriented software engineering including designed-in reuse and adaptable requirements. ROSE is designed to minimize abstraction and reduce complexity. A planning model for the reverse engineering of selected objects through object oriented analysis is depicted. Dynamic and functional modeling are used to develop a system design, the object design, the language, and a database management system. The return on investment for a ROSE pilot program and timelines are charted. *Applications programs (Computers); *Architecture (Computers); *Life cycle costs; *Object-oriented programming; *Reverse engineering; *Software engineering; *Software reuse; Cost reduction; Data base management systems; Distributed processing; Dynamic models; Systems engineering

Author: Cottrell, W. L.

Publisher: Rockwell Space Operations Co.

Reference Number: N95-14520/7/XAB

Sponsoring Organization: NASA

Producing Organization: Rockwell Space Operations Co.

Publication Date: 8/94

Reusable Computer Software. (Latest citations from the NTIS Bibliographic Database) Oct. 86 - Present

Abstract: The bibliography contains citations concerning a software development technology which stores common reusable software modules in a software library. The citations explore implementation, guidelines, handbooks, and standards for design architectures, software metrics, automated support, and configuration management. Software libraries, rapid prototyping, and ADA applications are also detailed. (Contains 250 citations and includes a subject term index and title list.) *Bibliographies; *Subroutine libraries; Computer systems programs; Productivity

Publisher: NERAC, Inc.

Reference Number: PB95-858973/XAB

Sponsoring Organization: NTIS

Producing Organization: NERAC, Inc.

Publication Date: 11/94

Towards a Class Library for Mission Planning

Author: Pujo, O. ; Smith, S. T. ; Starkey, P. ; Wolff, T.

Reference Number: N95-17233/4/XAB

Sponsoring Organization: National Aeronautics and Space Administration, Washington, DC.

Producing Organization: European Space Operations Centre, Darmstadt (Germany, F.R.).

Publication Date: 11/94

The Spacecraft Command Language (SCL)

Author: Buckley, B. ; Vangaasbeck, J.

Reference Number: N95-17243/3/XAB

Sponsoring Organization: National Aeronautics and Space Administration, Washington, DC.

Producing Organization: Interface and Control Systems, West Melbourne, FL.

Publication Date: 11/94

Software Interface Verifier

Author: Soderstrom, T. J. ; Krall, L. A. ; Hope, S. A. ; Zupke, B. S.

Reference Number: N95-17564/2/XAB

Sponsoring Organization: National Aeronautics and Space Administration, Washington, DC.

Producing Organization: Telos Corp., Pasadena, CA.

Publication Date: 11/94

Proven Approach for More Effective Software Development and Maintenance

Author: Pajerski, R. ; Hall, D. ; Sinclair, C.

Reference Number: N95-17566/7/XAB

Publication Date: 11/94

Taking Advantage of Ground Data Systems Attributes to Achieve Quality Results in Testing Software

Author: Sigman, C. B. ; Koslosky, J. T. ; Hageman, B. H.

Reference Number: N95-17570/9/XAB

Publication Date: 11/94

Transportable Payload Operations Control Center Reusable Software Building Blocks for Quality Ground Data Systems

Author: Mahmot, R. ; Koslosky, J. T. ; Beach, E. ; Schwarz, B.

Reference Number: N95-17587/3/XAB

Publication Date: 11/94

Glossary of Software Reuse Terms

Author: Katz, S. ; Dabrowski, C. ; Miles, K. ; Law, M.

Reference Number: PB95-178992/XAB

Publication Date: 12/94

CLIPS Template System for Program Understanding

Author: Finkbine, R. B.

Reference Number: N95-19638/2/XAB

Sponsoring Organization: National Aeronautics and Space Administration, Washington, DC.

Publication Date: 11/94

Software Agents for the Dissemination of Remote Terrestrial Sensing Data

Reference Number: N95-23675/8/XAB

Sponsoring Organization: National Aeronautics and Space Administration, Washington, DC.

Producing Organization: Lockheed Palo Alto Research Labs., CA.

Publication Date: 10/94

Using Dedal to Share and Reuse Distributed Engineering Design Information

Reference Number: N95-23678/2/XAB

Publication Date: 10/94

AMPHION Libraries

Reference Number: N95-23680/8/XAB

Sponsoring Organization: National Aeronautics and Space Administration, Washington, DC.

Publication Date: 10/94

Operations and Command Systems for the Extreme Ultraviolet Explorer

Reference Number: N95-23687/3/XAB

Publication Date: 10/94

Constraint Based Scheduling for the Goddard Space Flight Center Distributed Active Archive Center's Data Archive and

Reference Number: N95-24121/2/XAB

Publication Date: 3/94

Polylith: the early goals

Author: Purtilo, J.M.

Publisher: Univ. Illinois at Urbana-Champaign, IL, USA

Reference Number: C86009370

Publication Date: 4/85

Executive guide to software maintenance

Author: Osborne, W.

Publisher: Nat. Bur. Stand., Washington, DC, USA

Reference Number: C86032189

Publication Date: 10/85

Management overview of software reuse

Author: Wong, W.

Publisher: Nat. Bur. Stand., Washington, DC, USA

Reference Number: C87019567

Publication Date: 9/86

IEE Colloquium on 'Reusable Software Components' (Digest No.68)

Publisher: IEE, London, UK

Reference Number: C87054420

Sponsoring Organization: IEE

Publication Date: 1/87

Software Engineering Environments

Publisher: Peter Peregrinus, London, UK

Reference Number: C88064020

Publication Date: 1/86

Specifying the behavior of graphical objects using Esterel

Author: Clement, D.; Incerpi, J.

Publisher: Inst. Nat. Recherche Inf. Autom., Le Chesnay, France

Reference Number: C89021395

Publication Date: 4/88

Proceedings Software Engineering in the Nineties

Publisher: SERC, Utrecht, Netherlands

Reference Number: C89033304

Publication Date: 1/88

Management guide to software reuse

Author: Wong, W.

Publisher: Nat. Bur. Stand., Washington, DC, USA

Reference Number: C89036365

Publication Date: 4/88

Object-oriented programming. An evolutionary approach

Author: Cox, B.J.

Publisher: Addison-Wesley, Reading, MA, USA

Reference Number: C89049075

Publication Date: 1/87

Reusable data structures for C

Author: Sessions, R.

Publisher: Prentice Hall, Englewood Cliffs, NJ, USA

Reference Number: C89062414

Publication Date: 1/89

Programming a digital watch in Esterel v3

Author: Berry, G.

Publisher: Inst. Nat. Recherche Inf. Autom., Le Chesnay, France

Reference Number: C90014593

Publication Date: 5/89

Towards a framework for the process specification

Author: Souquieres, J.

Publisher: Inst. Nat. Recherche Inf. Autom., Le Chesnay, France

Reference Number: C90014594

Publication Date: 6/89

Toulouse '89. Second International Workshop. Software Engineering and its Applications. Proceedings

Publisher: EC2, Nanterre, France

Reference Number: C90027801

Publication Date: 1/89

Proceedings. TRI-Ada '89

Publisher: ACM, New York, NY, USA

Reference Number: C90064368

Publication Date: 1/89

Research Opportunities for Breakthrough Initiatives. Software Technology for Adaptable Reliable Systems (STARS)

Publisher: Software Eng. Technol, Vero Beach, FL, USA

Reference Number: C9202-6110B-220

Publication Date: 1/89

Proceedings of the Sixth IASTED International Symposium. Expert Systems: Theory and Application

Publisher: ACTA Press, Anaheim, CA, USA

Reference Number: C9210-6170-085

Sponsoring Organization: IASTED

Publication Date: 1/89

Software reuse with ADA

Publisher: Peter Peregrinus, London, UK

Reference Number: C90041306

Publication Date: 1/90

Program synthesis using derivational analogy

Author: Bhansali, S.; Harandi, M.T.

Publisher: Univ. Illinois at Urbana-Champaign, IL, USA

Reference Number: C90070668

Publication Date: 4/90

IEE Colloquium on 'Software Testing for Critical Systems' (Digest No.108)

Publisher: IEE, London, UK

Reference Number: C90070486

Sponsoring Organization: IEE

Publication Date: 1/90

Systematic catalogue of reusable abstract data types

Author: Uhl, J.; Schmid, H.A.

Publisher: Springer-Verlag, Berlin, Germany

Reference Number: C91016942

Publication Date: 1/90

IEE Colloquium on 'Applications and Experience of Object-Oriented Design': Reusability in OO Programming

Publisher: IEE, London, UK

Reference Number: B91029418, C91036389

Sponsoring Organization: IEE

Publication Date: 1/91

Software design, concepts and methods

Author: Stevens, W.P.

Publisher: Prentice Hall, Hemel Hempstead, UK

Reference Number: C91047911

Publication Date: 1/91

Proceedings. Fourteenth Annual International Computer Software and Applications Conference (Cat. No.90CH2923-1)

Publisher: IEEE Comput. Soc. Press, Los Alamitos, CA, USA

Reference Number: C91071959

Sponsoring Organization: IEEE

Publication Date: 1/90

Software Re-Use, Utrecht 1989. Proceedings of the Software Re-Use Workshop

Publisher: Springer-Verlag, Berlin, Germany

Reference Number: C9201-6110B-042

Sponsoring Organization: SERC

Publication Date: 1/91

Fourth International Workshop on Computer-Aided Software Engineering. Advance Working Papers (Cat. No.90CH2956-1)

Publisher: IEEE Comput. Soc. Press, Los Alamitos, CA, USA

Reference Number: C9201-6115-047

Sponsoring Organization: IEEE; Int. Workshop on CASE

Publication Date: 1/90

Acquisition and reuse of knowledge to design embedded software

Author: Seppanen, V.

Reference Number: C9202-6110B-218

Publication Date: 6/90

When objects collide: experiences with reusing multiple class hierarchies

Author: Berlin, L.M.

Publisher: Hewlett-Packard Lab., Palo Alto, CA, USA

Reference Number: C9202-6110B-252

Publication Date: 8/90

Beyond models and metaphors: visual formalisms in user interface design

Author: Nardi, B.A.; Zarmer, C.L.

Publisher: Hewlett-Packard Lab., Palo Alto, CA, USA

Reference Number: C9202-6180G-053

Publication Date: 9/90

Experience with the ET++ application framework

Author: Shaw, B.; Young, D.

Publisher: Hewlett-Packard Lab., Palo Alto, CA, USA

Reference Number: C9202-6110J-055

Publication Date: 6/90

Visual formalisms as application frameworks

Author: Nardi, B.; Zarmer, C.

Publisher: Hewlett-Packard Lab., Palo Alto, CA, USA

Reference Number: C9202-6130B-167

Publication Date: 12/90

Tangram modeling environment

Author: Golubchik, L.; Rozenblat, G.D.; Cheng, W.C.; Muntz, R.R.

Publisher: Univ. California, Comput. Sci. Dept., Los Angeles, CA, USA

Reference Number: C9202-7310-056

Publication Date: 1/91

Boltzmann: an object-oriented particle simulation programming system

Author: Lin, X.

Publisher: Univ. California, Comput. Sci. Dept., Los Angeles, CA, USA

Reference Number: C9202-6185-063

Publication Date: 1/91

Extensible stackable interface for file system development

Author: Heidemann, J.S.; Popek, G.J.

Publisher: Univ. California, Comput. Sci. Dept., Los Angeles, CA, USA

Reference Number: C9202-6120-071

Publication Date: 1/91

Reusing object-oriented designs

Author: Johnson, R.E.; Russo, V.F.

Publisher: Univ. Illinois at Urbana-Champaign, IL, USA

Reference Number: C9203-6110J-023

Publication Date: 5/91

Automated link creation in a hypertext-based software reuse library

Author: Tsien, C.L.

Publisher: Hewlett-Packard Lab., Palo Alto, CA, USA

Reference Number: C9203-6115-059

Publication Date: 9/91

Domain-based program synthesis using planning and derivational analogy

Author: Bhansali, S.

Publisher: Univ. Illinois at Urbana-Champaign, IL, USA

Reference Number: C9203-6115-063

Publication Date: 5/91

Empirical Foundations of Information and Software Science V

Publisher: Plenum, New York, NY, USA

Reference Number: C9204-6110B-025

Sponsoring Organization: Georgia Inst. Technol.; U.S. Army

Publication Date: 1/90

Algebraic specification techniques in object oriented programming environments

Author: Breu, R.

Publisher: Springer-Verlag, Berlin, Germany

Reference Number: C9204-6110J-012

Publication Date: 1/91

Reuse-oriented structured analysis for embedded systems

Author: Ihme, T.

Reference Number: C9207-6110B-064

Publication Date: 11/91

Proceedings of the Fifteenth Annual International Computer Software and Applications Conference (Cat. No.91CH3023-9)

Publisher: IEEE Comput. Soc. Press, Los Alamitos, CA, USA

Reference Number: C9211-7100-015

Sponsoring Organization: IEEE; Inf. Process. Soc. Japan

Publication Date: 1/91

Object Oriented Approach in Information Systems. Proceedings of the IFIP TC8/WG8.1 Working Conference

Publisher: North-Holland, Amsterdam, Netherlands

Reference Number: C9212-7100-022

Publication Date: 1/91

Technology of Object-Oriented Languages and Systems. Proceedings of the Second International Conference. TOOLS

Publisher: Angkor, Paris, France

Reference Number: C9301-6110J-002

Publication Date: 1/90

Software for parallel computers p.245-54

Author: Delves, L.

Publisher: Chapman and Hall, London, UK

Reference Number: C9204-6110P-033

Publication Date: 1/92

IEE Colloquium on 'Automating Formal Methods for Computer Assisted Prototying' (Digest No.008)

Publisher: IEE, London, UK

Reference Number: C9206-6110B-036

Sponsoring Organization: IEE

Publication Date: 1/92

Model of application integration and communication

Author: Gustafson, J.; Ketonen, J.; Sventek, J.

Publisher: Hewlett-Packard Lab., Palo Alto, CA, USA

Reference Number: B9206-6210L-125, C9206-6110J-017

Publication Date: 3/92

Bus-based kits fo reusable software

Author: Beach, B.W.; Griss, M.L.; Wentzel, K.D.

Publisher: Hewlett-Packard Lab., Palo Alto, CA, USA

Reference Number: C9207-6110B-040

Publication Date: 4/92

ACE: a new approach to building interactive graphical applications

Author: Johnson, J.A.; Nardi, B.A.; Zarmer, C.L.; Miller, J.R.

Publisher: Hewlett-Packard Lab., Palo Alto, CA, USA

Reference Number: C9301-6180-005

Publication Date: 9/92

Advanced Information Systems Engineering. 4th International Conference CAiSE '92. Proceedings

Publisher: Springer-Verlag, Berlin, Germany

Reference Number: C9301-6160-014

Publication Date: 1/92

Progress in simulation. Vol.1 p.159-85

Author: McHaney, R.

Publisher: Ablex Publishing, Norwood, NJ, USA

Reference Number: C9301-7420D-007

Publication Date: 1/92

Automated software generation approaches for the design and development of guidance and control systems software

Publisher: AGARD, Neuilly sur Seine, France

Reference Number: C9301-7420D-008

Publication Date: 3/92

Refactoring object-oriented frameworks

Author: Opdyke, W.F.

Publisher: Univ. Illinois at Urbana-Champaign, IL, USA

Reference Number: C9302-6110J-005

Publication Date: 6/92

Reusable data flow diagrams

Author: Islam, N.; Campbell, R.H.

Publisher: Univ. Illinois at Urbana-Champaign, IL, USA

Reference Number: C9304-6110J-028

Publication Date: 12/92

Next Generation CASE Tools

Publisher: IOS Press, Amsterdam, Netherlands

Reference Number: C9306-6115-017

Publication Date: 1/92

Exception handling mechanism for parallel object-oriented programming. Towards the design of reusable and robust

Author: Issarny, V.

Publisher: Inst. Nat. Recherche Inf. Autom., Le Chesnay, France

Reference Number: C9306-6110P-013

Publication Date: 10/92

IEE Colloquium on 'Case-Based Reasoning' (Digest No.036)

Publisher: IEE, London, UK

Reference Number: C9306-6170-035

Sponsoring Organization: IEE

Publication Date: 1/93

Concurrent programming notations in the object-oriented language Arche

Author: Benveniste, M.; Issarny, V.

Publisher: Inst. Nat. Recherche Inf. Autom., Le Chesnay, France

Reference Number: C9307-6140D-037

Publication Date: 12/92

Prototyping a collaborative CAD system by taking advantage of software reuse and a software bus framework

Author: Gisi, M.A.; Sacchi, C.

Publisher: Hewlett-Packard Lab., Palo Alto, CA, USA

Reference Number: C9309-7400-010

Publication Date: 4/93

Economics of software reuse revisited

Author: Malan, R.; Wentzel, K.

Publisher: Hewlett-Packard Lab., Palo Alto, CA, USA

Reference Number: C9309-0310F-016

Publication Date: 4/93

LOGIDATA+: deductive databases with complex objects p. 176-94

Author: Fabrizio, A.; Capaccioli, M.; Valeri, S.

Publisher: Springer-Verlag, Berlin, Germany

Reference Number: C9401-6110L-004

Publication Date: 1/93

Proceedings of the Seventh Knowledge-Based Software Engineering Conference (Cat. No.92TH0480-4)

Publisher: IEEE Comput. Soc. Press, Los Alamitos, CA, USA

Reference Number: C9401-6110B-057

Sponsoring Organization: IEEE; Rome Lab., Griffiss AFB; AAAI; ACM

Publication Date: 1/92

Proceedings IEEE Second Workshop on Program Comprehension (Cat. No.93TH0551-2)

Publisher: IEEE Comput. Soc. Press, Los Almitos, CA, USA

Reference Number: C9403-6110B-023

Sponsoring Organization: IEEE; CRIAI

Publication Date: 1/93

Advanced database systems p.87-103

Author: Bhargava, B.; Jiang, Y.-H.; Srinivasan, J.; Dewan, P.

Publisher: Springer-Verlag, Berlin, Germany

Reference Number: C9403-6160J-020

Publication Date: 1/93

Analytical methods in software engineering economics p. 39-73

Author: Banker, R.D.; Kauffman, R.J.

Publisher: Springer-Verlag, Berlin, Germany

Reference Number: C9406-7120-025

Publication Date: 1/93

Analytical methods in software engineering economics p. 99-137

Author: Cruickshank, R.D.; Gaffney, J.E., Jr.

Publisher: Springer-Verlag, Berlin, Germany

Reference Number: C9406-0310F-030

Publication Date: 1/93

Advances in software engineering and knowledge engineering

Author: Ambriola, V.; Tortora, G.

Publisher: World Scientific, Singapore

Reference Number: C9408-6110B-008

Publication Date: 1/93

Advances in software engineering and knowledge engineering p.159-71

Author: Maarek, Y.S.

Publisher: World Scientific, Singapore

Reference Number: C9408-6110B-049

Publication Date: 1/93

Experience With the Management of Software Projects 1992. Proceedings of the Fourth IFAC/IFIP Workshop

Publisher: Pergamon, Oxford, UK

Reference Number: C9304-0310F-005

Publication Date: 1/92

10th International Conference on Software Engineering, Singapore

Publisher: IEEE Computer Society Press

Publication Date: 4/88

Proceedings of the Ada Debut

Publication Date: 1/80

Proceedings of the Third Annual Ada Software Engineering Education and Training Symposium

Publication Date: 6/88

Proceedings of the Third Annual Nat'l Conference on Ada Technology

Publication Date: 3/85

Using Ada. A new Era in Adaptable, Reliable Software

Publication Date: 6/83

Ada 95 Rationale: The Language / The Standard Libraries

Abstract: This document describes the rationale for Ada 9X, the revised International Standard. It is arranged into four parts: 1) Introduction to Ada 9X, presenting a general discussion of the scope and objectives of Ada 9X and its major technical features; 2) a chapter-by-chapter account of the Core language; 3) annexes which address the needs of specialized application areas, and 4) an Appendix, which addresses the issue of upward compatibility with Ada 83 and shows that, for normal programs, the goal of compatibility has been achieved.

Author: The Ada 9X Design Team

Publisher: Intermetrics

Sponsoring Organization: Ada 9X Project Office

Producing Organization: Intermetrics

Publication Date: 1/95

Proposed ANSI/ISO Standard [ANSI/ISO/IEC CD 8652]: Ada 9X Reference Manual -- The Language and the Standard Libraries

Abstract: This Draft International Standard specifies the form and meaning of programs written in Ada. Its purpose is to promote the portability of Ada programs to a variety of data processing systems. This Draft International Standard specifies: the form of a program written in Ada, the effect of translating and executing such a program, the manner in which program units may be combined to form Ada programs, the language-defined program units that a conforming implementation is required to supply, the permissable variations within the standard and the manner in which they are to be documented, those violations of the standard that a conforming implementation is required to detect and the effect of attempting to translate or execute a program containing such violations, and those violations of the standard that a conforming implementation is not required to detect. The Ada 9X Reference Manual is divided into chapters, each with several sections: 1- General, 2- Lexical Elements, 3- Declarations and Types, 4- Names and Expressions, 5- Statements, 6- Subprograms, 7- Packages, 8- Visibility Rules, 9- Tasks and Synchronization, 10- Program Structure and Compilation Issues, 11- Exceptions, 12- Generic Units, 13- Representation Clauses and Implementation-Dependent Features, and 14- Input-Output.

Author: Ada 9X Mapping/Revision Team

Publisher: Intermetrics, Inc.

Reference Number: ANSI/ISO/IEC CD 8652; IR-MA-1363-3

Sponsoring Organization: AJPO

Producing Organization: Intermetrics, Inc.

Publication Date: 9/93

International Standard [ANSI/ISO/IEC-8652:1995]: Ada 95 Reference Manual -- The Language and the Standard Libraries

Abstract: This International Standard specifies the form and meaning of programs written in Ada. Its purpose is to promote the portability of Ada programs to a variety of data processing systems. This International Standard specifies: the form of a program written in Ada, the effect of translating and executing such a program, the manner in which program units may be combined to form Ada programs, the language-defined program units that a conforming implementation is required to supply, the permissable variations within the standard and the manner in which they are to be documented, those violations of the standard that a conforming implementation is required to detect and the effect of attempting to translate or execute a program containing such violations, and those violations of the standard that a conforming implementation is not required to detect. The Ada 95 Reference Manual is divided into chapters, each with several sections: 1- General, 2- Lexical Elements, 3- Declarations and Types, 4- Names and Expressions, 5- Statements, 6- Subprograms, 7- Packages, 8- Visibility Rules, 9- Tasks and Synchronization, 10- Program Structure and Compilation Issues, 11- Exceptions, 12- Generic Units, and 13- Representation Issues.

Author: Ada 9X Mapping/Revision Team

Publisher: Intermetrics, Inc.

Reference Number: ANSI/ISO/IEC-8652:1995 (replaces ISO 8652:1987)

Sponsoring Organization: AJPO

Producing Organization: Intermetrics, Inc.

Publication Date: 1/95

Proposed Military Standard [Proposed MIL-STD-CAIS]: Common APSE Interface Set (CAIS)

Abstract: This document provides specifications for a set of Ada packages, with their intended semantics, which together form a set of common interfaces for Ada Programming Support Environments (APSEs). This set of interfaces is known as the Common APSE Interface Set (CAIS) and is designed to promote the source-level portability of Ada programs, particularly Ada software development tools. This version of the CAIS is intended to provide the basis for evolution of the CAIS as APSEs are implemented, as tools are transported, and as tool interoperability issues are encountered. The goal of the CAIS is to promote interoperability and transportability of Ada software across DoD APSEs. The contents of this standard are divided into chapters, each with several sections: 1- Scope, 2- Referenced Documents, 3- Definitions, 4- General Requirements, and 5- Detailed Requirements.

Author: KIT/KITIA, CAIS Working Group

Publisher: DoD

Sponsoring Organization: AJPO

Producing Organization: KIT/KITIA, CAIS Working Group

Publication Date: 10/84

Proposed Military Standard: Common APSE Interface Set (CAIS)

Abstract: This document provides specifications for a set of Ada packages, with their intended semantics, which together form a set of common interfaces for Ada Programming Support Environments (APSEs). This set of interfaces is known as the Common APSE Interface Set (CAIS) and is designed to promote the source-level portability of Ada programs, particularly Ada software development tools. This version of the CAIS is intended to provide the basis for evolution of the CAIS as APSEs are implemented, as tools are transported, and as tool interoperability issues are encountered. The goal of the CAIS is to promote interoperability and transportability of Ada software across DoD APSEs. The contents of this standard are divided into chapters, each with several sections: 1- Scope, 2- Referenced Documents, 3- Definitions, 4- General Requirements, and 5- Detailed Requirements.

Author: KIT/KITIA, CAIS Working Group

Publisher: DoD

Sponsoring Organization: AJPO

Producing Organization: KIT/KITIA, CAIS Working Group

Publication Date: 8/84

Engineer's Handbook (CARDS)

Abstract: This Engineer's Handbook was developed under the Central Archive for Reusable Defense Software (CARDS) Program to help facilitate advances in software reuse techniques and technologies. This document provides guidance to government System Program Office (SPO) Engineers on envisioned changes to their duties and responsibilities as domain-specific software reuse becomes incorporated into mainstream DoD system/software acquisition and engineering processes.

Author: Fronczek, Chris et al.

Publisher: CARDS

Reference Number: STARS-VC-B002/002/00

Sponsoring Organization: Department of the Air Force

Producing Organization: Unisys Corporation

Publication Date: 2/94

Training Plan (CARDS)

Abstract: The Central Archive for Reusable Defense Software (CARDS) Training Plan serves as a comprehensive guide for creating training courses and training materials on domain-specific reuse for Department of Defense (DoD) organizations, DoD contractors, system engineers, and university professors. The Training Plan provides guidance for conducting three different domain-specific software reuse training courses for four different audiences. The intent of the courses in the Training Plan is to demonstrate how software reuse can reduce development and maintenance time and costs, reduce project risks, and increase productivity.

Author: Facemire, Harry J. and Kerrin Smith

Publisher: CARDS

Reference Number: STARS-VC-B003/001/00

Sponsoring Organization: Department of the Air Force

Producing Organization: Unisys Corporation

Publication Date: 1/94

Component Provider's and Tool Developer's Handbook (CARDS)

Abstract: This Component Provider's and Tool Developer's Handbook was developed under the Central Archive for Reusable Defense Software (CARDS) Program to help facilitate software reuse adoption. Government developers and software industry vendors supporting government acquisitions are provided with guidance for developing domain-specific, reusable components and tools supporting reuse. The goal of this handbook is to stimulate the development and commercialization of large-scale components and tools for vertical domains. Focus is placed on architecture-centric, library-assisted software reuse. It is assumed the reader is familiar with the design and development of software. The audience for this handbook consists of government employees [domain and System Program Office (SPO) engineers] and contractors [component creators and tool developers].

Author: Nilson, Roslyn et al.

Publisher: CARDS

Reference Number: STARS-VC-B017/001/00

Sponsoring Organization: Department of the Air Force

Producing Organization: Unisys Corporation

Publication Date: 3/94

Model Contracts/Agreements (CARDS)

Abstract: The Central Archive for Reusable Defense Software (CARDS) Program, sponsored by the U.S. Air Force (ESC/ENS), Hanscom AFT, MA, has been investigating business areas that impact software reuse. An on-going forum, made up of DoD lawyers and contracting officers familiar with software reuse, has been established by the CARDS Program to examine legal issues and concerns related to software reuse. One primary finding from these software reuse legal forums is risk can be managed by carefully negotiating and drafting agreements. This document provides sample agreements and associated guidelines for implementation by the CARDS Library staff. They are based on the current CARDS Command Center Library's business, operational, and qualification processes and concepts, as well as recommended policy changes [CARDS93b] [DSD]. This will allow the CARDS Library staff to interact with its customers (suppliers of components, users of the reusable components, and interoperating libraries) to help reduce operating risk, meet its operational and technical goals, and meet the needs of its customers.

Author: Bowes, Robert J. and Theresa R. Huber

Publisher: CARDS

Reference Number: STARS-VC-B014/001/00

Sponsoring Organization: Department of the Air Force

Producing Organization: Unisys Corporation

Publication Date: 3/94

Portable Reusable Integrated Software Modules (PRISM) Documentation Library Model Document (CARDS)

Abstract: This Portable, Reusable, Integrated Software Modules (PRISM) Documentation Library Release 1.0 Model Document was created by the Central Archive for Reusable Defense Software (CARDS) Program to help disseminate PRISM documentation and knowledge. It represents the current state of the PRISM Documentation Library Model. It is a 'living' document and will be updated with every Library release. This document describes library modeling and examines modeling concepts and specialization/aggregation hierarchies. This document is specific to PRISM Documention Library Model Release 1.0 in its description of document types, actual documents available and future direction of this model. The intended audience is anyone desiring an understanding of the PRISM Documentation Library Model and wanting a description of this current Library release. The reader should have an understanding of CARDS and PRISM.

Author: Petracca, Aleisa et al.

Publisher: CARDS

Reference Number: STARS-VC-B006/001/00

Sponsoring Organization: Department of the Air Force

Producing Organization: Unisys Corporation

Publication Date: 12/93

Market Study (CARDS)

Abstract: The Market Study supplies the Central Archive for Reusable Defense Software (CARDS) program with information regarding the current state-of-the-practice of software development and maintenance within the military services. Results of analysis of collected data reflect current practices, as well as identified needs within each military service for establishment of a suitable infrastructure to enable reuse. Full comprehension of the software needs of potential reusers is required before CARDS can address its ultimate goal of facilitating widespread software reuse throughout the DoD. The focus of results has therefore been geared toward facilitating the CARDS process of institutionalizing software reuse within the Department of Defense (DoD) by more finely concentrating our development, technology transfer, and franchising efforts toward satisfaction of identified requirements.

Author: Meheran, Lynn G.

Publisher: CARDS

Reference Number: STARS-VC-B001/004/00

Sponsoring Organization: Department of the Air Force

Producing Organization: Unisys Corporation

Publication Date: 3/94

Portable Reusable Integrated Software Modules (PRISM) Documentation Library User's Guide (CARDS)

Abstract: The Portable, Reusable, Integrated software Modules (PRISM) Documentation Library User's Guide was developed under the Central Archive for Reusable Defense Software (CARDS) Program to help disseminate PRISM documentation and knowledge. It represents the current state of the PRISM Documentation Library (PDL) Model. It is a 'living' document and will be updated with every Library release. This document describes the method needed to access the PDL Model. This Guide is specific to PDL Model release 1.0. The intended audience is anyone desiring an understanding of, or wanting access to, this release of the PDL Model.

Author: Trail, Glenn and George Jackelin

Publisher: CARDS

Reference Number: STARS-VC-B006/001/00

Sponsoring Organization: Department of the Air Force

Producing Organization: Unisys Corporation

Publication Date: 12/93

Portable Reusable Integrated Software Modules (PRISM) Documentation Library (CARDS)

Abstract: This Version Description Document has been prepared for CARDS (Central Archive for Reusable Defense Software) Portable, Reusable, Integrated Software Modules (PRISM) Documentation Library (PDL) Release 1.0 and describes: known problems and work arounds (where possible), Installation instructions, A list of files for this release, and A release tape file list. This VDD is part of the CARDS library release package which includes the actual release, a library user's manual, and a library model document.

Author: Jackelen, George and Larry McCutchan

Publisher: CARDS

Reference Number: STARS-VC-B007/000/01

Sponsoring Organization: Department of the Air Force

Producing Organization: Unisys Corporation

Publication Date: 12/93

Command Center Supported Components Report (CARDS)

Abstract: A software reuse library is only useful if the assets within the library can be quickly and easily located, evaluated, and the characteristics of the assets be easily understood. This Command Center Supported Components Report provides a set of guidelines, initially developed for Command Center Libraries, to assist domain engineers and/or the qualification team in charge of the library in providing information on domain-specific qualified library assets. These guidelines consist of one page templates describing a component from a high level viewpoint, i.e., "glossies," and a multi-page template describing a component in greater technical detail, i.e., "technical brief." Two examples of a glossy and technical brief are provided in the appendix.

Author: Estep, James and Kerri Haines

Publisher: CARDS

Reference Number: STARS-VC-B013/001/00

Sponsoring Organization: Department of the Air Force

Producing Organization: Unisys Corporation

Publication Date: 2/94

Command Center Library (CCL) Version Description Document (CARDS)

Abstract: This Version Description Document has been prepared for Comprehensive Approach to Reusable Defense Software (CARDS) Command Center Library (CCL) Release 4.0 and describes 1) changes from the previous release, 2) known problems and work arounds (where possible), 3) installation instructions, 4) a list of files for this release, and 5) a release tape file list. This VDD is part of the CARDS library release package which includes an electronic media containing a copy of the Library, a Library User's Guide, and a Library Model Document.

Author: Bock, Thomas M. and Larry McCutchan

Publisher: CARDS

Reference Number: STARS-VC-B007/006/00

Sponsoring Organization: Department of the Air Force

Producing Organization: Unisys Corporation

Publication Date: 8/94

Library Operations Policies and Procedures (CARDS)

Abstract: The Central Archive for Reusable Defense Software (CARDS) Program is a DoD initiative to transfer the technologies of library-assisted domain-specific reuse into other DoD software procedures and procurements. The Library Operations Policies and Procedures (LOPP) serves as a comprehensive guide for operating and maintaining a reuse library. Volume One of the LOPP is aimed toward upper level management through the technical supervisor level and provides a high level view of the policies and procedures for library operations. Volume One provides access to information concerning strategies for managing and maintaining an existing reuse library system. This document provides recommendations on implementing operations of the library, showing how to assure task accountability and completion, and indicating an expected level of knowledge for the staff at hand. Volume One focuses on the CARDS Library as its model implementation environment. To allow the library implementor to use this document as a reference guide, Volume One is intentionally organized to be free of a specific management structure.

Author: Cortes, Ricardo and Mark Quick

Publisher: CARDS

Reference Number: STARS-VC-B004/002/00

Sponsoring Organization: Department of the Air Force

Producing Organization: Unisys Corporation

Publication Date: 2/94

Library Operations Policies and Procedures (CARDS)

Abstract: The Central Archive for Reusable Defense Software (CARDS) Program is a DoD initiative to transfer the technologies of library-assisted domain-specific reuse into other DoD software procedures and procurements. The Library Operations Policies and Procedures (LOPP) serves as a comprehensive guide for operating and maintaining a reuse library. Volume Two of the Library Operation Policies and Procedures (LOPP) provides detailed operating instructions for day-to-day operation and maintenance of the Library. Volume Two targets the technical individual who will be implementing the policies and procedures of the LOPP, Volume One. Volume Two provides detailed descriptions of the day-to-day tasks for operating and maintaining a reuse library. This document also provides quick access to the specific areas of interest and is designed to allow the reader to retrieve only information specific to their area of interest or concern. In addition to outlining the CARDS daily operations, Volume Two contains those forms referenced in Volume One. Volume Two focuses on the CARDS Library as its model implementation environment. To allow the library implementor to use this document as a reference guide, Volume Two is intentionally organized to be free of a specific mnagement structure.

Author: Cortes, Ricardo and Mark Quick

Publisher: CARDS

Reference Number: STARS-VC-B004/002/01

Sponsoring Organization: Department of the Air Force

Producing Organization: Unisys Corporation

Publication Date: 6/95

Library Development Handbook (CARDS)

Abstract: The process of developing a domain-oriented reuse library is elaborate. This Library Development Handbook provides an overview of the phases involved in developing such a library: domain analysis, library encoding, and library population. This Handbook presents a generic library population process that has been developed by the Central Archive for Reusable Defense Software (CARDS) library development team. This Handbook enumerates specific instructions and examples for populating a domain-oriented reuse library, based on this library population process. We are currently assessing the implications of legal issues on our policies and procedures. Appropriate risk reduction procedures will be detailed in subsequent releases.

Author: Curfman, Brian et al.

Publisher: CARDS

Reference Number: STARS-VC-B005/001/00

Sponsoring Organization: Department of the Air Force

Producing Organization: Unisys Corporation

Publication Date: 10/93

Command Center Library User's Guide

Abstract: This Common Center Library (CCL) User's Guide was developed under the Comprehensive Approach to Reusable Defense Software (CARDS) Program to help disseminate the Portable Reusable Integrated Software Modules (PRISM) Program documentation and knowledge. It represents the current state of the CCL Models. It is a 'living' document and will be updated with every CCL release. This document describes the method needed to access the CCL Models. This Guide is specific to CCL Model Release 4.0. The intended audience is anyone desiring an understanding of, or wanting access to, the current release of the CCL Models.

Author: Bock, Tom

Publisher: CARDS

Reference Number: STARS-VC-B006/003/00

Sponsoring Organization: Department of the Air Force

Producing Organization: Unisys Corporation

Publication Date: 5/94

Acquisition Handbook (CARDS)

Abstract: The Acquisition Handbook is aimed towards all Government Program Managers and their support personnel, such as Contracting Officers and Administrators, procurement attorneys, and program control, involved in systems, subsystems, and component acquisition and maintenance. The concepts discussed assume that the reader has at least three years experience in acquisition. This guidebook will assist them in incorporating software reuse into all phases of the acquisition life cycle, from concept exploration to Post Deployment Software Support (PDSS). It is not a 'cookbook' for every possible reuse issue or strategy, rather it is meant to help you develop and tailor reuse programs. The goal of the Acquisition Handbook is to encourage software reuse during the acquisition and maintenance portions of the lifecycle process, ranging from planning the acquisition strategy through awarding the contract to managing the effort and follow-on support. Software reuse guidance will be presented by providing methods, examples, recommendations and techniques to implement various reuse strategies throughout the acquisition life cycle. The implications and effects of software reuse on the technical, management, cost, schedule, and risk aspects of a program/system during the acquisition process will be the foundation of this document.

Author: Delgado, Leandro V. et al.

Publisher: CARDS

Reference Number: STARS-VC-B011/001/00

Sponsoring Organization: Department of the Air Force

Producing Organization: Unisys Corporation

Publication Date: 3/95

Direction Level Handbook -- Update (CARDS)

Abstract: The Direction Level Handbook is directed towards acquisition executives of all the services to facilitate the institutionalization of software reuse. The audience of Program Executive Officers (PEOs), Designated Acquisition Commanders (DACs), and their supporting staff, are provided with a framework to assist them in establishing plans to manage reuse across their systems and to reach the goals outlined in the DoD Software Reuse Vision and Strategy document. Considerations are provided to assist in incorporating software reuse into the initial planning stages of an acquisition, as well as at critical points within the acquisition life cycle. The options provided the executive will allow him to gain the greatest benefits from software reuse while optimizing the use of shrinking resources. This publication of the Direction Level Handbook is an update of the initial 20 November 1992 published version.

Author: Delgado, Leandro V. et al.

Publisher: CARDS

Reference Number: STARS-VC-B012/001/00

Sponsoring Organization: Department of the Air Force

Producing Organization: Unisys Corporation

Publication Date: 3/94

Technical Concept Document (CARDS)

Abstract: The Central Archive for Reusable Defense Software (CARDS) program is a concerted DoD initiative to transition advances in the techniques and technology of library-aided, architecture-centric, domain-specific software reuse into mainstream DoD software procurement. This technology transition effort involves the development of a domain-specific reuse library for researching technologies and methodologies for creating reuse libraries. This document describes the technical concepts employed towards the development of the CARDS Command Center Library. It is an update to a previous version published on February 26, 1993 [39]. CARDS views a reuse library as reusable software components, a library model and supporting library applications. This view, and its consequences on library development are presented in this document. A discussion of model-based reuse library infrastructure presents a model-based view of library development, with an emphasis on distinctions between domain and library modeling. The component qualification process is presented as an integral part of the library development process. Modeling of the Command Center Library has evolved to support development and integration of various reuse library applications. The CARDS system composition and component qualification tools are discussed. This document also presents technical aspects of the operational library, such as distribution options (e.g. AFS), reuse library security issues (an overview of the CARDS security analysis is presented), and advances made in interoperation between reuse libraries.

Author: Estep, James L. and Scott A. Hissam

Publisher: CARDS

Reference Number: STARS-VC-B009/001/00

Sponsoring Organization: Department of the Air Force

Producing Organization: Unisys Corporation

Publication Date: 2/94

Franchise Plan (CARDS)

Abstract: The Central Archive for Reusable Defense Software (CARDS) Franchise Plan is a tool to help management, with assistance from CARDS, develop a detailed, tailored implementation plan which will prepare the organization to begin the process of software reuse. The CARDS Franchise Plan is targeted toward management level personnel and is meant to introduce reuse and obtain assistance from programs such as CARDS to do reuse. The Franchise Plan presents a planning process for building a reuse infrastructure. To establish a reuse infrastructure, the Franchise Plan will describe the steps that need to be accomplished: 1) Establish management commitment for reuse; 2) Develop a) An Organizational Assessment that defines an organization's current state of affairs and assesses its potential for reuse, b) A Requirements/Implementation Study that determines the organization's requirements for instituting reuse, and c) A Reuse Implementation Plan that describes those steps necessary to implement a reuse infrastructure. This document is an update to CARDS Franchise Plan, STARS-AC-04116/001/11, 30 March 93.

Author: Armstrong, Rose Marie

Publisher: CARDS

Reference Number: STARS-VC-B010/001/00

Sponsoring Organization: Department of the Air Force

Producing Organization: Unisys Corporation

Publication Date: 2/94

PRISM Distribution Library (PDL) Version Description Document (CARDS)

Abstract: This Version Description Document has been prepared for the Comprehensive Approach to Reusable Defense Software (CARDS) Program PRISM Distribution Library (PDL) Release 2.0 and contains: 1) Release Notes, 2) Tape Installation Procedures, and 3) A List of Files for this release.

Author: Bock, Thomas M.

Publisher: CARDS

Reference Number: STARS-VC-K007/001/00

Sponsoring Organization: Department of the Air Force

Producing Organization: Unisys Corporation

Publication Date: 10/94

Proceedings: Software Reuse Legal Issues Workshop (CARDS)

Abstract: This paper documents the Central Archive for Reusable Defense Software (CARDS) sponsored Software Reuse Legal Issues Workshop, held in Arlington, VA, 22-25 Mar 93. 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 liabliity, 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 proceedings are intended for use by managers responsible for formulating or implementing plans of operation for software reuse libraries. It provides an overview of some of the problem elements which must be taken into account and is intended to promote discussion and serve as the occasion for taking specific questions to counsel for their opinion.

Author: DSD Laboratories, Inc.

Publisher: CARDS

Reference Number: STARS-AC-04117/001/00

Sponsoring Organization: Department of the Air Force

Producing Organization: Paramax Systems Corporation

Publication Date: 4/93

Software Architecture Seminar Report (CARDS)

Abstract: In order to increase awareness, explore current research into software architectures as a means of implementing software reuse, and examine current practices and issues involving architectures, the Central Archive for Reusable Defense Software (CARDS) Program sponsored a Software Architecture Seminar and Workshop at West Virginia University's Concurrent Engineering Research Center (CERC) facility in Morgantown, West Virginia on November 16 and 17, 1993. The goals of the Seminar and Workshop were to understand the various meanings of software architecture, current research in the field of architecture, and current efforts in applying software architecture. This document provides highlights of the Seminar and Workshop. This document contains an overview of the proceedings of the Architecture Seminar on Tuesday, November 16 and the Architecture Workshop on Wednesday, November 17. It also includes issues discussed, questions and answers, working group discussions, and references. This document also contains presentation slides from the Seminar, the Seminar panel discussion, and the Workshop.

Author: Facemire, H. Jeff et al.

Publisher: CARDS

Reference Number: STARS-VC-B002/001/00

Sponsoring Organization: Department of the Air Force

Producing Organization: Unisys Corporation

Publication Date: 1/94

Software Reuse Acquisition Scenarios, A Discussion Paper (Draft)

Abstract: The eleven reuse acquisition scenarios in this report were developed by members of the RAAT for use by the DoD and other organizations to represent a variety of reuse-oriented business practices. They are models suggested by both government and industry representatives to facilitate reuse within the acquisition process. They were constructed as steady-state models, without being constrained by the immediate regulatory environment and available technical assets. However, most could be performed in some domains today. A few may require relatively minor changes in the regulations (although any change in the regulations is a non-trivial obstacle). The scenarios are a specific response to a request by the Reuse Executive Steering Committee of the OASD C3I for examples of how we can do business and what relative advantages and disadvantages these various business approaches have for both government and industry participants. All are designed to bring the general benefits of software reuse to the organizations involved. These include better management of a large organization's software assets, more reliable systems, reduced costs and risks, shorter schedules, and greatly improved maintenance operations. An individual organization may find advantages or disadvantages different from the ones identified or may need to apply variations to the scanarios presented. In that case, the applicable scenario(s) should be tailored by the organization to fit its specific circumstances.

Author: Reuse Acquisition Action Team (RAAT)

Publisher: Association for Computing Machinery (ACM) Special Interest Group on Ada (SIGAda) Reuse Working Group

Publication Date: 7/94

Glossary of Software Reuse Terms

Abstract: One method proposed for increasing the efficiency of software production is the development of large reliable software applications is the systematic reuse of existing software products. Effective software reuse will require new techniques to supplement traditional software engineering practices. Preliminary research has already produced new methods and reports. As a result, new terminology has emerged. This report provides a baseline set of recommended definitions for terms commonly used in the software reuse community. The glossary will be expanded as further research results become available and are evaluated for use in software reuse programs.

Author: Katz, Susan, et al.

Publisher: NIST

Reference Number: NIST Special Publication 500-222

Publication Date: 12/94

DoD Software Risk Assessment and Mitigation Procedure (RAMP) Final Technical Progress Report

Abstract: Department of Defense (DoD) software costs have grown substantially over the last thirty years and are expected to reach $42 billion in 1995. Moreover, DoD software-intensive systems have been subject to both schedule slippage and poor performance. The effective application of risk management and software reuse throughout the acquisition of a DoD system can be a major factor in containing software life cycle costs and in improving the performance and reliability of the system. This Technical Report documents the activities performed in the development of a prototype DoD procedure aimed at assisting in the management of risks, in particular risks associated with software reuse. The procedure is called the Software Risk Assessment and Mitigation Procedure (RAMP). This Technical Report documents the results of the Phase I and Phase II efforts of the RAMP Project. The purpose of Phase I and Phase II of the RAMP Project was to demonstrate the viability and appropriateness of RAMP within the DoD. RAMP is a prototype DoD risk assessment and mitigation procedure with special emphasis on software reuse. RAMP is intended to promote reuse within the DoD by assessing and mitigating risks associated with reuse. RAMP's target customer is a DoD project manager who depends on an in-place contractor to deliver a product containing a complex software system involving reuse who has concerns about the contractor's ability to deliver. RAMP leverages selected industry, government, and academic practices. In particular, RAMP leverages the Bell Canada Trillium product development process capability model [Tril94], the Software Engineering Institute (SEI) Capability Maturity Model (CMM) [SEI93B], and the SEI risk management paradigm [SEI93A]. Trillium is based upon the SEI CMM, the Malcolm Baldridge National Quality Award Criteria, the ISO 9001 and 8402 Standards, and the IEEE Software Engineering Standards, among others. RAMP is composed of three parts: 1) A product development process capability model that is an adaptation of the Trillium model to include DoD, risk management, and reuse principles, 2) An assessment procedure, 3) A mitigation procedure.

Publisher: DoD

Sponsoring Organization: DoD Software Reuse Initiative, DISA

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

Publication Date: 1/95

Component Evaluation Procedure (Phase II) Technical Report

Abstract: Department of Defense (DoD) software costs are projected to reach $42 billion in 1995. This is a result of drastic increases in software functionality incorporated in government systems over the last thirty years. The effective implementation of software reuse can contribute to the reduction in the incredible growth of government software development costs, while at the same time providing improved system performance and reliability. The Component Evaluation Procedure (CEP) being developed by the Software Engineering Division (SED) of the U.S. Army Space & Strategic Defense Command (USASSDC) is intended to provide a cost effective, quantitative measurement of the reusability of existing legacy software components. The CEP is a uniform, flexible procedure which is general enough to be applied to all types of software components (e.g., requirements, designs, documentation, test data). Current efforts have concentrated on the application of the CEP to Ada source code components. The CEP is being developed in phases, with current Phase II effort being a continuation of earlier work begun by the USASSDC SED. The initial output of Phase I was the CEP model and a list of 21 proposed reusability criteria divided into four categories. Near the end of Phase I activity, a project office supplied the SED with 13 reusability criteria being considered for use in an ongoing program. The criteria were integrated into the original set to exploit any synergy possible between activities. Phase II focused on the application and validation of the set of reusability criteria using Ada components from the BM/C3 domain. Phase III activities will involve the development of the Risk Analysis and Report Generation elements of the CEP, while Phase IV activities will address the validation of the entire CEP.

Publisher: DoD

Sponsoring Organization: DoD Software Reuse Initiative, DISA

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

Publication Date: 1/95

Software Reuse Business Model (SRBM) Technical Report

Abstract: The development of software-intensive systems can be enhanced by leveraging proven software components from previous or parallel efforts. Historically, government and industry software systems have been improved through the adoption of reuse principles. This document presents the Software Reuse Business Model (SRBM), which details the incorporation of reuse principles into the acquisition cycle of software-intensive systems within the Department of Defense (DoD) organizations. These systems can include weapon systems, command and control systems, information systems, and other software systems without respect to size of the system or regard to the phase of the system within the software engineering life cycle. A business model provides a complete, consistent structure that is used to define the typical architectures and implementation plans of a business [Spewak1993]. The SRBM addresses the business of software reuse within the DoD organizations. The purpose of the SRBM is to present a formal structure for DoD acquisition professionals to follow while considering the viability and applicability of reuse within the framework of DoD organizations. The purpose of this technical report is to describe the SRBM for the DoD upper level management as well as the user of the SRBM.

Publisher: DoD

Sponsoring Organization: DoD Software Reuse Initiative, DISA

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

Publication Date: 1/95

Missle Defense Domain Identification (MDDI) Technical Report

Abstract: This document provides the results fo the Missle Defense Domain Identification (MDDI) task and was prepared in accordance with the data item description (DID) DI-MISC-80048. This effort was performed for the Department of Defense (DoD) Software Reuse Initiative (SRI) by the Software Engineering Division (SED) of the U.S. Army Space and Strategic Defense Command (USASSDC) in Huntsville, Alabama. As the organization within the DoD responsible for sponsoring efforts to realize the potential life cycle cost savings from software reuse, SRI is in the process of determining how and where to invest in software reuse to achieve a high rate of return on investment. To that end, SRI funded SED to assist in investigating and identifying domains for investment in software reuse. SED initiated the MDDI task to establish a foundation for further investigation and analysis of the Missile Defense domain. The purpose of this technical report is to present the approach, analysis, findings, conclusions, and recommendations resulting from the domain identification of Missile Defense.

Publisher: DoD

Sponsoring Organization: DoD Software Reuse Initiative, DISA

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

Publication Date: 1/95

Software Reuse Videos

Abstract: This document lists several videos dealing with the topic of software reuse, including an outline of the video contents and ordering information.

Author: Reuse Acquisition Action Team (RAAT)

Publisher: Association for Computing Machinery (ACM) Special Interest Group on Ada (SIGAda) Reuse Working Group

Publication Date: 9/94

Software Reuse Initiative: Vision and Strategy

Abstract: This document describes software reuse as a powerful concept. The value of this approach has been demonstrated in many other engineering disciplines where the use of standard concepts, processes, and components allows prior accomplishments to be leveraged and speeds innovation for future systems. At this point, many different techniques which support reuse are being tried. This document provides the focus under which these efforts will continue, "lessons learned" will be collected, and experiences shared. Taken together, the ten strategic steps will bring about the cultural change necessary to make software reuse effective for DoD.

Publisher: DoD-SRI

Reference Number: Document #: 1222-04-210/53

Publication Date: 7/92

Software Reuse Best Practices: Generic Software Reuse Scenarios

Abstract: The objective of the Software Reuse Best Practices task is to identify and document software reuse best practices used in government and industry, in order to provide program managers and program executive officers with guidelines on what "tried and true" reuse practices are available and how they can be applied to DoD systems management. A reuse practice may be a management approach, a tool, a method to accomplish an activity, an organizational philosophy or a procedure; it may accomplish a tactical activity or be the driving force for an entire system's management strategy. This document defines four generic scenarios that provide a context for: 1) design of the best practices study; 2) probing to identify best practices among survey sites; and 3) subsequent analysis and presentation of best practices to this study's customers. The scenarios are: New Application Development, Reengineering, Domain Engineering, Operations and Support. The scenarios focus the area of study, provide context for activities to be observed, and provide a structure for hypotheses and questions to be articulated in the study protocol.

Publisher: DoD-DISA Center for Software

Reference Number: Contract #: DCA100-93-D-0066

Publication Date: 6/95

Technology Roadmap (Working Draft)

Abstract: The Software Reuse Initiative Technology Roadmap responds to the DoD Software Reuse Vision and Strategy [DoD92b], which calls for "a technology-based investment strategy which identifies, tracks, and transitions appropriate reuse-oriented process and product technologies." This roadmap identifies the technologies critical to the goal of institutionalizing software reuse within the DoD. This document consists of two volumes; the first is a technology assessment that provides the basis for recommended DoD technology research investment, and the second is an implementation strategy for performing the research in the recommended reuse technologies. VOLUME 1: Within a defined cause/effect framework, Volume 1 provides analyses of technologies at three different levels. First, the technologies judged to be critical to software reuse are selected and described. Second, maturity profiles for the critical trechnologies are developed. The maturity profiles indicate which of the critical technologies are "lagging," i.e., are not expected to be sufficiently mature in time to contribute adequately to attaining institutionalized software reuse. The third analysis made a judgement as to which of these lagging technologies would best respond to additional DoD investment and thereby contribute significantly to the software reuse goals expressed in the DoD Software Resue Vision and Strategy and draft DoD Software Technology Strategy [DoD91] documents. This analysis produces the investment recommendations. The critical technologies are defined as the enabling technologies for the two major elements, domain engineering and application engineering. Information presented for each of the technologies includes a description, state of the practice, research direction, and gaps between current and desired status.

Publisher: DoD-SRI

Publication Date: 1/95

Technology Roadmap (Working Draft)

Abstract: The Software Reuse Initiative Technology Roadmap responds to the DoD Software Reuse Vision and Strategy [DoD92b], which calls for "a technology-based investment strategy which identifies, tracks, and transitions appropriate reuse-oriented process and product technologies." This roadmap identifies the technologies critical to the goal of institutionalizing software reuse within the DoD. This document consists of two volumes; the first is a technology assessment that provides the basis for recommended DoD technology research investment, and the second is an implementation strategy for performing the research in the recommended reuse technologies. VOLUME 2- Volume 2 presents an implementation strategy for additional DoD investment in reuse technology that was recommended in Volume 1. The strategy covers the five-year period from FY1996 through FY2000. The reuse program described in this document attampts to build on existing reuse research and practice as described in Volume 1. Major programs include the ARPA STARS and DSSA efforts, Air Force and NASA CARDS, SEI, and DISA Software Reuse Program. Some of these (e.g., STARS and DSSA) are scheduled for completion soon. Most of these programs have addressed specific aspects of reuse technology; this one attempts to produce an integrated, usable DoD-wide reuse technology by exploiting the "best of breed" of what already exists and building on it, filling in the gaps, fusing the appropriate technologies, and integrating all parts of the program into a testbed and an environemtn that incorporates reuse as a philosophy. The five major technology thrusts described in this volume are 1) Mathematical Foundations of Reuse, 2) Framework for Measurement and Assessment, 3) Domain and Application Engineering, 4) Process Modeling, and 5) Integrated Environment Testbed.

Publisher: DoD-SRI

Publication Date: 1/95

Program Manager's Reuse Issues Handbook

Abstract: The "DOD Software Reuse Initiative Vision and Strategy" documents the need for Department of Defense (DOD) business managers to establish plans to manage software reuse across their systems. Although reuse seems attractive, it is important that the concept be understood, supported, and managed at corporate levels within the DOD in both the acquisition and software communities. Business, acquisition, and legal issues are perceived as inhibitors to implementing a successful, systematic reuse program within DOD. Program Executive Officers (PEOs) and Program Managers (PMs) must fully understand the contractual issues that need to be addressed in order to successfully incorporate reuse into systems acquisition. This document answers 25 commonly asked reuse questions on acquisition issues. These questions have been grouped into four areas: Strategy/Planning, Contract Preparation, System Development, and Post-Deployment Software Support. Strategy/Planning addresses reuse issues that occur during the acquisition planning stages, such as developing the technical approach, estimating costs, determining risk, and developing associated risk mitigation plans. Contract Preparation examines the contractual process with respect to reuse, such as choosing the best type of contract to meet reuse objectives, determining the data items to include in a contract so that software reuse can be monitored effectively and implemented in other programs. System Development addresses reuse-related activities that the Government performs during a software development effort that includes reuse, such as assessing the reuse progress and the cost effectiveness of a development effort. Post-Deployment Software Support covers the Government's activities after a reuse effort is complete. The answers to these questions are intended to promote consideration of software reuse, reduce or eliminate misconceptions of acquisition and legal barriers to software reuse, familiarize PEOs and PMs with the pertinent reuse acquisition issues, and prompt them to seek further guidance and information on the various topics.

Publisher: CACI

Reference Number: Document #: PD537:31-MAY-95

Sponsoring Organization: DISA

Producing Organization: CACI, Inc. - Federal

Publication Date: 5/95

DOD Software Reuse Initiative Legal/Acquisition Handbook (Coordination Draft)

Abstract: The "DOD Software Reuse Initiative Vision and Strategy" documents the requirement for DOD business managers toestablish plans to manage reuse across their systems. Although reuse seems attractive, it is important that the concept be understood, supported, and managed at corporate levels within the Department of Defense (DOD) for the acquisition, program manager, and functional communities. Legal and acquisition issues continue to be challenges inimplementing a successful, systematic reuse program within the DOD. Program Executive Officers (PEOs) and Program Managers (PMs) must fullycomprehend the impact of intellectual propertylaws pertaining to rights and responsibilities of providers and users of reusablesoftware assets (RSAs), ownership of assets, licensing agreements, and associated liabilities and exposure to damage resulting from claims of patent infringement or copyright violations. Also, DOD reuse libraries and repositories are concerned with product liability claims (e.g., legal recourse by a user or consumer to seek compensation fromthe provider for damages should the reuse asset fail during a critical application). This last issue is a major concern in defining DOD reuse repositories' (software libraries') roles and responsibilities as providers (or 'merchants') of RSAs tosoftware vendors for proposed development efforts. This document focusses on several key legal and acquisition issues that have been raised and addressed in various forums and previously published documents throughout DOD and Industry. Provided are recommended alternatives for a given set of scenarios whereby reuse may be employed. Use of appropritae contractual vehicles by procurement personnel is key ty achieving successful program reuse acquisition strategies that provide financial incentives to contractors. Twenty-five commonly asked reuse questions on legal and acquisition issues have been researched and are grouped according to contractual milestones. The information provided is intended toguide the reader to potential solutions to unique requirements. Recommended alternatives are not all-inclusive, as this handbook must respond to changes in the software reuse community and will require revisions as regulatory and environmental changes occur.

Publisher: CACI

Reference Number: Document #: PC435.2:05-APR-95

Sponsoring Organization: DISA

Producing Organization: CACI, Inc. - Federal

Publication Date: 4/95

DOD Software Reuse Initiative Legal/Acquisition Handbook (Working Draft)

Abstract: The "DOD Software Reuse Initiative Vision and Strategy" documents the requirement for business managers to establish plans to manage reuse across their systems. Although reuse seems attractive, it is important that the concept be understood, supported, and managed at corporate levels within the Department of Defense (DOD) for the acquisition, business manager, and functional communities. Legal and acquisition issues continue to be major inhibitors to implementing a successful, systematic reuse program within the DOD. Program Executive Officers (PEOs) and Program Managers (PMs) must fully comprehend the impact of intellectual property laws pertaining to rights and responsibilities of providers and users of reusable software assets (RSAs); ownership of assets; licensing agreements; and associated liabilities (e.g., legal recourse by a user or consumer to seek compensation from the provider for damages should the reuse asset fail during a critical application). The latter is a major concern in defining the DOD reuse repositories' (software libraries') roles and responsibilities as providers (or 'merchants') of RSAs to software vendors for proposed development efforts. This document focuses on several key legal and acquisition issues that have been raised and addressed in various forums and previously published documents throughout the DOD and Industry. Provided are recommended alternatives for a given set of scenarios whereby reuse may be employed. Use of appropriate contractual vehicles by procurement personnel is key to achieving successful program reuse acquisition strategies that provide financial incentives to contractors. Twenty-five commonly asked reuse questions on legal and acquisition issues have been researched and are grouped according to contractual milestones. The information provided is intended to guide the reader to potential solutions to unique reuqirements. Recommended alternatives are not all-inclusive, as this handbook must respond to the fluid and dynamic changes in the software reuse community and will require future revisions as regulatory and environmental changes occur.

Publisher: CACI

Reference Number: Document #: PD435.1:22-FEB-95

Sponsoring Organization: DISA

Producing Organization: CACI, Inc. - Federal

Publication Date: 2/95

Software Reuse Initiative: Operational Management Plan (Initial Draft for PMO Focal Point Review)

Abstract: The purpose of the DoD SRI Operational Management Plan is to identify activities for the next two years which are necesary to prove the value of adopting a product-line approach and to prepare the infrastructure for its widespread adoption during the following three years. The five strategic thrusts support the overall SRI by providing coordinated planning, tracking, and reporting to ensure the best investment of reuse dollars within DoD and to measure the return on that investment, to put in place the required infrastructure by filling in existing gaps and put a renewed emphasis on technology transfer to effect early success stories. These initial infrastructure investments and successes during the first two years will provide a baseline from which to propagate the transition to product-line orientations and to address the more difficult problems of cross-domain and inter-Service/Agency domain management. During the next two years, there will be tasks to 1) Coordinate planning, 2) Fill in gaps, and 3) Accelerate transfer.

Publisher: DoD

Reference Number: Document #: PD425.3:27-JAN-95

Publication Date: 1/95

Software Reuse Initiative: Vision and Strategy (Working Draft)

Abstract: This document describes software reuse as a powerful concept. The value of this approach has been demonstrated in many other engineering disciplines where the use of standard concepts, processes, and components allows prior accomplishments to be leveraged and speeds innovation for future systems. At this point, many different techniques which support reuse are being tried. This document provides the focus under which these efforts will continue, "lessons learned" will be collected, and experiences shared. Taken together, the ten strategic steps will bring about the cultural change necessary to make software reuse effective for DoD.

Publisher: DoD-SRI

Reference Number: Document #: PD134.3:27-MAR-95

Publication Date: 3/95

Software Reuse Initiative: Vision and Strategy (Working Draft)

Abstract: This document describes software reuse as a powerful concept. The value of this approach has been demonstrated in many other engineering disciplines where the use of standard concepts, processes, and components allows prior accomplishments to be leveraged and speeds innovation for future systems. At this point, many different techniques which support reuse are being tried. This document provides the focus under which these efforts will continue, "lessons learned" will be collected, and experiences shared. Taken together, the ten strategic steps will bring about the cultural change necessary to make software reuse effective for DoD.

Publisher: DoD-SRI

Reference Number: Document #: PD134.2:31-JAN-95

Publication Date: 1/95

Software Reuse Initiative: Strategic Plan (Coordination Draft)

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: DoD

Reference Number: Document #: PD436.2:24-FEB-95

Publication Date: 2/95

Software Reuse Initiative: Strategic Plan (Working Draft)

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: DoD

Reference Number: Document #: PD436.1:13-JAN-95

Publication Date: 1/95

Software Reuse Initiative: Operational Procedures (Working Draft)

Abstract: This report addresses definition and development of processes required for operation of the Software Reuse Initiative (SRI). In October 1994, the principles of the SRI gathered to set the stage for and plan the future of the program. Under the direction of the Program Manager, Service and Agency Focal Points, and other designated key individuals established initial guidelines for the program. During an October 1994 planning session, it was decided 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 & Reporting; the Coordination Process; and Process Definition & Improvement. The program principles next prioritized the processes and defined the time frame within which it would be reasonable to complete definition of the process itself. The specifics of each process are the essence of this document. Since these processes are being defined over a period of time, only the completed ones are included in this edition. As additional processes are defined and developed, this document will be updated and additional process definitions will be incorporated. The processes included in this document are crucial for guiding the future of the SRI program. As the result of cooperative efforts of the Program Management Office (PMO) and Service and Agency Focal Points, the material presented is representative of the excellent working relationships which have resulted thus far.

Publisher: CACI

Reference Number: Document #: PD491.1:21-Apr-95

Sponsoring Organization: DoD

Producing Organization: CACI, Inc. - Federal

Publication Date: 4/95

Software Reuse Initiative: Operational Procedures (Initial Draft)

Abstract: This report addresses definition and development of processes required for operation of the Software Reuse Initiative (SRI). In October 1994, the principles of the SRI gathered to set the stage for and plan the future of the program. Under the direction of the Program Manager, Service and Agency Focal Points, and other designated key individuals established initial guidelines for the program. During an October 1994 planning session, it was decided 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 & Reporting; the Coordination Process; and Process Definition & Improvement. The program principles next prioritized the processes and defined the time frame within which it would be reasonable to complete definition of the process itself. The specifics of each process are the essence of this document. Since these processes are being defined over a period of time, only the completed ones are included in this edition. As additional processes are defined and developed, this document will be updated and additional process definitions will be incorporated. The processes included in this document are crucial for guiding the future of the SRI program. As the result of cooperative efforts of the Program Management Office (PMO) and Service and Agency Focal Points, the material presented is representative of the excellent working relationships which have resulted thus far.

Publisher: CACI

Reference Number: Document #: PD491:10-Feb-95

Sponsoring Organization: DoD

Producing Organization: CACI, Inc. - Federal

Publication Date: 2/95

Software Reuse Initiative: Reuse Security Recommendations Report

Abstract: This document supports the five-phased evolution of the Virtual Reuse Library (VRL) capability for the Department of Defense (DOD) by presenting security recommendations that align with each phase. This report identifies the security measures that need to change as the VRL incrementally develops. The recommendations in this report constitute a checklist of actions that should be considered in each of the five phases.

Publisher: DISA

Reference Number: Document #: PD413.4:26-MAY-95

Sponsoring Organization: DoD

Publication Date: 5/95

Software Reuse Initiative: Reuse Security Recommendations Report (Coordination Draft)

Abstract: This document supports the five-phased evolution of the Virtual Reuse Library (VRL) capability for the Department of Defense (DOD) by presenting security recommendations that align with each phase. This report identifies the security measures that need to change as the VRL incrementally develops. The recommendations in this report constitute a checklist of actions that should be considered in each of the five phases.

Publisher: CACI

Reference Number: Document #: PD413.3:29-MAR-95

Sponsoring Organization: DoD

Producing Organization: CACI, Inc. - Federal

Publication Date: 3/95

Software Reuse Initiative: Reuse Security Recommendations Report (Working Draft)

Abstract: This document supports the five-phased evolution of the Virtual Reuse Library (VRL) capability for the Department of Defense (DOD) by presenting security recommendations that align with each phase. This report identifies the security measures that need to change as the VRL incrementally develops. The recommendations in this report constitute a checklist of actions that should be considered in each of the five phases.

Publisher: CACI

Reference Number: Document #: PD413.2:15-FEB-95

Sponsoring Organization: DoD

Producing Organization: CACI, Inc. - Federal

Publication Date: 2/95

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). 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. 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. A number of issues result from the current organizational structure that provides management direction to the Software Reuse Initiative. The five major issues are: 1- The Reuse Executive Steering Committee (RESC) membership has not been functioning at an appropriate level; 2- The Program Management Office has responsibility for, but not authority over, the SRI; 3- The working groups operate in an ad hoc fashion; 4- The committee structure needs to be simplified (currently too much overlap); and 5- The working groups should address issues identified by SRI stakeholders. This report proposes organizational realignment that is in concert with theMarch 1994 Report to Congress, "DOD Software Reuse Initiative."

Publisher: CACI

Reference Number: Document #: PD487.3:08-MAY-95

Sponsoring Organization: DoD

Producing Organization: CACI, Inc. - Federal

Publication Date: 5/95

Software Reuse Initiative: Organizational Structure and Relationship Report (Working Draft)

Abstract: This report addresses management issues associated with providing orderly and logical direction to the Software Reuse Initiative (SRI). 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. 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. A number of issues result from the current organizational structure that provides management direction to the Software Reuse Initiative. The five major issues are: 1- The Reuse Executive Steering Committee (RESC) membership has not been functioning at an appropriate level; 2- The Program Management Office has responsibility for, but not authority over, the SRI; 3- The working groups operate in an ad hoc fashion; 4- The committee structure needs to be simplified (currently too much overlap); and 5- The working groups should address issues identified by SRI stakeholders. This report proposes organizational realignment that is in concert with theMarch 1994 Report to Congress, "DOD Software Reuse Initiative."

Publisher: CACI

Reference Number: Document #: PD487.1:3-MAR-95

Sponsoring Organization: DoD

Producing Organization: CACI, Inc. - Federal

Publication Date: 3/95

Software Reuse Initiative: Organizational Structure and Relationship Report (Initial Draft)

Abstract: This report addresses management issues associated with providing orderly and logical direction to the Software Reuse Initiative (SRI). 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. 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. A number of issues result from the current organizational structure that provides management direction to the Software Reuse Initiative. The five major issues are: 1- The Reuse Executive Steering Committee (RESC) membership has not been functioning at an appropriate level; 2- The Program Management Office has responsibility for, but not authority over, the SRI; 3- The working groups operate in an ad hoc fashion; 4- The committee structure needs to be simplified (currently too much overlap); and 5- The working groups should address issues identified by SRI stakeholders. This report proposes organizational realignment that is in concert with theMarch 1994 Report to Congress, "DOD Software Reuse Initiative."

Publisher: CACI

Reference Number: Document #: PD487:27-JAN-95

Sponsoring Organization: DoD

Producing Organization: CACI, Inc. - Federal

Publication Date: 1/95

Software Reuse Executive Primer

Abstract: This Primer 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. No prior knowledge of software reuse by the reader is assumed. This Primer is aimed at whetting the appetite of those acquisition managers responsible for implementing software reuse within both the weapons systems and information systems communities of the DOD. Managers should be interested in reuse because they are looking for ways to reduce cost, accelerate schedules, and improve software quality. Program Managers, Program Executive Officers, and Directing Program Managers fall into this category, as does anyone else who may benefit by implementing a reuse program.

Author: SRI PMO

Publisher: DOD SRI

Reference Number: Document #: PD427.6:17-MAY-95

Publication Date: 5/95

Software Reuse Executive Primer (Coordination Draft)

Abstract: The "Software Reuse Executive Primer" provides an informal overview of software reuse. Technical and organizational issues are discussed along with successful reuse management techniques. The Primer presents the issues and benefits involved in transitioning to reuse-based acquisition, development, and maintenance processes, and discusses strategies that can best address these issues. Specifically, the Primer focuses on developing the seed of understanding for the executive who desires to: 1) transition technology, 2) minimize risks, and 3) make informed decisions. Strategic guidance is offered for the development of reuse programs and the acquisition of systems, as well as the development and reuse of software system ife-cycle products. No specific knowledge of reuse is assumed.

Author: SRI PMO

Publisher: CACI

Reference Number: Document #: PD427.3:22-MAR-95

Sponsoring Organization: SRI

Producing Organization: CACI, Inc. - Federal

Publication Date: 3/95

Reuse Executive Primer (Working Draft)

Abstract: The Primer represents the issues involved in transitioning to reuse-based acquisition, development, and maintenance processes, and discusses strategies that can best address these issues. Specifically, the Primer focuses on developing the seed of understanding for the executive who desires to: 1) transition the technology, 2) minimize the risks, and 3) make informed decisions. The Reuse Executive Primer discusses both technical and organizational issues and successful management techniques. Strategic guidance is offered for the development of reuse programs, the acquisition of systems, as well as the development and reuse of software system life-cycle products. No specific knowledge of reuse is assumed. The Reuse Executive Primer discusses both technical and organizational issues, successful management techniques, and refers to published works for greater detail (see Bibliography).

Author: SRI PMO

Publisher: CACI

Reference Number: Document #: PD427.2:08-FEB-95

Sponsoring Organization: SRI

Producing Organization: CACI, Inc. - Federal

Publication Date: 2/95

PST/Sun Test Plan

Abstract: This "PST/Sun Test Plan" describes the testing necessary to determine if the Products, Services, Tasks (PST) Database Product Production Package (PPP) operates correctly after conversion to UNIX-cpompatible code and installation on a Sun/UNIX workstation. When testing of the converted code is completed successfully, the PST PPP will be ready for installation on the ReuseIC BBS.

Publisher: CACI

Reference Number: Document #: PD509:16-MAR-95

Sponsoring Organization: DISA

Producing Organization: CACI, Inc. - Federal

Publication Date: 3/95

PST Installation Plan

Abstract: The Products, Services, Tasks (PST) Database Application, PST Database Tutorial, and other support software will be resident on a Sun Microsystems computer that will host the Reuse Information Clearinghouse (ReuseIC) Bulletin Board System (BBS). This document will describe the existing PST Product Production Package (PST PPP) and existing installation procedures for background purposes. Then, the plan will discuss the installation procedures for each of the three options presented in the PST Transition Plan. Once the PST PPP has been placed on the ReuseIC system, it will be available for interested members of the software reuse community to download and use on their computers.

Publisher: CACI

Reference Number: Document #: PD493:14-FEB-95

Sponsoring Organization: DISA

Producing Organization: CACI, Inc. - Federal

Publication Date: 2/95

PST Transition Plan

Abstract: The Products, Services, Tasks (PST) Database Application, PST Database Tutorial and other support software will be located on a Sun Microsystems computer, which will host the Reuse Information Clearinghouse (ReuseIC) Bulletin Board System (BBS). This document describes the existing PST Product Production Package (PST PPP) and provides a transition plan to relocate the PST PPP on the ReuseIC system. Once the PST PPP has been placed on the ReuseIC ystem, it will be available for interested members of the software reuse community to download and use on their computers.

Publisher: CACI

Reference Number: Document #: PD489:30-JAN-95

Sponsoring Organization: DISA

Producing Organization: CACI, Inc. - Federal

Publication Date: 1/95

PST User's Manual

Abstract: This document is the User's Manual for the Department of Defense (DOD) Software Reuse Products, Services, Tasks (PST) Database application. This manual provides the DOD PST System Administrator and other users who are permitted to use the System Administrator's user ID/password with a detailed guide for using this sytem. The manual contains sections describing system requirements, execution procedures, and the various system keyboard/input conventions.

Publisher: CACI

Reference Number: Document #: PD431.1:16-JAN-95

Sponsoring Organization: DISA

Producing Organization: CACI, Inc. - Federal

Publication Date: 1/95

Military Standard [MIL-STD-1838A]: Common Ada Programming Support Environment (APSE) Interface Set (CAIS), Revision A

Abstract: This document provides specifications for a set of Ada packages, with their intended semantics, which together form a set of common interfaces for Ada Programming Support Environments (APSEs). This set of interfaces is known as the Common APSE Interface Set (CAIS) and is designed to promote the source-level portability of Ada programs, particularly Ada software development tools. The goal of the CAIS is to promote interoperability and transportability of Ada software across DoD APSEs. The contents of this standard are divided into chapters, each with several sections: 1- Scope, 2- Referenced Documents, 3- Definitions, 4- General Requirements, 5- CAIS Node Management Detailed Requirements, 6- CAIS Process Management Detailed Requirements, 7- Input and Output Detailed Requirements, 8- Data Transfer Protocols Detailed Requirements, CAIS List Management Detailed Requirements, 10- CAIS Standard Detailed Requirements, 11- CAIS Calendar Detailed Requirements, 12- CAIS Pragmatics Detailed Requirements, 13- CAIS Status Management Detailed Requirements, and 14- Guidance Information.

Author: KIT/KITIA

Publisher: DoD

Reference Number: MIL-STD-1838A

Publication Date: 4/89

Ada in Mission Critical System Acquisition: A Guidebook

Abstract: This discusses several issues that influence the successful acquisition of major mission-critical systems. These issues range from the role of software in the system acquisition process and the state of software engineering practice in industry, to Ada compiler validation, Ada run-time environment, Ada programming environment, Ada reuse, and Ada productivity. A project manager must deal with each of these issues during the course of his procurement and must devise plans to identify them and eliminate them in order to make his program a successful one.This guidebook is arranged into six chapters: 1- Introduction, 2- System Acquisition Management, 3- Mission Critical Software Acquisition, 4- Ada-Based Technology, 5- Ada Experience, and 6- Recommendations.

Author: Mohanty, Siba N.

Publisher: Mitre

Reference Number: Mitre: MTR-84W00189

Sponsoring Organization: Office of the Deputy Under Seceretary of Defense (R&AT); AJPO

Producing Organization: Mitre

Publication Date: 9/84

Domain Specific Environment Repository Composite Paradigm Report, CDRL 03068. Publication GR-7670-1195(NP)

Author: Danner, B., and A. Marmor-Squires

Sponsoring Organization: Unisys Corporation, Reston, VA.

Publication Date: 5/91

Risk-Reduction Reasoning-Based Development Paradigm Tailored to Navy C2 Systems, GR-7670-1219(NP)

Author: Danner B., and A. Marmor-Squires

Sponsoring Organization: Unysis Corporation, Reston, VA

Publication Date: 7/95

Standards and Guidelines for the Repository for Software Technology for Adaptable Reliable Systems, CDRL Sequence No. 00320

Author: Davis, M. J.

Sponsoring Organization: The Boeing Company, Seattle, WA

Publication Date: 3/89

Consolidated Reuse Lessons Learned, CDRL 04049RA

Author: Davis, M. J.

Sponsoring Organization: The Boeing Company, Seattle, WA

Publication Date: 1/92

GCCS Common Operating Environment Baseline (Draft)

Sponsoring Organization: Defense Information Systems Agency

Publication Date: 11/94

Technical Architecture Framework for Information Management, Vol. 1, Version 2.0 (final draft), Falls Church, VA

Sponsoring Organization: Defense Information Systems Agency, Center for Architecture

Publication Date: 11/93

Defense Software Repository System (DSRS): Database Specification for DSRS Version 5, Softech, Falls Church, VA

Sponsoring Organization: Defense Information Systems Agency, Center for Information Management (DISA/CIM)

Publication Date: 6/93

Software Reuse Program Software Reuse Metric Plan, Version 4.1, Falls Church, VA

Sponsoring Organization: Defense Information Systems Agency, Joint Interoperability Engineering Organization, Center for Info

Publication Date: 8/93

Software Reuse Program Reuse Metrics FY93 Fourth Quarter Report, Falls Church, VA

Sponsoring Organization: Defense Information Systems Agency, Joint Interoperability Engineering Organization, Center for Info

Publication Date: 10/93

Software Reuse Program Software Reuse Metrics FY93 Q3 Quarterly Report, Falls Church, VA

Sponsoring Organization: Defense Information Systems Agency, Joint Interoperability Engineering Organization, Center for Info

Publication Date: 7/93

Procurement Domain Analysis and Design Pilot Project Report

Sponsoring Organization: Defense Information Systems Agency, Joint Interoperability Engineering Organization, Center for Info

Publication Date: 11/94

Quality, Productivity, and Competitive Position

Author: Deming, W. E.

Sponsoring Organization: MIT Center for Advanced Engineering Study, Cambridge MA

Publication Date: 1/82

Software Product Description: DECmessageQ for UNIX[R], Version 3.0, Maynard, MA

Sponsoring Organization: Digital Equipment Corporation

Publication Date: 1/94

Framework for Certification of Reusable Software Components (Draft), Department of Defense, Washington DC

Sponsoring Organization: DoD Center for Software Reuse Operations

Publication Date: 9/92

DoD Domain Definition Report, 1222-04-210/28

Sponsoring Organization: DoD Center for Software Reuse Operations

Publication Date: 7/92

Draft: Software Technology Strategy

Sponsoring Organization: DoD Software of Defense Research and Engineering (DDR&E)

Publication Date: 12/91

Virtual Library Operational Concept Document

Sponsoring Organization: DoD Software Reuse Initiative

Publication Date: 7/93

Software Reengineering Assessment Handbook, Version 1 (Draft), MIL-HDBK-SRAH, Washington DC

Sponsoring Organization: DoD

Publication Date: 2/94

Domain-Oriented Design Environments

Author: Fischer, G.

Publisher: Proceedings of The Seventh Knowledge-Based Software Engineering Conference, McLean , VA.

Publication Date: 9/92

An Empirical Framework for Software Reuse Research

Author: Frakes, W.B.

Publisher: Proc. Third Annual Workshop on Methods and Tools for Reuse, Syracuse Uni., Syracuse, New York

Sponsoring Organization: CASE Center Tech. Report 9014

Publication Date: 1/90

Testing a Technology for Reuse

Author: Freemon, B.W., and R.G. Crispen

Publisher: 14th International/Interservice Training Sim. Engineering (I/ITSEC) Proceedings, Huntsville, AL

Sponsoring Organization: Boeing Defense and Space Group

Publication Date: 1/92

The Smalltalk-76 Programming System Design and Implementation

Author: Ingalls, D.

Publisher: Proceedings of the Fifth Annual ACM Symposium on Principles of Programming Languages, New York, NY

Sponsoring Organization: Association of Computing Machinery

Publication Date: 1/77

"Woodenman" Set of Criteria and Needed Characteristics for a Common DOD High Order Programming Language (Working Paper)

Abstract: The purpose of the common HOL effort is to assure maximum useful DOD software commonality through the adoption of a common high-order programming language. The common HOL should support software development and maintenance for all DOD computer applications. These applications specifically include communications, weapons systems, command and control, test equipment, scientific applications, simulation, and data processing. The language is intended to eventually supplant all programming languages used in DOD except COBOL and Fortran, which already have wide user communities and some standardization within DOD.

Author: Fisher, David A.

Publisher: IDA

Publication Date: 8/75

Department of Defense Requirements for High Order Computer Programming Languages -- "Tinman"

Abstract: This report is the third in a series that defines the DOD's requirements for a high order computer programming language. On the basis of all inputs and the official responses from each of the Military Departments, a more complete set of requirements than "Strawman" or "Woodenman" has evolved and is presented here as "Tinman." This document represents a set of requirements for high order computer programming languages consistent with the input from hte Military Services.

Author: HOL Working Group

Publisher: HOL Working Group

Publication Date: 4/76

Department of Defense Requirements for High Order Computer Programming Languages -- "Tinman"

Abstract: This report is the third in a series that defines the DOD's requirements for a high order computer programming language. On the basis of all inputs and the official responses from each of the Military Departments, a more complete set of requirements than "Strawman" or "Woodenman" has evolved and is presented here as "Tinman." This document represents a set of requirements for high order computer programming languages consistent with the input from hte Military Services.

Author: HOL Working Group

Publisher: HOL Working Group

Publication Date: 6/76

Department of Defense Requirements for High Order Computer Programming Languages -- "Ironman"

Abstract: The technical requirements for a common DoD high order programming language given here are a synthesis of the requirements submitted by the Military Departments. They specify a set of language characteristics that are appropriate for embedded computer applications (i.e., command and control, communications, avionics, shipboard, test equipment, software development and maintenance, and support applications). The changes that produced this revision reflect the many comments on previous versions received from the Services, military contractors, the research community, and other organizations during 1976. The revision does not alter the basic intent or substance of the December 1975 ("Tinman") version of the requirements. It does incorporate changes to improve clarity, to correct errors, and to ensure feasibility.

Author: HOL Working Group

Publisher: HOL Working Group

Publication Date: 1/77

LTPL -- A Review of "Ironman"

Abstract: This document provides a transcript, chairman's report, and participant's notes on a review of "Ironman." The general impression was that Ironman was a better balanced and more practical document than Tinman.

Author: LTPL

Publication Date: 5/77

Department of Defense Requirements for High Order Computer Programming Languages -- Revised "Ironman"

Abstract: The technical requirements for a common DoD high order programming language given here are a synthesis of the requirements submitted by the Military Departments. They specify a set of language characteristics that are appropriate for embedded computer applications (i.e., command and control, communications, avionics, shipboard, test equipment, software development and maintenance, and support applications). The revision incorporates three kinds of changes. Most changes are clarifications (including the removal of redundancies) that do not alter the meaning or intent of the 14 January 1977 version. A few changes correct errors and inconsistencies found in the previous version (primarily Section 9). The remaining changes deal with special cases that arise from the interactions between facilities of the language.

Author: HOL Working Group

Publisher: HOL Working Group

Publication Date: 7/77

Department of Defense Requirements for High Order Computer Programming Languages -- Newly Revised "Ironman"

Abstract: The technical requirements for a common DoD high order programming language given here are a synthesis of the requirements submitted by the Military Departments. They specify a set of language characteristics that are appropriate for embedded computer applications (i.e., command and control, communications, avionics, shipboard, test equipment, software development and maintenance, and support applications). The revision incorporates three kinds of changes. Most changes are clarifications (including the removal of redundancies) that do not alter the meaning or intent of the 14 January 1977 version. A few changes correct errors and inconsistencies found in the previous version (primarily Section 9). The remaining changes deal with special cases that arise from the interactions between facilities of the language.

Author: Team 405-02, HOL Working Group

Publisher: Team 405-02, HOL Working Group

Publication Date: 3/78

Department of Defense Requirements for High Order Computer Programming Languages -- Preliminary "Steelman"

Abstract: The technical requirements for a common DoD high order programming language given here are a synthesis of the requirements submitted by the Military Departments. They specify a set of language characteristics that are appropriate for embedded computer applications (i.e., command and control, communications, avionics, shipboard, test equipment, software development and maintenance, and support applications). A primary goal of this revision has been to reduce the complexity of the resulting language.

Author: HOL Working Group

Publisher: HOL Working Group

Publication Date: 5/78

Department of Defense Requirements for High Order Computer Programming Languages -- "Steelman"

Abstract: The technical requirements for a common DoD high order programming language given here are a synthesis of the requirements submitted by the Military Departments. They specify a set of language characteristics that are appropriate for embedded computer applications (i.e., command and control, communications, avionics, shipboard, test equipment, software development and maintenance, and support applications). A primary goal of this revision has been to reduce the complexity of the resulting language.

Author: HOL Working Group

Publisher: HOL Working Group

Publication Date: 6/78

Department of Defense Requirements for the Programming Environment for the Common High Order Language: Pebbleman revised

Abstract: This document describes the requirements for the environment necessary to the success of the Common High Order Language. The requirements discussed are recognized as necessary for the production of reliable software.

Author: Department of Defense High Order Commonality Language Program

Publisher: Department of Defense High Order Commonality Language Program

Publication Date: 12/78

Department of Defense Requirements for the Programming Environment for the Common High Order Language: Pebbleman revised

Abstract: This document describes the requirements for the environment necessary to the success of the Common High Order Language. The requirements discussed are recognized as necessary for the production of reliable software.

Author: Department of Defense High Order Commonality Language Program

Publisher: Department of Defense High Order Commonality Language Program

Publication Date: 1/79

Initial Thoughts on the Pebbleman Process

Abstract: The purpose of the authors is to stimulate thinking and participation in planning and developing an effective environment for Ada, the DoD common high order programming language. The document gives some thoughts concerning the process for determining the characteristics that the Common Language environment should have. The term "requirements" will be used to refer to the system of characteristics, goals, and constraints that will result from such a process.

Author: Fisher, David A., and Thomas A. Standish

Publisher: IDA

Reference Number: IDA #: Paper P-1392

Sponsoring Organization: DARPA

Producing Organization: IDA

Publication Date: 1/79

Proceedings USC Center for Software Engineering Executive Workshop on Information Architectures and Software Product Line Management

Abstract: Proceedings include highlights of each panelist's remarks and of the subsequent discussions, plus each panelist's charts or text. An appendix provides the Workshop Agenda, Workshop Description and List of Participants.

Author: Westland, Chris and Barry Boehm (editors)

Publisher: USC - University of Southern California, Center for Software Engineering

Publication Date: 2/94

Knowledge Summary: USC Center for Software Engineering Focused Workshop on Software Architecture

Abstract: Summarizes highlights of the workshop from the standpoint of new technical insights, research priorities, and actions for teh USC-CSE software archiecture research program. These are presented in the categories of software architecture foundations, the architecting process, domain-specific software architecture (DSSA) and architecture representation.

Author: Clark, Bradford; et al.

Publisher: USC - University of Southern California, Center for Software Engineering

Publication Date: 6/94

A System Dynamics Based Study of Software Reuse Economics

Abstract: This thesis studies the economics of software reuse using a system dynamics computer model, the Dynamica Reuse Model, which stimulates the activities of a software development organization engaged in organization-wide, systematic software reuse.

Author: Gallup, Pamela Jean

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

Producing Organization: NPS -Naval Postgraduate School

Publication Date: 6/94

ADIS Preliminary Status Review

Abstract: Briefing viewgraphs

Publisher: NAWC - Naval Air Warfare Center, Aircraft Division, Patuxent River, MD

Sponsoring Organization: AJPO - Ada Joint Program Office

Producing Organization: NAWC - Naval Air Warfare Center

Publication Date: 2/94

JTCI TAG Meeting to Formulate U.S. Position on Fast Track of PCTE

Abstract: Ad Hoc meeting held by JTCI TAG Administrator to formulate the U.S. national position on the fast tracking of the Portable Common Tool Environment (PCTE) Draft International Standard (DIS), Parts 1-3 (References (a), (b), and (c) ).

Publisher: SPAWAR - Space and Naval Warfare Systems Command, Washington, DC 20363

Reference Number: 3915 Ser 331/002

Sponsoring Organization: Dept. of the Navy

Producing Organization: SPAWAR - Space and Naval Warfare Systems Command

Publication Date: 1/94

(Draft) Military Standard [DOD-STD-2167A]: Defense System Software Development (Superseding DOD-STD-2167, 4 June 1985)

Abstract: This standard establishes uniform requirements for software development that are applicable throughout the system life-cycle. The requirements of this standard provide the basis for Government insight into a contractor's software development, testing, and evaluation efforts. This standard is to be used in conjunction with DOD-STD-2168, Defense System Software Quality Program. This standard is not intended to specify or discourage the use of any particular software development method. The contractor is responsible for selecting software development methods that best support the achievement of contract requirements. This standard, together with the other DOD and military documents referenced in Section 2, provides the means for establishing, evaluating, and maintaining quality software and associated documentation. Guidance on the implementation of this standard and its relationship to these other documents is provided in DOD-HDBK-287. Data Item Descriptions (DIDs) applicable to this standard are listed in Section 6. These DIDs describe a set of documents for recording the information required by this standard. Production of deliverable data using automated techniques is encouraged.

Publisher: DoD

Reference Number: (Draft) DoD-STD-2167A (Superseding DOD-STD-2167, 4 June 1985)

Publication Date: 10/87

Command, Control, Communications, and Intelligence Node: A Durra Application Example

Abstract: This report describes an experiment in implementing a C3I node using reusable components. It illusrates the methodology for building complex, distributed systems supported by Durra.

Author: Barbacci, Mario R.; et al.

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

Reference Number: CMU/SEI-89-TR-9 ESD-TR-89-17

Sponsoring Organization: SEI joint Program Office

Producing Organization: SEI - Software Engineering Institute

Publication Date: 2/89

DoD Weapon Systems Software Management Study [Appendix C, Airborne Systems]

Abstract: This appendix to the DoD Weapon Systems Software Management Study conducted by the APL contains information on Airborne Systems presented in more detail than is given in the main report. The specific systems discussed here are the E-2C Tactical Data System, the P-3C Airborne Patrol System, the S-3A Airborne Weapon System, and the F-14 Avionics and Weapon Delivery System. Each section is divided into the following parts: General System Description; Computer System Architecture; Computer Program Architecture; Software Definition, Design, and Implementation; Software Validation and Integration; Software Acquisition Management Organization and Methods; Operational Software Maintenance; and Highlights.

Author: Park, J.M.

Publisher: The Johns Hopkins University Applied Physics Laboratory

Reference Number: JHU #: APL/JHU SR 75-3B

Sponsoring Organization: OASD

Producing Organization: The Johns Hopkins University Applied Physics Laboratory

Publication Date: 6/75

DoD Weapon Systems Software Management Study [Appendix D, Undersea and Landbased Systems]

Abstract: This appendix to the DoD Weapon Systems Software Management Study conducted by the APL contains information on Undersea and Landbased Systems presented in more detail than is given in the main report. The specific systems discussed are the Trident Command and Control System, the Pershing Weapon System, and the SAM-D Weapon System. Each section is divided into the following parts: General System Description; Computer System Architecture; Computer Program Architecture; Software Definition, Design, and Implementation; Software Validation and Integration; Software Acquisition Management Organization and Methods; Operational Software Maintenance; and Highlights.

Author: Park, J.M.

Publisher: The Johns Hopkins University Applied Physics Laboratory

Reference Number: JHU #: APL/JHU SR 75-3B

Sponsoring Organization: OASD

Producing Organization: The Johns Hopkins University Applied Physics Laboratory

Publication Date: 6/75

DoD Weapon Systems Software Acquisition and Management Study [Supporting Material]

Abstract: In December, 1974, DoD initiated a two-phase software acquisition study program to identify methods for controlling increasing costs, improving the quality, and minimizing the adverse impact of software in weapon systems. The MITRE Corporation and the Applied Physics Laboratory of Johns Hopkins University were requested to conduct separate, but coordinated, four-month studies in support of the first phase of this study program. Volume I contains the MITRE study findings and recommendations. This volume, Volume II, provides supporting information for the study findings and recommendations.

Author: Asch, A., et al.

Publisher: MITRE

Reference Number: MITRE #: MTR-6908

Sponsoring Organization: DoD

Producing Organization: MITRE

Publication Date: 5/75

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

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

Publisher: NPS - Naval Postgraduate School, Department of Administrative Services, Information Technology Mnagement Curriculum, Monterey, CA

Publication Date: 10/92

Evaluation and Validation (E&V) Team Public Report, Volume IV

Abstract: The Ada community, including government, industry, and academic personnel, needs the capability to assess Ada Programming Support Environments (APSEs) and their components, and to determine their conformance to applicable standards. The technology required to fully satisfy this need is extensive and largely unavailable. The purpose of this task is to provide a focal point for addressing the need by: identifying and defining specific technology requirements; developing selected elements of the required technology; encouraging others to develop some elements; and, collecting information describing elements which already exist.

Author: Szymanski, Raymond

Publisher: US Air Force, Wright Aeronautical Laboratories, Wright-Patterson AFB, OH 45433-6543

Reference Number: AFWAL-TR-85-1016, Vol IV

Sponsoring Organization: AJPO

Producing Organization: US Air Force, Wright Aeronautical Laboratories, Wright-Patterson

Publication Date: 1/89

Available Ada Bindings

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

Sponsoring Organization: AJPO - Ada Joint Program Office

Producing Organization: AdaIC - Ada Information Clearinghouse

Publication Date: 11/92

Ada 9X Adoption Handbook: A Guide to Investigating Ada 9X Adoption

Publisher: AJPO - Ada Joint Program Office

Producing Organization: AJPO

Publication Date: 9/94

A Survey of Computer Programming Languages Currently used in the Department of Defense

Author: Hook, Audrey A., et. al.

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

Reference Number: IDA Paper P-3054

Sponsoring Organization: DISA

Producing Organization: IDA - Institute for Defense Analyses

Publication Date: 1/95

Ada - The Business Case

Publisher: Reifer Consultants, Inc., 25550 Hawthorne Boulevard, Torrance, CA 90505

Reference Number: RCI-TN-548A

Sponsoring Organization: IDA - Institute for Defense Analyses

Producing Organization: RCI - Reifer Consultants, Inc.

Publication Date: 8/93

Computer System Operator's Manual for the Ada Information Clearinghouse Internet Server System

Publisher: IIRTI - IIT Research Institute, 4409 Forbes Boulevard, Lanham, MD 20706

Sponsoring Organization: AJPO - Ada Joint Program Office

Producing Organization: IITRI - IIT Research Institute

Publication Date: 12/94

Marketing Communications Study Precampaign Survey

Reference Number: RAC 6200

Sponsoring Organization: Telos Corporation

Publication Date: 5/94

Final Report of the Tools and Integration Review Board under the Special Working Group on Ada Programming Support Environments

Publisher: NATO

Reference Number: NATO-SWG-APSE:TIRB:RPT:001

Sponsoring Organization: NATO

Producing Organization: NATO

Publication Date: 2/93

EASY_SIM: A Visual Simulation System Software Architecture with an Ada 9X Application Framework - Thesis

Author: Kayloe, Jordan Russell

Publisher: AFIT - U.S. Air Force Institute of Technology, Wright-Patterson AFB, OH

Reference Number: AFIT/GCS/ENG/94D-11

Producing Organization: AFIT - U.S. Air Force Institute of Technology

Publication Date: 12/94

Management Overview of Ada Technology

Publisher: EVB Software Engineering, Inc

Publication Date: 1/88

Ada 9X Project Report, Introducing Ada 9X

Author: Barnes, John

Publisher: Intermetrics, Inc.

Sponsoring Organization: Ada Joint Project Office

Producing Organization: Ada 9X Project Office

Publication Date: 2/93

Ada 9X Project Report, Ada Support for Software Reuse

Author: Cohen, Sholom

Publisher: Office of the Under Secretary of Defense for Acquisition

Reference Number: SEI-90-SR-16

Sponsoring Organization: Ada 9x Project Office

Producing Organization: Software Engineering Institute, Carnegie Mellon University

Publication Date: 10/90

Draft Ada 9X Project Report, Transition Plan

Author: Anderson, Christine M.; et al.

Publisher: Office of the Undersecretary of Defense for Acquisition

Sponsoring Organization: Ada 9X Project Office

Publication Date: 9/91

Draft Ada 9X Project Report, Transition Plan

Author: Anderson, Christine M.

Publisher: Office of the Undersecretary of Defense for Acquisition

Sponsoring Organization: Ada 9X Project Office

Publication Date: 12/91

Ada 9X Draft Mapping Rationale Document

Author: Carlson, W.; et al.

Publisher: Intermetrics, Inc

Sponsoring Organization: Ada 9X Project Office

Producing Organization: Ada 9X Mapping/Revision Team

Publication Date: 8/91

Ada 9X Draft Mapping Rationale Document

Author: Carlson, W.; et al.

Publisher: Intermetrics, Inc

Reference Number: IR-MA-1223

Sponsoring Organization: Ada 9X Project Office

Producing Organization: Ada 9X Mapping/Revision Team

Publication Date: 2/91

Ada 9X Draft Mapping Document

Author: Carlson, W.; et al.

Publisher: Intermetrics, Inc

Reference Number: IR-MA-1224-1

Sponsoring Organization: Ada 9X Project Office

Producing Organization: Ada 9X Mapping/Revision Team

Publication Date: 2/91

Ada 9X Mapping, Volume II, Mapping Specification

Author: Carlson, W.; et al.

Publisher: Intermetrics, Inc

Reference Number: IR-MA-1250-1

Sponsoring Organization: Ada 9X Project Office

Producing Organization: Ada 9X Mapping/Revision Team

Publication Date: 11/91

Ada 9X Snapshot of Mapping Specification Prior to Revision

Author: Carlson, W.; et al.

Publisher: Intermetrics, Inc

Sponsoring Organization: Ada 9X Project Office

Producing Organization: Ada 9X mapping/Revision Team

Publication Date: 4/92

Ada 9X Mapping Overview

Abstract: Briefing.

Publisher: Intermetrics, Inc

Sponsoring Organization: Ada 9X Project Office

Producing Organization: Ada 9X Mapping/Revision Team

Publication Date: 3/91

Recommended Approach to Software Development, Revision 3

Author: Landis, Linda; et al.

Publisher: NASA - Goddard Space Flight Center, Greenbelt, MD 20771

Reference Number: SEL-81-305

Sponsoring Organization: NASA/Univ. of Maryland/ Computer Sciences Corporation

Producing Organization: SEL - Software Engineering Laboratory

Publication Date: 6/92

The Evaluation of the Special Working Group, Ada Programming Support Environments, Volume 1, Overview & Conclusions

Publisher: NATO

Reference Number: NATO-SWG-APSE:UK:RPT:001

Sponsoring Organization: NATO

Producing Organization: NATO

Publication Date: 10/93

The Evaluation of the Special Working Group, Ada Programming Support Environments, Volume 2, VAX Host Results

Publisher: NATO

Reference Number: NATO-SWG-APSE:UK:VAXH:001

Sponsoring Organization: NATO

Producing Organization: NATO

Publication Date: 10/93

The Evaluation of the Special Working Group, Ada Programming Support Environments, Volume 3, SUN Host Results

Publisher: NATO

Reference Number: NATO-SWG-APSE:UK:SUNH:001

Sponsoring Organization: NATO

Producing Organization: NATO

Publication Date: 10/93

The Evaluation of the Special Working Group, Ada Programming Support Environments, Volume 4, VAX/MC68020 Cross Target Results

Publisher: NATO

Reference Number: NATO-SWG-APSE:UK:VAXT:001

Sponsoring Organization: NATO

Producing Organization: NATO

Publication Date: 10/93

The Evaluation of the Special Working Group, Ada Programming Support Environments, Volume 5, SUN/MC68020 Cross Target Results

Publisher: NATO

Reference Number: NATO-SWG-APSE:UK:SUNT:001

Sponsoring Organization: NATO

Producing Organization: NATO

Publication Date: 10/93

ASEET Advanced Ada Workshop

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

Sponsoring Organization: DoD - Department of Defense

Producing Organization: SEI - Software Engineering Institute

Publication Date: 1/88

DACS Bibliographic Search

Publisher: IITRI/DACS - Data & Analysis Center for Software (DACS), Griffiss AFB, NY 13441

Producing Organization: IITRI/DACS - Data & Analysis Center for Software

Publication Date: 3/89

Military Standard MIL-STD-498: Software Development and Documentation

Publisher: DoD

Reference Number: MIL-STD-498

Publication Date: 12/94

Catalog of Resources for Education in Ada and Software Engineering (CREASE) - Version 7.0

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

Sponsoring Organization: AJPO - Ada Joint Program Office

Producing Organization: IITRI - IIT Research Institute

Publication Date: 1/95

Ada-based Replicated Program Distributed Computing Environment

Author: Masters, Michael W.

Publisher: NSWC - Naval Surface Warfare Center, Dahlgren, VA 22448

Reference Number: NAVSWC TR 91-597

Producing Organization: NSWC - Naval Surface Warfare Center

Publication Date: 3/92

Ada Compiler Validation Procedures

Abstract: This version of the Ada Compiler Validation Procedures has been updated to reflect a transition period when compiler vendors will transition their copmilers to the features provided by the revised Ada Language standard, Ada 95. The transition period is from December 1994, when Ada 95 became an approved standard, until March 1997, when the Ada 95 Compiler Validation Capability (ACVC) version 2.1 is required for use in the validation process. During the transition period, two ACVC versions will be "current" versions used for validation testing -- ACVC 1.11 for Ada 83 and ACVC 2.0 for Ada 95. Compiler vendors may choose one or the other and get a certificate for either one. ACVC 1.11 will expire March 1997 and certificates for validations using ACVC 1.11 will expire March 1998. The body of this document provides the full definition of terms and specific rules for the validation of Ada compilers.

Author: IDA

Publisher: IDA

Sponsoring Organization: AJPO

Producing Organization: IDA

Publication Date: 1/95

Reengineering Technology Report, Volume I

Author: Olsem, Michael R., and Chris Sittenauer

Publisher: STSC - U.S. Air Force Software Technology Support Center, Hill AFB, UT 84056

Producing Organization: STSC - U.S. Air Force Software Technology Support Center

Publication Date: 8/93

Project Management Technology Report

Publisher: STSC - U.S. Air Force Software Technology Support Center, Hill AFB, UT 84056

Producing Organization: STSC - U.S. Air Force Software Technology Support Center

Publication Date: 12/94

Process Technologies Method and Tool Report (Volume I)

Author: Allgood, Bruce, et. al.

Publisher: STSC - U.S. Air Force Software Technology Support Center, Hill AFB, UT 84056

Producing Organization: STSC - U.S. Air Force Software Technology Support Center

Publication Date: 3/94

Software Configuration Management Technology Report

Publisher: STSC - U.S. Air Force Software Technology Support Center, Hill AFB, UT 84056

Producing Organization: STSC - U.S. Air Force Software Technology Support Center

Publication Date: 9/94

Documentation Technology Report

Author: Atkinson, Shane,and Reed Sorensen

Publisher: STSC - U.S. Air Force Software Technology Support Center, Hill AFB, UT 84056

Producing Organization: STSC - U.S. Air Force Software Technology Support Center

Publication Date: 4/94

Requirements Analysis and Design Technology Report

Author: Ganska, Ralph, et. al.

Publisher: STSC - U.S. Air Force Software Technology Support Center, Hill AFB, UT 84056

Producing Organization: STSC - U.S. Air Force Software Technology Support Center

Publication Date: 3/94

Software Test Technologies Report

Author: Daich, Gregory T., et. al.

Publisher: STSC - U.S. Air Force Software Technology Support Center, Hill AFB, UT 84056

Producing Organization: STSC - U.S. Air Force Software Technology Support Center

Publication Date: 8/94

Software Engineering Environment Technology Report

Author: Hanrahan, Robert, et. al.

Publisher: STSC - U.S. Air Force Software Technology Support Center, Hill AFB, UT 84056

Producing Organization: STSC - U.S. Air Force Software Technology Support Center

Publication Date: 4/94

Software Estimation Technology Report

Author: Barrow, Dean, et. al.

Publisher: STSC - U.S. Air Force Software Technology Support Center, Hill AFB, UT 84056

Producing Organization: STSC - U.S. Air Force Software Technology Support Center

Publication Date: 3/93

Army STARS Demonstration Project Experience Report: Informal Technical Data

Author: Lettes, Judith A., & John Willison

Publisher: Unisys Corporation, 12010 Sunrise Valley Drive, Reston, VA 22091

Reference Number: STARS-VC-A011R/002/02

Sponsoring Organization: ESC/ENS, USAF

Producing Organization: Unisys Corporation

Publication Date: 2/95

Proceedings of the Software Re-Use Workshop

Abstract: These proceedings are the outcome of a workshop on software reuse organized in November 1989. The contents are divided into fourteen chapters: 1- Introduction to Reuse, 2- Workshop Overview and Conclusions, 3- Reuse Bibliography, 4- REDO at Oxford, 5- Sharing for Quality, 6- The MERLIN Approach to the Reuse of Software, 7- Reusability and Software Prototyping, 8- A Design Method to MAke Reuse Happen, 9- PRACTITIONER: Pragmatic Support for the Reuse of Concepts in Existing Software, 10- The Abuse of Reuse: Why Cognitive Aspects of Sofwtare Reusability are Important, 11- Design-Aspects Supporting Software Reuse, 12- Structures for Supporting Sofwtare Reuse, 13- Perspectives of Software Reusability, and 14- Using Formal Transformations to Construct a Component Repository.

Author: Dusink, Liesbeth and Patrick Hall

Publisher: Springer-Verlag

Reference Number: ISBN: 0-387-19652-8; Library of Congress: 91-10595

Publication Date: 1/91

Proceedings of the 1994 Monterey Workshop: Increasing the Practical Impact of Formal Methods for Computer-Aided Software Development: Software Evolution

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

Sponsoring Organization: ONR/ARPA/AFOSR/ARO/NSF

Producing Organization: NPS - Naval Postgraduate School

Publication Date: 9/94

Proceedings of the ARO/AFOSR/ONR Workshop: Increasing the Practical Impact of Formal Methods for Computer-Aided Software Development: Software Slicing, Merging and Integration

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

Sponsoring Organization: ARO/AFOSR/ONR

Producing Organization: NPS - Naval Postgraduate School

Publication Date: 10/93

Automated Interface for Retrieving Reusable Software Components (Thesis)

Author: Dolgoff, Scott Joel

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

Producing Organization: NPS - Naval Postgraduate School

Publication Date: 9/93

Normalized Specifications for Identifying Reusable Software

Author: Luqi

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

Reference Number: NPS52-87-007

Publication Date: 3/87

Rapid Prototyping Languages for Expert Systems

Author: Luqi

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

Reference Number: NPS52-89-032

Publication Date: 3/89

Software Evolution via Prototyping

Author: Luqi

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

Reference Number: NPS52-88-039

Publication Date: 10/88

Generating a Language Translator Based on an Attribute Grammar Tool

Author: Luqi, & Robert Herndon

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

Reference Number: NPS52-88-007

Publication Date: 4/88

An Integrated Tool Environment for Embedded Real-Time Software

Author: Galik, Daniel, & Luqi

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

Reference Number: NPS52-88-008

Publication Date: 4/88

Automated Translation from a Prototyping Language into Ada

Author: Moffitt, C., II, & Luqi

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

Reference Number: NPS52-88-009

Publication Date: 4/88

Computer Aided Maintenance of Prototype Systems

Author: Luqi

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

Reference Number: NPS52-88-037

Publication Date: 10/88

Semantics of a Real-Time Language

Author: Berzins, Valdis, & Luqi

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

Reference Number: NPS52-88-033

Publication Date: 9/88

Automated Prototyping Data and Knowledge Translation

Author: Luqi

Publisher: US Naval Postgraduate School, Monterey, CA

Reference Number: NPS52-88-034

Publication Date: 9/88

Execution of a High Level Real-Time Language

Author: Luqi, & Valdis Berzins

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

Reference Number: NPS52-88-035

Publication Date: 9/88

Handling Timing Constraints in Rapid Prototyping

Abstract: This paper presents the concepts and mechanisms for handling the real-time constraints of embedded systems in rapid prototyping. Rapid prototyping of embedded systems can be accomplished using a Computer Aided Prototyping System (CAPS) and its associated Prototyping Language (PSDL). This system and language are used to aid the designer in the early stages of software engineering for hard real-time systems. Time critical operations have maximum execution times, maximum response times, and minimum calling periods. Time critical operations in a real-time prototype are handled by constructing static and dynamic schedules to coordinate execution and to meet the requred prototype execution times. The mechanisms for expressing timing constraints in PSDL are described along with their effects on schedules.

Author: Luqi

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

Reference Number: NPS52-88-036

Publication Date: 9/88

Software Technology for Adaptable, Reliable Systems (STARS)

Abstract: This document proposes a strategy for the Software Technology for Adaptable, Reliable Systems (STARS) program to improve our ability to exploit the advantages of computer technology. This revised and expanded version was produced by the STARS Joint Task Force based on Service and Agency comments on the earlier version and a variety of public comment, including those growing out of discussions at a public workshop. The STARS Program Strategy contains several levels of detail. The Executive Summary provides an overview of STARS. The body develops the rationale and guiding principles, explaining the motivation for the goal, supporting objectives, implementation approach, and organizational mechanisms. Supporting documents provide additional detail.

Publisher: DoD

Publication Date: 3/83

Ada Implementation Guide, Volume I

Abstract: This guide provides information to help Program Managers and Project Managers, as well as their staff, implement policies developed by the Department of the Navy for using Ada.

Author: Stuart, A.D., et al.

Publisher: Department of Navy

Publication Date: 3/92

Ada Implementation Guide, Volume II

Abstract: This guide provides information to help Program Managers and Project Managers, as well as their staff, implement policies developed by the Department of the Navy for using Ada. This volume contains supporting Appendices.

Author: Stuart, A.D. NISMC (Chair)

Publisher: Department of Navy

Publication Date: 3/92

Reengineering Technology Report, Volume 2

Abstract: The purpose of this report is to increase contact, awareness, and understanding of software reengineering tools. Use of this report should be the first step in transferring effective software reengineering processes, methods, and tools into practical use. The targets of this report are organizations responsible for the development and maintenance of computer software. This report defines the ideas of software reengineering and identifies their value in improving software quality for embedded, MCRR, and MIS applications. It explains how the features of current reengineering tools can improve software development and maintenance. It includes information about specific products in the marketplace. The information is aimed at those who must make the decisions about acquiring advanced technology and prepare their organizations to use it effectively. Also, this report attempts to identify the future directions of the field to help in planning long-range strategies.

Author: Olsem, M.R. and C. Sittenauer

Publisher: STSC - U.S. Air Force Software Technology Support Center, Hill AFB, UT 84056

Producing Organization: STSC - U.S. Air Force Software Technolog Support Center

Publication Date: 12/93

Final Report: The Effectiveness of Ada as an Administrative Progamming Language

Abstract: This report objectively assesses the administrative, technical, and human resouce issues associated with introducing Ada into a U.S. Navy AIS development organization, specifically the feasibility of using Ada as an administrative language for nonmission-critical AISs. This report includes, but is not limited to, procurement considerations, costs, training, staff acceptance/resistance, assimilation with existing tools and procedures, resource impact, productivity assessment (for both AIS development and maintenance), and management conclusions about how using Ada will affect nonmission-critical AIS use. The report also includes a discussion of strengths and weaknesses, and advantages and disadvantages of Ada in such areas as efficiency, ease of use, system quality, applications type, maintainability, and reusability compared to COBOL and 4GLs used in similar environments. The scope of the report covers training selected personnel to use Ada, creating an Ada environment through appropriate acquisitions and redesign efforts, converting existing systems to pilot systems in an Ada environment, exercising and evaluating pilot stystems, and initiating a report addressing NAVDAC objectives.

Author: Black, L. et. al.

Publisher: RJO Enterprises, Inc.

Sponsoring Organization: U.S. Naval Academy

Producing Organization: RJO Enterprises, Inc.

Publication Date: 9/89

Annotated Ada 9x Reference Manual Draft, Version 2.0

Abstract: This is one of two parallel documents describing the Ada 9X language. The other of the pair, the Ada 9X Reference Manual (RM9X), is intended eventually to become the ISO standard. This document, a draft version, contains all of the text in the RM9X, plus various annotations. It is intended for compiler writers, validation test writers, and other language lawyers--anyone interested in a more in-depth analysis of the language. Whereas the RM9X discusses what the rules of the language are, this draft discusses why the rules are the way they are, as well as the interactions among rules and the differences between Ada 9x and other versions of the language.

Author: Ada 9x Mapping/Revision Team; Intermetrics, Inc.

Publisher: Intermetrics, Inc.

Reference Number: IR-MA-1364--1

Sponsoring Organization: Ada 9X Project Office

Producing Organization: Intermetrics, Inc.

Publication Date: 3/93

Ada 9x Reference Manual Draft, Version 2.0 (Sections 3,7,8,10 only)

Abstract: Sections 3, 7, 8, and 10 of the Annotated Ada 9X Reference Manual, one of two parallel documents describing the Ada 9X language. The other of the pair, the Ada 9X Reference Manual (RM9X), is intended eventually to become the ISO standard. This document, a draft version, contains all of the text in the RM9X, plus various annotations. It is intended for compiler writers, validation test writers, and other language lawyers--anyone interested in a more in-depth analysis of the language. Whereas the RM9X discusses what the rules of the languge are, this draft discusses why the rules are the way they are, as well as the interactions among rules and the differences between Ada 9x and other versions of the language.

Author: Ada 9x Mapping/Revision Team; Intermetrics, Inc.

Publisher: Intermetrics, Inc.

Reference Number: IR-MA-1363-1

Sponsoring Organization: Ada Project Office

Producing Organization: Intermetrics, Inc.

Publication Date: 3/93

Formal Studies of Ada 9X

Abstract: This report, edition January 1993, contains mathematical studies of particular language issues and features, as part of the Language Precision Project, which was established to provide helpful criticism of Ada 9X design proposals from a mathematical point of view, and to provide a basis for future work on the formal semantics of Ada.

Author: Anderson, C.M. (Project Manager, Langauge Precision Project) et. al

Publisher: Office of the Under Secretary of Defense for Acquisition

Sponsoring Organization: ADA 9X Project Office

Producing Organization: ORA, Inc.

Publication Date: 1/93

Formal Studies of Ada 9X, Interim Report

Abstract: This interim report, January 1992, contains mathematical studies of particular language issues (such as optimization) and particular language features (such as the protected record proposal), as part of the Language Precision Project, which was established to provide helpful criticism of Ada 9X design proposals from a mathematical point of view, and to provide a basis for future work on the formal semantics of Ada.

Author: Anderson, C.M. (Project Manager, Langauge Precision Project) et. al

Publisher: Office of the Under Secretary of Defense for Acquisition

Sponsoring Organization: ADA 9X Project Office

Producing Organization: ORA, Inc.

Publication Date: 1/92

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

Back to FAQ