Implementation Work Product
- Implementation Work Product
- a work product
that may be produced during the
implementation activity
- Implementation Set of Work Products
- the cohesive collection of all inplementation work products
During business engineering, the following work products may
be implemented for integration into the [re]engineered
business:
During application development, the following work products
may be implemented for integration into the application:
- Centers:
-
Components:
-
Data Component,
which is a component consisting of a cohesive
collection of data (content) that is part of an
application, contact center, or data center.
-
Hardware Component,
which is a component consisting of a physical
device that is part of a system application, contact
center, or data center.
-
Personnel Component,
which is a component consisting of a
person playing a
role that
is part of a system application, contact center, or data
center.
-
Procedural Component,
which is a component consisting of procedure that
is performed by one or more persons playing one or more
roles.
-
Software Component,
which is a component consisting of an encapsulated
cohesive piece of computer software that:
- Offers a cohesive set of services via one or more
interfaces.
- Is designed, implemented, and tested as a unit
prior to integration.
- Is part of an application, contact center, or data
center.
- Different endeavors require different processes, which in
turn will require different implementation work
products.
- Every endeavor does not require the production of every
implementation work product.
- Select only those implementation work products that are
appropriate for the endeavor.
- Naturally, only implement those work products required
for integration into the business or application.
- Selected implementation work products should be:
- Relevant.
- Useful.
- Usable.
- Cost-effective.