Hardtware Component Deployment
Hardware component deployment is the
deployment subactivity consisting
of the cohesive collection of all
tasks that are primarily
performed to deploy one or more
hardware components onto their
production environments.
The typical goals of the hardware component deployment
subactivity are to:
The typical objectives of the hardware component deployment
subactivity are to:
- Deploy the hardware components to their production
environments.
- Deliver the final version of all associated deliverable
work products to the customer organization.
- Notify the user organizations regarding the readiness of
the hardware components for use.
Typical examples of the hardware component deployment
subactivity include:
- Upgrading clients
- Upgrading servers
- Upgrading networks (i.e., network connectivity
devices)
- Upgrading storage (e.g., from tape drives to tape
libraries or disk libraries)
- Going from client/server to n-tier distributed
applications with multiple kinds of servers (e.g., web
servers, security servers, application servers, database
servers)
The hardware component deployment subactivity may typically
begin when the following preconditions hold:
The hardware component deployment subactivity is typically
complete when the following postconditions hold:
- The hardware components have been officially accepted by
the customer organization.
- The hardware components are in use in their production
environments.
- The delivery phase is complete.
The hardware component deployment subactivity typically
involves the following producers performing the following
deployment tasks:
Environments
The hardware component deployment subactivity typically
involves the following environments:
The hardware component deployment subactivity typically
results in the production of all or part of the following
deployment work products:
Phases
The hardware component deployment subactivity typically
involves the following phases:
- 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.