SOFTWARE PROJECT MANAGEMENT PLAN NEXUS Rescue Management System Document Revision #: 1.
3 Date of Issue: 12th Nov, 2013 Project Manager: Ahsan Shakeel
Software Project Management Plan
Rescue Management System
Approval Signatures
MUSA RAJA ( CEO )
Approved by: Business Project Leader
MASHOOD SHAUKAT (CIO)
Approved by: IM/IT Project Leader
Version: 1.3
Issue Date: 12th November 2013
Page i
Software Project Management Plan
Rescue Management System
PREFACE
Software Project Management Plan specifies the technical and managerial approaches to develop the software product. It is Companion document to requirements analysis document. Changes in either may imply changes in the other document. SPMP may be part of project agreement. Project agreement: Document written for a client that defines the scope, duration, cost and deliverables for the project, the exact items, quantities, delivery dates, delivery location. It can be a contract, a statement of work, a business plan, or a project charter. Moreover, it specifies the process model for the project and its organizational structure. In addition, the project specifies the technical methods, tools, and techniques to be used on the project. It also includes identification of the work products and reviews to be held and the plans for the support group activities in user documentation, training, software quality assurance, and configuration management as shown. Lastly it also specifies the work packages, dependency relationships, resource requirements, allocation of budget and resources to work packages, and a project schedule.
Organisation NEXUS Owner Musa Raja
Title/Subject SPMP Approved by Mashood Shaukat
Number 1.2
th
Date 12 Nov, 2013
1.2
Page ii
Software Project Management Plan
Rescue Management System
TABLE OF FIGURES
Figure 1: Senior projects committee....................................................... 10 Figure 2:functions division ..................................................................... 27 Figure 3:Quality control ......................................................................... 33
TABLES
Table 1 Version History ....................................................................... ix Table 2: Project Deliverables Documentations ...................................... 3 Table 3: Schedule of Documentation ..................................................... 4 Table 4: Estimated Budget ..................................................................... 5 Table 5: Evolution of the Plan ................................................................ 6 Table 6 : Senior Management................................................................ 11 Table 7: Requirements team ................................................................ 12 Table 8: Design team ............................................................................ 13 Table 9: Testing team ........................................................................... 13 Table 10: Verification team ................................................................... 14 Table 11 : Role and Responsibility ........................................................ 15
Organisation NEXUS Owner Musa Raja
Title/Subject SPMP Approved by Mashood Shaukat
Number 1.2
th
Date 12 Nov, 2013
1.2
Page iii
Software Project Management Plan
Rescue Management System
Table 12: Staff training responsibilities ................................................ 18 Table 13: Complete Work Plan ............................................................. 20 Table 14: Work Breakdown Of SPMP .................................................. 21 Table 15: Work Breakdown Of SRS ..................................................... 21 Table 16: Work Breakdown Of SDD .................................................... 22 Table 17: Work Breakdown Of Coding and Testing ............................ 22 Table 18: Work Breakdown Of Demo .................................................. 23 Table 19: Resource for work activity .................................................... 29 Table 20: SW and HW used .................................................................. 30 Table 21: Budget Allocation.................................................................. 31 Table 22: Risk Management Plan.......................................................... 36 Table 23: Process Model ....................................................................... 38 Table 24: Infrastructure ......................................................................... 39
Organisation NEXUS Owner Musa Raja
Title/Subject SPMP Approved by Mashood Shaukat
Number 1.2
th
Date 12 Nov, 2013
1.2
Page iv
Software Project Management Plan
Rescue Management System
Contents
Version History ...................................................................... ix 1. Project Overview ....................................................................... 1 1.1 Purpose ................................................................................. 1 1.2 Scope .................................................................................... 1 1.3 Objectives .............................................................................. 1 1.4 Assumptions, Constraints and Risks...................................... 2 1.5 Project Deliverables ............................................................... 3 1.5.1 Documentations ......................................................... 3
1.5.2 Other Deliverables ........................................................ 4 1.6 Schedule and Budget Summary ............................................ 4 1.6.1Schedule........................................................................ 4 1.6.2Budget ........................................................................... 5 1.7 Evolution of the Plan .............................................................. 6 1.8 References ............................................................................ 7 1.9 Definitions and Acronyms ...................................................... 9 2. Project Organization ............................................................... 10
Organisation NEXUS Owner Musa Raja
Title/Subject SPMP Approved by Mashood Shaukat
Number 1.2
th
Date 12 Nov, 2013
1.2
Page v
Software Project Management Plan
Rescue Management System
2.1 External Interfaces ............................................................... 10 2.2 Internal Structure ................................................................. 10 Members ................................................................................... 11 3. Managerial Process Plans ...................................................... 16 3.1 Start-up Plan........................................................................ 16 3.1.1Estimates ..................................................................... 16 3.1.2Staffing ........................................................................ 16 3.1.3Resource Acquisition ................................................... 16 3.1.4Project Staff Training ................................................... 17 3.2 Work Plan ............................................................................ 19 3.2.1Work Breakdown Structure .......................................... 19 3.2.2Schedule Allocation ..................................................... 23 FUNCTIONAL...................................................................... 23 Processing ........................................................................... 24 Non-Functional .................................................................... 25 Performance ........................................................................ 25 Portability............................................................................. 26 3.2.3Resource Allocation ..................................................... 28 3.2.4Budget Allocation ......................................................... 31 3.3 Project Tracking Plan........................................................... 31 3.3.1Requirements Management ......................................... 31 3.3.2Schedule management ................................................ 32
Organisation NEXUS Owner Musa Raja Title/Subject SPMP Approved by Mashood Shaukat Number 1.2
th
Date 12 Nov, 2013
1.2
Page vi
Software Project Management Plan
Rescue Management System
3.3.3Budget Control ............................................................. 32 3.3.4Quality Control ............................................................. 33 3.3.5Reporting ..................................................................... 34 3.3.6Project Metrics ............................................................. 34 3.4 Risk Management Plan........................................................ 35 3.5 Project Closeout Plan .......................................................... 36 4. Technical Process Plans ........................................................ 38 4.1 Process Model ..................................................................... 38 4.2 Methods, Tools, and Techniques ......................................... 39 4.3 Infrastructure ....................................................................... 39 4.4 Product Acceptance............................................................. 40 5. Supporting Process Plans ...................................................... 41 5.1 Configuration Management.................................................. 41 5.2 Verification and Validation ................................................... 41 5.3 Documentation .................................................................... 42 5.4 Quality Assurance ............................................................... 42 5.5 Reviews and Audits ............................................................. 42 5.6 Problem Resolution ............................................................. 42 5.7 Subcontractor Management................................................. 43 5.8 Process Improvement .......................................................... 43 6. Additional Plans ...................................................................... 44 7. Project Evolution ..................................................................... 45
Organisation NEXUS Owner Musa Raja Title/Subject SPMP Approved by Mashood Shaukat Number 1.2
th
Date 12 Nov, 2013
1.2
Page vii
Software Project Management Plan
Rescue Management System
7.1 Project support and maintenance ........................................ 45 7.2 Follow-up projects ............................................................... 45
Organisation NEXUS Owner Musa Raja
Title/Subject SPMP Approved by Mashood Shaukat
Number 1.2
th
Date 12 Nov, 2013
1.2
Page
viii
Software Project Management Plan
Rescue Management System
Document Change Control
Version History
Date 12th Nov 15th Nov Status* Draft / First plan Preliminary Version Version 1.0 Version 1.1 Author Ahsan Shakeel Ahsan Shakeel Description Of Version Initial draft created for distribution and review comments Second draft incorporating initial review comments, distributed for final review First complete draft, which is placed under change control
18th Nov
Final
Version 1.2
Ahsan Shakeel
Table 1 : Version History
Organisation NEXUS Owner Musa Raja
Title/Subject SPMP Approved by Mashood Shaukat
Number 1.2
th
Date 12 Nov, 2013
1.2
Page ix
SOFTWARE PROJECT MANAGEMENT PLAN
RESCUE MANAGMENT SYSTEM
1.
Project Overview
Rescue Management System is basically to provide bulk of facilities to the administration branch of Rescue.
1.1
Purpose
The purpose of the Project plan document is to clearly define the system under development, namely the RESCUE MANAGEMENT SYSTEM (RMS). The intended audience of this document includes the whole rescue team, the clerks of the department, and the end users of the RMS. Other intended audience includes the development team such as the requirements team, requirements analyst, design team, and other members of the developing organization.
1.2
Scope
The local rescue department wanted to create a new software where everything such as the record and functionality of the system can be accessed online .therefore the system will have two interfaces Employee inter phase Citizen inter phase
1.3
Objectives
Therefore, the new RMS will allow the following functionality: . Vehicles management Types of vehicles
Existing human record. Fleet tracking system Surveillance through external and internal cameras
Organisation NEXUS Owner Musa Raja
Title/Subject SPMP Approved by Mashood Shaukat.
Number 1.2
th
Date 12 Nov, 2013
1.2
Page 1
SOFTWARE PROJECT MANAGEMENT PLAN
RESCUE MANAGMENT SYSTEM
Call monitoring Expenditure management Funds management. Wireless communication system Web-site management, Planning and development, Pre-disaster precaution, Complaint cells Equipments management.
This software will manage the record of the rescue team and will also serve as a gate in the time of severe pain and suffering.
1.4
Assumptions, Constraints and Risks
There will be many risks. The imposed constraints and risks are as follows:
Scheduling for RMS is dependent to the scheduling plans of software engineering course since it is a term project. Resources, Insure best quality, The budget of the project must be maximum Rs. 600,000.and RMSs total cost is Rs. 537000/-.
Organisation NEXUS Owner Musa Raja
Title/Subject SPMP Approved by Mashood Shaukat.
Number 1.2
th
Date 12 Nov, 2013
1.2
Page 2
SOFTWARE PROJECT MANAGEMENT PLAN
RESCUE MANAGMENT SYSTEM
Software to be reused, Existing software to be incorporated, Using a microcontroller Communication between the sensors and GPRS modem Temporarily activating web page High sensor sensitivity The assumption made in RMS is there is no electrical failure in the system
1.5 Project Deliverables
Major work products, including content and timing
1.5.1 Documentations Project Deliverables Documentations
S.NO 1. 2. 3. 4. 5. 6. Documents Problem Statement Software Requirement Specification Software Project management Plan Test Plan System Architecture and Application Design Quality Insurance Plan Planned Completion Week 5th Week 6th Week 8th Week 9th Week 11th Week 13th Week
Table 2: Project Deliverables Documentations
Organisation NEXUS Owner Musa Raja
Title/Subject SPMP Approved by Mashood Shaukat.
Number 1.2
th
Date 12 Nov, 2013
1.2
Page 3
SOFTWARE PROJECT MANAGEMENT PLAN
RESCUE MANAGMENT SYSTEM
1.5.2 Other Deliverables
UML Diagrams. User Manual. A system with a camera and a modem and sensors. A web-site that user can access. A wap-site that user can access.
1.6 Schedule and Budget Summary 1.6.1 Schedule
Sr.No 1 2 3 4 5 6 7
Documentation Requirements Project manager Architectural Design Detail Design Test Plan Quality Assurance Plan Presentation Aamna Tahir
MEMBER
Ahsan Shakeel Sana Naseem Sana Naseem Muhammad Nouman Asad Malik C.E.O, C.F.O, C.I.O & TEAM LEADS
Table 3: Schedule of Documentation
Organisation NEXUS Owner Musa Raja
Title/Subject SPMP Approved by Mashood Shaukat.
Number 1.2
th
Date 12 Nov, 2013
1.2
Page 4
SOFTWARE PROJECT MANAGEMENT PLAN
RESCUE MANAGMENT SYSTEM
1.6.2 Budget
Budget will be around about Rs. 537000/-
Estimated Budget
Sr .No Description Minimum Estimated Budget 65000/Maximum Estimated Budget 67000/-
System requirement specification Software management plan Architecture structure Detail design Test plan Quality assurance plan Presentation Total Cost
50000/-
55000/-
3 4 5 6 7
70000/55000/70000/100000/50000/460000/-
75000/60000/75000/150000/55000/-
537000/-
Table 4: Estimated Budget
Organisation NEXUS Owner Musa Raja
Title/Subject SPMP Approved by Mashood Shaukat.
Number 1.2
th
Date 12 Nov, 2013
1.2
Page 5
SOFTWARE PROJECT MANAGEMENT PLAN
RESCUE MANAGMENT SYSTEM
1.7 Evolution of the Plan
The structure of this Project Plan is in compliance with the recommendations of IEEE STD 1058-1998.
Evolution of the Plan
Version Primary Author(s) Ahsan Shakeel Description of Version Initial draft created for distribution and review comments Second draft incorporating initial review comments, distributed for final review Date Expected 12/11/2013
Draft
Preliminary
Ahsan Shakeel
15/11/2013
Final
Ahsan Shakeel
First complete draft, which is placed under change control
18/11/2013
Table 5: Evolution of the Plan
It will be evolved to its mega stage in no time.
Organisation NEXUS Owner Musa Raja
Title/Subject SPMP Approved by Mashood Shaukat.
Number 1.2
th
Date 12 Nov, 2013
1.2
Page 6
SOFTWARE PROJECT MANAGEMENT PLAN
RESCUE MANAGMENT SYSTEM
The updates will be made if there are any problems found in the program. It will be implemented immediately. Updates will solve all known issues.
1.8 References
www.google.com www.ieee.com www.wikipedia.com nexus.viehosting.com
www.ooatool.com/docs/ProjMat
www.authorstream.com www.eecs.ucf.edu
en.wikipedia.org/wiki/Software_Requirements_Specification http://inderpsingh.blogspot.com/2010/02responsibilities-of-software.html
www.cs.ox.ac.uk/people/michael.wooldridge/teaching/ www.cs.sunysb.edu/~cse523 www.astrainfotech.com/software-engineering/softwareengineering/project
Organisation NEXUS Owner Musa Raja
Title/Subject SPMP Approved by Mashood Shaukat.
Number 1.2
th
Date 12 Nov, 2013
1.2
Page 7
SOFTWARE PROJECT MANAGEMENT PLAN
RESCUE MANAGMENT SYSTEM
Administrator Executive member of company and manage the system. Clerk - Personnel staff who is working in the respective company. locals people on which user-check will be performed by the system RMS website A website that gives opportunity to Citizens so that they can Ask for online emergency help. NADRA website- that will be linked with RMS website.
Organisation NEXUS Owner Musa Raja
Title/Subject SPMP Approved by Mashood Shaukat.
Number 1.2
th
Date 12 Nov, 2013
1.2
Page 8
SOFTWARE PROJECT MANAGEMENT PLAN
RESCUE MANAGMENT SYSTEM
1.9 Definitions and Acronyms
This subsection of the PROJECT PLAN should list each of the factors that affect the requirements stated in the PROJECT PLAN. These factors are not design constraints on the software but are, rather, any changes to them that can affect the requirements in the PROJECT PLAN. For example, an assumption might be that a specific operating system will be available on the hardware designated for the software product. If, in fact, the operating system is not available, the PROJECT PLAN would then have to change accordingly.
DBMS: Database Management System WBS: Work Breakdown Structure SRS: Software Requirements Specification SPMP: Software Project Management Plan DD: Design Description STD: Software Test Documentation IE: Internet Explorer MS: Microsoft QAP: Quality assurance plan GUI: Graphical User Interface DB: Database HW: Hardware SW: Software
Organisation NEXUS Owner Musa Raja
Title/Subject SPMP Approved by Mashood Shaukat.
Number 1.2
th
Date 12 Nov, 2013
1.2
Page 9
SOFTWARE PROJECT MANAGEMENT PLAN
RESCUE MANAGMENT SYSTEM
2. Project Organization
2.1 External Interfaces Senior projects committee
Musa Habib Raja (CEO)
Ahsan Shakeel (CFO)
Mashood Shaukat (CIO)
Muhammad Nouman (TESTING Head)
Aamna Tahir (REQUIRMENT Head)
Sana Naseem (DESIGN Head)
Asad Malik (VERIFICATION Head)
Figure 1: Senior projects committee
We will use Sun micro-computers. Every computer will be a client and will be connected to a server.
2.2 Internal Structure
Record system. Connectivity with printer. Support will be given by the software tem.
Title/Subject SPMP Approved by Mashood Shaukat. Number 1.2
th
Organisation NEXUS Owner Musa Raja
Date 12 Nov, 2013
1.2
Page
10
SOFTWARE PROJECT MANAGEMENT PLAN
RESCUE MANAGMENT SYSTEM
Members
CEO CFO CIO Musa Habib Ahsan Shakeel Muhammad Mashood Shaukat
Table 6 : Senior Management
Requirements problems are widely acknowledged to reduce the quality of software. Our analysis aims to provide practitioners with some insight into designing appropriate RE processes in order to achieve better results. This research was a two-fold process; firstly, a requirements process maturity was assessed and secondly, the types and number of problems faced by different practitioners during their software project was documented. The results indicate that there is no significant difference in problems faced by companies with mature and immature process. These findings suggest that a holistic approach is required in order to achieve quality software and organizations should not solely concentrate on improving requirement process. Through our empirical study we have also analysed problems identified by different groups of practitioners and found that there are more differences than similarities in the problems across practitioner groups.
Organisation NEXUS Owner Musa Raja
Title/Subject SPMP Approved by Mashood Shaukat.
Number 1.2
th
Date 12 Nov, 2013
1.2
Page
11
SOFTWARE PROJECT MANAGEMENT PLAN
RESCUE MANAGMENT SYSTEM
REQUIRMENT DEPARTMENT
Aamna Tahir (Head) Hassaan Mustafa Fahad Saleem Yasir Nawaaz Zeeshan Shaukat Abbasi Rabia Mushtaq
Table 7:Requirements team
Designing in software engineering is more difficult task because before we go through coding/implementing step should be understand user requirement and design the particular sketch . Moreover, they must support a set of requirements that are known only in broad scope the details are unknowable until the actual products are created. Furthermore, the initial stages of architecture design are where the most fundamental design decisions are made; these are the decisions that are the most difficult to correct when they are in error. Design process is follow by according to organization decision made during the actual process. Makes clear why the steps of the method exist and how they relate to each other. A design document is a complete high-level solution to the problem presented. It should be detailed enough that somebody who already understands the problem.
Organisation NEXUS Owner Musa Raja
Title/Subject SPMP Approved by Mashood Shaukat.
Number 1.2
th
Date 12 Nov, 2013
1.2
Page
12
SOFTWARE PROJECT MANAGEMENT PLAN
RESCUE MANAGMENT SYSTEM
DESIGNING DEPARTMENT
Sana Naseem Hasan(Head) Khadija Yameen Atif Mehmood Arslan Arshad Sidra Ashraf Faisal Aitaf
Table 8: Design team
TESTING DEPARTMENT
Muhammad Nouman (Head) Umair Ahmed kayani Muhammad Tayyab Muneeb Zahid
Table 9: Testing team
The responsibilities of a Software Test Engineer can be: Go through the software requirements and get clarifications on ones doubts Become familiar with the software under test and any other software related to it Understand the master test plan and/ or the project plan Create or assist in creating own test plan Generate test cases based on the requirements and other documents Procure or create test data required for testing Set up the required test beds (hardware, software and network)
Title/Subject SPMP Approved by Mashood Shaukat. Number 1.2
th
Organisation NEXUS Owner Musa Raja
Date 12 Nov, 2013
1.2
Page
13
SOFTWARE PROJECT MANAGEMENT PLAN
RESCUE MANAGMENT SYSTEM
Create or assist in creating assigned test automation Test software releases by executing assigned tests (manual and/ or automated) Report defects (usually in a defect database) to the stakeholders Create test logs Report test results to the stakeholders Reply to returned bug reports (for example, when a bug report is returned as not reproducible) Re-test resolved defects Update test cases based on the discovered defects Update test automation based on the updated test cases Provide inputs to the team in order to improve the test process Log own time in the project management software or time tracking system Report work progress and any problems faced to the Test Lead or Project Manager as required (If applicable) Support the team with testing tasks as required Keep himself/ herself up-to-date on the overview of the development technology, the popular testing tools (e.g. automated testing tools and test management systems) and the overview of the business domain
VALIDATION AND VERIFICATION
Asad Malik (Head) Awais Akram Abdul Raafay Ayesha Nawaaz
Table 10: Verification team
Organisation NEXUS Owner Musa Raja
Title/Subject SPMP Approved by Mashood Shaukat.
Number 1.2
th
Date 12 Nov, 2013
1.2
Page
14
SOFTWARE PROJECT MANAGEMENT PLAN
RESCUE MANAGMENT SYSTEM
Roles and responsibilities of all group members are given in the above table. Our
Sr.No 1 2 3 4 5 6 7 8
Roles and responsibilities
MEMBER Musa Raja Ahsan Shakeel Mashood Shaukat Aamna Tahir & team Sana Naseem & team Muhammad Nouman & team Asad Malik & team C.E.O, C.F.O, C.I.O & TEAM LEADS
Project supervisor Project manager IT manager Requirements Design Test Plan Quality Assurance Plan Presentation
Table 11 :Role and Responsibility
Organisation NEXUS Owner Musa Raja
Title/Subject SPMP Approved by Mashood Shaukat.
Number 1.2
th
Date 12 Nov, 2013
1.2
Page
15
SOFTWARE PROJECT MANAGEMENT PLAN
RESCUE MANAGMENT SYSTEM
3. Managerial Process Plans The full team is prepared and do the work accordingly as we divide.
3.1 Start-up Plan
3.1.1 Estimates
Estimated cost is Rs. 537000/We are using waterfall method to develop software. If there is some major changes in PROJECT PLAN then contract will be reviewed as budget is consult.
3.1.2 Staffing
Number of required staff, providing the following details: Expert in JAVA language, Can test a software, and Time punctual.
No new hiring required.
3.1.3 Resource Acquisition
Specify the plan for acquiring the resources and assets, in addition to personnel, needed to successfully complete the project. Describe the resource acquisition process. Specify the assignment of responsibility for all aspects of resource acquisition. Specify acquisition plans for equipment, computer hardware and software, training, service contracts, transportation, facilities, and administrative and janitorial services.
Organisation NEXUS Owner Musa Raja
Title/Subject SPMP Approved by Mashood Shaukat.
Number 1.2
th
Date 12 Nov, 2013
1.2
Page
16
SOFTWARE PROJECT MANAGEMENT PLAN
RESCUE MANAGMENT SYSTEM
Specify when in the project schedule the various acquisition activities will be required. Specify any constraints on acquiring the necessary resources. If necessary, expand this subsection to lower levels, to accommodate acquisition plans for various types of resources.
3.1.4 Project Staff Training
Specify the training needed to ensure that necessary skill levels in sufficient numbers are available to successfully conduct the IM/IT project. Specify the following training information: the types of training to be provided, numbers of personnel to be trained, entry and exit criteria for training, and the training method, for example: lectures, consultations, mentoring, computer-assisted training, etc.
Identify training as needed in technical, managerial and supporting activity skill
Responsibilities
Maintaining the team home page Updating the web site(announcements etc. Updating the website by adding project products and documents
Organisation NEXUS Owner Musa Raja
Title/Subject SPMP Approved by Mashood Shaukat.
Number 1.2
th
Date 12 Nov, 2013
1.2
Page
17
SOFTWARE PROJECT MANAGEMENT PLAN
RESCUE MANAGMENT SYSTEM
Responsibility Project Manager Developer Developer Tester Web Master
Persons responsible Ahsan Shakeel Satti Sana Naseem Hassan Muhammad Tayyab Muhammad Nouman Muhammad Mashood
Table 12: Staff training responsibilities
Organisation NEXUS Owner Musa Raja
Title/Subject SPMP Approved by Mashood Shaukat.
Number 1.2
th
Date 12 Nov, 2013
1.2
Page
18
SOFTWARE PROJECT MANAGEMENT PLAN
RESCUE MANAGMENT SYSTEM
3.2 Work Plan
3.2.1 Work Breakdown Structure
Work Breakdown Structure (WBS) to specify the various work activities to be performed in the IM/IT project, and to depict the relationships among these work activities.
Code 1 1.1 1.2 1.3 2 2.1 2.2 2.3 3 3.1 3.2 3.3 4 4.1 4.2 4.2.1 4.2.2
Organisation NEXUS Owner Musa Raja
Task Name Initiation Team format Select project topic Prepare tender proposal Project Planning Complete the draft of tender proposal Internal meeting of tender proposal Deliver tender proposal Create project management plan (SPMP) Prepare SPMP Present draft of SPMP Deliver SPMP Project Execution Analyse Produce Software Requirement Specification Receive client requirements Develop solution overviews
Title/Subject SPMP Approved by Mashood Shaukat. Number 1.2
th
Date 12 Nov, 2013
1.2
Page
19
SOFTWARE PROJECT MANAGEMENT PLAN
RESCUE MANAGMENT SYSTEM
4.2.3 4.2.4 4.2.5 4.3 4.3.1 4.3.2 4.4 4.4.1 4.4.2 4.4.2.1 4.4.2.2 4.4.3 4.4.3.1 4.4.3.2 4.4.4 4.4.4.1 4.4.4.2 4.4.4.3 4.5 4.5.1 4.5.2 4.6 4.6.1 4.6.2 4.6.3
Prepare presentation Present draft SRS Deliver SRS Produce SDD Prepare draft of SDD Deliver SDD Implement Initialize source control solution Design system structure Interface Major functions Design system database User authentication Main window and coding Testing Interface testing User acceptance testing System/ implementation testing Maintain Email support Documentation amendments Closing Project report Project presentation Team dismissed
Table 13: Complete Work Plan
Organisation NEXUS Owner Musa Raja
Title/Subject SPMP Approved by Mashood Shaukat.
Number 1.2
th
Date 12 Nov, 2013
1.2
Page
20
SOFTWARE PROJECT MANAGEMENT PLAN
RESCUE MANAGMENT SYSTEM
Work Breakdown Of SPMP Preparing SPMP 1 2 3 4 5 6 7 8 9 10 11 12 Defining Roles & Responsibilities Estimating of Problem Size Project Planning Technical Planning Staff Planning Resource Planning Train Planning Documenting of SPMP Building Web Site of Project Reviewing SPMP Revising SPMP Approving SPMP
Table 14: Work Breakdown Of SPMP
1 2 3 4 5 6 7 8 9
Work Breakdown Of SRS Preparing SRS Getting customer ideas Determining user groups Defining Product Properties Behavioral Requirements Specifying Non-Behavioral Requirements Specifying Documenting Reviewing SRS Revising SRS Approving SRS
Table 15: Work Breakdown Of SRS
Organisation NEXUS Owner Musa Raja
Title/Subject SPMP Approved by Mashood Shaukat.
Number 1.2
th
Date 12 Nov, 2013
1.2
Page
21
SOFTWARE PROJECT MANAGEMENT PLAN
RESCUE MANAGMENT SYSTEM
1 2 3 4 5 6 7 8
Work Breakdown Of SDD Preparing SDD Defining SDD Basic Concepts Interface Designing Database Designing Code Designing Documenting Reviewing SDD Revising SDD Approving SDD
Table 16: Work Breakdown Of SDD
1 2 3 4 5 6 7
Work Breakdown Of Coding and Testing Coding and Testing Implementing of Authentication Designing of Login Module Determining Authorization Level of users Web Site Module Coding Customizable Menus Coding Checking Security of Web Site Testing Web Site
Table 17: Work Breakdown Of Coding and Testing
Organisation NEXUS Owner Musa Raja
Title/Subject SPMP Approved by Mashood Shaukat.
Number 1.2
th
Date 12 Nov, 2013
1.2
Page
22
SOFTWARE PROJECT MANAGEMENT PLAN
RESCUE MANAGMENT SYSTEM
Work Breakdown Of DEMO DEMO 1 2 3 4 5
Preparing of Demonstration Demonstrating Reviewing of Demonstration Updating Product Approving of Demonstration
Table 18: Work Breakdown Of Demo
Decompose the work activities to a level that exposes all project risk factors, and that allows accurate estimation of resource requirements and schedule duration for each work activity. Specify the following factors for each work activity: necessary resources, estimated duration, products or deliverables of the activity, acceptance criteria for the work activity products, and Predecessor and successor work activities.
The level of decomposition internally within the WBS may vary depending on the quality of the requirements, familiarity of the work, applicable level of technology, etc.
3.2.2 Schedule Allocation FUNCTIONAL Input User name Type of incident Location Assistance desired Search object description
Organisation NEXUS Owner Musa Raja Title/Subject SPMP Approved by Mashood Shaukat. Number 1.2
th
Date 12 Nov, 2013
1.2
Page
23
SOFTWARE PROJECT MANAGEMENT PLAN
RESCUE MANAGMENT SYSTEM
Processing During this stage dispatch SAR (system and rescue) resources to the scene implement action plans, provide initial medical care and provide or deliverer proper medical safety. Outputs The system shall be able to manage connection between the streaming server and clients. Error Handling The system shall prompt a message for wrong inputs and errors. The system shall be able to display error messages in case of connection problems. The system shall be able to handle problems like low internet connectivity. The system shall be able to handle the frame rate for transmission. The system shall be able to identify valid user. Description The information in this section shall be provided by the remote servers This feature shall facilitate the server by providing the required information and preventing from misfortunes or save from fake users. Input
User name Location Type of emergency Uncertainty Alert Distress
Organisation NEXUS Owner Musa Raja
Title/Subject SPMP Approved by Mashood Shaukat.
Number 1.2
th
Date 12 Nov, 2013
1.2
Page
24
SOFTWARE PROJECT MANAGEMENT PLAN
RESCUE MANAGMENT SYSTEM
Processing The system shall be able to check if the input data is correct or not. The system shall be able to trace user place by tracking its phone signals or frequency. Output
No fake user will be allowed. No uncertainty will occur or reduced.
Non-Functional These are constraints on the services or functions offered by the FRS. They include timing constraints, constraints on the development process, and constraints imposed by standards. Non-functional requirements often apply to the system as a whole, rather than individual system features or services. Performance
Specifies time to do things, required throughput rates. Measure using response times or times to undertake an action (speed), actions per time period (throughput), or numbers of units handled (load). Test using response timing, load tests, throughput tests.
Reliability
Specifies levels of failure supported in the FRS Measure using mean-time between (defined) failures. Test using product reliability trials, customer evidence.
Availability
Specifies nature and levels of access to the RMS.
Title/Subject SPMP Approved by Mashood Shaukat. Number 1.2
th
Organisation NEXUS Owner Musa Raja
Date 12 Nov, 2013
1.2
Page
25
SOFTWARE PROJECT MANAGEMENT PLAN
RESCUE MANAGMENT SYSTEM
Measure using times when available, %age downtimes Test using system-level trials and user experiences.
Security
Specifies levels of illegal access to the RMS. Measure using specified access functions, and mean-time between breaches. Test using security experts.
Maintainability
Specifies the acceptable levels of upgrade of RMS. Measure using time and resources to maintain. Test using simple maintenance tasks.
Portability
Specifies platforms that RMS needs to operate on. Measure using the names and versions of operating systems Test using usage trials on range of products.
Organisation NEXUS Owner Musa Raja
Title/Subject SPMP Approved by Mashood Shaukat.
Number 1.2
th
Date 12 Nov, 2013
1.2
Page
26
SOFTWARE PROJECT MANAGEMENT PLAN
RESCUE MANAGMENT SYSTEM
SENIOR MANAGEMENT
To manage budget developments/ improvement Gathered funds & Expenditure Salary management Officers &Trainee Management
CLERKS/ Employees
Record of Vehicles Equipments Caller detail NORMAL Emergency detail USER/CITIZENS History Emergency contact numbers Reporting Nearest rescue office Fake calls Suggestions for Call tracking improvement Expenditure on catastrophes Donations Expenditure on Maintenance Complaint cells Demanded equipments Workshops Worn out equipments
Advertisements Social awareness
Figure 2:functions division
Organisation NEXUS Owner Musa Raja
Title/Subject SPMP Approved by Mashood Shaukat.
Number 1.2
th
Date 12 Nov, 2013
1.2
Page
27
SOFTWARE PROJECT MANAGEMENT PLAN
RESCUE MANAGMENT SYSTEM
Specify the scheduling relationships among the project work activities in a manner that depicts the time sequencing constraints and illustrates opportunities for concurrent work activities. Identify the critical path in the schedule. Indicate any constraints on the scheduling of particular work activities, that are caused by external factors. Identify appropriate schedule milestones to assess the scope and quality of project work products and of project achievement status. Techniques for depicting schedule relationships may include milestone charts, activity lists, activity Gantt charts, activity networks, critical path networks and PERT charts.
3.2.3 Resource Allocation
Provide a detailed itemization of the resources allocated to each major work activity in the project WBS. Specify the numbers and required skill levels of personnel for each work activity. each type of resource for each work activity are as follows
Organisation NEXUS Owner Musa Raja
Title/Subject SPMP Approved by Mashood Shaukat.
Number 1.2
th
Date 12 Nov, 2013
1.2
Page
28
SOFTWARE PROJECT MANAGEMENT PLAN
RESCUE MANAGMENT SYSTEM
Activities Defining Roles & Responsibilities Estimating of Problem Size Project Planning Technical Planning Staff Planning Resource Planning Train Planning Documenting of SPMP Building Web Site of Project Reviewing SPMP Revising SPMP Approving SPMP
Human Resources Management Management Planning team Planning team Planning team Planning team Planning team Management IT team All teams Management Senior Management
Title/Subject SPMP
LEVEL Well qualified Well qualified Well qualified Well qualified Well qualified Well qualified Well qualified Well qualified Well qualified Well qualified Well qualified Well qualified
Number 1.2
Table 19: resource for work activity
Organisation NEXUS Owner Musa Raja
Approved by Mashood Shaukat.
Date 12 Nov, 2013
th
1.2
Page
29
SOFTWARE PROJECT MANAGEMENT PLAN
RESCUE MANAGMENT SYSTEM
Activities Preparing of Demonstration
SW Tools MS Office, Java, Eclipse, HTML, Notepad++, CSS, PHP, MySQL MS Office, Java, Eclipse, HTML, Notepad++, CSS, PHP, MySQL MS Office, Java, Eclipse, HTML, Notepad++, CSS, PHP, MySQL MS Office, Java, Eclipse, HTML, Notepad++, CSS, PHP, MySQL _
Table 20: SW and HW used
HW Resources PC/ laptop
Demonstrating
PC/ laptop
Reviewing of Demonstration
PC/ laptop
Updating Product
PC/ laptop
Approving of Demonstration
PC/ laptop
Organisation NEXUS Owner Musa Raja
Title/Subject SPMP Approved by Mashood Shaukat.
Number 1.2
th
Date 12 Nov, 2013
1.2
Page
30
SOFTWARE PROJECT MANAGEMENT PLAN
RESCUE MANAGMENT SYSTEM
3.2.4 Budget Allocation
Sr .No
Description
Maximum Estimated Budget 67000/-
System requirement specification Software management plan
55000/-
3 4 5 6 7
Architecture structure Detail design Test plan Quality assurance plan Presentation Total Cost
Table 21: Budget Allocation
75000/60000/75000/150000/55000/-
537000/-
3.3 Project Tracking Plan
3.3.1 Requirements Management
We discussed and considered hardware and software requirements during preparing SPMP, but it may change during the stage of Software Requirement Specification.. Software Requirements Specification (SRS) part of the project we will communicate people of this field. If the customers needs change, we can update our website by considering their wants for customer satisfaction
Organisation NEXUS Owner Musa Raja Title/Subject SPMP Approved by Mashood Shaukat. Number 1.2
th
Date 12 Nov, 2013
1.2
Page
31
SOFTWARE PROJECT MANAGEMENT PLAN
RESCUE MANAGMENT SYSTEM
3.3.2 Schedule management
Specify the schedule control activities by identifying the processes to be used for the following purposes: to measure the progress of work completed at the major and minor project milestones, to compare actual progress to planned progress, and to implement corrective action when actual progress does not conform to planned progress.
Specify the methods and tools that will be used to measure and control schedule progress. Identify the objective criteria that will be used to measure the scope and quality of work completed at each milestone, and hence to assess the achievement of each schedule milestone.
3.3.3 Budget Control
Specify the budget control activities by identifying the processes to be used for the following purposes: to measure the cost of work completed, to compare the actual cost to the planned and budgeted costs, and to implement corrective action when the actual cost does not conform to the budgeted cost.
Specify when cost reporting will be done in the project schedule. Specify the methods and tools that will be used to track the project cost.
Organisation NEXUS Owner Musa Raja
Title/Subject SPMP Approved by Mashood Shaukat.
Number 1.2
th
Date 12 Nov, 2013
1.2
Page
32
SOFTWARE PROJECT MANAGEMENT PLAN
RESCUE MANAGMENT SYSTEM
Identify the schedule milestones and objective indicators that will be used to assess the scope and quality of the work completed at those milestones. Specify the use of a mechanism such as earned value tracking to report the budget and schedule plan, schedule progress, and the cost of work completed.
3.3.4 Quality Control
Specify the processes to be used to measure and control the quality of the work and the resulting work products
.
Figure 3:Quality control
Organisation NEXUS Owner Musa Raja
Title/Subject SPMP Approved by Mashood Shaukat.
Number 1.2
th
Date 12 Nov, 2013
1.2
Page
33
SOFTWARE PROJECT MANAGEMENT PLAN
RESCUE MANAGMENT SYSTEM
Specify the use of quality control processes such as quality assurance of conformance to work processes, verification and validation, joint reviews, audits and process assessment.
3.3.5 Reporting
Specify the reporting mechanisms, report formats and information flows to be used in communicating the status of requirements, schedule, budget, quality, and other desired or required status metrics within the project and to entities external to the project. Specify the methods, tools and techniques of communication. Specify a frequency and detail of communications related to project management and metrics measurement that is consistent with the project scope, criticality, risk and visibility.
3.3.6 Project Metrics
Specify the methods, tools, and techniques to be used in collecting and retaining project metrics. Specify the following metrics process information: identification of the metrics to be collected, frequency of collection, and processes for validating, analyzing, and reporting the metrics.
Organisation NEXUS Owner Musa Raja
Title/Subject SPMP Approved by Mashood Shaukat.
Number 1.2
th
Date 12 Nov, 2013
1.2
Page
34
SOFTWARE PROJECT MANAGEMENT PLAN
RESCUE MANAGMENT SYSTEM
3.4 Risk Management Plan
We try to persuade them to bring them into agreement for the reports regularity This risk can happen when two or more team member has different thoughts about the report and communication problems between them All members know the deadlines of the project reports. We can overcome from all of them by doing them on time. There will be one server for web application from team members, but we are planning to have all the source codes in every person to bring them back. To get rid of this risk, we can have extra system and all team members have copy of all works. Our team wants to have a good project and if quality controllers cannot catch the problem, the project is under the thread. This risks may happen when our reports or our web site is not enough good.
Organisation NEXUS Owner Musa Raja
Title/Subject SPMP Approved by Mashood Shaukat.
Number 1.2
th
Date 12 Nov, 2013
1.2
Page
35
SOFTWARE PROJECT MANAGEMENT PLAN
RESCUE MANAGMENT SYSTEM
Factor
Risk rating(H,M,L) L
Response
comments
Goals
Change project or apply extensions. Meeting the client
This risk should be solved at the beginning. Project team need to keep in touch with client. Plan the schedule well at the beginning When conflicts exist, project manager has responsibility to solve this problem. Team members should keep learning about the related knowledge
Customer
Schedule
Analysis the schedule and reallocate the human resources Reallocate the human resources
Staff
Techniques
Ask help from external environment
Table 22:Risk Management Plan
We can increase the number of our weekly meetings to having the report before the deadline if there is one or two team members absent.
3.5 Project Closeout Plan
Identify the plans necessary to ensure orderly closeout of the IM/IT project. Specify the following:
a staff reassignment plan a process for archiving project materials, a process for capturing project metrics in the business projects database,
Title/Subject SPMP Approved by Mashood Shaukat. Number 1.2
th
Organisation NEXUS Owner Musa Raja
Date 12 Nov, 2013
1.2
Page
36
SOFTWARE PROJECT MANAGEMENT PLAN
RESCUE MANAGMENT SYSTEM
a process for post-mortem debriefings of project personnel, and a plan for preparation of a final report to include lessons learned and an analysis of project objectives achieved.
Organisation NEXUS Owner Musa Raja
Title/Subject SPMP Approved by Mashood Shaukat.
Number 1.2
th
Date 12 Nov, 2013
1.2
Page
37
SOFTWARE PROJECT MANAGEMENT PLAN
RESCUE MANAGMENT SYSTEM
4. Technical Process Plans
4.1 Process Model
In our project we analyse all process plan then we choose a plan which is the classical of system development that is also known as Waterfall model. One reason for choose this model is a sequence of process working from top to bottom and it creates natural milestones at the end of each phase. Other reason is all project requirements are well defined and the development methods are well understood. In other words, we define our project requirements at the beginning of the project and these are constant to the end of the project. Our project deadlines were planned at the beginning of the project and we do not return back at any phases. Because of this situation, the Waterfall process model is the best choice for our project.
Table 23: Process Model
Organisation NEXUS Owner Musa Raja
Title/Subject SPMP Approved by Mashood Shaukat.
Number 1.2
th
Date 12 Nov, 2013
1.2
Page
38
SOFTWARE PROJECT MANAGEMENT PLAN
RESCUE MANAGMENT SYSTEM
4.2 Methods, Tools, and Techniques
We can divide our project as two parts which are reporting parts and coding parts. In the reporting part some software tools are used that tools are MS Office, MS Project, Notepad, Mozilla Firefox and Google Chrome. Some hardware tools are used in our project which is PC and database server. In coding part, JSP,PHP,CSS, HTML for developing web pages of our project. MySQL and MS Dreamweaver are used for our project
4.3 Infrastructure
Our project infrastructure plan is given in Table Hardware Four PCs consists of Intel and Windows XP/Vista/7 with minimum 4 GB free disc space Java Runtime Environment, MS Dreamweaver, My-SQL, Photoshop CS5, MS Office Operating System Standards Windows XP/ Vista/ 7/Linux IEEE Standards will be using our project. All the citizens of Islamic Republic of Pakistan. .Table 24: Infrastructure
Software
Facilities
Organisation NEXUS Owner Musa Raja
Title/Subject SPMP Approved by Mashood Shaukat.
Number 1.2
th
Date 12 Nov, 2013
1.2
Page
39
SOFTWARE PROJECT MANAGEMENT PLAN
RESCUE MANAGMENT SYSTEM
4.4 Product Acceptance
All deliverables of project are prepared then our project supervisor examines and evaluates it. After the evaluation is completed, our supervisor will give feedback and supervisor may want to change, add or drop some parts of deliverables. After making the necessary changes, the last version of the deliverable will be evaluated again by our project supervisor. This process will continue until all necessary changes finished and deliverables are approved by our project supervisor then we will start other deliverables. Before the last delivery of our project, we will make a presentation to our supervisor and other examiners at this presentation we will reply questions about our project. At the end of this presentation our project will be evaluated by the senior project committee and our final product will be tested for acceptance by this committee.
Organisation NEXUS Owner Musa Raja
Title/Subject SPMP Approved by Mashood Shaukat.
Number 1.2
th
Date 12 Nov, 2013
1.2
Page
40
SOFTWARE PROJECT MANAGEMENT PLAN
RESCUE MANAGMENT SYSTEM
5. Supporting Process Plans
5.1 Configuration Management
Specify or reference the configuration management plan for the IM/IT project, providing the information identified in the following lines. Specify the methods that will be used to perform the following activities:
configuration identification, configuration control, status accounting, , and release management.
Specify the processes of configuration management including procedures for the following activities:
initial baselining of work products, logging and analysis of change requests, change control board procedures, tracking of changes in progress, and procedures for notification of concerned parties when baselines are established or changed.
Identify the automated configuration management tools used to support the configuration management process.
5.2 Verification and Validation
The objectives of verification, validity activities are to assess and improve the quality of the work products generated during development and modification of the software. Quality depends upon the various attributes like correctness, completeness, consistency, reliability, usefulness, usability, efficiency and conformance to standards.
Organisation NEXUS Owner Musa Raja
Title/Subject SPMP Approved by Mashood Shaukat.
Number 1.2
th
Date 12 Nov, 2013
1.2
Page
41
SOFTWARE PROJECT MANAGEMENT PLAN
RESCUE MANAGMENT SYSTEM
The terms verification and validation are used synonymously. These are defined as under: Verification: Are we building the product right? Validation: Are we building the right product? .
5.3 Documentation
The documentation will be provided within given time. Administrative branch will control all the documentation. Following information or object identification:
Software Requirements Specification, IEEE standards are followed, Team member will prepare the documentation, Team leader will review all the documentation,
5.4 Quality Assurance
We are using best processes for this product. We are using best tools for this product. We are using best database system for this product.
5.5 Reviews and Audits
An Charted Accounted is hired who will audit this project.. Customers reviews are followed then audit starts..
5.6 Problem Resolution
Waterfall method is used for this project. Developers will do their work in time according to problem resolution. .
Organisation NEXUS Owner Musa Raja
Title/Subject SPMP Approved by Mashood Shaukat.
Number 1.2
th
Date 12 Nov, 2013
1.2
Page
42
SOFTWARE PROJECT MANAGEMENT PLAN
RESCUE MANAGMENT SYSTEM
5.7 Subcontractor Management
There management will we handed to are some special persons of management branch. A separate management plan for each subcontract, using a tailored version of this Project Plan, and include all items necessary to ensure successful completion of each subcontract as follows:
Requirements management, Monitoring of technical progress, Schedule and budget control is perfect. Product acceptance criteria is fulfilled , Risk management procedures are prepared.,
5.8 Process Improvement
By using good tools the process is improved.. T he process improvement plan is closely related to the problem resolution plan. Include in the improvement plan, a process to identify the project processes that can be improved without serious disruption to an ongoing project, and to identify the project processes that can best be improved by process improvement initiatives at the organizational level.
Organisation NEXUS Owner Musa Raja
Title/Subject SPMP Approved by Mashood Shaukat.
Number 1.2
th
Date 12 Nov, 2013
1.2
Page
43
SOFTWARE PROJECT MANAGEMENT PLAN
RESCUE MANAGMENT SYSTEM
6. Additional Plans
Some additional plans::
Best security plan is followed., Some special networking devices are needed., Product installation is very simple. Easy to copy database, Update needed every year.
Organisation NEXUS Owner Musa Raja
Title/Subject SPMP Approved by Mashood Shaukat.
Number 1.2
th
Date 12 Nov, 2013
1.2
Page
44
SOFTWARE PROJECT MANAGEMENT PLAN
RESCUE MANAGMENT SYSTEM
7. Project Evolution
7.1 Project support and maintenance
The best process, tools are used to make this project with friendly GUI.
7.2 Follow-up projects
Working hard for this project.
Organisation NEXUS Owner Musa Raja
Title/Subject SPMP Approved by Mashood Shaukat.
Number 1.2
th
Date 12 Nov, 2013
1.2
Page
45
