online education system project report
Upcoming SlideShare
Loading in...5
×

Like this? Share it with your network

Share

online education system project report

  • 3,772 views
Uploaded on

online education system project report

online education system project report

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
No Downloads

Views

Total Views
3,772
On Slideshare
3,771
From Embeds
1
Number of Embeds
1

Actions

Shares
Downloads
218
Comments
0
Likes
3

Embeds 1

https://twitter.com 1

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. CASE Online Education System Project Plan and Initiation By Hafsa Muhammed B08-006 23-12-10
  • 2. 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
  • 3. 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
  • 4.  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 belong all around the world are also major
  • 5. 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 to do jobs. The university timings may not be suitable to such students. The online
  • 6. 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  Course evaluation (quizzes)
  • 7.  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.  The system should be deployed and operation within 6 months.
  • 8.  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 project, to gather information and one meeting with both type
  • 9. 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.
  • 10. 11. Project Responsibility Matrix: Activity Responsible Person Acquiring Resources Saima Imtiaz Assigning and managing resources Saima Imtiaz Requirement gathering, specification and validation Rabia Malik Designing User interface, validating User interfaces Rabila Malik Design application including database design Saima Imtiaz Implementation and testing Samya Kashif Acceptance testing of the system Samya Kashif User Manuals and Help Rabia 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 President of C@SE UNIVERSITY Mr. Hassan Akhtar 12th August 2010
  • 11. 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 Register Name Position Role Contact Informatio n Requirements Expectations Mr. Hassan Akhtar President of C@SE University Investor/client s 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 Project should be done in the given budget and in the required timeline.
  • 12. knows on which specifications the system will be delivered to him. 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. 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
  • 13. 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 Implementatio n 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 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
  • 14. 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.
  • 15. Project Deliverables:
  • 16. Role: Responsibility: Investor/ clients To invest in the project He is part of inception, approves resources for the project, directly oversees the project business manager, and is responsible for the project meeting the goals of all stakeholders. 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 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 Requirement Engineer Acquiring and Managing Resource In charge of eliciting, defining, maintaining, and tracing detailed product requirements. Data base Administrator Design application including database design Responsible for the system architecture and overseeing design activities. As appropriate may assign sub-leads for functional areas of the product or for technical specialties such as database, graphics, driver, distributed processing, communications protocol, etc. Requirement Engineer Requirement gathering, specification and validation In charge of eliciting, defining, maintaining, and tracing detailed product Requirements. Software Engineer Designing User interface, validating User interfaces A pool of software engineers that can be assigned various tasks on a project based on ability and interest Tester Design and document test cases, execute test cases, record test case results, document and track defects, and perform test coverage analysis. Technical Writers They document processes and other user manuals, create online courses and product demonstrations Staff Acquisition: Following staff is acquired for our project:- • Project manager • Financial analyst • Requirement engineers • Configuration manager • Software Engineer
  • 17. 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 & head of department After achieving a milestone or once in 2 months Roles and responsibility Resources • Hardware Resources  All team members will require laptops/systems.  One projector will be required for consultancy sessions to brief the audience  One printer will be used to print the documents and agreements of the project  Scanner may be required for designing the interfaces of the system.  Internet connection will be required.
  • 18. • Software licenses  System should be licensed so that it should not get illegally used or copied. It is owned by C@SE University. • Consulting  Three meetings (one with student representative and 2 with university representatives) will be conducted before the start of project, to gather information and one meeting with both type of representatives will be conducted after the completion of each phase in order to ensure that work is going on as required by the stakeholders and one meeting of project team and related department representatives (finance department, accounts department etc) will be arranged in order to analyze whether the project is going with the same progress as planned or we need some modifications. In total we will need approximately 10 consultation sessions. • Staffing Requirements:  A project manager is required.  One financial analyst is required.  We need 2 requirement engineers for gathering requirements, one for gathering requirements from user side and second for gathering requirements from university faculty and other stakeholders.  A group of three analysts is required to analyze and specify the requirements.  We will require 2 designers to plan the architecture of the project  4 members are required to work as coders  2 testers will be hired.
  • 19.  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
  • 20. 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 scope. He should have contract so that he knows on which specifications the system will be delivered to him. Contract requirements High Project should be done in the given budget and in the required timeline. 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 High Project should be done according to the specified time period and results in profit. Tahira Project is done according to the criteria mentioned by the overseeing authority. Feasibility report, project charter should be provided to the project manager Operation requirements High Schedule should be followed accurately and the required functionality must be delivered.
  • 21. Saima Imtiaz All the non functional and functional requirements of the desired system System Requirement Specification document and software requirement specification documentation are also required Operation requirements Medium All 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 Medium All 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 High The code executes properly and no error is found. Help and guidance needed for system is provided.
  • 22. 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
  • 23. Project Deliverables: • 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
  • 24. 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.
  • 25. Activity list ID WBS TaskName Duration Start Finish Predecessors 1 1 ONLINE EDUCATION SYSTEM 114days Wed 9/1/10 Mon2/7/11 2 1.1 PROJECT MANAGEMENT 107days Wed 9/1/10 Thu 1/27/11 3 1.1.1 Planning andEstimation 20days Wed9/1/10 Tue9/28/10 4 1.1.2 Organizing &Staffing 39days Wed9/29/10 Mon11/22/10 3 5 1.1.3 Directing 52days Wed9/29/10 Thu12/9/10 3 6 1.1.4 Project ManagementPlan 0days Tue9/28/10 Tue9/28/10 3 7 1.1.5 Monitor & Control 87days Wed9/29/10 Thu1/27/11 6 8 1.2 PRODUCT REQUIREMENT 78days Wed 9/1/10 Fri12/17/10 9 1.2.1 SoftwareRequirement Specification7days Wed9/1/10 Thu9/9/10 10 1.2.2 SRSDone 0days Thu9/9/10 Thu9/9/10 9 11 1.2.3 SystemRequirements Specification10days Fri 9/10/10 Thu9/23/10 10 12 1.2.4 SystemRequirementSpecificationDone0days Thu9/23/10 Thu9/23/10 11 13 1.2.5 User Documentation 48days Wed9/1/10 Fri 11/5/10 14 1.2.6 User Manual 0days Fri 11/5/10 Fri 11/5/10 13 15 1.2.7 Training Material 26days Wed9/1/10 Fri 12/17/10 16 1.2.8 Training Material 0days Fri 12/17/10 Fri 12/17/10 15 17 1.3 DETAIL DESIGN 60days Fri9/10/10 Thu 12/2/10 9 18 1.3.1 Designing User Interface 30days Fri 9/10/10 Thu10/21/10 19 1.3.2 Designing Database 60days Fri 9/10/10 Thu12/2/10 20 1.3.3 Detail DesignDone 0days Thu12/2/10 Thu12/2/10 18,19 21 1.4 DEVELOPMENT 25days Fri12/3/10 Thu 1/6/11 17 22 1.4.1 Developmentof FrontEnd 25days Fri 12/3/10 Thu1/6/11 23 1.4.2 Front EndDeveloped 0days Thu1/6/11 Thu1/6/11 22 24 1.4.3 implementing database 20days Fri 12/3/10 Thu12/30/10 25 1.4.4 Implementing Business Layer 4days Fri 12/31/10 Wed1/5/11 24 26 1.5 INTEGRATION AND TESTING 47days Fri12/3/10 Mon2/7/11 27 1.5.1 UnitTesting 25days Fri 12/3/10 Thu1/6/11 22SS 28 1.5.2 IntegrationTesting 20days Fri 1/7/11 Thu2/3/11 27 29 1.5.3 SystemTesting 2days Fri 2/4/11 Mon2/7/11 28 30 1.5.4 SystemTesting Done 0days Mon2/7/11 Mon2/7/11 29 31 1.5.5 Project Closing 0days Mon2/7/11 Mon2/7/11 29 PC1[1],Saima PC3[1],Nadia,Sadia Daud,PC4[1] 9/28 Khawar,Raza,Eshal,PC5[1] Nadeem,Shahrukh,Salman,PC6[1] 9/9 PC7[1],Eshal,Naveed,PC11[1] 9/23 PC7[1],Hafsa 11/5 Amal,PC8[1] 12/17 Farwa,Shahrukh,Nadeem,PC9[1],PC10[1],PC11[1] Humza,PC12[1] 12/2 Ali,Farwa,PC9[1],PC10[1] 1/6 Humza,PC12[1],PC6[1],Saga[50%] Naveed,Umer[50%],PC3[1],PC4[1] PC8[1],Sara Samya[50%],Huma[50%],PC6[1],PC12[1] Salman,Huma,Naveed,PC12[1] 2/7 2/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 Half1,2010 Half2,2010 Half1,2011 Half2,2011 Half1,2012
  • 26. 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
  • 27. Project schedule Network Diagram Organizing &Staffing St art : 9/29/10 ID: 4 Finish: 11/22/10 Dur: 39 days Res: PC3[1] , Nadia, Sadia Directing St art : 9/29/10 ID: 5 Finish: 12/9/ 10 Dur: 52 days Res: Daud, PC4[1] Software Requi rement Specification St art : 9/1/10 ID: 9 Finish: 9/ 9/10 Dur: 7days Res: Nadeem, Shahrukh, Salman, PC6[1] System Requirements Specifi cati on St art : 9/10/10 ID: 11 Finish: 9/ 23/ 10 Dur: 10 days Res: PC7[1] , Eshal, Naveed, PC11[ 1] User Documentation St art : 9/1/10 ID: 13 Finish: 11/5/ 10 Dur: 48 days Res: PC7[1] , Hafs a Training Material St art : 9/1/10 ID: 15 Finish: 12/17/10 Dur: 26 days Res: Amal, PC8[1] DETAIL 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% Implementing Business Layer St art : 12/ 31/ 10 ID: 25 Finish: 1/ 5/11 Dur: 4days Res: Naveed, Umer[50%], PC3[1] , PC4[ 1] Front End Developed Milest one Date: Thu1/6/ 11 ID: 23 Designing Database St art : 9/10/10 ID: 19 Finish: 12/2/ 10 Dur: 60 days Res: Humza, PC12[1] Designing UserInterface 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 Done Milest one Date: Thu9/9/ 10 ID: 10 User Manual Milest one Date: Fr i11/5/ 10 ID: 14 Training Material Milest one Date: Fr i12/17/10 ID: 16 PROJECT MANAGEMENT St art : 9/1/10 ID: 2 Finish: 1/ 27/ 11 Dur: 107 days Comp: 0% Planning and Estimation St art : 9/1/10 ID: 3 Finish: 9/ 28/ 10 Dur: 20 days Res: PC1[1] , Saima Project ManagementPlan Milest one Date: Tue9/28/10 ID: 6 Monitor& Control St art : 9/29/10 ID: 7 Finish: 1/ 27/ 11 Dur: 87 days Res: Khawar , Raza, Eshal, PC5[ 1] System RequirementSpecification Done Milest one Date: Thu9/23/10 ID: 12 Detail Design Done Milest one Date: Thu12/2/10 ID: 20 Developmentof Front End St art : 12/ 3/10 ID: 22 Finish: 1/ 6/11 Dur: 25 days Res: Ali, Far wa, PC9[1], PC10[1] implementing database St art : 12/ 3/10 ID: 24 Finish: 12/30/10 Dur: 20 days Res: Humza, PC12[1] , PC6[ 1], Saga[ 50%] System Testing St art : 2/4/11 ID: 29 Finish: 2/ 7/11 Dur: 2days Res: Salman, Huma, Naveed, PC12[1] Integration Testing St art : 1/7/11 ID: 28 Finish: 2/ 3/11 Dur: 20 days Res: Samya[50%] , Huma[50%], PC6[1] , PC12[1] UnitTesting St art : 12/ 3/10 ID: 27 Finish: 1/ 6/11 Dur: 25 days Res: PC8[1] , Sara INTEGRATIONAND TESTING St art : 12/ 3/10 ID: 26 Finish: 2/ 7/11 Dur: 47 days Comp: 0% DEVELOPMENT St art : 12/ 3/10 ID: 21 Finish: 1/ 6/11 Dur: 25 days Comp: 0% ONLINE EDUCATION SYSTEM St art : 9/1/10 ID: 1 Finish: 2/ 7/11 Dur: 114 days Comp: 0%
  • 28. Activity Resource Requirement
  • 29. Critical Tasks
  • 30. Quality 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. List of control and monitoring staff 1. Eshal 2. Raza 3. Khawar
  • 31. 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
  • 32. Budget Estimate
  • 33. Human Resource Plan
  • 34. Role: Responsibility: Investor/ clients To invest in the project He is part of inception, approves resources for the project, directly oversees the project business manager, and is responsible for the project meeting the goals of all stakeholders. 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 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 Requirement Engineer Acquiring and Managing Resource In charge of eliciting, defining, maintaining, and tracing detailed product requirements. Data base Administrator Design application including database design Responsible for the system architecture and overseeing design activities. As appropriate may assign sub-leads for functional areas of the product or for technical specialties such as database, graphics, driver, distributed processing, communications protocol, etc. Requirement Engineer Requirement gathering, specification and validation In charge of eliciting, defining, maintaining, and tracing detailed product Requirements. Software Engineer Designing User interface, validating User interfaces A pool of software engineers that can be assigned various tasks on a project based on ability and interest Tester Design and document test cases, execute test cases, record test case results, document and track defects, and perform test coverage analysis. Technical Writers They document processes and other user manuals, create online courses and product demonstrations Staff Acquisition: Following staff is acquired for our project:- • Project manager • Financial analyst • Requirement engineers • Configuration manager • Software Engineer
  • 35. 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.
  • 36. Resource Calendars:
  • 37. STAKEHOLDER MANAGEMENT STRATEGY
  • 38. Communication Management Plan Name Influence Involvement Assessment Strategies 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
  • 39. Method Audience Conductors Frequency 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 month Performance Status reports : Must be conducted once a week Risk Register
  • 40. Risk ID Risk Statement Probability Impact Scope Quality Schedule Cost 1 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
  • 41. 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
  • 42. 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
  • 43. Risk Categories Ris k 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
  • 44. 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 Problem Holiday Risk Unavailability of programmer Electricity Problem Natural Disaster
  • 45. Risks probability 40% 30% 4% 20% 5% 1% Cost 20%-40% increase 10%- 20% increase Insignificant increase 10-20% increase Insignificant increase Insignificant increase Time 10%-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
  • 46. 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 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.