| Acquisition |
The process of obtaining products and
services via contract
|
| Acquisition strategy |
A plan of action for achieving a
specific goal or result through contracting for products and
services
|
| Acquisition plan |
The artifact that is typically used to
document the acquisition strategy
|
| Application
engineering |
An engineering process that develops
software products from partial solutions or knowledge embodied in
software-related assets
|
| Attached process |
The process associated with a core
asset that tells a product builder how to instantiate it or otherwise put it to
use in a specific product.
|
| Business model |
A framework that relates the different
forms of a product line approach to an organization's business context and
strategy
|
| Commission |
Contract with another party to build a
product or provide a service
|
| Concept of
operations |
Document describing an organization's
structure, roles and responsibilities, processes, and policies that all detail
the way the organization operates
|
| Core asset |
An artifact or resource that is used
in the production of more than one product in a software product line. A core
asset may be an architecture, a software component, a process model, a plan, a
document, or any other useful result of building a system.
|
| Development |
Generic word used to describe how
software comes to be
|
| Domain |
An area of knowledge or activity
characterized by a set of concepts and terminology understood by practitioners
in that area
|
| Domain analysis |
Process for capturing and representing
information about applications in a domain, specifically common characteristics
and reasons for variability
|
| Domain engineering |
An engineering process that develops
software assets for one or more domains
|
| Economies of scale |
The condition where fewer inputs such
as effort and time are needed to produce greater quantities of a single
output
|
| Economies of scope |
The condition where fewer inputs such
as effort and time are needed to produce a greater variety of outputs. Greater
business value is achieved by jointly producing different outputs. Producing
each output independently fails to leverage commonalities that affect costs.
Economies of scope occur when it is less costly to combine two or more products
in one production system than to produce them separately.
|
| Mining |
Resurrecting and rehabilitating a
piece of an existing software system to serve in a new system for which it was
not originally intended
|
| Platform |
Core software asset base that is
reused across systems in the product line
|
| Practice area |
A body of work or a collection of
activities that an organization must master to successfully carry out the
essential work of a software product line
|
| Product line |
A group of products sharing a common,
managed set of features that satisfy specific needs of a selected market or
mission area
|
| Product line
approach |
A system of software production that
uses reusable software-related assets to modify, assemble, instantiate, or
generate a line of software or software-intensive products
|
| Product line
architecture |
Description of the structural
properties for building a group of related systems (i.e., product line),
typically the components and their interrelationships. The inherent guidelines
about the use of components must capture the means for handling required
variability among the systems. (Sometimes called a reference
architecture)
|
| Product line scope |
Description of the products that will
constitute the product line
|
| Product line system |
A member of a software product
line
|
| Production plan |
The guide to how products in the
software product line will be constructed from the product line's core assets
|
| Project |
An undertaking typically requiring
concerted effort that is focused on developing or maintaining a specific
product or products. Typically a project has its own funding, accounting, and
delivery schedule.
|
| Software
architecture |
Structure or structures of the system,
which consists of software components, the externally visible properties of
those components, and the relationships among them
|
| Software product
line |
A set of software-intensive systems
sharing a common, managed set of features that satisfy the specific needs of a
particular market segment or mission and that are developed from a common set
of core assets in a prescribed way
|
| Software product line practice
pattern |
A description of an organization's
context, the product line problem it is trying to solve, and the set of
practice areas to use in concert to solve the problem.
|
