5.3 Control Plan - School of Computing & Software Engineering

plumpbustlingInternet και Εφαρμογές Web

4 Δεκ 2013 (πριν από 3 χρόνια και 6 μήνες)

149 εμφανίσεις


DRAFT



GGDA
-
Siege Expansion Project
-
Software Project Management

Version: 1.04
















The GGDA
-
SIEGE Expansion Project


Software Project Management Plan











Developed By:

Sponsored By:



Team Initech

Bates Westmoreland

Jonathan Meek

Ken Anderso
n

Michael Smith

Dr. Jon Preston

Clinton Lowe

Andrew Greenberg


DRAFT

GGDA
-
Siege Expansion Project
-
Software Project Management

Version: 1.04

Last printed
12/4/2013 5:40 PM


Page
2

of
21


Filename:
plumpbustling_6a6e77a9
-
0f41
-
4f16
-
8ad5
-
c014e2514a59.doc



Version

History

Version management of the document is addressed within this section of the document. On initial creation, the
document is labeled with the version 0.01. Once the informatio
n in the draft document has been baselined, then
the document will be released as version 1.00. Further changes to the document will be addressed through the use
of 1/100 fractional (0.01) version labeling. Before a document can be released, it must be r
eviewed and approved
and once approved, will be labeled with a version value of the next whole number.

NOTE:
No changes to the
document will be allowed when the document is pending approval.


VERSION
NUMBER

REVISION
DATE

AUTHOR

APPROVED BY

SUMMARY OF CHAN
GE

0.01

2/06/10

Jonathan Meek


Initial version

0.02

2/13/10

Ken Anderson


Integration of Jonathan’s project description into the
SPMP. Additional updates to the document include
formatting, information about the project constraints,
and an appendix.

0.
03

02/14/10

Jonathan Meek


Section 4.1 & 4.2 drawings were re
-
done and
corrected.

0.04

02/18/10

Jonathan Meek


Updated the 5.2 section with task matrix and
drawings

0.05

02/23/10

Jonathan Meek


Updated the 5.2 section with additional
requirements and ad
dition of approval column in
Version History

0.06

2/27/10

Ken Anderson


Additional changes made to address the client’s
suggestions.

0.07

02/28/10

Jonathan Meek


Corrected internal structure section and the task
matrix along with the drawings for the tas
k matrix

1

02/28/10

Jonathan Meek


Version 0.07 approved by Clinton A. Lowe

1.01

03/14/10

Jonathan Meek


Corrected internal structure section and added due
dates to the task matrix

1.02

03/27/10

Jonathan Meek


Corrected due dates for phase 1

1.03

04/18
/10

Jonathan Meek


Corrected an issue with the task matrix diagram

1.04

04/18/10

Jonathan Meek


Imported document onto new template

1.05

04/19/10

Jonathan Meek


Re
-
created the table of contents

NOTE:
No changes to the document will be allowed when the
document is pending approval.


DRAFT

GGDA
-
Siege Expansion Project
-
Software Project Management

Version: 1.04

Last printed
12/4/2013 5:40 PM


Page
3

of
21


Filename:
plumpbustling_6a6e77a9
-
0f41
-
4f16
-
8ad5
-
c014e2514a59.doc


Table of Contents


1

Overview

................................
................................
................................
................................
................................
...

5

1.1

Project Summary

................................
................................
................................
................................
........................

5

1.1.1

Purpose, scope, and objectives

................................
................................
................................
................................
..

5

1.1.2

Assumptions
and constraints

................................
................................
................................
................................
......

5

1.1.3

Project deliverables

................................
................................
................................
................................
....................

5

1.1.4

Schedule and budget summary

................................
................................
................................
................................
..

6

1.2

Evolution of the plan

................................
................................
................................
................................
...................

7

2

References

................................
................................
................................
................................
................................

7

3

Definitions

................................
................................
................................
................................
................................
.

7

4

Project Organization

................................
................................
................................
................................
................

8

4.1

External Interfaces

................................
................................
................................
................................
......................

8

4.2

Internal Structure

................................
................................
................................
................................
........................

8

4.3

Roles and responsibi
lities

................................
................................
................................
................................
.........

10

5

Managerial process plans

................................
................................
................................
................................
......

11

5.1

Start
-
up Plan
................................
................................
................................
................................
.............................

11

5.1.1

Estimation Plan

................................
................................
................................
................................
.........................

11

5.1.2

Staffing Plan

................................
................................
................................
................................
.............................

11

5.1.3

Resource
-
Acquisition Plan

................................
................................
................................
................................
.......

11

5.1.4

Project Staff Training Plan

................................
................................
................................
................................
........

11

5.2

Work Plan

................................
................................
................................
................................
................................
.

11

5.2.1

Work Activities

................................
................................
................................
................................
..........................

12

5.2.2

Schedule Allo
cation

................................
................................
................................
................................
..................

15

5.2.3

Resource Allocation

................................
................................
................................
................................
..................

17

5.2.4

Budget Allocation

................................
................................
................................
................................
......................

17

5.3

Control Plan

................................
................................
................................
................................
..............................

18

5.3.1

Requirements Control Plan

................................
................................
................................
................................
......

18

5.3.2

Schedule Control Plan

................................
................................
................................
................................
..............

18

5.3.3

Budget Control Plan

................................
................................
................................
................................
.................

18

5.3.4

Quality Control Plan

................................
................................
................................
................................
..................

18

5.3.4.1

Input Quality Control Plan

................................
................................
................................
................................
......
18

5.3.4.2

Interpretation Quality Control Plan

................................
................................
................................
.........................
18

5.3.4.3

Presentation Quality Control Plan

................................
................................
................................
...........................
18

5.3.4.4

Installation Quality Control Plan

................................
................................
................................
.............................
18

5.3.5

Reporting Plan

................................
................................
................................
................................
..........................

19

5.3.6

Metric Collection Plan

................................
................................
................................
................................
...............

19

5.4

Risk Management Plan

................................
................................
................................
................................
............

19

5.5

Closeout Plan

................................
................................
................................
................................
...........................

19

6

Technical Process Plan

................................
................................
................................
................................
.........

19

6.1

Process Model

................................
................................
................................
................................
..........................

19

6.2

Methods, Tools, and Techniques

................................
................................
................................
..............................

19

6.3

Infrastructure Plan

................................
................................
................................
................................
....................

19

6.4

Product Acceptance Plan

................................
................................
................................
................................
.........

19

7

Supporting P
rocess Plan

................................
................................
................................
................................
.......

20

7.1

Configuration Management Plan

................................
................................
................................
..............................

20

7.2

Verification and Validation Plan

................................
................................
................................
................................

20

7.3

Documentation Plan

................................
................................
................................
................................
.................

20

7.4

Quality Assura
nce Plan

................................
................................
................................
................................
............

20

7.5

Reviews and Audits

................................
................................
................................
................................
..................

20

7.6

Problem Resolution Plan

................................
................................
................................
................................
..........

20

7.7

Subcontractor Management Plan

................................
................................
................................
.............................

20

7.8

Process Improvement Plan
................................
................................
................................
................................
.......

21


DRAFT

GGDA
-
Siege Expansion Project
-
Software Project Managemen
t

Version: 1.04

Last printed
12/4/2013 5:40 PM


Page
4

of
21


Filename:
plumpbustling_6a6e77a9
-
0f41
-
4f16
-
8ad5
-
c014e2514a59.doc

8

Additional Plans

................................
................................
................................
................................
.....................

21

9

Appendix

................................
................................
................................
................................
................................
.

21

9.1

Document Template

................................
................................
................................
................................
.................

21




DRAFT

GGDA
-
Siege Expansion Project
-
Software Project Management

Version: 1.04

Last printed
12/4/2013 5:40 PM


Page
5

of
21


Filename:
plumpbustling_6a6e77a9
-
0f41
-
4f16
-
8ad5
-
c014e2514a59.doc


1

Overview

The purpose of this project management plan is to specify h
ow the resources of the team members as well as
resources provided by SPSU and/or Georgia Game Developer’s Association (GGDA) will be used throughout the
duration of the project. The expansion project entails expanding the current features and capabilitie
s of the GGDA
and SIEGE sites, by improving upon the user management for the GGDA site and implementing the presentation,
event, and speaker management capabilities for the SIEGE site. Currently the latter items do not exist within
SIEGE and must be desig
ned and developed.

This project assumes the team has full administrative access to a development environment of the website as well
as approval from the client will be done in a reasonable manner. The project will be constrained by a time deadline
of Apr
il 28
th
, 2010 as well as the technical limitations of the hardware of the development environment.



1.1

Project Summary

The project’s summary is detailed in the following subsections.

1.1.1

Purpose, scope, and objectives

The GGDA
-
SIEGE expansion project is designed

to create better collaboration between registered users of both
respected sites through improvements in user, event, presentation, and speaker management. User management
currently exists on the GGDA site, but lacks the full functionality that the client

expects. Presentation, event, and
speaker management are desired features for the SIEGE site, but do not currently exist. In addition, a bridging
mechanism, in the form of speaker management, must be developed to allow an authorized member of SIEGE to
s
elect from a list of available speakers.

1.1.2

Assumptions and constraints

The following items are project constraints that may impact the project’s development:



Development must be done using the following software components

o

Joomla

o

CiviCRM

o

ccBoard

o

VirtueMart



P
HP & MySQL must be used if additional functionality is required beyond the capabilities of Joomla and its
many extensions.



The hardware is managed by the service provider Peak10.

o

John Scott, the contact at Peak10, may only be addressed through Mr. Clinton
Lowe.

The following items are assumptions that may impact the project:



The hardware and development environment will be partially available February 26
th
, 2009.



Other aspects of the system such as PHP & MySQL administration will be available shortly.

1.1.3

Proje
ct deliverables

The project deliverables may be provided individually or as a group. If a project deliverable is to be provided
individually, it shall be provided as material for specific stakeholders to review and approve before further
documentation can

be provided. Additionally, due to the agile methodology approach, documents should be
supplied with completed, but may only address a limited scope of the client’s requirements.


DRAFT

GGDA
-
Siege Expansion Project
-
Software Project Management

Version: 1.04

Last printed
12/4/2013 5:40 PM


Page
6

of
21


Filename:
plumpbustling_6a6e77a9
-
0f41
-
4f16
-
8ad5
-
c014e2514a59.doc

The following stakeholders will be involved in either receiving or reviewing

the noted deliverables.



Professor Brianna Morrison



Dr. Jon Preston



Mr. Clinton Lowe



Mr. Andrew Greenberg



IAB (Industry Advisory Board)


Only as members of a capstone review board.

Furthermore, the following deliverables will be provided to the listed st
akeholders:



Software Requirements Specification



Software Design Specification



Source code.

o

Additional plug
-
ins for Joomla to extend its functionality.

o

Any custom developed plug
-
ins for Joomla to extend functionality not available.

o

Database scripts used to
restore custom items created through the Joomla operating system, and
any of its associative plug
-
ins.



Verification and Validation Documentation.



User Documentation


Note this may be encapsulated within the GGDA & Siege sites.

1.1.4

Schedule and budget summary

The budgetary needs of the project shall be addressed by GGDA on a case by case basis, with the current and any
future developments that may arise with this project. The team members of Initech

1
work on a volunteer basis
through SPSU but provided an estim
ated value of $9600. Please refer to section 5.1 for further details on the
estimated value.

With this project there is a scheduled completion date of April 28
th
, 2010 and milestones that will be met throughout
the course of the project. Detailed informa
tion about the deliverables and the individual stakeholders receiving the
deliverables can be found in section 1.1.3, while the milestones and the target dates of each milestone is shown
below in the milestones table.

Please note that this schedule will be

revised and addressed as the project evolves and the agile methodology is
refined for this project. The scope of each phase is currently undergoing reevaluation.

Milestones

Deliverable

Target Date

Recipient

Software Project Management Plan
(Submission f
or final
approval)

2/28/2010

Mr. Clinton Lowe

Software Project Management Plan
(Initial Plan)

(Approved by Mr. Lowe)

2/28/2010

Professor Briana Morrison

Progress Report & Artifacts due.

(Artifacts to be delivered have not been disclosed at this time)

3/2
8/2010

Professor Briana Morrison

Progress Report & Artifacts due.

(Artifacts to be delivered have not been disclosed at this time)

4/11/2010

Professor Briana Morrison

Software Project Management Plan
(Final Revision)

4/30/2010

Professor Briana Morrison




1

Initech is a fictit
ious organizational name adopted by the Southern Polytechnic State University Capstone team for this project.


DRAFT

GGDA
-
Siege Expansion Project
-
Software Project Management

Version: 1.04

Last printed
12/4/2013 5:40 PM


Page
7

of
21


Filename:
plumpbustling_6a6e77a9
-
0f41
-
4f16
-
8ad5
-
c014e2514a59.doc

Software Requirements Specification
(
Final Revision)

Software Design Specification

(Final Revision)

Source Code
(Review section 1.1.3 for more details)

Verification and Validation Documentation

(Final
Revision)

User Documentation
(Final Revision)

IAB

Mr. Cl
inton Lowe

Dr. Jon Preston

1.2

Evolution of the plan

This project adheres to the agile methodology, where all artifacts within this project, including this document, are
updated to reflect the constantly changing development effort in response to time restrai
nts, developmental
environmental delays, and discovery of requirement complexity. Please note that each artifact will evolve further as
the software development lifecycle is addressed and the process is refined to meet the needs of this project.

2

Reference
s

This standard shall be used in conjunction with the following publication. When the following standard is
superseded by an approved revision, the revision shall apply.

IEEE Std 1058
-
1998, IEEE Software Requirements Specification.
2

GGDA
-
Siege Expansion Pr
oject
-
SRS.
3

3

Definitions

This section defines a series of definitions that are used within the context of this document.

CiviCrm:

CivicCRM is a constituent relationship management system, and is used to manage the various users
and sponsors within the GGDA
& SIEGE; it extends Joomla.

ccB
oard
: ccBoard is a forum management system that is used within the GGDA, and extends Joomla.

GGDA
: Georgia Game Developer’s Association is one of the client’s main sites, providing collaboration for local
game development com
panies.

IAB
: The Industry Advisory Board helps to maintain Southern Polytechnic State University’s accreditation.

Initech
:

is a fictitious organizational name adopted by the Southern Polytechnic State University Capstone team for
this project.

Joomla
: Joom
la is a content manager system, used for building dynamic websites simply and easily. Both the
GGDA & SIEGE sites are built on top of this software.

SDL
: Software Development Lifecycle.

SIEGE
: Southern Interactive Entertainment & Game Expo is another site

belonging to the client that provides
detailed information about yearly convention.

SPSU
: Southern Polytechnic State University is the university providing and sponsoring this capstone project.

VirtualMart
: Virtualmart is an open source e
-
commerce solutio
n that extents Joomla.




2

IEEE formats are available from the Institute of Electrical and Electronics Engineers website http://www.ieee.org/

3

Please refer to the latest
version of this SRS.


DRAFT

GGDA
-
Siege Expansion Project
-
Software Project Management

Version: 1.04

Last printed
12/4/2013 5:40 PM


Page
8

of
21


Filename:
plumpbustling_6a6e77a9
-
0f41
-
4f16
-
8ad5
-
c014e2514a59.doc

4

Project Organization

4.1

External Interfaces

This project is setup for coordination through Initech, GGDA, and Southern Polytechnic State University. Diagramed
below is how the coordination will work for the project. In addition to the
diagram is a table detailing the contact
information of the individuals external to the project.

External Contacts

Name

Phone

Email

Ken Anderson

770
-
910
-
0588

kanders4@spsu.edu

Mr. Clinton Lowe

770
-
313
-
3332

Clinton.lowe@ggda.org

Dr. Jon Preston

678
-
915
-
4
982

jpreston@spsu.edu

Professor Briana Morrison

678
-
915
-
4295

bmorriso@spsu.edu


External Interface Diagram


4.2

Internal Structure

With this project, all decisions will be decided as a group internally. The structure is subject to change depending
on the s
ituation facing the group; however, the external contact to the external interface will not unless through
some unforeseen circumstance. The team structure and contacts are detailed below.

Internal Contacts

Name

Phone

Email

Jonathan Meek

678
-
439
-
6335

jmeek@spsu.edu

lemuelmeek@gmail.com

Bates Westmoreland

706
-
280
-
9063

rwestmor@spsu.edu


DRAFT

GGDA
-
Siege Expansion Project
-
Software Project Management

Version: 1.04

Last printed
12/4/2013 5:40 PM


Page
9

of
21


Filename:
plumpbustling_6a6e77a9
-
0f41
-
4f16
-
8ad5
-
c014e2514a59.doc

Ken Anderson

770
-
910
-
0588

kanders4@spsu.edu

kda30@comcast.net

Michael Smith

678
-
644
-
4127

Lanceleonheart@gmail.com

msmith29@spsu.edu


Internal Team Structure
















DRAFT

GGDA
-
Siege Expansion Project
-
Software Project Management

Version: 1.04

Last printed
12/4/2013 5:40 PM


Page
10

of
21


Filename:
plumpbustling_6a6e77a9
-
0f41
-
4f16
-
8ad5
-
c014e2514a59.doc


4.3

Roles and responsibilities

The roles and responsibilities of the team members are defined within this section. Due to the nature of the project,
and the small team size, each individual may take on multiple roles, or change roles as needed to complete a
n area
of the project. While team members may deviate from their listed roles, the responsibilities listed below will remain
their primary concern.


Anderson, Ken



Developer (Primary)



Documentation (Primary)



Client / Sponsor Communication (Primary)


Meek,

Jonathan



Developer (Primary)



Documentation (Primary)


Smith, Michael



Developer (Primary)



Documentation (Secondary)


DRAFT

GGDA
-
Siege Expansion Project
-
Softwa
re Project Management

Version: 1.04

Last printed
12/4/2013 5:40 PM


Page
11

of
21


Filename:
plumpbustling_6a6e77a9
-
0f41
-
4f16
-
8ad5
-
c014e2514a59.doc



Client / Sponsor Communication (Secondary)



Joomla Expert (Primary)


Westmoreland, Bates



Developer (Primary)



Documentation (Secondary)



Wee
kly Reporting (Primary)



Blog Administrator (Primary)


5

Managerial process plans

5.1

Start
-
up Plan

5.1.1

Estimation Plan

The budgetary needs of the project shall be addressed by GGDA on a case by case basis, where the total cost is
estimated at about $9600. It is ass
umed that the team members of Initech will provide at least 32 man hours per
week, for a duration of 3 man months, providing a total of 384 man hours. While each member is volunteering his
time to the project, the rate of compensation is determined to be
$25 per hour. This estimated value does not
include the additional cost and effort of external members, such as John Scott from Peak10 or Mr. Clinton Lowe.

The resource costs are estimated by the experiences of Initech and the timeline the team has to com
plete the
project. As a rule of thumb, there will be at least 2 weeks spent on each phase of the project. At the weekly
meetings, the estimations will be reviewed by Initech and adjustments will be made if needed.

5.1.2

Staffing Plan

The Initech team was pred
etermined by Southern Polytechnic State University Computer Science Capstone based
on each individual’s work history, scheduling, and experience with specific technologies.

5.1.3

Resource
-
Acquisition Plan

The primary way of resource acquisition will be done thro
ugh the client, Mr. Clinton A. Lowe. All acquisitions will be
submitted via email where the Initech team will be carbon copied as to be kept aware of the request. The request
will contain the reason for the resource along with how it will be used.

5.1.4

Project
Staff Training Plan

Training shall consist of a group of at least three people from the client and it will be conducted by members of the
documentation team. The documentation team will be responsible for providing Quick Reference Cards for future
referenc
e along with a PowerPoint that explain the project. Entry to the training will be on the client’s need to
maintain the additions to the website done by the project. Consulting may be done after the project’s completion but
at the discretion of the team mem
bers being consulted.

5.2

Work Plan




DRAFT

GGDA
-
Siege Expansion Project
-
Software Project Management

Version: 1.04

Last printed
12/4/2013 5:40 PM


Page
12

of
21


Filename:
plumpbustling_6a6e77a9
-
0f41
-
4f16
-
8ad5
-
c014e2514a59.doc

5.2.1

Work Activities

Task Number

Task

Due Date

Dependency

T1

View/Edit User Profile
Requirement Analysis

02/28/10

None

T2

View/Edit User Profile
Requirement Approval

02/28/10

T1

T3

View/Edit User Profile
Requirement Design

04/01/10

T2

T4

View/Edit User Profile
Requirement Implementation

04/08/10

T3

T5

View/Edit User Profile
Requirement Testing

04/15/10

T4

T6

User Profile History
Requirement Analysis

02/28/10

None

T7

User Profile History
Requirement Approval

02/28/10

T6

T8

User Profile History
Requirement Design

04/01/10

T7

T9

User Profile History
Requirement Implementation

04/08/10

T8

T10

User Profile History
Requirement Testing

04/15/10

T9

T11

User Interest & Skills
Requirement Analysis

02/28/10

None

T12

User In
terest & Skills
Requirement Approval

02/28/10

T11

T13

User Interest & Skills
Requirement Design

04/01/10

T12

T14

User Interest & Skills
Requirement Implementation

04/08/10

T13

T15

User Interest & Skills
Requirement Testing

04/15/10

T14

T16

View/Print
User List
Requirement Analysis

02/28/10

None

T17

View/Print User List
Requirement Approval

02/28/10

T16

T18

View/Print User List
Requirement Design

04/01/10

T17

T19

View/Print User List
Requirement Implementation

04/08/10

T18

T20

View/Print User List
Requirement Testing

04/15/10

T19

T21

Create Presentation
Requirement Analysis

02/28/10

None


DRAFT

GGDA
-
Siege Expansion Project
-
Software Project Management

Version: 1.04

Last printed
12/4/2013 5:40 PM


Page
13

of
21


Filename:
plumpbustling_6a6e77a9
-
0f41
-
4f16
-
8ad5
-
c014e2514a59.doc

T22

Create Presentation
Requirement Approval

02/28/10

T21

T23

Create Presentation
Requirement Design

03/30/10

T22

T24

Create Presentation
Requirement Implementa
tion

04/05/10

T23

T25

Create Presentation
Requirement Testing

04/08/10

T24

T26

Remind Speakers
Requirement Analysis

02/28/10

None

T27

Remind Speakers
Requirement Approval

02/28/10

T26

T28

Remind Speakers
Requirement Design

03/30/10

T27

T29

Remind Spea
kers
Requirement Implementation

04/05/10

T28

T30

Remind Speakers
Requirement Testing

04/08/10

T29

T31

Rate Presentation
Requirement Analysis

02/28/10

None

T32

Rate Presentation
Requirement Approval

02/28/10

T31

T33

Rate Presentation
Requirement Desig
n

03/30/10

T32

T34

Rate Presentation
Requirement
Implementation

04/05/10

T33

T35

Rate Presentation
Requirement Testing

04/08/10

T34

T36

Create Event Requirement
Analysis

02/28/10

None

T37

Create Event Requirement
Approval

02/28/10

T36

T38

Create Ev
ent Requirement
Design

04/13/10

T37

T39

Create Event Requirement
Implementation

04/19/10

T38

T40

Create Event Requirement
Testing

04/22/10

T39

T41

Create Event Tickets
Requirement Analysis

02/28/10

None

T42

Create Event Tickets
Requirement Approval

02/28/10

T41

T43

Create Event Tickets
Requirement Design

04/13/10

T42


DRAFT

GGDA
-
Siege Expansion Project
-
Software Project Management

Version: 1.04

Last printed
12/4/2013 5:40 PM


Page
14

of
21


Filename:
plumpbustling_6a6e77a9
-
0f41
-
4f16
-
8ad5
-
c014e2514a59.doc

T44

Create Event Tickets
Requirement Implementation

04/19/10

T43

T45

Create Event Ticket
Requirement Testing

04/22/10

T44

T46

Event Archival Requirement
Analysis

02/28/10

None

T47

Event Archival Requirement
Approval

02/28/10

T46

T48

Event Archival Requirement
Design

04/13/10

T47

T49

Event Archival Requirement
Implementation

04/19/10

T48

T50

Event Archival Requirement
Testing

04/22/10

T49

T51

Pool Speakers Requirement
Analysis

02/28/10

None

T52

Pool Speakers Requirement
Approval

02/28/10

T51

T53

Pool Speakers Requirement
Design

04/13/10

T52

T54

Pool Speakers Requirement
Implementation

04/19/10

T53

T55

Pool Speakers Requirement
Testing

04/22/10

T54

T56

Promote Event Requir
ement
Analysis

02/28/10

None

T57

Promote Event Requirement
Approval

02/28/10

T56

T58

Promote Event Requirement
Design

04/13/10

T57

T59

Promote Event Requirement
Implementation

04/19/10

T58

T60

Promote Event Requirement
Testing

04/22/10

T59

T61

View/P
rint Speaker
Requirement Analysis

02/28/10

None

T62

View/Print Speaker
Requirement Approval

02/28/10

T61

T63

View/Print Speaker
Requirement Design

04/13/10

T62

T64

View/Print Speaker
Requirement Implementation

04/19/10

T63

T65

View/Print Speaker
Requ
irement Testing

04/22/10

T64


DRAFT

GGDA
-
Siege Expansion Project
-
Software Project Management

Version: 1.04

Last printed
12/4/2013 5:40 PM


Page
15

of
21


Filename:
plumpbustling_6a6e77a9
-
0f41
-
4f16
-
8ad5
-
c014e2514a59.doc

T66

View/Print Presentations
Requirement Approval

02/28/10

None

T67

View/Print Presentations
Requirement Analysis

02/28/10

T66

T68

View/Print Presentations
Requirement Design

04/13/10

T67

T69

View/Print Presentations
Requir
ement Implementation

04/19/10

T68

T70

View/Print Presentations
Requirement Testing

04/22/10

None

T71

Press Invitation Requirement
Approval

02/28/10

T70

T72

Press Invitation Requirement
Analysis

02/28/10

T71

T73

Press Invitation Requirement
Design

04/
24/10

T72

T74

Press Invitation Requirement
Implementation

04/26/10

T73

T75

Press Invitation Requirement
Testing

04/29/10

T74

T76

Volunteer Invitation
Requirement Analysis

02/28/10

None

T77

Volunteer Invitation
Requirement Approval

02/28/10

T76

T78

Vo
lunteer Invitation
Requirement Design

04/24/10

T77

T79

Volunteer Invitation
Requirement Implementation

04/26/10

T78

T80

Volunteer Invitation
Requirement Testing

04/29/10

T79

5.2.2

Schedule Allocation

The Schedule allocation contains the Gantt chart and is bas
ed on the numbering system used in Section 5.2.1
Work activities.


DRAFT

GGDA
-
Siege Expansion Project
-
Software Project Management

Version
: 1.04

Last printed
12/4/2013 5:40 PM


Page
16

of
21


Filename:
plumpbustling_6a6e77a9
-
0f41
-
4f16
-
8ad5
-
c014e2514a59.doc




DRAFT

GGDA
-
Siege Expansion Project
-
Software Project Management

Version: 1.04

Last printed
12/4/2013 5:40 PM


Page
17

of
21


Filename:
plumpbustling_6a6e77a9
-
0f41
-
4f16
-
8ad5
-
c014e2514a59.doc


5.2.3

Resource Allocation

In order for the work to be completed, the team will be involved in a rotating team system where there will be a team
lead that changes based on what phase a certa
in component is in (i.e. Design) List below is how the team will be
organized in a given setting:

Project Phase

Primary Lead

Secondary Lead

Support 1

Support 2

Requirements

Ken Anderson


Michael Smith

Bates Westmoreland

Jonathan Meek

Design

Michael Smi
th

Ken Anderson

Jonathan Meek

Bates Westmoreland

Implementation

Ken Anderson

Michael Smith

Bates Westmoreland

Jonathan Meek

Testing

Jonathan Meek

Bates Westmoreland

Michael Smith

Ken Anderson


The above mentioned table can be changed or moved around to
circumstances that occur with the project or a
person's understanding of a given module. This will be decided as a team with the intention that everyone has a
chance to work on this project and gain an understanding to its internal workings.


5.2.4

Budget Alloc
ation

Budget allocation will be handled by GGDA, which will handle all expenses incurred by the students and faculty.


DRAFT

GGDA
-
Siege Expansion Pr
oject
-
Software Project Management

Version: 1.04

Last printed
12/4/2013 5:40 PM


Page
18

of
21


Filename:
plumpbustling_6a6e77a9
-
0f41
-
4f16
-
8ad5
-
c014e2514a59.doc

5.3

Control Plan

5.3.1

Requirements Control Plan

The requirements will be controlled thru the use of a versioning system where only approved version
s will be a
whole number (ie 4.0) and changes in between will be increased a 1/100 in a version (ie. 4.1). There will be a
facilitator of the requirements who will makes changes to the requirements as new information from Initech,
Southern Polytechnic Sta
te University or GDDA comes forth.

5.3.2

Schedule Control Plan

The schedule is driven by the varying priorities of the tasks detailed in sections 5.2.1 and 5.2.2, which have been
derived from the requirements specified in the SRS. Items with little to no prior
ity will be deferred for
implementation in a future project when time allows.

5.3.3

Budget Control Plan

All budget related aspects of the project are controlled by GGDA. Please refer to sections 1.1.4, 5.1.1, and 5.2.4 for
additional budgeting details.

5.3.4

Quality
Control Plan

Quality control will be done internally through the Quality Assurance team. Quality control will assessed mainly
through usability evaluations, but will address the four levels of quality control.

5.3.4.1

Input Quality Control Plan

Input quality con
trol shall assure that all new data introduced to the system are valid. All inputs shall be uniquely
identified and shall have a defined set of acceptable values. Each field shall be tested for min, max, valid, and
invalid values, types, and sizes.

Integr
ity Level:

4

5.3.4.2

Interpretation Quality Control Plan

Interpretation quality control shall assure that all data entered into or read from the system results in logically
correct usage of the data fields and values. All literal values and prompts displayed to t
he system users shall be
uniquely identified, spell
-
checked, and tested by focus group to assure proper interpretation.

Integrity Level:

2

5.3.4.3

Presentation Quality Control Plan

Presentation Quality Control shall assure that all information displayed to the use
r is consistent with the look, feel,
and style of the client system (website). All information displayed by the system shall use one or more style
guides (e.g.
-

cascading style sheets) to govern visual presentation. Data fields and labels shall also be
oriented,
aligned, and sized to promote logical data flow and groupings. The presentation of fields shall preserve
appropriate tab
-
ordering between fields

Integrity Level:

1

5.3.4.4

Installation Quality Control Plan

Installation Quality Control shall assure that
the resulting product components may be installed successfully and
repeatedly by a non
-
project team member. The non
-
project team member must have no prior knowledge of the
system design or goals and may be provided only with written instructions for guida
nce.

Integrity Level:

4


DRAFT

GGDA
-
Siege Expansion Project
-
Software Project Management

Version: 1.04

Last printed
12/4/2013 5:40 PM


Page
19

of
21


Filename:
plumpbustling_6a6e77a9
-
0f41
-
4f16
-
8ad5
-
c014e2514a59.doc

5.3.5

Reporting Plan

Weekly reports, which include the team’s meeting minutes and task matrix, shall be delivered to Professor Briana
Morrison on a weekly basis, as well as providing updates during mandatory meetings. Additional reportin
g should
be provided to the client, the professor, and other stakeholders when deliverables are due.

5.3.6

Metric Collection Plan

The number of man hours spent on the project shall be detailed by each member of the team and reported with the
weekly meetings.

5.4

Ris
k Management Plan

Personnel availability is the largest risk to the project and should be monitored carefully to determine if tasks cannot
be completed due to the loss of a team member for any reason. The production environment for the GGDA and
SIEGE webs
ites has been safe
-
guarded regardless of the modifications made to the development environment.

5.5

Closeout Plan

At the project’s end, the Initech team will be allowed to pursue other interests since they are working pro
-
bono on
this project. The project mate
rial will be archived electronically per SPSU’s policies. Specific artifiacts such as the
SPMP, SRS, SDS, and V&V will be made available to the team members of Initech; however, items such as the
source code and scripts shall not be released to the team m
embers. The final report will be composed of a
summary from the team members about lessons learned and analysis of the final project.

6

Technical Process Plan

6.1

Process Model

For this project, the team will be using the agile methodology in order to develop t
he software. Agile methodology
requires that requirements, documentation, development, and testing be worked on together thru iterative
processes. More information can be found on www.agilemanifesto.org/principles.html

6.2

Methods, Tools, and Techniques

The t
ools used throughout this project are detailed below:



IEEE Standards such as std 1058
-
1998, std 1012
-
1998, std 830
-
1998.



Microsoft Word 2003
-
2007.



Dia version 0.97.1
-
1 for Windows (http://dia
-
installer.de/index_en.html)



GoogleWave (http://wave.google.com)



BeanStalk (http://beanstalkapp.com/)

6.3

Infrastructure Plan

The development environment will be provided by the client through their technical resource. The client’s technical
resource will be responsible for the maintenance and upkeep of this environment. A
part of the development may
occur on a team member’s personal machine or resources provided by Southern Polytechnic State University. Any
work that occurs outside of the development environment will be backed up a secondary source in case of a
hardware fai
lure or system failure.

6.4

Product Acceptance Plan

The product acceptance plan shall consist of an Acceptance Test which maps each system feature identified by the
Product Concept Document to the final System User Documentation. The client shall use the Sys
tem User

DRAFT

GGDA
-
Siege Expansion Project
-
Software Project Management

Version: 1.04

Last printed
12/4/2013 5:40 PM


Page
20

of
21


Filename:
plumpbustling_6a6e77a9
-
0f41
-
4f16
-
8ad5
-
c014e2514a59.doc

Documentation to exercise the desired features of the system. The Acceptance Test Plan shall include a line
-
by
-
line checklist which may initialed by the client to express acceptance.

7

Supporting Process Plan

7.1

Configuration Management Plan

Migration

from environments is handled by John Scott at Peak10, since the members of Initech do not have access
to this aspect of the system. Once a phase of development has been completed, which includes verification and
validation testing of the item, the client

shall review the component to confirm that it does not disrupt normal system
operation of the GGDA or SIEGE websites. The component should be deployed to production after client approval.

Project items, such as source and document, will be managed by a s
ource control web
-
application called
Beanstalk. These items will be protected against concurrent modification by locking an instance of that item until
the team member holding the item returns it to source code via check
-
in. Beanstalk will also maintain
an archive of
items for necessary recovery.

7.2

Verification and Validation Plan

With this project, the team will be doing unit and system testing through the development process. Quality Control
will handle the unit testing while Quality Assurance will handle

the system testing. All documents pertaining to
documentation and planning will be reviewed by an external party. Documents not to be include are ones of internal
team communication. .

7.3

Documentation Plan

Documentations will be generated and maintained by

the documentation team within Initech. Documentation will
have version control to them and be backed up by placing them in a off
-
site resource such as BeanStalk or Google
Wave. The version control will consist of a numbering scheme that works in this mann
er:



Approved, signed versions of the document will designated by a whole number (ie. 4.0)



Unapproved versions of the document will be designated by a 1/100
th

suffix (ie. 4.01)

7.4

Quality Assurance Plan

Quality assurance will be done internally through the Q
uality Assurance team. The use of unit testing along with
system testing will be used and the results of the testing will be reviewed. The testing will be conducted by the
quality assurance team as new items are developed within the program.

7.5

Reviews and

Audits

Throughout the project, the team will be conducting personal and mutual evaluations that will be submitted to
Professor Morrison. These are to see how much a team member is contributing to the project in their own eyes as
well as the eyes of their
peers. Also, all documentation and project deliverables is subject to approval by the client
or their designated person.

7.6

Problem Resolution Plan

Conflicts that arise amongst team members shall be resolved by fellow team members. If the conflict cannot b
e
resolved internally, an external resource, such as Professor Morrison shall act as a mediator to resolve the issue. If
a conflict resolution is not possible, extreme measures may be taken that result in the loss of a team member.

7.7

Subcontractor Managemen
t Plan

Subcontractors will not be used in this project and therefore no subcontract management is required.


DRAFT

GGDA
-
Siege Expansion Project
-
Software Project Management

Version: 1.04

Last printed
12/4/2013 5:40 PM


Page
21

of
21


Filename:
plumpbustling_6a6e77a9
-
0f41
-
4f16
-
8ad5
-
c014e2514a59.doc

7.8

Process Improvement Plan

Process improvement will be addressed by GGDA post
-
product deployment. In addition, the lessons learned will
be reviewed a
nd discuss to determine possible improvement.

8

Additional Plans

There are none at this current point in time.

9

Appendix

9.1

Document Template

This document template was provided by Dr. Abi Salimi from Southern Polytechnic State University.