Professional Documents
Culture Documents
Software Project Management Plan (SPMP) for Automated Ticket Issuing System for Bangladesh Road Transport Corporation (BRTC)
::
Title Page
::
ID 10-16377-1 10-16025-1 10-16234-1 08-11361-2
NAME HAQUE, MAZHARUL AHMED, ISTIAK AHMED, ABIR RAFI, HASIB ADNAN ARR
Revision History
Revision
Version 0.0.1
Date
June 12, 2012
Authors
HAQUE, MAZHARUL AHMED, ABIR RAFI, HASIB ADNAN ARR AHMED, ISTIAK
Description
First Version
2012
Page 1 of 15
Table of Contents
SOFTWARE PROJECT MANAGEMENT PLAN (SPMP) FOR AUTOMATED TICKET ISSUING SYSTEM FOR BANGLADESH ROAD TRANSPORT CORPORATION (BRTC) ...... 1 TITLE PAGE ..................................................................................................................................................... 1 REVISION HISTORY....................................................................................................................................................... 1 INTRODUCTION ........................................................................................................................................................... 3 PROCESS MODEL ......................................................................................................................................................... 3 SOFTWARE MODEL ...................................................................................................................................................3 BECAUSE OF THIS.....................................................................................................................................................3 SOFTWARE LIFE CYCLE FLOW CHART ....................................................................................................................4 QUALITY GATES FOR EACH PHASE OF SW DEVELOPMENT ........................................................................................................ 4 LIST OF TASKS ............................................................................................................................................................ 5 ESTIMATION FOR EACH TASK .......................................................................................................................................... 5 SCHEDULE THE TASKS .................................................................................................................................................. 6 PREPARE LIST OF MILESTONE.......................................................................................................................................... 7 STAFFING PLAN ........................................................................................................................................................... 7 ROLE REQUIREMENTS ..............................................................................................................................................7 STAFF ASSIGNED TO ROLES ...................................................................................................................................8 STAFF RESOURCE LOADING CHART........................................................................................................................8 MONITORING & CONTROLLING MECHANISM ......................................................................................................................... 9 COMMUNICATION AND REPORTING PLAN ..................................................................................................................9 RISK MANAGEMENT ...................................................................................................................................................... 9 LIST OF DELIVERS ...................................................................................................................................................... 10 SCHEDULE TRACKING PROCESS ..................................................................................................................................... 12 TEAM LEADER MEETINGS .......................................................................................................................................12 DEFECT TRACKING PROCESS......................................................................................................................................... 13 METRICS ................................................................................................................................................................. 14 POSTMORTEM ........................................................................................................................................................... 15
2012
Page 2 of 15
Introduction
This document addresses the requirements for automated system of bus-ticket vending machine for Bangladesh Road Transport Corporation (BRTC). The intended audience for this document is the designers and the BRTCs of the project. It is the controlling document for this project. It specifies the technical and managerial approaches to develop the software product. As such it is the companion document to Requirements Analysis Document (RAD). Changes in either may imply changes in the other document. All technical and managerial activities required to turn over the deliverables to the BRTC are included. This includes scheduling, identification of tasks, and factors that may impact the project and planning
Process Model
Software Model
Rapid Application Development (RAD) is a software development methodology that focuses on building applications in a very short amount of time; traditionally with compromises in usability, features and/or execution speed. The term has recently become a marketing buzzword that generically describes applications that can be designed and developed within 60 - 90 days, but it was originally intended to describe a process of development that involves application prototyping and iterative development.
Because of this
To prevent cost overruns (RAD needs a team already disciplined in cost management) To prevent runaway schedules (RAD needs a team already disciplined in time management) To converge early toward a design acceptable to the customer and feasible for the developers To limit a project's exposure to the forces of change To save development time, possibly at the expense of economy or product quality In certain situations, a usable 80% solution can be produced in 20% of the time that would have been required to produce a total solution. In certain situations, the business requirements for a system can be fully satisfied even if some of its operational requirements are not satisfied. The acceptability of a system can be assessed against the agreed minimum useful set of requirements rather than all requirements. 2012
Page 3 of 15
Line Of Code (LOC) Source code comment percentage Defects per KLOC
2012
Page 4 of 15
List of Tasks
Requirements Elicitation Project Presentation by BRTC Project Planning Requirements Analysis Analysis Review System Design Object Design Project Review with BRTC Implementation & Unit Testing Object Design Review Project Agreement System Integration & System Testing Internal Project Review (functional prototype) Project Acceptance by BRTC
Days
28 25 32 16 10
Hours
210 187.5 240 120 75
12 90 Implementation & Unit Testing 15 112.5 System Integration & System Testing *Total days are 105 days and working days are 93 days without national holydays.
System Design
Object Design Implementation & Unit Testing System Integration & System Testing
2012
Page 5 of 15
Project Phases
Requirements Elicitation Project Planning Requirements Analysis System Design Object Design Implementation & Unit Testing System Integration & System Testing
2012
Page 6 of 15
Project Milestones
Project Presentation by BRTCs Analysis Review Project Review with BRTC Object Design Review Project Agreement Internal Project Review (functional prototype) Project Acceptance by BRTC
Staffing Plan
The purpose staffing plan is to make certain the project has sufficient staff with the right skills and experience to ensure a successful project completion.
Role Requirements
The following is a detailed breakdown of the roles required to execute the project. It includes: the project role, the project responsibility of the role, skills required, number of staff required fulfilling the role, the estimated start date and the expected duration the staff resource will be needed on the project.
Role Project Responsibility Skills Required No. of Staff Required Estimated Start Date Duration Required
Java Developer
Java Development
Java programming expert(J2ME,J2EE) BSc in Software Engineering HTML,CSS,XHTML,X ML,AJAX, JavaScript, PHP (Strong knowledge in MVC Platform) Expert in Oracle10g, SQL, MYSql Strong Knowledge in Capability Maturity Model Integration (CMMI) & Spice, ISO 9001:2000 for Software
10
October 2, 2012
Web Developer
Web Development
October 2, 2012
2 3
2012
Page 7 of 15
Role
Name
Rate
Rate Unit
1. ISTIAK AHMED Java Developer 2. ABIR AHMED 3. MAZARUL HAQUE Web Developer 1. ANNAS BISWAS Database Management Software Engineer 1. TANVIR HASAN
FY 2012-2013
FY2012-2013
FY 2012-2013 FY 2012-2013
FY 2012-2013
Total:
Role
Java Developer Web Developer Database Management Software Engineer Total :
July
20 15 25 20 90
Aug
20 20 20 15 75
Sept
20 15 20 15 70
Oct
20 10 25 20 75
Total
85 60 90 70 305
2012
Page 8 of 15
Weekly Weekly
Project Review
Project Team
Software Manager
Monthly
Risk Management
This section mentions a number of possible risks for the project. Also, actions or measures are described to prevent or to reduce the risks. Four categories of risks are identified: Risks with respect to the work to be done. Risks with respect to the management. Risks with respect to the resources. Risks with respect to the customer. The risks for each category are listed below. For each risk, a description, a probability to occur, the action associated and the impact of the risk are given. It is obvious that problems will occur during the project. To avoid problems the following rules should be followed by all team members: Try to signal problems as early as possible and report them to the PM, so that action can be taken. Pay attention to communication and make sure everybody understands the things the same way. 2012
Page 9 of 15
1
0.5 0
List of Delivers
The System documentation will describe the principles of operation. The delivery consists of a presentation of the system, a demonstration of the working system and the successful passing of the acceptance test. The BRTC expects the acceptance test to be successfully demonstrated remotely via the Internet November 8, 2012.from 8:30 pm to 10:20 pm. All work deliverables will be on November 12, 2012.The work products will also be delivered on a CD-ROM after any working days on November 12, 2012.
2012
Page 10 of 15
End-user Documentation
IEEE 1063-2001
Technical Writer 1
Consultant 2
November 8, 2012
Software Test Plan template (adapted from IEEE 829-1998) IEEE 730-2002
Project Manager
October 1, 2012
Quality Analyst 1
Project Manager
Verification Engineer 1,
Project Manager
October 3, 2012
2012
Page 11 of 15
Quality
Meeting
Action
Status meetings Reports
Weekly
Project Team Meeting, Project Manager & Department Director Complete Tasks, Details on Schedules & Tasks for Next Week
Monthly
Project Manger & Directors Summary of Standard Reports
2012
Page 12 of 15
2012
Page 13 of 15
High
Medium
A response or action plan should be provided within 3 working days and the situation should be resolved before test exit. A response or action plan should be provided within 5 working days and the situation should be resolved before test exit. An action plan should be provided for next release or future enhancement
Low
Others
Metrics
Metrics
Schedule Staff Usage Expenditures No. of Requirements No. of Requirements Defects No. of Objects Coding Progress Coding Size Test progress Defect Tracking Test Progress Defect Tracking
Description
Milestones Graph of person hrs used per month Both projected and actual Graph of total expenditures over time Both projected actual Graph of total requirements Identified per module over time Graph of number of defects identified per module over time Graph of number of objects identified Over time Number of objects coded Lines of code measured daily Unit test causes passed over time Number of code defects Number of integration test Passed over time Number of code defects test Passed over time
Tracking Tool
MS Project MS Excel MS Excel MS Excel MS Excel
2012
Page 14 of 15
Postmortem
The overall project plan follows the model, a modified RAD model. 3 prototypes have to be delivered: A graphical user interface, a functional prototype and a system integration prototype. Analysis is started before Project Planning is finished. System Design is followed by Object Design. Important Milestones are the Analysis Review September 22 to September 26, the Project Status on September 26, the Project Review on October 4 and the Object Design Review on October 24. Implementation and Unit Testing are scheduled to overlap significantly. System Integration is scheduled to immediately follow Unit Testing. System Testing starts immediately after system integration and leads to the BRTC Acceptance Test on December 8, 2012.
THE END
2012
Page 15 of 15