1. Multimedia Project life cycle www.wsolvt.com

2. Purpose The purpose of this Presentation is to define the life cycle of any multimedia project.

3. The Problems Missing data. changing the data. Unpublished work plan. Low management. Due date is missing

4. Why process ? Clear Work plan. Team management. Monitor & Control Risk management. Due Date. Client satisfaction.

5. Process Phases Preparation Phase. Development Phase. Deliver Phase.

6. Multimedia Process life Cycle Deliver Phase Preparation Phase Development Phase

7. Project Request New project should be started and initiated by a request form . Approval from the higher management.

8. Project Initiation Meeting Understanding the project details and discuss the requirements and data status. Project flow chart.

9. Project Requirement Document The requirement document will be the guide through the development of the project and will be a check list in the delivery form at the end of the project. Requirement document should be under version control and change request process.

10. Content gathering and Data Validation Each project will have its forms template according to the project type. It is not accepted to start the project before ensuring of the completeness of data. language and scientific approval .

11. Look and Feel Project Design theme. Acceptance form. Changing in the theme is so critical Later. Acceptance should be within certain time.

12. Storyboard Sponsor know exactly what will be delivered. Technical team will know exactly what work should be done.

13. Kickoff meeting Publish Work Plan. All stakeholders of the project attending this meeting.

14. Design and media manipulation Tasks should be assigned to the team members after ensuring that each one understood his assigned task and be informed with the due time.

15. Development Phase 1 Team Work Plan.

16. Prototype Contains project screens, links, media locations and main functions The prototype acceptance form should be signed.

17. Development Phase 2 Prototype Notes. Team Work Plan Continued.

18. Validation A beta version from the project should be delivered to the sponsor for reviewing the data placement and all the media in the project.

19. Testing Testing for project final version.

20. Documentation Project documents, reports, mails and source code should be documented for further usage or for planning to any new versions.

21. Deliver & Close A Final version of the project should be delivered to the sponsor. Project is Closed.

22. Change Control Procedure Change Request Form.

23. Change Control Cycle Change request System Review Board (SRB) Accepted Changing in work plan Change in Requirement document. Configuration control Board (CCB) Refused Inform stakeholders Process the change

24. System review board (SRB) Technical team Level meeting.

25. Configuration control board (CCB) CCB is the higher level of review board, it is for the strategically decision which approve or disapprove the SRB results. concerns the changes that will affect the budget considerations, priorities, etc .