Software Component Deployment
Software component deployment is the
deployment subactivity consisting
of the cohesive collection of all
tasks that are primarily
performed to deploy one or more
software components onto the
hardware components in the
production environments.
The typical goals of the software component deployment
subactivity are to:
The typical objectives of the software component deployment
subactivity are to:
- Deploy the software components to their hardware
components.
- Deliver the final version of all associated deliverable
work products to the customer organization.
- Notify the user organizations regarding the readiness of
the software components for use.
Typical examples of the software component deployment
subactivity include:
- Upgrading applications.
- Incorporating a new commercial-off-the-shelf (COTS)
software package.
- Automatically installing a COTS software application on
multiple clients from a remote operator's console.
The software component deployment subactivity may typically
begin when the following preconditions hold:
The software component deployment subactivity is typically
complete when the following postconditions hold:
- The software components have been officially accepted by
the customer organization.
- The software components are in use by the user
organizations.
- The delivery phase is complete.
The software component deployment subactivity typically
involves the following producers performing the following
deployment tasks:
Environments
The software component deployment subactivity typically
involves the following environments:
The software component deployment subactivity typically
results in the production of all or part of the following
deployment work products:
Phases
The software component deployment activity typically
involves the following phases:
- Software deployment can be performed:
- Manually, automatically with an installation script, or
automatically using a deployment tool.
- Locally or remotely over a network.
- This subactivity is documented using the typical
configuration for large projects. It is intended to be
configured (i.e., instantiated, extended, and tailored) to
meet the needs of specific projects.
- The preconditions of this subactivity should be the union
of the preconditions of its constituent tasks.
- The completion criteria for this subactivity should be
the union of the postconditions of its constituent
tasks.