Project: {Project Name}

snailyakSecurity

Nov 5, 2013 (3 years and 5 months ago)

56 views







Project:

{
Project Name
}

{Team
Member
1
-
Team member2
}

CSE 5325/4322



Spring 2013


Module:

Project
Plan

Deliverable:

Project Plan
Document


Version:

[1.0]

Date:

[mm/dd/yyyy]









i

Prepared by
:

{
Contributors list
}



Revision History

Version
number


Date

Originator

Reason for
change

High level description of
changes

1.0

mm/dd/yyyy

Name(s)

Initial draft





















Distribution
List



Recipient Name

Recipient Title

Reception
Date




















Approval Information



Approver Name

Approver Signature

Approval
Date























ii

TABLE OF CONTENTS

1.
EXECUTIVE SUMMARY

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

5

2. PROJECT ACRONYMS

AND GLOSSARY OF TERM
S

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

6

3. PROJECT ORGANIZA
TION

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

7

3.1 Organizational Structure

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

7

3.2 Roles and Responsibilities

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

7

3.3 Staffing Plan

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

7

3.4 Communication Plan

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

7

4. MANAGEMENT PROCE
SS

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

8

4.1 Pr
oject Phases

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

8

4.2 Project Assumptions

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

8

4.3 Project Dependencies

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

8

4.4 Project Constraints

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

8

5. RI
SK MANAGEMENT

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

9

5.1 Project Monitoring and Control

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

9

5.2 Project Risks

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

9

5.3 Risks Contingency and Mitigation

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

9

5.4 Escalation Procedure

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

9

6. TECHNICAL PROCES
S

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

10

6.1 Architecture Plan

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

10

6.2 Required Software and Development Tools

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

10

6.3 Required Hardware

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

10

6.4 Required Security Tools and Algorithms

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

10

6.5 Web Technology

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

10

7. PROJECT COST
PLANNING

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

11

7.1 Hardware Cost

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

11

7.2 Commercial Off
-
the
-
Shelf (COTS) Component Cost

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

11

7.3 COCOMO Software Cost Estimation

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

11

7.4 Overhead Cost

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

11

7.5 Total Cost

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

11

8. PROJECT SC
HEDULE

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

12

9. PROJECT SUCCESS
CRITERIA

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

13




iii

9.1 Project Milestones

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

13

9.2 Acceptance Criteria

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

13

9.3
Success Metrics

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

13

9.4 Client Approval Process

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

13

10. PROJECT PROCURE
MENT PLAN

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

14

11. PROJECT DEVELOP
MENT PLAN

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

15

11.1 Development Environment

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

15

11.2 Tasks and Deliverables

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

15

11.3 Configuration Management

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

15

12. PROJECT TEST ST
RATEGY

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

16

12.1 Unit Testing

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

16

12.2 Syste
m Integration Testing

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

16

12.3 Stress Testing

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

16

12.4 Performance Testing

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

16

12.5 Data Validation Testing

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

16

12.6 User Acceptance Testing

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

16

13. PROJECT DEPLOYM
ENT AND ROLLOUT PLAN

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

17

13.1 Delivery Date

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

17

13.2 Delivery Method

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

17

13.3 Pen
alty for Late Delivery

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

17

14. PROJECT TRAININ
G PLAN

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

18

14.1 User Manual

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

18

14.2 Client Onsite Training

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

18

15. PROJECT MAINTEN
ANCE AND SUPPORT PLA
N

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

19

15.1 Data Maintenance

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

19

15.2 Fixing Bugs After Release

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

19

15.3 Change Operating Environment

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

19

15.4 Adding New Functionality
................................
................................
................................
...

19

16. POST PROJECT IS
SUES

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

20

16.1 Project Artifact Ownership
................................
................................
................................
..

20

16.2 Quality Assurance

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

20

16.3 F
uture Releases

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

20

17. GLOSSARY OF TER
MS

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

21




iv

APPENDICES
................................
................................
................................
.....

22






5

1.
Executive Summary


{
Provide a
high
-
level
overview of the project that includes the following:



Project high
-
level description



Project deliverables



Client

information



In
-
scope



Out
-
of
-
scope



High
-
level cost and schedule

}










6

2.
Project Acronyms and Glossary of Terms


{
A list of terms and acronyms used in this project}

Customer/Client


The term “Customer” or “Client” are used interchangeably
throughout this

document to refer to our client

Cost


Cost is in US $








7

3
.
Project Organization


3
.1

O
RGANIZATIONAL
S
TRUCTURE

{Provide a brief history of the organization and why you are qualified to handle this project.
Include all relevant information suc
h as
development philosophy, e.
g. conventional
development or agile, if agile what type (XP
or Scrum
), management style (i.e.
hierarchical,

matrix, etc.), if the company is public (if so, provide ticker symbol under which the company
trades on the stock market)

or private, plus any other relevant information.}





3
.2

R
OLES AND
R
ESPONSIBILITIES

{List all team members, for each
member;

list their qualifications, the years working for your
organization, technical skills and other relevant qualifications}





3.3

S
TAFFING
P
LAN

{Specify any additional personnel that you need
to complement your current staff, listed
above, to conduct the project.
}






3.4

C
OMMUNICATION
P
LAN

{What is the primary means for communication in this project? For information passing, error
reporting, etc.}






8

4
.

Management Process


4
.1

P
ROJECT
P
HASES

{
I
s project delivered in one phase or multiple phases? If multiple phases, what is included in
each phase.}








4.2

P
ROJECT
A
SSUMPTIONS

{Includes all
assumptions
}






4
.3

P
ROJECT
D
EPENDENCIES

{Includes all
project dependencies
}






4.4

P
ROJECT
C
ONSTRAINTS

{Includes all
constraints
}










9

5
.

Risk Management


5
.1

P
ROJECT
M
ONITORING AND
C
ONTROL

{
What monitoring measures do you have in place to
monitor and control
all risks to the
project?
}










5.2

P
ROJECT
R
ISKS

{
I
dentify and assess
all risks
associated with the
project
}







5.3

R
ISKS
C
ONTINGENCY AND
M
ITIGATION

{For each risk identified, what is the mitigation? i.e. what do you
do
to remedy the risk if it
happens?}





5.4

E
SCALATION
P
ROCEDURE

{What is the escalation procedure to report problems and risk

concern
s?}









10

6
.
Technical Process


6.1

A
RCHITECTURE
P
LAN

{
Description of the high
-
level architectural plan,
e.g. agile vs. conventional

development
methodology: waterfall,
incremental, etc.
}






6.2

R
EQUIRED
S
OFTWARE
AND
D
EVELOPMENT
T
OOLS

{
R
equired external software and
CASE
packages, e.g. databases,
data dictionary,
query
generator, configuration management tools;

etc.
}




6.3

R
EQUIRED
H
ARDWARE

{The
list of required hardwa
re
}





6.4

R
EQUIRED
S
ECURITY

T
OOLS AND
A
LGORITHMS


{
Required
Security and related software purchases
}





6.5

W
EB
T
ECHNOLOGY


{
W
eb
technologies
; web

development environment such as

ASP,
PHP,

web
hosting, etc.}








11

7. Project Cost Planning


7.1

H
ARDWARE
C
OST

{
Hardware cost,

a detailed list including price competition from different vendors}






7.2

C
OMMERCIAL
O
FF
-
THE
-
S
HELF
(COTS)

C
OMPONENT
C
OST

{Cost of buying support software, a detailed list including price competition from different
vendors}







7.3

COCOMO

S
OFTWARE
C
OST
E
STIMATION

{
Use COCOMO to estimate software development cost using your resources
, refer to
http://ranger.uta.edu/~khalili/Overview%20of%20COCOMO.htm
}





7.4

O
VERHEAD
C
OST

{Consultants, Rents, utility bills, phone cost, etc.
, you may want to abstract some of the
details from your client and just show a certain percentage, say 25%, overhead as an
example
}




7.
5

T
OTAL
C
OST

{
Sum of 7.1, 7.2, 7.3 & 7.4; make sure
to reflect overhead cost and your
profit
}







12

8. Project Schedule


{Detailed delivery schedule

from start to the end when product is delivered to your customer
,
provide
cross reference with
Microsoft Project P
rofessional 2010
}







13

9. Project Success Criteria


9
.1

P
ROJECT
M
ILESTONES

{
List of Milestones from customer’s point of view
}




9.2

A
CCEPTANCE
C
RITERIA

{Customer acceptance criteria for the project}






9
.3

S
UCCESS
M
ETRICS

{
List of success metrics
}




9
.4

C
LIENT
A
PPROVAL
P
ROCESS

{
Identify management
process for obtaining client approval, i.e. what takes to start the
project. Also include any external approvals if required, e.g. government, etc.
}






14

10. Project Procurement Plan


{T
HIS SECTION WILL DES
CRIBE HOW HARDWARE
,

SOFTWARE
,

LICENSE
,

OR ANY COMPONEN
TS
WILL BE PROCURED FOR

THE PROJECT
.

T
HE ITEMS MAY BE PROC
URED BY PURCHASE
,

LEASED
,

OR BORROWED
}







15

11. Project Development Plan


11.1

D
EVELOPMENT
E
NVIRONMENT

{
What is the Programming language and development environment….
}






11.2

T
ASKS AND
D
ELIVERABLES

{
List
of
high
-
level deliverables
;

Provide reference/link
to
Microsoft Project P
rofessional
2010

for task details
. E.g. defining requirements, designing web screens, database tables
and queries, coding, creating test cases and test data
}




11.3

C
ON
FIGURAT
ION
M
ANAGEMENT

{
Where & how to store code and other project artifacts
}







16

12. Project Test Strategy


12.1

U
NIT
T
ESTING

{T
esting strategy by developers

at the module level, e.g. uses test cases, JUnit, etc.
}







12.2

S
YSTEM
I
NTEGRATION
T
ESTING

{
System
level testing strategy
}





12.3

S
TRESS

T
ESTING

{
Test strategy for stressing the system by overloading
}





12.4

P
ERFORMANCE
T
ESTING

{
Test
strategy

to measure performance
}





12.5

D
ATA
V
ALIDATION

T
ESTING

{
Validate all fields for accuracy
}





12.6

U
SER
A
CCEPTANCE
T
ESTING

{T
est

plan
by clients
}







17

13. Project Deployment and Rollout Plan


13.1

D
ELIVERY
D
ATE

{
Expected delivery
date}







13.2

D
ELIVERY
M
ETHOD

{
How is it delivered to the
client?

What is
included?
}





13.3

P
ENALTY FOR
L
ATE
D
ELIVERY

{
What is
penalty for late delivery, typically certain $ amount for each business day that is it
delivered late
}







18

14.
Project Training Plan


14.1

U
SER
M
ANUAL

{
Prepare user manual
}






14.2

C
LIENT
O
NSITE
T
RAINING

{
Training plans to train clients if applicable}










19

15
.
Project Maintenance
and Support
Plan


15.1

D
ATA
M
AINTENANCE

{
Include contractual details for maintaining data, e.g. normalizing, routing backups, securing
access, etc.}





15.
2

F
IXING
B
UGS
A
FTER
R
ELEASE

{Include

error reporting mechanism
}






15.
3

C
HANGE
O
PERATING
E
NVIRONMENT

{
Include contractual details and charge structure for changing operating environments such
as updating new OS, changing hardware, changing web hosting, etc.
}






15.
4

A
DDING
N
EW
F
UNCTIONALITY

{Include contractual details and c
harge structure for adding new functionality}







20

16.
Post Project Issues


16.1

P
ROJECT
A
RTIFACT
O
WNERSHIP

{Does client own project artifacts, e.g. requirements, source code, etc., or the client}








16.2

Q
UALITY
A
SSURANCE

{Agreements that product will
meet client’s expectation after delivery. What are the criteria if it
does or does not
}
?




16.3

F
UTURE
R
ELEASES

{
Contractual details for future commitments of (how long) to support this customer}







21

17. Glossary of Terms


Acceptance Test



Formal
test perf
ormed by the client
prior to accepting the system


Activity

-

A project task that requires resources and time to complete

Web Hosting



….










22

Appendices


{
Additional documents
, web links,
and references that were not included in the sections above
}