|
|
|
| |
|
2- Project Execution: |
|
|
|
Project Life Cycle: |
|
The project shall follow ICONS project life cycle methodology. |
|
|
|
Project Procedures: |
|
|
|
 |
Testing, includes the following test cycles: |
|
|
|
Unit/Program Testing to be done by
assigned developers.
|
|
|
|
Integration testing to be done by
ICONS quality team/developers team
|
|
|
|
System testing to be done by Client
team.
|
|
|
|
User acceptance testing to be
done/coordinated by Client team.
|
|
|
|
|
Testing, includes the following test cycles: |
|
|
|
|
3- Project Completion: |
|
|
|
Customer Contractual Acceptance and Installation: |
|
It is Client team responsibility to define the acceptance criteria with cooperation with ICONS team, and both teams shall approve it, as part of the quality plan. Client should accept each activity according to the defined criteria. |
|
|
|
Handover: |
|
|
|
|
Post Implementation Report: Based on the project plan, the implementation for each module will be divided into: |
|
|
|
Technical training for dedicated
Client members.
|
|
|
|
Business training for dedicated
Client team members
|
|
|
|
Implement the tested module.
|
|
|
|
Evaluate the module compliance with
requirements.
|
|
|
Apply the predefined test criteria
(prepared by Client team)
|
|
|
|
Receive the module approval from
dedicated Client members.
|
|
|
|
Send a copy of this approval to
Client management.
|
|
|
|
|
|
|
Project Close Down: When all of the activities specified in the project plan are finished and accepted by Client the project will be considered closed and other continuation plans (maintenance agreement) will be discussed and agreed between Client and ICONS. |
|
|
|
|
|
|
|
|
BACK ... |
