CASE

Online Education
System

Project Plan and Initiation

By Hafsa Muhammed B08-006

23-12-10
Contents

1. Initiation
1.1. Project Charter . . . . . . . 3
1.2. Stake holder Register . . . . . . 12

2. Planning
1.1. Project integration management
2.1.1. Project Management Plan . . . . . 14

2.2 Project Scope Management

2.1.2. Requirement Document. . . . . . 20
2.1.3. Scope Statement . . . . . . 22
2.1.4. WBS (a separate document attached with)

2.3. Project Time Management

2.3.1. Activity List . . . . . . . 25
2.3.2. Milestone Plan . . . . . . . 26
2.3.3. Project schedule and Network Diagram . . . . 27
2.3.4. Activity resource requirement . . . . . 28
2.3.6 Critical Tasks . . . . . . . 29

2.4. Project Quality Management

2.4.1. Quality Management Plan . . . . . . 30

2.5. Project Cost Management

2.5.1. Activity Cost Estimates . . . . . . 31
2.5.2. Budget Estimate . . . . . . . 32

2.6. Project Human Resource Management

2.6.1. Human Resource Plan . . . . . . 33
2.6.2. Stakeholder Management Plan . . . . . 37

2.7. Project Communication Plan

2.7.1. Communication Plan . . . . . . 38

2.8. Project Risk Management

2.8.1. Risk Register . . . . . . . 41
2.8.2. Risk Management Plan . . . . . . 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

million budget
Completed on Time Project should be completed within 6
months
Customer Satisfaction 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 reliability for future purpose.
Faculty Member ------------------- Neutral Performance and -----------------------
Security -
Administrator ------------------- Neutral Performance System should be
-- useable on
minimum of
512kpbs
Students Able to gain Strongly Usability, System should be
quality Supportive efficiency, easy to use and
education at performance operate.
home
HEC Promote Strongly Reliability The tool should be
Higher Supportive developed within
Education in 0.5 million of
Pakistan budget.

5. 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 Students
Who Are unable to study as regular students
The Online education program
Is a Online solution
That Will provide quality education to students
living in rural areas just by connecting via
internet.
Unlike The regular programs being offered by
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 Probability Impact Mitigation

There is a risk of network failure we 70% Severe We need to maintain session
need experts to handle such errors. information to save and restart
system from that point.
For data bases we need strong tool to 40% Severe We need to have backup server
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
Rabia Malik
validation
Designing User interface, validating User
Rabila Malik
interfaces
Design application including database
Saima Imtiaz
design
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 Dr. Ali Ahsan 10th August 2010
Development

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 Contact Requirements Expectations
Informatio
n
Mr. Hassan President of Investor/client 092-51- Functionality, cost and Project should be
Akhtar C@SE s 9155556 schedule of the system done in the given
University should be according to budget and in the
the criteria given in required timeline.
project scope.
He should have
contract so that he
 knows on which
specifications the
system will be
delivered to him.

Dr. Ali Ahsan Head of Overseeing 092-51- Project contract should Project should be
Software authority 9155555 be with him so as to done according to
Development know what the specified time
requirements should be period and results
met in which in profit.
constraints in order to
deliver the final
project.
Functionality, cost and
schedule of the system
should be according to
the criteria given in
project scope.

Tahira Project Manager 092-51- Project is done Schedule should be

Manager responsible 9155554 according to the criteria followed accurately
for online mentioned by the and the required
education overseeing authority. functionality must
program Feasibility report, be delivered.
project charter should
be provided to the
project manager.

Acquiring 092-51- All the non functional All the resources

Requirement and Managing 9155553 and functional needed are properly
Engineer Resource requirements of the acquired and
desired system. managed.
Saima Imtiaz
Design System Requirement The design of the
application Specification document database should
Data base including and software cover all aspects of
Manager database requirement requirements.
design specification
documentation are also
required.
 Requirement 092-51- All the non functional All the
gathering, 9155552 and functional requirements
specification requirements of the should be gathered
Requirement
and validation desired system with specifications
Engineer
and should be
validated.

Designing Complete database is The user interface

User interface, required. should be designed
Rabia Malik validating according to the
User requirements and
interfaces should be validated.
Software
Engineer
User Manuals Executable code should
and Help be providing to her is Help and guidance
that so she can perform needed for system
various tests on it and is provided
implement it.

Implementatio 092-51- Executable code should The code executes

Tester n and 9155551 be provide to her so properly and no
acceptance that she can perform error is found.
Samya testing of the various tests on it and
Kashif system validate it. Help and guidance
Technical needed for system
writer User Manuals is provided.
and Help

Project Management Plan

Product Scope Description:
This project is made for a C@SE University which wants to conduct online education in
Pakistan
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.

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

Course evaluation (quizzes)

Assignment submission

Marks lists

Uploading course content

Online lectures

Downloading course content

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.
Project Deliverables:

Role: Responsibility:
Investor/ To invest in the project
clients 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.
Head of Software Experienced and objective technical and management oversight from individuals
Development who are not directly involved in the project

Project To release the funds to Project Manager at the end of each working period. And
Manager 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, top-
level 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
Acquiring and Managing Resource
Requirement
In charge of eliciting, defining, maintaining, and tracing detailed product
Engineer
requirements.
Design application including database design
Responsible for the system architecture and overseeing design activities.
Data base
As appropriate may assign sub-leads for functional areas of the product or
Administrator
for technical specialties such as database, graphics, driver, distributed
processing, communications protocol, etc.
Requirement gathering, specification and validation
Requirement In charge of eliciting, defining, maintaining, and tracing detailed product
Engineer Requirements.

Designing User interface, validating User interfaces

Software
A pool of software engineers that can be assigned various tasks on a project based on
Engineer
ability and interest
Project Deliverables:
Design and document test cases, execute test cases, record test case results, document
Tester
and track defects, and perform test coverage analysis.
They document processes and other user manuals, create online courses and product
Technical Writers 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:
It is a web based tool and will be supported by the following web browser.

Internet Explorer
Firefox.
Netscape Navigator
Google Chrome
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.

Communications:-
Method Audience Initiators Frequency
Performance status Reports Team Team leader Once A Week
members
Performance Review Meetings Team leader Project Once a month
(Presentations) Manager
Presentations Investor Project After achieving a milestone or
manager, once in 2 months
team &
head of
department

Roles and responsibility

Resources
14. 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.

15. Software licenses

System should be licensed so that it should not get illegally

used or copied. It is owned by C@SE University.
16. 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.

17. 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 1-sep -2010
End of Project 7- feb-2011
Duration 114 days
Work 8504 hours
Cost $106,100
Completed work 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 Category Priority Acceptance

Criteria
Mr. Hassan Akhtar Functionality, cost and Project should be
schedule of the system Contract High done in the given
should be according to the requirements budget and in the
criteria given in project required timeline.
scope.
He should have contract so
that he knows on which
specifications the system
will be delivered to him.
Dr. Ali Ahsan Functionality, cost and Project should be
schedule of the system Development High done according to
should be according to the requirements the specified time
criteria given in project period and results
scope. in profit.
Functionality, cost and
schedule of the system
should be according to the
criteria given in project
scope.
Tahira Project is done according to Schedule should be
the criteria mentioned by Operation High followed accurately
the overseeing authority. requirements and the required
Feasibility report, project functionality must
charter should be provided be delivered.
to the project manager
 All the non functional and All the resources
functional requirements of Operation Medium needed are properly
Saima Imtiaz the desired system requirements acquired and
System Requirement managed.
Specification document and The design of the
software requirement database should
specification documentation cover all aspects of
are also required requirements.

All the non functional and All the

functional requirements of Operation Medium requirements
the desired system requirements should be gathered
with specifications
Complete database is and should be
required. validated.

Executable code should be Help and guidance

Rabia Malik providing to her is that so needed for system
she can perform various is provided
tests on it and implement it.
The user interface
should be designed
according to the
requirements and
should be
validated.
Executable code should be The code executes
provide to her so that she Performance High properly and no
can perform various tests requirement error is found.
Samya Kashif on it and validate it.
Help and guidance
needed for system
is provided.
 Project Scope statement
Product Scope Description:
This project is made for a C@SE University which wants to conduct online education in
Pakistan
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.

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

Course evaluation (quizzes)

Assignment submission

Marks lists

Uploading course content

Online lectures

Downloading course content

Video conferencing
Project Acceptance Criteria:
It must perform the following functions :-
Online registration

Log in

Course evaluation (quizzes)

Assignment submission

Marks lists

Uploading course content

Online lectures

Downloading course content

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:
It is a web based tool and will be supported by the following web browser.

Internet Explorer
Firefox.
Netscape Navigator
Google Chrome
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.
 Activity list
ID WBS Task Name Duration Start Finish 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 ONLINE EDUCATION SYSTEM 114 days W ed 9/1/10 Mon 2/7/11
2 1.1 PROJECT MANAGEMENT 107 days W ed 9/1/10 Thu 1/27/11
3 1.1.1 Planning and Estimation 20 days Wed 9/1/10 Tue 9/28/10 PC1[1],Saima
4 1.1.2 Organizing & Staffing 39 days Wed 9/29/10 Mon 11/22/10 3 PC3[1],Nadia,Sadia
5 1.1.3 Directing 52 days Wed 9/29/10 Thu 12/9/10 3 Daud,PC4[1]
6 1.1.4 Project Management Plan 0 days Tue 9/28/10 Tue 9/28/10 3 9/28
7 1.1.5 Monitor & Control 87 days Wed 9/29/10 Thu 1/27/11 6 Khawar,Raza,Eshal,PC5[1]
8 1.2 PRODUCT REQUIREMENT 78 days W ed 9/1/10 Fri 12/17/10
9 1.2.1 Software Requirement Specification7 days Wed 9/1/10 Thu 9/9/10 Nadeem,Shahrukh,Salman,PC6[1]
10 1.2.2 SRS Done 0 days Thu 9/9/10 Thu 9/9/10 9 9/9
11 1.2.3 System Requirements Specification10 days Fri 9/10/10 Thu 9/23/10 10 PC7[1],Eshal,Naveed,PC11[1]
12 1.2.4 System Requirement Specification Done
0 days Thu 9/23/10 Thu 9/23/10 11 9/23
13 1.2.5 User Documentation 48 days Wed 9/1/10 Fri 11/5/10 PC7[1],Hafsa
14 1.2.6 User Manual 0 days Fri 11/5/10 Fri 11/5/10 13 11/5
15 1.2.7 Training Material 26 days Wed 9/1/10 Fri 12/17/10 Amal,PC8[1]
16 1.2.8 Training Material 0 days Fri 12/17/10 Fri 12/17/10 15 12/17
17 1.3 DETAIL DESIGN 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 Farwa,Shahrukh,Nadeem,PC9[1],PC10[1],PC11[1]
19 1.3.2 Designing Database 60 days Fri 9/10/10 Thu 12/2/10 Humza,PC12[1]
20 1.3.3 Detail Design Done 0 days Thu 12/2/10 Thu 12/2/10 18,19 12/2
21 1.4 DEVELOPMENT 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 Ali,Farwa,PC9[1],PC10[1]
23 1.4.2 Front End Developed 0 days Thu 1/6/11 Thu 1/6/11 22 1/6
24 1.4.3 implementing database 20 days Fri 12/3/10 Thu 12/30/10 Humza,PC12[1],PC6[1],Saga[50%]
25 1.4.4 Implementing Business Layer 4 days Fri 12/31/10 Wed 1/5/11 24 Naveed,Umer[50%],PC3[1],PC4[1]
26 1.5 INTEGRATION AND TESTING 47 days Fri 12/3/10 Mon 2/7/11
27 1.5.1 Unit Testing 25 days Fri 12/3/10 Thu 1/6/11 22SS PC8[1],Sara
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
 Milestone Plan

Milestone Milestone Description Type

Project Management plan Project Management plan Document
completed

SRS Done Software requirement Document

specification finalized

System Requirement System requirement Document

Specification done specification finalized

User Manual Helping material finalized Document

Front end developed User Interface finalized Document

Training Material Training material for the Document

project completed

Detail Design done Database of the system Document

Finalized

System Testing done All the testing including unit Document

integration and system level
testing completed

Project closing Project completed according to Project completion

requirements
 Project schedule Network Diagram
ONL INE EDUCATION SYST EM PROJ ECT M ANAGEMENT Pla nnin g a nd Es tima ti on M oni tor & Co nt rol
Proje ct M a na geme nt Pla n
St art : 9/1/10 ID: 1 St art : 9/1/10 ID: 2 St art : 9/1 /10 ID: 3 St art : 9/29/10 ID: 7

Finish: 2/ 7/11 Dur: 114 da ys Fin ish: 1/ 27/ 11 Dur: 107 days Fin ish: 9/ 28/ 10 Dur: 20 day s M ilest one Da te: Tue 9/28/10 Fin ish: 1/ 27/ 11 Du r: 87 days

Comp : 0% Comp: 0% Res: PC1 [1] , Saim a ID: 6 Re s: Khawar , Raza, Eshal, PC5[ 1]

Org aniz ing & Sta ffi ng

St art : 9/29/10 ID: 4

Finish: 11/22/10 Dur: 39 day s

Res: PC3[1] , Nadia , Sadia

Dire c tin g
St art : 9/29/10 ID: 5

Finish: 12/9/ 10 Dur: 52 day s

Res: Daud, PC4[1]

PRODUCT REQUIREMENT Sof tware Re qui re men t Sp eci fic a tion SRS Done Sys te m Re quireme nts Spe c ifi ca ti on Sys te m Re quireme nt Spec if ic at io n
Don e
St art : 9/1/10 ID: 8 St art : 9/1 /10 ID: 9 St art : 9/10/10 ID: 11

Fin ish: 12/17/10 Dur: 78 days Fin ish: 9/ 9/1 0 Dur: 7 days M ilest one Da te: Thu 9/9/ 10 Fin ish: 9/ 23/ 10 Du r: 10 days M ilest one Date: Thu 9/23/10

Comp: 0% Res: Nad eem, Shahrukh, Salman, PC6[1] ID: 1 0 Re s: PC7[1] , Eshal, Naveed, PC11[ 1] ID: 12

Use r Do c ume n ta tion

Use r M anu al
St art : 9/1 /10 ID: 13

Fin ish: 11/5/ 10 Dur: 48 day s M ilest one Da te: Fr i 11/5/ 10

Res: PC7 [1] , Hafs a ID: 1 4

Tra inin g M at eria l

T ra in ing Mat eria l
St art : 9/1 /10 ID: 15

Fin ish: 12/17 /10 Dur: 26 day s M ilest one Da te: Fr i 12/17/10

Res: Am al, PC8[1] ID: 1 6

DET AIL DESIGN Des ig nin g Us e r I nt erfa ce Det ai l De si gn Done

St art : 9/10/10 ID: 17 St art : 9/10/10 ID: 18

Finish: 12/2/ 10 Dur: 60 day s Fin ish: 10/21/10 Du r: 30 days M ilest one Date: Thu 12/2/10

Comp : 0% Re s: Far wa, Shahr ukh, Nadeem, P C9[ 1], PC10[ 1], PC11[ 1] ID: 20

Des ig nin g Da ta bas e

St art : 9/10/10 ID: 19

Fin ish: 12/2/ 10 Du r: 60 days

Re s: Humza, PC12[1]

DEVELOPMENT Dev e lopme n t o f Front End

F ront End De ve loped
St art : 12/ 3/10 ID: 21 St art : 12/ 3/10 ID: 22

Fin ish: 1/ 6/11 Du r: 25 days Fin ish: 1/ 6/11 Dur: 25 day s M ilest one Da te: Thu 1/6/ 11

Comp: 0% Re s: Ali, Far wa, PC9[1], PC10[1] ID: 2 3

imple me nt in g da ta bas e Imp le me nting Bu s ines s Lay e r

St art : 12/ 3/10 ID: 24 St art : 12/ 31/ 10 ID: 25

Fin ish: 12/30/10 Dur: 20 day s Fin ish: 1/ 5/1 1 Dur: 4 days

Re s: Humza, PC12[1] , PC6[ 1], Sa ga[ 50%] Res: Nav eed, Umer[50%], PC3[1] , PC4[ 1]

INT EGRATION AND TESTING Uni t Te st in g In te g ra tion T es ti ng Sys te m Te sting

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

Fin ish: 2/ 7/11 Dur: 47 days Fin ish: 1/ 6/1 1 Dur: 25 day s Fin ish: 2/ 3/11 Dur: 20 day s Fin ish: 2/ 7/11 Dur: 2 days

Comp: 0% Res: PC8 [1] , Sara Re s: Samya[50%] , Huma[50%], PC6[1] , PC12 [1] Re s: Salm an, Hum a, 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: Responsibility:
Investor/ To invest in the project
clients 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.
Head of Software Experienced and objective technical and management oversight from individuals
Development who are not directly involved in the project

Project To release the funds to Project Manager at the end of each working period. And
Manager 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, top-
level 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
 Acquiring and Managing Resource
Requirement
In charge of eliciting, defining, maintaining, and tracing detailed product
Engineer
requirements.
Design application including database design
Responsible for the system architecture and overseeing design activities.
Data base
As appropriate may assign sub-leads for functional areas of the product or
Administrator
for technical specialties such as database, graphics, driver, distributed
processing, communications protocol, etc.
Requirement gathering, specification and validation
Requirement In charge of eliciting, defining, maintaining, and tracing detailed product
Engineer Requirements.

Designing User interface, validating User interfaces

Software
A pool of software engineers that can be assigned various tasks on a project based on
Engineer
ability and interest
Design and document test cases, execute test cases, record test case results, document
Tester
and track defects, and perform test coverage analysis.
They document processes and other user manuals, create online courses and product
Technical Writers 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 Strategies
Assessment
 Mr. Hassan High Low To have a unique and reliable, high quality
Involvement system.
Akhtar Influence

Dr. Ali Ahsan High Medium To deliver a unique reliable and high quality
Involvement system to Mr. Hassan Akhtar.
Influence

Tahira Medium High To produce a high quality system according to

Involvement the given budget and schedule and the
Influence requirements.

Saima Low Very high To do the specified job according to the

involvement criteria set by the project management
Imtiaz Influence

Low Very high To do the specified job according to the

involvement criteria set by the project management
Influence
Rabia Malik

Low Very high To do the specified job according to the

Samya involvement criteria set by the project management
Influence
Kashif

Communication Management Plan

Method Audience Conductors Frequency

Performance status Reports Team Team leader Once A
members Week
Performance Review Meetings Team leader Project Once a
(Presentations) Manager month

Term or Definition
Acronym
The performance review meeting is a process where
manager and employee work together to assess the
Performance
degree to which the employee ha attained agree-upon
Review Meetings
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
Performance
it is working correctly, the intended reader can tell
status reports
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 Statement Probability Impact

Risk Scope Quality Schedule Cost
ID
1 Pcs not working properly .40

2 Network not working 0.30

properly
3 Unexpected holidays 0.04

4 Programmer not available .20

due to unforeseen event

5 Electricity .05
cutoff(unexpected)

6 Natural Disasters .01

Risk Management Plan

Methods and approaches

Risk Risk Statement Methods and approaches
ID

1 Pcs not working properly Extra pieces will be kept

2 Network not working properly Restart the network system

3 Unexpected holidays Overtime on working days

4 Programmer not available due to unforeseen Same competency and qualification

event substitute programmer will be kept for the
while

5 Electricity cutoff(unexpected) Generator will be used

6 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 Risk Statement Responsibility

ID

1 Pcs not working properly Administrator

2 Network not working properly Network Administrator

3 Unexpected holidays Administrator

4 Programmer not available due to unforeseen Team Leader

event

5 Electricity cutoff(unexpected) Administrator

6 Natural Disasters NA
Risk Categories

Risk Risk Statement Risk Category

ID

1 Pcs not working properly Operational Risk

2 Network not working properly Technical Risk

3 Unexpected holidays Environmental risk

4 Programmer not available due to Resource risk

unforeseen event
5 Electricity cutoff(unexpected) Operational risk

6 Natural Disasters Environmental Risk

Stakeholder Risk Tolerance:

General Risks Level of Stakeholder Risk Tolerance

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

Cost Change will not be acceptable

Probability of risk

Risk Risk Statement Probability Risk expectancy of occurring

ID

1 Pcs not working properly .40 High

2 Network not working properly 0.30 Moderate

3 Unexpected holidays 0.04 Very low

4 Programmer not available due to .20 Moderate

unforeseen event

5 Electricity cutoff(unexpected) .05 Very low

6 Natural Disasters .01 Very low

Probability and Impact by Objective matrix:

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

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.