RETRO CHESS Requirements

AnalysisSteven Kolenda, Jacob Brown, Johnpaul

Barrieau, Jen Bilotta, Felix RohrerCS673 Software Engineering

02-22-12

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

Our User

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

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

Software Project Management Plan (SPMP)Roles

Team Member Document responsibility Primary Role Secondary Role

Steve Kolenda Project Plan/Presentation Project Lead Requirements Management Lead

Felix Rohrer SCMP Developer Configuration Management Lead

Jake Brown SQAP Graphic Design Quality Assurance Lead

Jen Bilotta Proposal Developer Implementation Lead

Johnpaul Barrieau SPMP Developer Design Lead

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 Completio

n Date1 Android

learning curve

10 8 1 3 Practice as background task

Developers 08-Feb-12

2 Network Capabilities

10 5 8 48 make it retro All 01-Apr-12

3 Checkmate 8 3 10 240 make it retro Developers 14-Apr-12

4 Porting issues

4 9 2 28 Dedicate resource full time

Developers 15-Mar-12

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.

Software Project Management Plan (SPMP)

Work Breakdown StructureCompletion 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 StructureFebruar

y March April1 2 3 4 1 2 3 4 1 2 3 4

SCMP X SQAP X SPMP rev 1 X Freeze Requirements X Version 1 X Version 2 X

Software Project Management Plan (SPMP)

Project Size Estimates

Microsoft Office Excel Worksheet

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

Software Configuration Management Plan (SCMP)

Configuration Items

• Approved by Project Leader• Implemented by Configuration

Leader• Documents versioned as 1.0, 1.1,

etc.

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

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.

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

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

Project PlanTask Name Start Finish Resource

Names Work

Chess Android Application Wed 1/18/12 Wed 5/2/12 56 hrs

Project Planning Wed 1/18/12 Wed 2/8/12 48 hrs

Proposal Wed 2/1/12 Wed 2/8/12 jen 8 hrs

Software Configuration Management Plan (SCMP) Wed 2/1/12 Wed 2/8/12 felix 8 hrs

Software Quality Assurance Plan (SQAP) Wed 2/1/12 Wed 2/8/12 jake 8 hrs

Software Project Management Plan (SPMP) Wed 2/1/12 Wed 2/8/12 jp 8 hrs

Presentation Wed 2/1/12 Wed 2/8/12 steve 8 hrs

Weekly Report (Part 1) Sun 1/29/12 Sun 1/29/12 steve 2 hrs

Meeting Minutes (Part 1) Sun 1/29/12 Sun 1/29/12 steve 2 hrs

Weekly Report (Part 2) Sun 2/5/12 Sun 2/5/12 jake 2 hrs

Meeting Minutes (Part 2) Sun 2/5/12 Sun 2/5/12 jake 2 hrs

Project Planning COMPLETE Tue 2/7/12 Tue 2/7/12 0 hrs

Requirements Analysis Wed 2/8/12 Wed 2/22/12 8 hrs

RevisionsVersion

Author Date Changes

1.0 Steven Kolenda

06-Feb-12

Initial draft

1.1 Steven Kolenda

07-Feb-12

Condense bullet points

1.2 Steven Kolenda

07-Feb-12

Update WBS from SPMP, create revisions slide