1. Steven Kolenda, Jacob Brown, Johnpaul Barrieau, Jen Bilotta, Felix Rohrer CS673 Software Engineering 02-22-12

2. Purpose Understand what an Android user wants in a chess app Refine a set of requirements that focus on the user wants Track progress towards meeting the requirements

3. Our User

4. So our user is probably over 25. What else? Sufficient expertise to operate an Android device Able to install an app from the Android Market General chess knowledge Chess fact: En Passant capture was one of the last major rule changes to chess, and became universally accepted in 1880. Source: Wikipedia

5. Software Project Management Plan (SPMP) Process Model Project will be executed using a spiral model due to the project risk assessment Spiral 1: develop a functioning chess version Spiral 2: add network capability Due to the risks, there will be an early form prototype developed in parallel

6. Software Project Management Plan (SPMP) Roles Team MemberDocument responsibilityPrimary RoleSecondary Role Steve KolendaProject Plan/PresentationProject LeadRequirements Management Lead Felix RohrerSCMPDeveloperConfiguration Management Lead Jake BrownSQAPGraphic DesignQuality Assurance Lead Jen BilottaProposalDeveloperImplementation Lead Johnpaul BarrieauSPMPDeveloperDesign Lead

7. Software Project Management Plan (SPMP) Risk Management Risk #Risk Title Likelihood to occur [1-10] L Impact [1-10] l Retirement Cost [1-10] R Priority (11-L)*(11-l)*R Retirement or mitigation plan Responsible Engineer Target Completion Date 1Android learning curve 10813Practice as background task Developers08-Feb-12 2Network Capabilities 105848make it retroAll01-Apr-12 3Checkmate8310240make it retroDevelopers14-Apr-12 4Porting issues 49228Dedicate resource full time Developers15-Mar-12

8. Software Project Management Plan (SPMP) Technical Process Eclipse will be used for the development environment. Google Code will be used as the repository and for version management.

9. Software Project Management Plan (SPMP) Work Breakdown Structure Completion of version 1 is dependent on the ability of playing chess on a single device. Version 2 depends on completion of version 1 as well as the design and implementation of a successful network solution using two devices. Work Breakdown Structure Februar yMarchApril 123412341234 SCMPX SQAPX SPMP rev 1X Freeze RequirementsX Version 1X Version 2 X

10. Software Project Management Plan (SPMP) Project Size Estimates

11. Software Configuration Management Plan (SCMP) Responsibilities Configuration Leader –responsible for the installation and maintenance of the configuration management tool(s) Project Leader –monitor cost, time, quality and functionality of the project. Engineers –responsible for implementing the code related CI's

12. Software Configuration Management Plan (SCMP) Configuration Items Approved by Project Leader Implemented by Configuration Leader Documents versioned as 1.0, 1.1, etc.

13. Software Quality Assurance Plan (SQAP) Responsibilities QA tasks: –Documentation –Review meetings –Verification –Validation (primarily testing) –Activities designed to improve the quality assurance process, which are detailed below Quality Assurance Leader –Ensure tasks above are completed

14. Software Quality Assurance Plan (SQAP) Content Standards: –IEEE standards, with appropriate modifications. Practices: –All project artifacts maintained in Google SVN. –All code reviewed by the entire team –Brief weekly code reviews. Conventions: –All source code will be written in accordance to Java programming conventions as defined by Oracle Metrics: –Time spent by individuals on tasks and subtasks. –Number of defects per hundred lines of code.

15. Software Quality Assurance Plan (SQAP) Reviews and Audits – Min. Requirements Software requirements review Preliminary design review Critical design review Functional audit SCMP review Post mortem review

16. Software Quality Assurance Plan (SQAP) Problem Reporting & Corrective Action Tools & Techniques –Google Code Issues –Meeting Minutes –Individual Wiki notes The values for issue type are as follows: –Defect – Report of a software defect –Enhancement – Request for enhancement –Task – Work item that doesn’t change the code or docs –Review – Request for a source code review –Other – Some other kind of issue The values for severity are as follows: –Critical – Must resolve in the specified milestone –High – Strongly want to resolve in the specified milestone –Medium – Normal priority –Low – Might slip to later milestone

17. Project Plan Task NameStartFinish Resource Names Work Chess Android ApplicationWed 1/18/12Wed 5/2/1256 hrs Project PlanningWed 1/18/12Wed 2/8/1248 hrs ProposalWed 2/1/12Wed 2/8/12jen8 hrs Software Configuration Management Plan (SCMP)Wed 2/1/12Wed 2/8/12felix8 hrs Software Quality Assurance Plan (SQAP)Wed 2/1/12Wed 2/8/12jake8 hrs Software Project Management Plan (SPMP)Wed 2/1/12Wed 2/8/12jp8 hrs PresentationWed 2/1/12Wed 2/8/12steve8 hrs Weekly Report (Part 1)Sun 1/29/12 steve2 hrs Meeting Minutes (Part 1)Sun 1/29/12 steve2 hrs Weekly Report (Part 2)Sun 2/5/12 jake2 hrs Meeting Minutes (Part 2)Sun 2/5/12 jake2 hrs Project Planning COMPLETETue 2/7/12 0 hrs Requirements AnalysisWed 2/8/12Wed 2/22/128 hrs

18. Revisions VersionAuthorDateChanges 1.0Steven Kolenda06-Feb-12Initial draft 1.1Steven Kolenda07-Feb-12Condense bullet points 1.2Steven Kolenda07-Feb-12Update WBS from SPMP, create revisions slide