Hafsa (The - Best)

CASE
Online Education
System
Project Plan and Initiation
By Hafsa Muhammed B08-006

23-12-10
Contents
1.
Initiation
1.1. Project Charter
.
1.2. Stake holder Register
.
.
.
.
.
.
.
.
.
.
.
.
3
12
2. Planning
1.1. Project integration management
2.1.1. Project Management Plan
14
.
.
.
.
.
.
20
22
2.2 Project Scope Management

2.1.2. Requirement Document.
.
.
2.1.3. Scope Statement
.
.
.
2.1.4. WBS (a separate document attached with)
2.3. Project Time Management
2.3.1. Activity List
.
.
.
2.3.2. Milestone Plan
.
.
.
2.3.3. Project schedule and Network Diagram
2.3.4. Activity resource requirement
.
2.3.6 Critical Tasks
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
25
26
27
28
29
2.4. Project Quality Management

2.4.1. Quality Management Plan .
30
2.5. Project Cost Management

2.5.1. Activity Cost Estimates
2.5.2. Budget Estimate .
.
.
.
.
.
.
.
.
.
.
31
32
2.6. Project Human Resource Management

2.6.1. Human Resource Plan
.
.
2.6.2. Stakeholder Management Plan
.
.
.
.
.
.
.
.
.
33
37
2.7. Project Communication Plan

2.7.1. Communication Plan
38
2.8. Project Risk Management

2.8.1. Risk Register
.
2.8.2. Risk Management Plan
.
.
.
.
.
.
.
.
.
.
.
.
41
42
2.9. Project Procurement Management

2.9.1 Procurement Plan .
.
45
.
.
Project Charter
1. Project Description
This project is made for a C@SE University which wants to conduct online education in
Pakistan. As the idea of online education is getting more popular day by day and is
growing dramatically so the opportunities for such kind of software has increased and
will continue to increase in future.
Main stakeholders of this system are university management, faculty members, students
and Higher Education Commission (HEC) in Pakistan. Present system of C@SE
University is the simple university website and different applications. These systems are
only sufficient for dealing with regular students and potential students. This system
should be secure enough and efficient so that online quizzes and video conferencing
should be done accurately and without delay.
The proposed software product is the Online Education System (OES). The system will
be used to upload, download lectures, in time assignment submission, conducting online
quizzes, student admission, course registration, managing results. Moreover the product
will manage all the record of teachers, courses, exam section, fee section, students and
will be able to search the available record.
The system is recommended to have a unique username and password so that nobody can
misuse it. This system must be right protected and rights of every category of user must
be clearly described so that limits for every user access are defined.
2.
Critical success factors
2.1. Technical
Systemshouldbescalable
Systemshouldhavewelldescribedandcleardocumentationsothatitmay
giveclearidearegardingsystem.
2.2. Business
System should fulfill all requirements specified by the university but
meanwhileitshouldbegeneralenoughfordifferentprojects.
2.3. Quality
Systemshouldbe75%testedbeforeuse.
SystemshouldfollowIEEEstandardsintesting,deployment,configuration
management.
SystemshouldbedevelopedusingtheISO9216qualitystandard.
3.
Success Measurement Criteria:
A project is said to be successful if it is completed on time, within budget, meet the

requirements of stakeholders.
Success Criteria
Recommendation
Completed within Budget
Project should be completed within 0.5
Completed on Time
million budget
Project should be completed within 6
Customer Satisfaction
months
System should be Secure, Efficient, Usable
and Reliable enough to support operations
in an effective manner.
4.
Stakeholders
The main stakeholders that would be benefited by this system the university management
which is providing this facility, the faculty members involved in the online education
program and administrator who is responsible for keep the online education program
active and up to date. The students who may belong all around the world are also major
stakeholders of this system. The Higher Education Commission is also an important

stakeholder as programs as well as course outlines would be finalized by it.
Stakeholder
Major Benefits
Attitudes
Win Conditions
Constraints
University
Earn Revenue
Strongly
Usability,
System should be
Management
by reaching
Supportive
extensibility and
made extensible
more students
Faculty Member ------------------- Neutral
reliability
Performance and
for future purpose.

----------------------
Administrator
Security
Performance
-System should be
------------------- Neutral
--
useable on
minimum of
Students
Able to gain
Strongly
Usability,
512kpbs
System should be
quality
Supportive
efficiency,
easy to use and
performance
operate.
Reliability
The tool should be
education at
HEC
5.
home
Promote
Strongly
Higher
Supportive
developed within
Education in
0.5 million of
Pakistan
budget.
Vision
At present time university is running various programs as full time courses. The students
who can study as full time students can facilitate from these education programs. The
university timings make it difficult to study for students who are doing some jobs or are
unable to attend regular classes due to any other reason. Because of current economic
crisis in the country most of the parents are unable to afford the expenditures of higher
education so many students especially the ones belonging to lower or middle class have
to do jobs. The university timings may not be suitable to such students. The online
education program would help such students and students who are not allowed to attend
university because they live far away and do not have such educational institute in their
area.
Most of the Pakistani youth are deprived of higher education especially with science
subjects as they are living in rural areas or such far off places where universities are not
present and they have to go to other cities which are not possible due our societys
constraints.
All those students which are not able to acquire education due to living in distant areas or
who are unable to attend regular university classes due to their jobs or any other reason
will surely be interested in this sort of learning. This product will strengthen the idea of
distant learning and will promote ease of seeking education.
For
Who
The
Is a
That
Students
Are unable to study as regular students
Online education program
Online solution
Will provide quality education to students
living in rural areas just by connecting via
internet.
The regular programs being offered by
Unlike
C@SE University which can only benefit

regular students.
6.
Project Scope
It is an online system of C@SE University which is made for the purpose of educating
students of rural areas. The In scope features of the system are:
Online registration
Log in
Course evaluation (quizzes)
Assignment submission
Marks lists
Uploading course content
Online lectures
Downloading course content
Video conferencing
The features which are currently out of scope and may be added later on as an extension
to the application are:
Infoservice
Comprehensiveinformationlibrary
7.
Assumptions and Dependencies
It is a web based tool and will be supported by the following web browser.
InternetExplorer
Firefox.
NetscapeNavigator
GoogleChrome
The speed of the system is dependent upon the network speed but a minimum of 512kbps
speed is required for operation.
Rules and regulations regarding grading policy will be provided by university.
8.
Constraints
The system should develop within the 0.5 million budget
grantedbyHEC.
Thesystemshouldbedeployedandoperationwithin6months.
Thesystemshouldbeinteroperatablewiththecurrentsystemof
C@SEUniversity.
9.
Business Risks
Risk
There is a risk of network failure we
Probability
Impact
Mitigation
70%
Severe
We need to maintain session
need experts to handle such errors.
information to save and restart
For data bases we need strong tool to
system from that point.

We need to have backup server
40%
Severe
avoid loss of data.
to avoid this situation.
10. Resources
10.1. Hardware Resources
Allteammemberswillrequirelaptops/systems.
Oneprojectorwillberequiredforconsultancysessionstobrief
theaudience
Oneprinterwillbeusedtoprintthedocumentsandagreements
oftheproject
Scanner maybe requiredfordesigning the interfaces ofthe
system.
Internetconnectionwillberequired.
10.2. Software licenses
Systemshouldbelicensedsothatitshouldnotgetillegally
usedorcopied.ItisownedbyC@SEUniversity.
10.3. Consulting
Three meetings (one with student representative and 2 with
universityrepresentatives)willbeconductedbeforethestartof
project,togatherinformationandonemeetingwithbothtype
of representatives will be conducted after the completion of
eachphaseinordertoensurethatworkisgoingonasrequired
by the stakeholders and one meeting of project team and
related department representatives (finance department,

accountsdepartmentetc)willbearrangedinordertoanalyze
whethertheprojectisgoingwiththesameprogressasplanned
or we need some modifications. In total we will need
approximately10consultationsessions.
10.4. Staffing Requirements:
Aprojectmanagerisrequired.
Onefinancialanalystisrequired.
Weneed2requirementengineersforgatheringrequirements,
oneforgatheringrequirementsfromusersideandsecondfor
gathering requirements from university faculty and other
stakeholders.
Agroupofthreeanalystsisrequiredtoanalyzeandspecifythe
requirements.
We will require 2 designers to plan the architecture of the
project
4membersarerequiredtoworkascoders
2testerswillbehired.
One change configuration manager role is required for
managingchangestosystem.
10.5. External Training Requirements:

Weneedsomeextratrainingforourteammembersasitistheir
firstonlineprojectandtheymustbeequippedwithlatesttools
tocopewiththecurrentchallengesoftechnology.
11. Project Responsibility Matrix:

Activity
Responsible Person
Acquiring Resources
Saima Imtiaz
Assigning and managing resources
Saima Imtiaz
Requirement gathering, specification and

validation
Designing User interface, validating User
interfaces
Design application including database
design
Rabia Malik
Rabila Malik
Saima Imtiaz
Implementation and testing
Samya Kashif
Acceptance testing of the system
Samya Kashif
Rabia Malik and
User Manuals and Help
Samya Kashif
12. Approvals
Approval Decision:
Approved, development of detailed project plan is authorized
Approved, project execution is authorized
Approved, but project is on hold until future notice
Revise charter and resubmit for approval
Charter and project proposal are rejected
Role or Title
Name and Signature
Date
HEC
Mr. Anwar
12th August 2010
President of C@SE
Mr. Hassan Akhtar
12th August 2010
UNIVERSITY
Head of Software
Development
Dr. Ali Ahsan
10th August 2010
Project Manager
Ms. Tahira
10th August 2010
13. Revision History

Name
Date
Reason For Changes
Version
Online Education
12th August
-----------------------------------------------------
1.0
System
2010
-----
Stakeholder Register
Name
Position
Role
Mr. Hassan
Akhtar
President of
C@SE
University
Investor/client
s
Contact
Informatio
n
092-519155556
Requirements
Expectations
Functionality, cost and

schedule of the system
should be according to
the criteria given in
project scope.
He should have
contract so that he
Project should be
done in the given
budget and in the
required timeline.
knows on which
specifications the
system will be
delivered to him.
Dr. Ali Ahsan Head of

Software
Development
Overseeing
authority
092-519155555
Project contract should

be with him so as to
know what
requirements should be
met in which
constraints in order to
deliver the final
project.
should be according to
the criteria given in
project scope.
Project should be
done according to
the specified time
period and results
in profit.
Tahira
Manager
responsible
for online
education
program
092-519155554
Project is done
according to the criteria
mentioned by the
overseeing authority.
Feasibility report,
project charter should
be provided to the
project manager.
Schedule should be
followed accurately
and the required
functionality must
be delivered.
Acquiring
and Managing
Resource
092-519155553
All the non functional

and functional
requirements of the
desired system.
All the resources

needed are properly
acquired and
managed.
System Requirement
Specification document
and software
requirement
specification
documentation are also
required.
All the non functional
and functional
requirements of the
desired system
The design of the

database should
cover all aspects of
requirements.
Project
Manager
Requirement
Engineer
Saima Imtiaz
Data base
Manager
Rabia Malik
Requirement
Engineer
Design
application
including
database
design
Requirement
gathering,
specification
and validation
092-519155552
All the
requirements
should be gathered
with specifications
and should be
validated.
Designing
User interface,
validating
User
interfaces
Complete database is
required.
User Manuals
and Help
Executable code should

be providing to her is
that so she can perform
various tests on it and
implement it.
The user interface

should be designed
according to the
requirements and
should be validated.
Software
Engineer
Tester
Samya
Kashif
Technical
writer
Implementatio
n and
acceptance
testing of the
system
092-519155551
Executable code should

be provide to her so
that she can perform
various tests on it and
validate it.
User Manuals
and Help
Help and guidance

needed for system
is provided
The code executes
properly and no
error is found.
Help and guidance
needed for system
is provided.
Project Management Plan

Product Scope Description:
Pakistan
will be able to search the available record. The system is recommended to have a unique
username and password so that nobody can misuse it. This system must be right protected
and rights of every category of user must be clearly described so that limits for every user
access are defined.
Project Deliverables:
It is an online system which has a a system, a user manual and training material as its deliverables. This system
must perform the following functions:
Online registration
Log in
Marks lists
Online lectures
Video conferencing
The deliverables i.e. The software, user manual and the training material will be delivered to Mr. Hassan Akhtar on
8th of February 2011.
Role:
Investor/
clients
Head of Software
Development
Project
Manager
Responsibility:
To invest in the project
He is part of inception, approves resources for the project, directly oversees the
project business manager, and is responsible for the project meeting the goals of
all stakeholders.
Experienced and objective technical and management oversight from individuals
who are not directly involved in the project
To release the funds to Project Manager at the end of each working period. And
see the performance of the project.
Responsible for successful business outcome of the project. In charge of
project staffing, acquiring resources for the project, personnel issues, toplevel work assignments, and stakeholder interaction.
She is the top decision maker on the project, but normally defers technical
decisions to the appropriate technical lead. Resolves disputes between
project participants. Responsible for coordinating the activities with the
stakeholders, project sponsor, and project reviewers
Requirement
Engineer
Acquiring and Managing Resource

In charge of eliciting, defining, maintaining, and tracing detailed product
requirements.
Data base
Administrator
Design application including database design

Responsible for the system architecture and overseeing design activities.
As appropriate may assign sub-leads for functional areas of the product or
for technical specialties such as database, graphics, driver, distributed
processing, communications protocol, etc.
Requirement
Engineer
Requirement gathering, specification and validation

Requirements.
Software
Engineer
Designing User interface, validating User interfaces

A pool of software engineers that can be assigned various tasks on a project based on
ability and interest
Tester
Design and document test cases, execute test cases, record test case results, document
and track defects, and perform test coverage analysis.
Technical Writers
They document processes and other user manuals, create online courses and product
demonstrations
Staff Acquisition:
Following staff is acquired for our project: Project manager
Financial analyst
Requirement engineers
Configuration manager
Software Engineer
Technical Writer
Computer Programmer
Database Administrator
Database Designer
Database Developer
Functional Manager
Graphic Designer
Project Manager
Report Designer
Report Developer
Requirements Analyst
Software Tester
Support Technician
System Architect
Technical Writer
User Interface Designer
Web Designer
Web Developer
Web Programmer
Web Site Builder
Monitoring and control
Project Assumptions:
Internet Explorer
Firefox.
Netscape Navigator
Google Chrome
Communications:Method
Performance status Reports
Performance Review Meetings
(Presentations)
Presentations
Audience
Team
members
Team leader
Investor
Initiators
Team leader
Frequency
Once A Week
Project
Manager
Project
manager,
team &
head of
department
Once a month
After achieving a milestone or
once in 2 months
Roles and responsibility
Resources
Hardware Resources
All team members will require laptops/systems.
One projector will be required for consultancy sessions to brief

the audience
One printer will be used to print the documents and agreements
of the project
Scanner may be required for designing the interfaces of the
system.
Internet connection will be required.
Software licenses
System should be licensed so that it should not get illegally
used or copied. It is owned by C@SE University.
Consulting
Three meetings (one with student representative and 2 with
university representatives) will be conducted before the start of
project, to gather information and one meeting with both type
of representatives will be conducted after the completion of
each phase in order to ensure that work is going on as required
by the stakeholders and one meeting of project team and
related
department
representatives
(finance
department,
accounts department etc) will be arranged in order to analyze

whether the project is going with the same progress as planned
or we need some modifications. In total we will need
approximately 10 consultation sessions.
Staffing Requirements:
A project manager is required.
One financial analyst is required.
We need 2 requirement engineers for gathering requirements,
one for gathering requirements from user side and second for
gathering requirements from university faculty and other
stakeholders.
A group of three analysts is required to analyze and specify the

requirements.
We will require 2 designers to plan the architecture of the
project
4 members are required to work as coders
2 testers will be hired.
One change configuration manager role is required for
managing changes to system.
Estimation plan
Start of Project
End of Project
Duration
Work
Cost
Completed work
1-sep -2010
7- feb-2011
114 days
8504 hours
$106,100
0% (only planning not estimation)
Work plan/ Milestones

Milestone
Milestone Description
Project Management plan
Project Management plan completed
SRS Done
Software requirement specification finalized
System Requirement Specification done
System requirement specification finalized
User Manual
Helping material finalized
Front end developed
User Interface finalized
Training Material
Training material for the project completed
Detail Design done
Database of the system Finalized
System Testing done
All the testing including unit integration and

system level testing completed
Project closing
Project completed according to requirements
Refferences:Internet
PMBOK 4RTH Edition
Requirement Documentation
Stakeholder
Requirement
Mr. Hassan Akhtar

should be according to the
criteria given in project
scope.
He should have contract so
that he knows on which
specifications the system
will be delivered to him.
scope.
scope.
Dr. Ali Ahsan
Category
Priority
Contract
requirements
High
Development
requirements
High
Acceptance
Criteria
Project should be
done in the given
budget and in the
required timeline.
Project should be
done according to
the specified time
period and results
in profit.
Tahira
Project is done according to

the criteria mentioned by
the overseeing authority.
Feasibility report, project
charter should be provided
to the project manager
Operation
requirements
High
Schedule should be
followed accurately
and the required
functionality must
be delivered.
Saima Imtiaz
All the non functional and

functional requirements of
the desired system
System Requirement
Specification document and
software requirement
specification documentation
are also required
All the non functional and
functional requirements of
the desired system
Operation
requirements
Medium
Operation
requirements
Medium
Complete database is
required.
Rabia Malik
Samya Kashif
Executable code should be

providing to her is that so
she can perform various
tests on it and implement it.
Executable code should be

provide to her so that she
can perform various tests
on it and validate it.
All the resources

needed are properly
acquired and
managed.
The design of the
database should
cover all aspects of
requirements.
All the
requirements
should be gathered
with specifications
and should be
validated.
Help and guidance
needed for system
is provided
Performance
requirement
High
The user interface

should be designed
according to the
requirements and
should be
validated.
The code executes
properly and no
error is found.
Help and guidance
needed for system
is provided.
Project Scope statement

Product Scope Description:
Pakistan
will be able to search the available record. The system is recommended to have a unique
username and password so that nobody can misuse it. This system must be right protected
and rights of every category of user must be clearly described so that limits for every user
access are defined.
It is an online system which has a a system, a user manual and training material as its
deliverables. This system must perform the following functions:
Online registration
Log in
Marks lists
Online lectures
Video conferencing
Project Acceptance Criteria:

It must perform the following functions : Online registration
Log in
Marks lists
Online lectures
Video conferencing
Network should be available all the time and the data should be kept confidential and
there should be no data loss from the database of the program. Program should be very
reliable.
Project Exclusions:
The features which are currently out of scope and may be added later on as an extension
to the application are:
Info service
Comprehensive information library
Project Constraints:
The system should develop within the 0.5 million budget granted by HEC.
The system should be deployed and operation within 6 months.
The system should be inter operatable with the current system of C@SE
University
Project Assumptions:
Internet Explorer
Firefox.
Netscape Navigator
Google Chrome
Activity list
ID
1
WBS
Task Name
1 ONLINE EDUCATION SYSTEM
PROJECT MANAGEMENT
Duration
Start
Finish
114 days
W ed 9/1/10
Mon 2/7/11
107 days
W ed 9/1/10
Thu 1/27/11
Predecessors
Half 1, 2010
Half 2, 2010
Half 1, 2011
Half 2, 2011
Half 1, 2012
A M J J A S O N D J F M A M J J A S O N D J F M A M
1.1
1.1.1
Planning and Estimation
20 days
Wed 9/1/10
Tue 9/28/10
1.1.2
Organizing & Staffing
39 days
Wed 9/29/10
Mon 11/22/10 3
1.1.3
Directing
52 days
Wed 9/29/10
Thu 12/9/10 3
1.1.4
Project Management Plan
0 days
Tue 9/28/10
Tue 9/28/10 3
1.1.5
1.2
Monitor & Control
87 days
Wed 9/29/10
Thu 1/27/11 6
78 days
W ed 9/1/10
Fri 12/17/10
1.2.1
Software Requirement Specification7 days
Wed 9/1/10
Thu 9/9/10
10
1.2.2
SRS Done
0 days
Thu 9/9/10
Thu 9/9/10 9
11
1.2.3
System Requirements Specification10 days
Fri 9/10/10
Thu 9/23/10 10
12
1.2.4
System Requirement Specification Done

0 days
Thu 9/23/10
Thu 9/23/10 11
13
1.2.5
User Documentation
48 days
Wed 9/1/10
Fri 11/5/10
14
1.2.6
User Manual
0 days
Fri 11/5/10
Fri 11/5/10 13
15
1.2.7
Training Material
26 days
Wed 9/1/10
Fri 12/17/10
16
1.2.8
Training Material
0 days
Fri 12/17/10
Fri 12/17/10 15
17
1.3
60 days
Fri 9/10/10
Thu 12/2/10 9
18
1.3.1
Designing User Interface
30 days
Fri 9/10/10 Thu 10/21/10
19
1.3.2
Designing Database
60 days
Fri 9/10/10
20
1.3.3
Detail Design Done
0 days
Thu 12/2/10
Thu 12/2/10 18,19
21
1.4
25 days
Fri 12/3/10
Thu 1/6/11 17
22
1.4.1
Development of Front End
25 days
Fri 12/3/10
Thu 1/6/11
23
1.4.2
Front End Developed
0 days
Thu 1/6/11
Thu 1/6/11 22
24
1.4.3
implementing database
25
1.4.4
Implementing Business Layer
PRODUCT REQUIREMENT
DETAIL DESIGN
DEVELOPMENT
INTEGRATION AND TESTING
20 days
Thu 12/2/10
Fri 12/3/10 Thu 12/30/10
4 days
Fri 12/31/10
Wed 1/5/11 24
Mon 2/7/11
PC1[1],Saima
PC3[1],Nadia,Sadia
Daud,PC4[1]
9/28
Khawar,Raza,Eshal,PC5[1]
Nadeem,Shahrukh,Salman,PC6[1]
9/9
PC7[1],Eshal,Naveed,PC11[1]
9/23
PC7[1],Hafsa
11/5
Amal,PC8[1]
12/17
Farwa,Shahrukh,Nadeem,PC9[1],PC10[1],PC11[1]
Humza,PC12[1]
12/2
Ali,Farwa,PC9[1],PC10[1]
1/6
Humza,PC12[1],PC6[1],Saga[50%]
Naveed,Umer[50%],PC3[1],PC4[1]
26
1.5
47 days
Fri 12/3/10
27
1.5.1
Unit Testing
25 days
Fri 12/3/10
28
1.5.2
Integration Testing
20 days
Fri 1/7/11
Thu 2/3/11 27
Samya[50%],Huma[50%],PC6[1],PC12[1]
29
1.5.3
System Testing
2 days
Fri 2/4/11
Mon 2/7/11 28
Salman,Huma,Naveed,PC12[1]
30
1.5.4
System Testing Done
0 days
Mon 2/7/11
Mon 2/7/11 29
2/7
31
1.5.5
Project Closing
0 days
Mon 2/7/11
Mon 2/7/11 29
2/7
Thu 1/6/11 22SS
PC8[1],Sara
Milestone Plan
Milestone
Milestone Description
Type

completed
Document
SRS Done
Software requirement
specification finalized
Document
System Requirement
Specification done
System requirement
specification finalized
Document
User Manual
Helping material finalized
Document
Front end developed
User Interface finalized
Document
Training Material
Training material for the

project completed
Document
Detail Design done
Database of the system

Finalized
Document
System Testing done
All the testing including unit

integration and system level
testing completed
Document
Project closing
Project completed according to

requirements
Project completion
Project schedule Network Diagram

ONLINE EDUCATION SYST EM
PROJ ECT M ANAGEMENT
Pla nn ing a nd Es tima ti on
St art : 9/1/10
ID: 1
St art : 9/1/10
ID: 2
St art : 9/1/10
ID: 3
Fin ish: 2/ 7/11
Dur: 114 days
Finish: 1/ 27/ 11
Dur: 107 days
Fin ish: 9/ 28/ 10
Dur: 20 days
Comp: 0%
Comp: 0%
Res:
Proje ct M a na geme nt Pla n

M ilest one Date: Tue 9/28/10
ID: 6
PC1[1] , Saim a
Mo ni to r & Cont rol

St art : 9/29/10
ID: 7
Finish: 1/ 27/ 11
Dur: 87 days
Res:
Khawar , Raza, Eshal, PC5[ 1]
Org aniz ing & Sta ffi ng

St art : 9/29/10
ID: 4
Finish: 11/22/10
Dur: 39 days
Res:
PC3[1] , Nadia, Sadia
Dire c tin g
St art : 9/29/10
ID: 5
Finish: 12/9/ 10
Dur: 52 days
Res:
PRODUCT REQUIREMENT
Sof tware Re q ui re ment Spe ci fic a tio n
St art : 9/1/10
ID: 8
St art : 9/1/10
ID: 9
Finish: 12/17/10
Dur: 78 days
Fin ish: 9/ 9/10
Dur: 7days
Comp: 0%
Res:
Daud, PC4[1]
SRS Do ne
M ilest one Date: Thu 9/9/ 10
ID: 10
Nadeem, Shahrukh, Salman, PC6[1]
Use r Doc ume nta tio n

St art : 9/1/10
ID: 13
Fin ish: 11/5/ 10
Dur: 48 days
Res:
St art : 9/10/10
ID: 11
Finish: 9/ 23/ 10
Dur: 10 days
Res:
Sys te m Re quireme nt Sp ec if ic at io n
Don e
Milest one Date: Thu9/23/10
ID: 12
PC7[1] , Eshal, Naveed, PC11[ 1]
Use r M anu al
M ilest one Date: Fr i 11/5/ 10
ID: 14
PC7[1] , Hafsa
T ra in ing Mat eria l
T ra in ing Mat eria l
St art : 9/1/10
ID: 15
Fin ish: 12/17/10
Dur: 26 days
Res:
Sys te m Re quir eme nts Spe c ifi ca ti on
M ilest one Date: Fr i 12/17/10

ID: 16
Amal, PC8[1]
DET AIL DESIGN
Des ign ing Us e r I nt erfa ce
St art : 9/10/10
ID: 17
St art : 9/10/10
ID: 18
Finish: 12/2/ 10
Dur: 60 days
Finish: 10/21/10
Dur: 30 days
Comp: 0%
Res:
Detai l De si gn Do ne
Milest one Date: Thu12/2/10
ID: 20
Far wa, Shahr ukh, Nadeem, PC9[ 1], PC10[ 1], PC11[ 1]
Des ign ing Da ta bas e

St art : 9/10/10
ID: 19
Finish: 12/2/ 10
Dur: 60 days
Res:
Humza, PC12[1]
DEVELOPM ENT
Dev e lo pme nt o f Front En d
St art : 12/ 3/10
ID: 21
St art : 12/ 3/10
ID: 22
Finish: 1/ 6/11
Dur: 25 days
Finish: 1/ 6/11
Dur: 25 days
Comp: 0%
Res:
Fro nt End De ve lo ped

Milest one Date: Thu1/6/ 11
ID: 23
Ali, Far wa, PC9[1], PC10[1]
imp le me nting da ta bas e
Imp le me nt ing Bu s ines s Lay e r
St art : 12/ 3/10
ID: 24
St art : 12/ 31/ 10
ID: 25
Finish: 12/30/10
Dur: 20 days
Finish: 1/ 5/11
Dur: 4days
Res:
Humza, PC12[1] , PC6[ 1], Saga[ 50%]
Res:
Naveed, Umer[50%], PC3[1] , PC4[ 1]
INT EGRATION AND TESTING
Uni t Te st in g
Inte gra tion Tes ti ng
Sys te m Te st in g
St art : 12/ 3/10
ID: 26
St art : 12/ 3/10
ID: 27
St art : 1/7/11
ID: 28
St art : 2/4/11
ID: 29
Finish: 2/ 7/11
Dur: 47 days
Finish: 1/ 6/11
Dur: 25 days
Finish: 2/ 3/11
Dur: 20 days
Finish: 2/ 7/11
Dur: 2days
Comp: 0%
Res:
PC8[1] , Sara
Res:
Samya[50%] , Huma[50%], PC6[1] , PC12[1]
Res:
Salm an, Huma, Naveed, PC12[1]
Activity Resource Requirement
Critical Tasks
Quality Management Plan

List of control and monitoring staff
1. Eshal
Quality Assurance Approach:

2. Raza
Process Improvement model:3. Khawar
ISO 9216
It describes standards for a formally organized process to manufacture a

product and the methods of managing and monitoring progress.
System should follow IEEE standards in testing, deployment,
configuration management.
System should be developed using the ISO 9216 quality standard
To follow the following standard when the project will start:
We will follow the spiral model approach as a quality assurance model

approach when we put this project into action in this project.
ISO 9216 and IEEE will make sure that the quality reviews are held,
deliverables are tested and clients acceptance is acquired.
Quality Control Approach:
We have to make sure that end product conforms with the customer
requirements for this all the changes will be documented properly and to apply
change in a proper way in our project keeping in mind that the design of the
project is not disturbed. And that the project and its requirements did in fact follow
the standard that is IEEE and ISO 9216, all the requirements are verified or
validated.
System should be 75% tested before use.
Cost Estimates
Budget Estimate
Human Resource Plan
Role:
Investor/
clients
Head of Software
Development
Project
Manager
Responsibility:
To invest in the project
He is part of inception, approves resources for the project, directly oversees the
project business manager, and is responsible for the project meeting the goals of
all stakeholders.
Experienced and objective technical and management oversight from individuals
who are not directly involved in the project
To release the funds to Project Manager at the end of each working period. And
see the performance of the project.
Responsible for successful business outcome of the project. In charge of
project staffing, acquiring resources for the project, personnel issues, toplevel work assignments, and stakeholder interaction.
She is the top decision maker on the project, but normally defers technical
decisions to the appropriate technical lead. Resolves disputes between
project participants. Responsible for coordinating the activities with the
stakeholders, project sponsor, and project reviewers
Requirement
Engineer
Acquiring and Managing Resource

requirements.
Data base
Administrator
Design application including database design

Responsible for the system architecture and overseeing design activities.
As appropriate may assign sub-leads for functional areas of the product or
for technical specialties such as database, graphics, driver, distributed
processing, communications protocol, etc.
Requirement
Engineer
Requirement gathering, specification and validation

Requirements.
Software
Engineer
Designing User interface, validating User interfaces

A pool of software engineers that can be assigned various tasks on a project based on
ability and interest
Tester
Design and document test cases, execute test cases, record test case results, document
and track defects, and perform test coverage analysis.
Technical Writers
They document processes and other user manuals, create online courses and product
demonstrations
Staff Acquisition:
Following staff is acquired for our project: Project manager
Financial analyst
Requirement engineers
Configuration manager
Software Engineer
Technical Writer
Computer Programmer
Database Administrator
Database Designer
Database Developer
Functional Manager
Graphic Designer
Project Manager
Report Designer
Report Developer
Requirements Analyst
Software Tester
Support Technician
System Architect
Technical Writer
User Interface Designer
Web Designer
Web Developer
Web Programmer
Web Site Builder
Monitoring and control
Staff Release:
The staff worked from 1st September 2010 till 7th February 2011.
Training Needs:
Training will be provided to the programmers as it is their first online
Rewards and Recognition:

At the end of the project a bonus will be given if the project is done according to the
requirement.
Regulations, Standards, and Policy Compliance:

System should be developed according to IEEE standards and ISO 9216 quality
standard.
Resource Calendars:
S TAK E H O L D E R M A N A G E M E N T S T R ATE G Y
Name
Influence
Involvement
Assessment
Strategies
Mr. Hassan
High
Akhtar
Influence
Low
Involvement
To have a unique and reliable, high quality

system.
Dr. Ali Ahsan
High
Medium
Involvement
To deliver a unique reliable and high quality

system to Mr. Hassan Akhtar.
High
Involvement
To produce a high quality system according

to the given budget and schedule and the
requirements.
Very high
involvement
To do the specified job according to the

criteria set by the project management
Very high
involvement

Very high
involvement

Influence
Tahira
Medium
Influence
Saima
Low
Imtiaz
Influence
Low
Rabia Malik
Samya
Kashif
Influence
Low
Influence
Communication Management Plan
Method
Performance status Reports
Performance Review Meetings
(Presentations)
Term or
Acronym
Performance
Review Meetings
Performance
status reports
Audience
Team
members
Team leader
Conductors
Team leader
Project
Manager
Frequency
Once A
Week
Once a
month
Definition
The performance review meeting is a process where
manager and employee work together to assess the
degree to which the employee ha attained agree-upon
goals, and work together to overcome any difficulties
encountered.
A status report is a clear summary of how a project is
progressing against its schedule, scope and budget. If
it is working correctly, the intended reader can tell
instantly if anything is off plan and whats being done
about it
Communication Constraints or Assumptions:

Performance Review Meetings : Must be conducted once a month
Performance Status reports :
Must be conducted once a week
Risk Register
Risk
ID
Risk Statement
Probability
Impact
Scope
Quality
Schedule
Cost
Pcs not working properly
.40
Network not working

properly
0.30
Unexpected holidays
0.04
Programmer not available

due to unforeseen event
.20
Electricity
cutoff(unexpected)
.05
Natural Disasters
.01
Risk Management Plan
Methods and approaches
Risk
ID
Risk Statement
Methods and approaches
Extra pieces will be kept
Network not working properly
Restart the network system
Unexpected holidays
Overtime on working days
Programmer not available due to unforeseen

event
Same competency and qualification

substitute programmer will be kept for the
while
Electricity cutoff(unexpected)
Generator will be used
Natural Disasters
Will try to start working as soon as

possible as this is an unavoidable risk we
will have to face it
Responsibilities
Risk
ID
Risk Statement
Responsibility
Administrator
Network Administrator
Unexpected holidays
Administrator
Programmer not available due to unforeseen Team Leader

event
Administrator
Natural Disasters
NA
Risk Categories
Risk
ID
Risk Statement
Risk Category
Operational Risk
Technical Risk
Unexpected holidays
Environmental risk
Programmer not available due to

unforeseen event
Resource risk
Operational risk
Natural Disasters
Environmental Risk
Stakeholder Risk Tolerance:

General
Risks
Quality
Level of Stakeholder Risk Tolerance

Cannot be compromised on
Schedule
Cost
A little delay can be compromised

Change will not be acceptable
Probability of risk
Risk
ID
Risk Statement
Probability
Risk expectancy of occurring
.40
High
0.30
Moderate
Unexpected holidays
0.04
Very low
Programmer not available due to

unforeseen event
.20
Moderate
.05
Very low
Natural Disasters
.01
Very low
Probability and Impact by Objective matrix:

Risks
Pc problem
Network Holiday
Problem Risk
Unavailability Electricity
of
Problem
programmer
Natural
Disaster
Risks
probability
Cost
40%
20%-40%
increase
Time
10%-20%
increase
Scope
Quality
30%
10%20%
increase
5%-10%
increase
Scope
Major
reduction
areas of
unacceptable
scope
by investor
affected
Quality
Quality
reduction
reduction
unacceptable requires
by investor investors
approval
4%
Insignificant
increase
20%
10-20%
increase
5%
1%
Insignificant Insignificant
increase
increase
Insignificant
increase
5-10%
increase
Insignificant Insignificant
increase
increase
Decrease
barely
noticeable
Major areas of
scope affected
Decrease
barely
noticeable
Decrease
barely
noticeable
Quality
degradation
barely
noticeable
Quality
reduction
requires
investors
approval
Quality
degradation
barely
noticeable
Quality
degradation
barely
noticeable
Risk Management Funding:

Low level risks will be funded by the project manager and the leader but where the high level risks are
approved of and funded by the investor after his approval if these risks occur.
Procurement Management Plan
Procurement Explanation:
As the project is not so big so project manager will do project procurement as well. For
this project we are hiring a front end developer as we dont have one. Our work is
done on computers and we had already bought them in past for some other project so
we dont need to procure anything else.
Roles and Responsibilities:
Roles
Responsibilities
Head of Software Development
Approve Procurement Management Plan

Approve staff selection
Approve all contracts
Approve procurement actions by submitting
tenders and advertisements
Project manager
Provide oversight for all procurement actions

Approve procurement actions
Develop procurement requirements
Manage staff selection
Procuring the staff
Developing contracts
Closing out staff contracts
Development of procurement requirements
Standard Procurement Documents:

1. Tenders
2. Official Advertisement
3. Contract
Selection Criteria
Should know how to work on: Coral Draw
Adobe Photoshop etc
He should be good at Web page designing as he will be designing the front end of the
software.

Hafsa (The - Best)

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Hafsa (The - Best)

Încărcat de

Drepturi de autor:

Formate disponibile

CASE

Project Plan and Initiation

By Hafsa Muhammed B08-006

2.2 Project Scope Management

2.4. Project Quality Management

2.5. Project Cost Management

2.6. Project Human Resource Management

2.7. Project Communication Plan

2.8. Project Risk Management

2.9. Project Procurement Management

Critical success factors

Success Measurement Criteria:

A project is said to be successful if it is completed on time, within budget, meet the

Completed within Budget

Project should be completed within 0.5

stakeholders of this system. The Higher Education Commission is also an important

for future purpose.

easy to use and

The tool should be

C@SE University which can only benefit

Assumptions and Dependencies

We need to maintain session

need experts to handle such errors.

information to save and restart

For data bases we need strong tool to

system from that point.

avoid loss of data.

to avoid this situation.

related department representatives (finance department,

10.5. External Training Requirements:

11. Project Responsibility Matrix:

Assigning and managing resources

Requirement gathering, specification and

Implementation and testing

Acceptance testing of the system

User Manuals and Help

Name and Signature

12th August 2010

Mr. Hassan Akhtar

12th August 2010

Dr. Ali Ahsan

10th August 2010

10th August 2010

13. Revision History

Reason For Changes

Functionality, cost and

Dr. Ali Ahsan Head of

Project contract should

All the non functional

All the resources

The design of the

Executable code should

The user interface

Executable code should

Help and guidance

Project Management Plan

Course evaluation (quizzes)

Uploading course content

Downloading course content

Acquiring and Managing Resource

Design application including database design

Requirement gathering, specification and validation

Designing User interface, validating User interfaces