1. FotoGazmic Software Project Plan Senior Project: CS 425 Spring 2003

4. Overview Objective Objective Easily Correct Color and Density of TIFF Images Easily Correct Color and Density of TIFF Images Two Main Features: Two Main Features: Automatic Density Correction Automatic Density Correction Color Correction Color Correction Discussion Discussion Client – Bernard Waxman Client – Bernard Waxman SIUE SIUE Photographer Photographer Wants a system that would allow users to easily correct the color and density of TIFF images Wants a system that would allow users to easily correct the color and density of TIFF images

5. Process Plan Evolutionary Delivery w/Risk Management Spiral (beginning) Evolutionary Delivery w/Risk Management Spiral (beginning) Client – Early Prototype Client – Early Prototype Early Discovery Early Discovery Difficulties with Specific Features Difficulties with Specific Features Delivery Delivery Product with the Most Important Functionality Product with the Most Important Functionality

6. Process Plan (cont.)

7. Definition Process Timeline

8. Process Plan (cont.) Design Process Timeline

9. Process Plan (cont.) Acceptance Tesitng Timeline

10. Process Plan (cont.) Installation Testing Timeline

11. Process Plan (cont.) System Release Timeline

12. Organization Plan Dr. Xudong Yu Upper Management Dr. Bernard Waxman Client

13. Test Plan Module Testing Module Testing Each Code Module Each Code Module Integration Testing Integration Testing Individual Components Individual Components Modules that are Dependent or Related to One Another Modules that are Dependent or Related to One Another

14. Test Plan (cont.) System Testing System Testing Ensure Functional and Nonfunctional Requirements Ensure Functional and Nonfunctional Requirements Includes Functional and Performance Testing Includes Functional and Performance Testing Acceptance Testing Acceptance Testing Internal Acceptance Test Internal Acceptance Test Team Members Team Members Acceptance Test with Client Acceptance Test with Client

15. Change Management Plan Baselines Baselines Problem Specification – Requirements Analysis Doc. Problem Specification – Requirements Analysis Doc. Design Specification – Project Design Doc. Design Specification – Project Design Doc. Who May Propose Changes? Who May Propose Changes? Fotogazmic Members Fotogazmic Members Rob Mills, Josey Baker, Myra Bergman, Tinate Dejtiranukul, and Chad Zbinden. Rob Mills, Josey Baker, Myra Bergman, Tinate Dejtiranukul, and Chad Zbinden. Client Client Bernard Waxman Bernard Waxman Upper Management Upper Management Professor Xudong Yu Professor Xudong Yu

16. Change Management Plan (cont.) All team members must review the proposed change and make recommendations before adoption All team members must review the proposed change and make recommendations before adoption Decisions will be based on the impact on Decisions will be based on the impact on Project Goals Project Goals Timelines Timelines All change requests will be documented All change requests will be documented

17. Change Management Plan (cont.) Investigators Report: Investigators Report: A summary of the proposed changes A summary of the proposed changes The name of the person requesting the change The name of the person requesting the change Classification of the change Classification of the change Impact on schedules Impact on schedules Recommendations for the proposed change Recommendations for the proposed change

18. Change Management Board Membership Membership All members of the FotoGazmic Team All members of the FotoGazmic Team When It Meets When It Meets When each member has been notified of the change request When each member has been notified of the change request How it operates How it operates Discuss request and it’s impact Discuss request and it’s impact Vote Vote Tie vote – Project Manager decides Tie vote – Project Manager decides

19. Documentation Plan One member will be responsible for writing each assigned document One member will be responsible for writing each assigned document All members review and edit document together All members review and edit document together Completed documents placed on FotoGazmic website Completed documents placed on FotoGazmic website Upper Management receives copy of document Upper Management receives copy of document Revisions will be made based on recommendations from Upper Management Revisions will be made based on recommendations from Upper Management

20. Commercial Break

21. Training Plan C++ C++ Microsoft Foundation Class (MFC) Microsoft Foundation Class (MFC) Open Source TIFF libraries Open Source TIFF libraries

22. Training Plan (cont.) Internal Training Internal Training Training team members – as needed Training team members – as needed Group Group Individual Individual Coding Languages Coding Languages C++ C++ Reading code and consulting books or online sources Reading code and consulting books or online sources Visual Basic Visual Basic Not planned, but possible choice for front-end interface Not planned, but possible choice for front-end interface

23. Training Plan (cont.) Non-Technical Training Non-Technical Training Management techniques Management techniques Upper Management will train team leader in how to oversee their particular project responsibilities Upper Management will train team leader in how to oversee their particular project responsibilities External Training External Training Installing Software Installing Software Standard Setup Package Standard Setup Package Using the System Using the System Online Help System Online Help System User Manual User Manual

24. Review and Reporting Plan Internal Reviews Internal Reviews Definition Process Review Definition Process Review At the end of the definition process At the end of the definition process Review the RAD and Project Plan Review the RAD and Project Plan Design Process Review Design Process Review At the end of the design process At the end of the design process Review the SDD and ODD Review the SDD and ODD Programming Process Review Programming Process Review At the end of the programming process At the end of the programming process Analyze program integration results Analyze program integration results

25. Review and Reporting Plan (cont.) Internal Reviews Internal Reviews System Test Process System Test Process At the end of the system test process At the end of the system test process Review all documentation produced Review all documentation produced Review system test results Review system test results Postmortem Review Postmortem Review When the project has been successfully completed When the project has been successfully completed Discuss overall project Discuss overall project Review project steps Review project steps

26. Review and Reporting Plan (cont.) External Reviews External Reviews Preliminary Design Review Preliminary Design Review Midway in Design Process, after internal review Midway in Design Process, after internal review Review and analyze validity of design approach Review and analyze validity of design approach Design Review Design Review At the end of the Design Process At the end of the Design Process Review the design specification and Project Plan Review the design specification and Project Plan Acceptance Review Acceptance Review At the end of the Acceptance Process At the end of the Acceptance Process Review acceptance test results Review acceptance test results

27. Review and Reporting Plan (cont.) Reports Generated by Non-managers Reports Generated by Non-managers Frequency: When needed. Frequency: When needed. To: Section Manager To: Section Manager Format: Technical Status Report. Format: Technical Status Report. Scope: A report at the end of any major task as needed. Scope: A report at the end of any major task as needed. Reports Generated by Section Managers Reports Generated by Section Managers Frequency: When needed. Frequency: When needed. To: Project Manager To: Project Manager Format: Technical Status Report Format: Technical Status Report Scope: A report at the end of each completed milestone by the manager responsible for that phase. Scope: A report at the end of each completed milestone by the manager responsible for that phase. Reports Generated by Project Manager Reports Generated by Project Manager Frequency: Bimonthly. Frequency: Bimonthly. To: Upper Management. To: Upper Management. Format: Technical Status Report. Format: Technical Status Report. Scope: Two reports a month to keep upper management updated on the status of the project. Scope: Two reports a month to keep upper management updated on the status of the project.

28. Installation and Operation Plan Installation Installation Standard setup package Standard setup package Installation Responsibility Installation Responsibility FotoGazmic team – development phase FotoGazmic team – development phase Client – after client accepts product Client – after client accepts product Schedule Schedule Meeting with client Meeting with client Demonstrate installation Demonstrate installation

29. Installation and Operation Plan (cont.) Operation Responsibility Operation Responsibility FotoGazmic team – currently FotoGazmic team – currently User – after software release User – after software release Maintenance and Tuning Responsibility Maintenance and Tuning Responsibility The development team The development team Duration of Responsibilities Duration of Responsibilities FotoGazmic team – until the release of the system FotoGazmic team – until the release of the system Client – after the release of the system Client – after the release of the system

30. Questions?