 |
||||
 |
 |
|
|
AcceptanceAcceptance phase activities and timing are dependent on the nature of a given project. On many projects, the client performs acceptance phase activities parallel with other project activities. In general, the acceptance phase activities include final user testing and signoff on all major system deliverables. At the same time, WESCO often incorporates user testing comments into the system during a software creation phase that occurs parallel to the acceptance phase. This is done only after an analysis determines that an acceptable risk level exists. Tasks
Deliverables Typically, there are no new deliverables associated with the acceptance phase. Client must signoff on all major deliverables in a timely fashion. Quality Continually updating software versions as deliverables are accepted allows for efficient maintenance activities. In addition, during this phase quality audits are often performed to ensure the robustness of the project lifecycle. As part of these process audits, complex metrics are calculated and evaluated to determine trends that are adverse to quality. These metrics provide quantifiable evidence of HELPcycle strengths and weaknesses. << Summary | Phases | Development Process| Maturity Model | Back >> |
 |
 |