Professional Documents
Culture Documents
Online Education
System
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
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.1. Technical
2.2. Business
2.3. Quality
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.
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 society’s
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
Marks lists
Online lectures
Video conferencing
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
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.
8. Constraints
9. Business Risks
10. Resources
10.3. Consulting
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
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 Head of Overseeing 092-51- Project contract should Project should be
Ahsan 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.
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
• Assignment submission
• 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.
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.
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.
Staff Acquisition:
Following staff is acquired for our project:-
• Project manager
• Financial analyst
• Requirement engineers
• Configuration manager
• Software Engineer
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
Resources
• Hardware Resources
• Consulting
• Staffing Requirements:
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)
System Testing done All the testing including unit integration and
system level testing completed
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.
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
• Assignment submission
• Marks lists
• Online lectures
Project Deliverables:
• Downloading course content
• Video conferencing
• Log in
• Assignment submission
• 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:
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
Fin ish: 2/ 7/1 1 Du r: 114 days Fin ish: 1/ 27/ 11 Du r: 107 days Fin ish: 9/ 28/ 10 Dur: 20 days M ilest one Date: Tue 9/28/10 Fin ish: 1/ 27/ 11 Dur: 87 day s
Comp: 0% Co mp: 0 % Res: PC1[1] , Saim a ID: 6 Res: Khawar , Raza, Eshal, PC5[ 1]
Direc ting
St art : 9/29/10 ID: 5
PRODUCT REQUIREMENT Sof tware Re qui rement Speci fic a tion Sys te m Requ irements Spe cifi ca ti on Sys tem Re quireme nt Spec ific ation
SRS Done
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 Du r: 78 day s Fin ish: 9/ 9/10 Dur: 7 days M ilest one Date: Th u 9/9/ 10 Fin ish: 9/ 23/ 10 Dur: 10 day s Milest one Date: Thu 9/23/10
Co mp: 0 % Res: Nadeem , Sha hrukh, Sa lman, PC6[1] ID: 10 Res: PC7[1] , Eshal, Naveed, PC11[ 1] ID: 12
Fin ish: 12/2/ 10 Dur: 60 days Fin ish: 10 /21/10 Dur: 30 day s Milest one Date: Thu 12/2/10
Co mp: 0 % Res: Far wa, Sh ahr ukh , Nadeem , PC9[ 1], PC10[ 1], PC11[ 1] ID: 20
Fin ish: 1/ 6/11 Dur: 25 day s Fin ish: 1/ 6/11 Dur: 25 days Milest one Date: Thu 1/6/ 11
Fin ish: 12 /30/10 Dur: 20 days Fin ish: 1/ 5/11 Dur: 4 d ays
Res: Hum za, PC12[1] , PC6[ 1], Saga[ 50%] Res: Naveed, Umer[5 0%], PC3[1] , PC4[ 1]
INTEGRAT ION AND T EST ING Uni t Test ing Inte gratio n T es ti ng System T est ing
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 Du r: 47 day s Fin ish: 1/ 6/11 Dur: 25 days Fin ish: 2/ 3/11 Dur: 20 days Fin ish: 2/ 7/11 Dur: 2 d ays
Co mp: 0 % Res: PC8[1] , Sara Res: Sam ya [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
2. Raza
3. Khawar
• 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.
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.
Staff Acquisition:
Following staff is acquired for our project:-
• Project manager
• Financial analyst
• Requirement engineers
• Configuration manager
• Software Engineer
Staff Release:
The staff worked from 1st September 2010 till 7th February 2011.
Training Needs:
At the end of the project a bonus will be given if the project is done according to the
requirement.
System should be developed according to IEEE standards and ISO 9216 quality
standard.
Resource Calendars:
STAKEHOLDER MANAGEMENT STRATEGY
Communication Management Plan
Dr. Ali Ahsan High Medium To deliver a unique reliable and high quality
Involvement system to Mr. Hassan Akhtar.
Influence
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 what’s being done
about it
Risk Register
Risk Risk Statement Probability Impact
ID Scope Quality Schedule Cost
1 Pc’s not working properly .40
5 Electricity .05
cutoff(unexpected)
6 Natural Disasters NA
Risk Categories
General
Level of Stakeholder Risk Tolerance
Risks
Cannot be compromised on
Quality
Schedule A little delay can be compromised
Probability of risk
Roles Responsibilities
Head of Software Development • Approve Procurement Management Plan
• Approve staff selection
• Approve all contracts
• Approve procurement actions by submitting
tenders and advertisements
Selection Criteria
He should be good at Web page designing as he will be designing the front end of the
software.