PAL CARD CATALOG ENTRY

SHORT DESCRIPTION

A description of reuse in terms of the processes involved


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

ASSET PROFILE

UNIT NAME
CFRPDEF
VERSION
3.0
ORIGIN
STARS
REVIEW CODE
OK
INET ADDRESS
librarian@source.asset.com
AUTHOR
Boeing, IBM, Unisys
RIGHTS
Approved for public release; distribution unlimited
COPYRIGHT
1993, 1994 UNISYS
LOCATION
ASSET
PAL

FILE LISTING

Directory Display


languages/ada/docs/cfrp/cfrp3:
  File Name                 Size
  ---------                 ----
  README                   3,142
  cfrp3.zip              384,184


Totals
  ==============  ==============
    2 Files              387,326

ABSTRACT

STARS Conceptual Framework for Reuse Processes (CFRP) Volume I:
Definition    

     This document defines a conceptual framework that describes reuse
in terms of the processes involved. This STARS Conceptual Framework for
Reuse Processes (CFRP) is intended to:

   o articulate, and promote understanding of, STARS reuse concepts,
   o identify reuse processes that are candidates for detailed definition,
   o provide techniques for modeling interrelationships among reuse
     processes, and
   o identify organizational and management issues associated with reuse
     and provide a framework for managing change in that context.

In addition, this document elaborates on the STARS vision and mission
with respect to reuse and provides a context for understanding STARS
reuse products and plans.
     The CFRP is intended to be generic with respect to domains,
organizations, economic sectors, methodologies, and technologies. 
Furthermore, even though this document focuses discussion of the CFRP by
describing it primarily in the context of software engineering, CFRP
concepts should generally be applicable to reuse in any
information-intensive context, such as technical documentation, general
information retrieval, and business, scientific, or personal information
management.
     The CFRP is a reuse process framework; its scope is limited to
identifying the processes involved in reuse and describing at a high
level how those processes operate and interact. In so doing, it offers
an indication of how some reuse processes can be integrated with other
processes and how the transition to reuse can be managed from a process
perspective. The CFRP does not prescribe how reuse should be implemented
in any particular context, nor does it include processes that do not
directly contribute to reuse.  It thus should not be interpreted as
providing prescriptive process definitions or imposing a particular life
cycle model. However, in separate efforts, STARS is developing detailed
reuse process definitions and life cycle models that are consistent with
the CFRP.  In general, legal, business, and acquisition aspects of reuse
are outside the scope of this document.
     This document is targeted to readers having one or more of the
following roles in their organizations:

   o Program/Project Planner - Responsible for planning the objectives,
strategy, processes, infrastructure, and resources for software
engineering programs or projects.  Interested in incorporating
domain-specific reuse into those programs/projects.
   o Process Engineer - Responsible for defining, instantiating,
tailoring, installing, monitoring, administering, and evolving software
engineering process models. Intereste*d in defining reuse processes or
integrating them with overall life cycle process models.
   o Reuse Advocate - Responsible for keeping abreast of reuse concepts,
technology, and trends and promoting the establishment/improvement of
reuse capabilities and practices within an organization. Interested in
understanding how new concepts and technology can be applied to
accelerate reuse adoption.


REVISION HISTORY

3.0  25 Oct 93  Release to ASSET
3.0  12 Feb 94  Initial 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.