PAL CARD CATALOG ENTRY

SHORT DESCRIPTION

Directions for institutionalization of software reuse


MOVEMENT WITHIN THE PAL CARD CATALOG
Move to top-level taxonomy
Move to keyword list

ASSET PROFILE

UNIT NAME
Direction Level Handbook
VERSION
3-94
ORIGIN
CARDS/ASSET
REVIEW CODE
OK
INET ADDRESS
None
AUTHOR
Leandro V. Delgado, Robert J. Bowes, Robert O. Saisi,
Theresa R. Huber for UNISYS
RIGHTS
Approved for public release; distribution unlimited
COPYRIGHT
Assigned to the U.S. Government
LOCATION
ASSET
CARDS
PAL

FILE LISTING

Directory Display


languages/ada/docs/dl_hb:
  File Name                 Size
  ---------                 ----
  README                     999
  dl_hb.zip              200,050


Totals
  ==============  ==============
    2 Files              201,049

ABSTRACT

CARDS Direction Level Handbook

     The Central Archive for Reusable Defense Software (CARDS) Program
is a concerted Department of Defense (DoD) effort to transition advances
in the techniques and technology of library-assisted, domain-specific
software reuse into mainstream DoD software procurements.  There are
four key elements to the CARDS approach:

   o  Develop a CARDS knowledge-base for development of domain-specific
      reuse processes designed to support reuse based system development.

   o  Define a plan to perform technology transfer to other government
      organizations (Franchise Plan).

   o  Implement the plan for technology transfer through franchising.

   o  Improve the knowledge-base and blueprint through continuous
      process improvement.

     The Franchise Plan provides a description of reuse processes and 
instructions for tailoring development processes to effect
domain-specific reuse; in addition, it will describe in precise steps a
scenario for implementing a domain-specific library.
     Along with the Franchise Plan, organizations will be provided with
three sets of documents:  Reuse Adoption Handbooks, CARDS library
operation and maintenance related documents, and training and education
material.  The Reuse Adoption Handbooks consist of:  Direction Level
Handbook, Acquisition Handbook, Engineer's Handbook, and the Component
Developer's and Tool Vendor's Handbook.  The Engineer's Handbook and
the Component Developer's and Tool Vendor's Handbook are technically
oriented; the Direction Level and Acquisition Handbooks emphasize the
business aspects of reuse, including strategy, schedule, risk, cost and
rights issues.  The CARDS Library Model Contracts/Agreements document
provides a background of related legal issues, guidance to the CARDS
Library Staff in applying the agreements to suppliers, subscribers and
a starting point to develop library interoperability.  
     This 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.


REVISION HISTORY

20 November 1992  Robert Bowes et al  FINAL release
26 August 1993    CARDS               Release to the PAL
25 March 1994     UNISYS              Release to ASSET
30 September 94   ASSET               Release to the PAL


RELEASE NOTICE

Approved for public release; distribution unlimited


DISCLAIMER

This documentation is provided "AS IS" and without any expressed or
implied warranties whatsoever.  No warranties as to performance,
merchantability, or fitness for a particular purpose exist.

The user must assume the entire risk and liability of using this
document.  In no event shall any person or organization of people be
held responsible for any direct, indirect, consequential or
inconsequential damages or lost profits.