 |
||||
 |
 |
|
|
MaintenanceMaintenance phase activities fall into three distinct types:
Scheduled system maintenance is included in the project lifecycle for a time defined in the contract. After this time expires, system maintenance becomes the customer’s responsibility. The time during which WESCO is responsible for system maintenance allows for a complete knowledge transfer from the project team to the customer’s maintenance personnel. During the maintenance phase, as bugs are identified, a modification schedule is created and executed. All bugs are tracked and progress toward fixing them is reported regularly. Once resolved, the bug report is removed from the list and archived as part of the project documentation. System enhancements are defined as those system change that fall outside of the scope of the original project. These enhancements can be as simple as a new report, or as complicated as creating a new subsystem. System enhancements must be well defined. They then fall under the HELPcycle rules until they are completed. Enhancement requirements engineering, design, coding, and testing are managed and executed by applying the same standard processes that are used during the initial development effort. Tasks Maintenance phase tasks are defined on a per project basis. Deliverables Post implementation deliverables can include any type of deliverable from the project lifecycle. Quality Tasks from all other phases can occur during the maintenance phase. Often, less stringent application of quality tasks is required during the maintenance phase because of the less complex nature of most phase objectives and deliverables. It is critical that the following quality activities are performed to ensure ongoing system viability:
<< Summary | Phases | Development Process| Maturity Model | Back >> |
 |
 |