FotoGazmic Software Project Plan Senior Project: CS 425 Spring 2003.
-
Upload
aubrie-bryant -
Category
Documents
-
view
217 -
download
0
Transcript of FotoGazmic Software Project Plan Senior Project: CS 425 Spring 2003.
FotoGazmic FotoGazmic SoftwareSoftware
Project PlanProject Plan
Senior Project: CS 425Senior Project: CS 425
Spring 2003Spring 2003
OverviewOverview ObjectiveObjective
Easily Correct Color and Density of TIFF Easily Correct Color and Density of TIFF ImagesImages
Two Main Features:Two Main Features: Automatic Density CorrectionAutomatic Density Correction Color CorrectionColor Correction
DiscussionDiscussion Client – Bernard WaxmanClient – Bernard Waxman
SIUESIUE PhotographerPhotographer Wants a system that would allow users to easily Wants a system that would allow users to easily
correct the color and density of TIFF imagescorrect the color and density of TIFF images
Process PlanProcess Plan
Evolutionary Delivery w/Risk Evolutionary Delivery w/Risk Management Spiral (beginning) Management Spiral (beginning) Client – Early PrototypeClient – Early Prototype
Early DiscoveryEarly Discovery Difficulties with Specific FeaturesDifficulties with Specific Features
DeliveryDelivery Product with the Most Important Product with the Most Important
FunctionalityFunctionality
Process Plan (cont.)Process Plan (cont.)
Design Process Timeline
ID Task Name Subtask Name Assigned to: Start Finish DurationApr 2003 May 2003Mar 2003
4/13 5/115/43/303/16 4/6 4/273/233/9
2
3
4
5
16d4/10/20033/26/2003Project Design
16d4/10/20033/26/2003TinatePersistent Data Management
16d4/10/20033/26/2003JoseySDD
16d4/10/20033/26/2003ChadODD
25d4/19/20033/26/2003Rob/MyraInitial Prototype
1
4/20
Test PlanTest Plan
Module TestingModule Testing Each Code Module Each Code Module
Integration TestingIntegration Testing Individual ComponentsIndividual Components Modules that are Dependent or Related Modules that are Dependent or Related
to One Anotherto One Another
Test Plan (cont.)Test Plan (cont.)
System TestingSystem Testing Ensure Functional and Nonfunctional Ensure Functional and Nonfunctional
RequirementsRequirements Includes Functional and Performance Includes Functional and Performance
TestingTesting Acceptance TestingAcceptance Testing
Internal Acceptance TestInternal Acceptance Test Team MembersTeam Members
Acceptance Test with ClientAcceptance Test with Client
Change Management Change Management PlanPlan
BaselinesBaselines Problem Specification – Requirements Analysis Problem Specification – Requirements Analysis
Doc.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 Rob Mills, Josey Baker, Myra Bergman, Tinate Dejtiranukul, and Chad Zbinden.Dejtiranukul, and Chad Zbinden.
Client Client Bernard WaxmanBernard Waxman
Upper ManagementUpper Management Professor Xudong YuProfessor Xudong Yu
Change Management Change Management Plan (cont.)Plan (cont.)
All team members must review the All team members must review the proposed change and make proposed change and make recommendations before adoptionrecommendations before adoption
Decisions will be based on the impact Decisions will be based on the impact on on Project GoalsProject Goals TimelinesTimelines
All change requests will be All change requests will be documenteddocumented
Change Management Change Management Plan (cont.)Plan (cont.)
Investigators Report:Investigators Report: A summary of the proposed changesA summary of the proposed changes The name of the person requesting the The name of the person requesting the
changechange Classification of the changeClassification of the change Impact on schedulesImpact on schedules Recommendations for the proposed Recommendations for the proposed
changechange
Change Management Change Management BoardBoard
MembershipMembership All members of the FotoGazmic TeamAll members of the FotoGazmic Team
When It MeetsWhen It Meets When each member has been notified of When each member has been notified of
the change requestthe change request How it operatesHow it operates
Discuss request and it’s impactDiscuss request and it’s impact VoteVote
Tie vote – Project Manager decidesTie vote – Project Manager decides
Documentation PlanDocumentation Plan
One member will be responsible for writing One member will be responsible for writing each assigned documenteach assigned document
All members review and edit document All members review and edit document togethertogether
Completed documents placed on Completed documents placed on FotoGazmic websiteFotoGazmic website
Upper Management receives copy of Upper Management receives copy of documentdocument
Revisions will be made based on Revisions will be made based on recommendations from Upper Managementrecommendations from Upper Management
Training PlanTraining Plan
C++C++ Microsoft Foundation Class (MFC)Microsoft Foundation Class (MFC) Open Source TIFF librariesOpen Source TIFF libraries
Training Plan (cont.)Training Plan (cont.)
Internal TrainingInternal Training Training team members – as neededTraining team members – as needed
GroupGroup IndividualIndividual
Coding LanguagesCoding Languages C++C++
Reading code and consulting books or online Reading code and consulting books or online sourcessources
Visual BasicVisual Basic Not planned, but possible choice for front-end Not planned, but possible choice for front-end
interfaceinterface
Training Plan (cont.)Training Plan (cont.)
Non-Technical TrainingNon-Technical Training Management techniquesManagement techniques
Upper Management will train team leader in Upper Management will train team leader in how to oversee their particular project how to oversee their particular project responsibilitiesresponsibilities
External TrainingExternal Training Installing SoftwareInstalling Software
Standard Setup PackageStandard Setup Package Using the SystemUsing the System
Online Help SystemOnline Help System User ManualUser Manual
Review and Reporting Review and Reporting PlanPlan
Internal ReviewsInternal Reviews Definition Process ReviewDefinition Process Review
At the end of the definition processAt the end of the definition process Review the RAD and Project Plan Review the RAD and Project Plan
Design Process ReviewDesign Process Review At the end of the design processAt the end of the design process Review the SDD and ODD Review the SDD and ODD
Programming Process ReviewProgramming Process Review At the end of the programming processAt the end of the programming process Analyze program integration results Analyze program integration results
Review and Reporting Plan Review and Reporting Plan (cont.)(cont.)
Internal ReviewsInternal Reviews System Test ProcessSystem Test Process
At the end of the system test processAt the end of the system test process Review all documentation produced Review all documentation produced Review system test results Review system test results
Postmortem ReviewPostmortem Review When the project has been successfully When the project has been successfully
completedcompleted Discuss overall projectDiscuss overall project Review project stepsReview project steps
Review and Reporting Plan Review and Reporting Plan (cont.)(cont.)
External ReviewsExternal Reviews Preliminary Design ReviewPreliminary Design Review
Midway in Design Process, after internal reviewMidway in Design Process, after internal review Review and analyze validity of design approach Review and analyze validity of design approach
Design ReviewDesign Review At the end of the Design ProcessAt the end of the Design Process Review the design specification and Project PlanReview the design specification and Project Plan
Acceptance Review Acceptance Review At the end of the Acceptance ProcessAt the end of the Acceptance Process Review acceptance test results Review acceptance test results
Review and Reporting Plan Review and Reporting Plan (cont.)(cont.)
Reports Generated by Non-managersReports Generated by Non-managers FrequencyFrequency:: When needed. When needed. To: Section ManagerTo: Section Manager FormatFormat:: Technical Status Report. Technical Status Report. ScopeScope:: A report at the end of any major task as needed. A report at the end of any major task as needed.
Reports Generated by Section ManagersReports Generated by Section Managers Frequency: When needed.Frequency: When needed. To: Project ManagerTo: Project Manager Format: Technical Status ReportFormat: Technical Status Report Scope:Scope: A report at the end of each completed milestone by the A report at the end of each completed milestone by the
manager responsible for that phase.manager responsible for that phase. Reports Generated by Project ManagerReports 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 Scope: Two reports a month to keep upper management
updated on the status of the project.updated on the status of the project.
Installation and Installation and Operation PlanOperation Plan
InstallationInstallation Standard setup packageStandard setup package
Installation ResponsibilityInstallation Responsibility FotoGazmic team – development phaseFotoGazmic team – development phase Client – after client accepts productClient – after client accepts product
ScheduleSchedule Meeting with clientMeeting with client
Demonstrate installation Demonstrate installation
Installation and Operation Installation and Operation Plan (cont.)Plan (cont.)
Operation ResponsibilityOperation Responsibility FotoGazmic team – currentlyFotoGazmic team – currently User – after software releaseUser – after software release
Maintenance and Tuning ResponsibilityMaintenance and Tuning Responsibility The development team The development team
Duration of ResponsibilitiesDuration of Responsibilities FotoGazmic team – until the release of the FotoGazmic team – until the release of the
systemsystem Client – after the release of the systemClient – after the release of the system