61
CASE Online Education System Project Plan and Initiation By Hafsa Muhammed B08-006 23-12-10

hafsa (the_best)

  • Upload
    adamx

  • View
    7

  • Download
    0

Embed Size (px)

DESCRIPTION

online system education

Citation preview

Page 1: hafsa  (the_best)

CASE

Online Education System

Project Plan and Initiation

By Hafsa Muhammed B08-00623-12-10

Page 2: hafsa  (the_best)

Contents

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

2. Planning2.1. Project integration management

2.1.1. Project Management Plan . . . . . 14

2.2 Project Scope Management2.1.2. Requirement Document. . . . . . 202.1.3. Scope Statement . . . . . . 222.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 . . . . . . . 412.8.2. Risk Management Plan . . . . . . 42

2.9. Project Procurement Management2.9.1 Procurement Plan . . . . . . . 45

Page 3: hafsa  (the_best)

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

System should be scalable

Page 4: hafsa  (the_best)

System should have well described and clear documentation so that it may

give clear idea regarding system.

2.2. Business

System should fulfill all requirements specified by the university but

meanwhile it should be general enough for different projects.

2.3. Quality

System should be 75% tested before use.

System should follow IEEE standards in testing, deployment, configuration

management.

System should be developed using the ISO 9216 quality standard.

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

Page 5: hafsa  (the_best)

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

Management

Earn Revenue

by reaching

more students

Strongly

Supportive

Usability,

extensibility and

reliability

System should be

made extensible

for future purpose.

Faculty Member ------------------- Neutral Performance and

Security

----------------------

--

Administrator -------------------

--

Neutral Performance System should be

useable on

minimum of

512kpbs

Students Able to gain

quality

education at

home

Strongly

Supportive

Usability,

efficiency,

performance

System should be

easy to use and

operate.

HEC Promote

Higher

Education in

Pakistan

Strongly

Supportive

Reliability The tool should be

developed within

0.5 million of

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

Page 6: hafsa  (the_best)

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

Page 7: hafsa  (the_best)

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:

Info service

Comprehensive information library

7. Assumptions and Dependencies

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

The system should develop within the 0.5 million budget

granted by HEC.

Page 8: hafsa  (the_best)

The system should be deployed and operation within 6 months.

The system should be interoperatable with the current system of

C@SE University.

9. Business Risks

Risk Probability Impact Mitigation

There is a risk of network failure we

need experts to handle such errors.

70% Severe We need to maintain session

information to save and restart

system from that point.

For data bases we need strong tool to

avoid loss of data.

40% Severe We need to have backup server

to avoid this situation.

10. Resources

10.1. 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.

10.2. Software licenses

System should be licensed so that it should not get illegally

used or copied. It is owned by C@SE University.

10.3. Consulting

Three meetings (one with student representative and 2 with

university representatives) will be conducted before the start of

Page 9: hafsa  (the_best)

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.

10.4. 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.

10.5. External Training Requirements:

We need some extra training for our team members as it is their

first online project and they must be equipped with latest tools

to cope with the current challenges of technology.

Page 10: hafsa  (the_best)

11. Project Responsibility Matrix:

Activity Responsible Person

Acquiring Resources Saima Imtiaz

Assigning and managing resources Saima Imtiaz

Requirement gathering, specification and

validationRabia Malik

Designing User interface, validating User

interfacesRabila Malik

Design application including database

designSaima Imtiaz

Implementation and testing Samya Kashif

Acceptance testing of the system Samya Kashif

User Manuals and HelpRabia Malik and

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

Page 11: hafsa  (the_best)

President of C@SE

UNIVERSITY

Mr. Hassan Akhtar 12th August 2010

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

System

12th August

2010

-----------------------------------------------------

-----

1.0

Stakeholder RegisterName Position Role Contact

Information

Requirements Expectations

Page 12: hafsa  (the_best)

Mr. Hassan Akhtar

President of C@SE University

Investor/clients

092-51-9155556

Functionality, cost and schedule of the system 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.

Project should be done in the given budget and in the required timeline.

Dr. Ali Ahsan

Head of Software Development

Overseeing authority

092-51-9155555

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.Functionality, cost and schedule of the system 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 Project Manager

Manager responsible for online education program

092-51-9155554

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.

Saima Imtiaz

Requirement Engineer

Acquiring and Managing Resource

092-51-9155553

All the non functional and functional requirements of the desired system.

All the resources needed are properly acquired and managed.

Data base Manager

Design application including database design

System Requirement Specification document and software requirement specification documentation are also required.

The design of the database should cover all aspects of requirements.

Page 13: hafsa  (the_best)

Rabia Malik

Requirement Engineer

Requirement gathering, specification and validation

092-51-9155552

All the non functional and functional requirements of the desired system

All the requirements should be gathered with specifications and should be validated.

Software Engineer

Designing User interface, validating User interfaces

Complete database is required.

The user interface should be designed according to the requirements and should be validated.

User Manuals and Help

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

Help and guidance needed for system is provided

Samya Kashif

Tester Implementation and acceptance testing of the system

User Manuals and Help

092-51-9155551

Executable code should be provide to her so that she can perform various tests on it and validate it.

The code executes properly and no error is found.

Help and guidance needed for system is provided.

Technical writer

Project Management PlanProduct Scope Description:This project is made for a C@SE University which wants to conduct online education in PakistanThe proposed software product is the Online Education System (OES). The system will

Page 14: hafsa  (the_best)

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.

Role: Responsibility:Investor/ clients

To invest in the projectHe 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 Development

Experienced and objective technical and management oversight from individuals who are not directly involved in the project

Page 15: hafsa  (the_best)

Project Manager

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 ofproject 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 technicaldecisions to the appropriate technical lead. Resolves disputes betweenproject participants. Responsible for coordinating the activities with thestakeholders, project sponsor, and project reviewers

Requirement Engineer

Acquiring and Managing ResourceIn charge of eliciting, defining, maintaining, and tracing detailed productrequirements.

Data base Administrator

Design application including database designResponsible for the system architecture and overseeing design activities.As appropriate may assign sub-leads for functional areas of the product orfor technical specialties such as database, graphics, driver, distributedprocessing, communications protocol, etc.

Requirement Engineer

Requirement gathering, specification and validationIn charge of eliciting, defining, maintaining, and tracing detailed productRequirements.

Software Engineer

Designing User interface, validating User interfacesA pool of software engineers that can be assigned various tasks on a project based on ability and interest

TesterDesign and document test cases, execute test cases, record test case results, document and track defects, and perform test coverage analysis.

Technical WritersThey 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

Page 16: hafsa  (the_best)

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 members

Team leader Once A Week

Performance Review Meetings (Presentations)

Team leader Project Manager

Once a month

Presentations Investor Project manager, team &

After achieving a milestone or once in 2 months

Page 17: hafsa  (the_best)

head of department

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

Page 18: hafsa  (the_best)

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 planStart of Project 1-sep -2010End of Project 7- feb-2011Duration 114 daysWork 8504 hoursCost $106,100Completed work 0% (only planning not estimation)

Work plan/ MilestonesMilestone 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

Page 19: hafsa  (the_best)

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:-InternetPMBOK 4RTH Edition

Requirement Documentation

Stakeholder Requirement Category Priority Acceptance Criteria

Mr. Hassan Akhtar Functionality, cost and schedule of the system should be according to the criteria given in project

Contract requirements

HighProject should be done in the given budget and in the required timeline.

Page 20: hafsa  (the_best)

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 schedule of the system should be according to the criteria given in project scope.Functionality, cost and schedule of the system should be according to the criteria given in project scope.

Development requirements

HighProject 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

HighSchedule should be followed accurately and the required functionality must be delivered.

Page 21: hafsa  (the_best)

Saima Imtiaz

All the non functional and functional requirements of the desired systemSystem Requirement Specification document and software requirement specification documentation are also required

Operation requirements

MediumAll the resources needed are properly acquired and managed. The design of the database should cover all aspects of requirements.

Rabia Malik

All the non functional and functional requirements of the desired system

Complete database is required.

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

Operation requirements

MediumAll the requirements should be gathered with specifications and should be validated.

Help and guidance needed for system is provided

The user interface should be designed according to the requirements and should be validated.

Samya Kashif

Executable code should be provide to her so that she can perform various tests on it and validate it.

Performance requirement

HighThe code executes properly and no error is found.

Help and guidance needed for system is provided.

Page 22: hafsa  (the_best)

Project Scope statement

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

Page 23: hafsa  (the_best)

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

Page 24: hafsa  (the_best)

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.

Page 25: hafsa  (the_best)

Activity list

ID WBS Task Name Duration Start Finish Predecessors

1 1 ONLINE EDUCATION SYSTEM 114 days W ed 9/1/10 Mon 2/7/112 1.1 PROJECT MANAGEMENT 107 days W ed 9/1/10 Thu 1/27/113 1.1.1 Planning and Estimation 20 days Wed 9/1/10 Tue 9/28/10

4 1.1.2 Organizing & Staffing 39 days Wed 9/29/10 Mon 11/22/10 3

5 1.1.3 Directing 52 days Wed 9/29/10 Thu 12/9/10 3

6 1.1.4 Project Management Plan 0 days Tue 9/28/10 Tue 9/28/10 3

7 1.1.5 Monitor & Control 87 days Wed 9/29/10 Thu 1/27/11 6

8 1.2 PRODUCT REQUIREMENT 78 days W ed 9/1/10 Fri 12/17/109 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 Done0 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 DETAIL DESIGN 60 days Fri 9/10/10 Thu 12/2/10 918 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 Thu 12/2/10

20 1.3.3 Detail Design Done 0 days Thu 12/2/10 Thu 12/2/10 18,19

21 1.4 DEVELOPMENT 25 days Fri 12/3/10 Thu 1/6/11 1722 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 20 days Fri 12/3/10 Thu 12/30/10

25 1.4.4 Implementing Business Layer 4 days Fri 12/31/10 Wed 1/5/11 24

26 1.5 INTEGRATION AND TESTING 47 days Fri 12/3/10 Mon 2/7/1127 1.5.1 Unit Testing 25 days Fri 12/3/10 Thu 1/6/11 22SS

28 1.5.2 Integration Testing 20 days Fri 1/7/11 Thu 2/3/11 27

29 1.5.3 System Testing 2 days Fri 2/4/11 Mon 2/7/11 28

30 1.5.4 System Testing Done 0 days Mon 2/7/11 Mon 2/7/11 29

31 1.5.5 Project Closing 0 days Mon 2/7/11 Mon 2/7/11 29

PC1[1],SaimaPC3[1],Nadia,Sadia

Daud,PC4[1]9/28

Khawar,Raza,Eshal,PC5[1]

Nadeem,Shahrukh,Salman,PC6[1]9/9PC7[1],Eshal,Naveed,PC11[1]9/23

PC7[1],Hafsa11/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]

PC8[1],SaraSamya[50%],Huma[50%],PC6[1],PC12[1]Salman,Huma,Naveed,PC12[1]2/72/7

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 JHalf 1, 2010 Half 2, 2010 Half 1, 2011 Half 2, 2011 Half 1, 2012

Page 26: hafsa  (the_best)

Milestone Plan

Milestone Milestone Description Type

Project Management plan Project Management plan 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

Page 27: hafsa  (the_best)

Project schedule Network Diagram

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: Daud, PC4[1]

Sof twar e Re qui re m ent Sp e ci fic a tion

St art : 9/1/10 ID: 9

Finish: 9/ 9/10 Dur: 7 days

Res: Nadeem, Shahrukh, Salman, PC6[1]

Sys te m Re quir em e nts Spe c ifi ca ti on

St art : 9/10/10 ID: 11

Finish: 9/ 23/ 10 Dur: 10 days

Res: PC7[1] , Eshal, Naveed, PC11[ 1]

Use r Do c ume n ta tion

St art : 9/1/10 ID: 13

Finish: 11/5/ 10 Dur: 48 days

Res: PC7[1] , Hafsa

Tra in in g M ater ia l

St art : 9/1/10 ID: 15

Finish: 12/17/10 Dur: 26 days

Res: Amal, PC8[1]

DET AIL DESIGN

St art : 9/10/10 ID: 17

Finish: 12/2/ 10 Dur: 60 days

Comp: 0%

PRODUCT REQUIREMENT

St art : 9/1/10 ID: 8

Finish: 12/17/10 Dur: 78 days

Comp: 0%

Imp le m e nt ing Bus ines s Lay e r

St art : 12/ 31/ 10 ID: 25

Finish: 1/ 5/11 Dur: 4 days

Res: Naveed, Umer[50%], PC3[1] , PC4[ 1]

Fro nt E nd De ve lop ed

Milest one Date: Thu 1/6/ 11

ID: 23

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]

Des ign ing Us e r I nt erfa ce

St art : 9/10/10 ID: 18

Finish: 10/21/10 Dur: 30 days

Res: Far wa, Shahr ukh, Nadeem, PC9[ 1], PC10[ 1], PC11[ 1]

SRS Do ne

Milest one Date: Thu 9/9/ 10

ID: 10

Use r M anu al

Milest one Date: Fr i 11/5/ 10

ID: 14

Tra in in g M at er ia l

Milest one Date: Fr i 12/17/10

ID: 16

PROJ ECT M ANAGEMENT

St art : 9/1/10 ID: 2

Finish: 1/ 27/ 11 Dur: 107 days

Comp: 0%

Pla nnin g a nd Es tima ti on

St art : 9/1/10 ID: 3

Finish: 9/ 28/ 10 Dur: 20 days

Res: PC1[1] , Saima

Pro je ct Ma na g em e nt Pla n

Milest one Date: Tue 9/28/10

ID: 6

Mo ni to r & Cont ro l

St art : 9/29/10 ID: 7

Finish: 1/ 27/ 11 Dur: 87 days

Res: Khawar , Raza, Eshal, PC5[ 1]

Sys te m Re quir em e nt Spec if ic at ion Don e

Milest one Date: Thu 9/23/10

ID: 12

Det ai l De si gn Done

Milest one Date: Thu 12/2/10

ID: 20

Dev e lo pm e nt o f Front En d

St art : 12/ 3/10 ID: 22

Finish: 1/ 6/11 Dur: 25 days

Res: Ali, Far wa, PC9[1], PC10[1]

imp le m e nt ing da ta bas e

St art : 12/ 3/10 ID: 24

Finish: 12/30/10 Dur: 20 days

Res: Humza, PC12[1] , PC6[ 1], Saga[ 50%]

Sys te m Te st in g

St art : 2/4/11 ID: 29

Finish: 2/ 7/11 Dur: 2 days

Res: Salman, Huma, Naveed, PC12[1]

In te gra tion Tes ti ng

St art : 1/7/11 ID: 28

Finish: 2/ 3/11 Dur: 20 days

Res: Samya[50%] , Huma[50%], PC6[1] , PC12[1]

Uni t Te st in g

St art : 12/ 3/10 ID: 27

Finish: 1/ 6/11 Dur: 25 days

Res: PC8[1] , Sara

INT EGRATION AND TESTING

St art : 12/ 3/10 ID: 26

Finish: 2/ 7/11 Dur: 47 days

Comp: 0%

DEV ELOPM ENT

St art : 12/ 3/10 ID: 21

Finish: 1/ 6/11 Dur: 25 days

Comp: 0%

ONL INE EDUCAT ION SYSTEM

St art : 9/1/10 ID: 1

Finish: 2/ 7/11 Dur: 114 days

Comp: 0%

Page 28: hafsa  (the_best)

Activity Resource Requirement

Page 29: hafsa  (the_best)

Critical Tasks

Page 30: hafsa  (the_best)

Qual i ty Management Plan

Quality Assurance Approach:

Process Improvement model:-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 client’s 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

List of control and monitoring staff1. Eshal

2. Raza

3. Khawar

Page 31: hafsa  (the_best)

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

Page 32: hafsa  (the_best)

Human Resource Plan

Role: Responsibility:

Page 33: hafsa  (the_best)

Investor/ clients

To invest in the projectHe 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 Development

Experienced and objective technical and management oversight from individuals who are not directly involved in the project

Project Manager

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 ofproject 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 technicaldecisions to the appropriate technical lead. Resolves disputes betweenproject participants. Responsible for coordinating the activities with thestakeholders, project sponsor, and project reviewers

Page 34: hafsa  (the_best)

Requirement Engineer

Acquiring and Managing ResourceIn charge of eliciting, defining, maintaining, and tracing detailed productrequirements.

Data base Administrator

Design application including database designResponsible for the system architecture and overseeing design activities.As appropriate may assign sub-leads for functional areas of the product orfor technical specialties such as database, graphics, driver, distributedprocessing, communications protocol, etc.

Requirement Engineer

Requirement gathering, specification and validationIn charge of eliciting, defining, maintaining, and tracing detailed productRequirements.

Software Engineer

Designing User interface, validating User interfacesA pool of software engineers that can be assigned various tasks on a project based on ability and interest

TesterDesign and document test cases, execute test cases, record test case results, document and track defects, and perform test coverage analysis.

Technical WritersThey 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

Page 35: hafsa  (the_best)

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.

Page 36: hafsa  (the_best)

Resource Calendars:

Page 37: hafsa  (the_best)

STAKEHOLDER MANAGEMENT STRATEGYName Influence Involvement

AssessmentStrategies

Page 38: hafsa  (the_best)

Mr. Hassan

Akhtar

High

Influence

Low Involvement

To have a unique and reliable, high quality system.

Dr. Ali Ahsan High

Influence

Medium Involvement

To deliver a unique reliable and high quality system to Mr. Hassan Akhtar.

Tahira Medium

Influence

High Involvement

To produce a high quality system according to the given budget and schedule and the

requirements.

Saima

Imtiaz

Low

Influence

Very high involvement

To do the specified job according to the criteria set by the project management

Rabia Malik

Low

Influence

Very high involvement

To do the specified job according to the criteria set by the project management

Samya

Kashif

Low

Influence

Very high involvement

To do the specified job according to the criteria set by the project management

Communication Management Plan

Method Audience Conductors Frequency

Page 39: hafsa  (the_best)

Performance status Reports Team members

Team leader Once A Week

Performance Review Meetings (Presentations)

Team leader Project Manager

Once a month

Term or Acronym

Definition

Performance Review Meetings

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.

Performance status reports

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 what’s being done about it

Communication Constraints or Assumptions:

Performance Review Meetings : Must be conducted once a monthPerformance Status reports : Must be conducted once a week

Risk Register

Risk Risk Statement Probability Impact

Page 40: hafsa  (the_best)

ID Scope Quality Schedule Cost1 Pc’s not working properly .40

2 Network not working properly

0.30

3 Unexpected holidays 0.04

4 Programmer not available due to unforeseen event

.20

5 Electricity cutoff(unexpected)

.05

6 Natural Disasters .01

Risk Management Plan

Methods and approaches

Page 41: hafsa  (the_best)

Risk ID

Risk Statement Methods and approaches

1 Pc’s 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 event

Same competency and qualification 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

Page 42: hafsa  (the_best)

Responsibilities

Risk ID

Risk Statement Responsibility

1 Pc’s not working properly Administrator

2 Network not working properly Network Administrator

3 Unexpected holidays Administrator

4 Programmer not available due to unforeseen event

Team Leader

5 Electricity cutoff(unexpected) Administrator

6 Natural Disasters NA

Page 43: hafsa  (the_best)

Risk Categories

Risk ID

Risk Statement Risk Category

1 Pc’s not working properly Operational Risk

2 Network not working properly Technical Risk

3 Unexpected holidays Environmental risk

4 Programmer not available due to unforeseen event

Resource risk

5 Electricity cutoff(unexpected) Operational risk

6 Natural Disasters Environmental Risk

Stakeholder Risk Tolerance:

General Risks Level of Stakeholder Risk Tolerance

Quality Cannot be compromised on

Page 44: hafsa  (the_best)

Schedule A little delay can be compromised

Cost Change will not be acceptable

Probability of risk

Risk ID

Risk Statement Probability Risk expectancy of occurring

1 Pc’s 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 unforeseen event

.20 Moderate

5 Electricity cutoff(unexpected) .05 Very low

6 Natural Disasters .01 Very low

Probability and Impact by Objective matrix:Risks Pc problem Network

ProblemHoliday Risk

Unavailability of programmer

Electricity Problem

Natural Disaster

Page 45: hafsa  (the_best)

Risks probability

40% 30% 4% 20% 5% 1%

Cost20%-40% increase

10%-20%

increase

Insignificant increase 10-20%

increase

Insignificant increase

Insignificant increase

Time10%-20% increase

5%-10% increase

Insignificant increase

5-10% increase

Insignificant increase

Insignificant increase

Scope Scope reduction

unacceptable by investor

Major areas of scope

affected

Decrease barely

noticeable

Major areas of scope affected

Decrease barely

noticeable

Decrease barely

noticeable

Quality Quality reduction

unacceptable by investor

Quality reduction requires investors approval

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

Page 46: hafsa  (the_best)

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 don’t have one. Our work is done on computers and we had already bought them in past for some other project so we don’t need to procure anything else.

Roles and Responsibilities:

Roles ResponsibilitiesHead 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 Advertisement3. 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.

Page 47: hafsa  (the_best)