Search This Blog

Tuesday, October 11, 2016

Software Development Project Management Plan for Dhaka Subway Ticketing System


Software Development Project Management Plan for
Dhaka Subway Ticketing System
Revision 1.1.0 (Draft_A)


Project 1
Software Development and Project Management
Section: B
Department of Computer Science
American International University of Bangladesh

Prepared By
SL
Name
ID
1
Jamil, S.M. Aishwarja
14-25529-1
2
Qaium, Muhammad Abdul
14-26210-1
3
Alam, Sany
14-26005-1
4
Hossain, Md Tanvir
14-25524-1








Index
No
Title
Page
1
Revision History Page :
3
2
Introduction
4
3
Process Model
5
4
Quality Gate
7
5
List of Task (WBS)
8
6
Estimation of Each Task
10
7
Scheduling Task
11
8
Major Milestones
12
9
Staffing Plan
13
10
Monitoring  and Controlling Mechanism
14
11
Risk Management
15
12
List of deliverables
16
13
Defect and Bug Tracking:
17
14
Costing
18
15
Post Mortem
19







1.     Revision History Page :

Revision
Author
Description
Date
1.0.0 Draft_A
1. Jamil, S.M. Aishwarja
2. Qaium, Muhammad Abdul
3. Hossain, Md Tanvir
4. Alam, Sany
First Draft / Initial Creation of Statement of Work
20/06/2016
1.1.0 Draft_A
1. Jamil, S.M. Aishwarja
2. Qaium, Muhammad Abdul
3. Hossain, Md Tanvir
4. Alam, Sany
First Draft / Initial Creation of Project Planning
28/08/2016





2. Introduction

This document describes the project plan for the software development project for automated ticket issuing system for Dhaka Subway System. The S/W supports menu selection using touch screen. This is an android platform based software. Almost every new version after 4.1 Jelly Bean OS will be support the software. Now a day in Dhaka city it is a big deal to go anywhere and buy a bus or train ticket. Some time we spend our long time only for buying ticket and go one place to another place. It is a big source of wasting our valuable time even some time we cannot know about journey time too.
So now we are coming with a new software to remove our traveling problems and save valuable time. By using this software we may get a lot of benefit if we can use it perfectly.
 

3. Process Model :

Here we chose the agile methods to deliver features incrementally to our clients and take feedback from them to validate the requirements. This will allow us to deliver the all possible requirements of the customers. Using incremental process model also helps to reduce risks. Since agile development method encourages active user involvement, the client or product owner will have the clear view of the project progress, on the other hand we will have the clear view of the user’s requirements.


Diagram : Life Cycle flow Chart

 



                                                                                                           

 

4. Quality Gate­

Work Product
QA Technique
Software Project Management Plan
Formal Technical Review / Inspection
Schedule
Formal Technical Review / Inspection
Deigning
Inspection / Formal Technical Review
Testing
Inspection / Formal Technical Review
Coding
Code Review / Inspection
System testing
Test Coverage Measurement
Alpha test
3 weeks field test @developers site
Beta test
4 weeks field test @developers site

5. List of Task (Work Breakdown Structure) :

ID No
Work Breakdown
structure
Task Names
1
1.0
Dhaka Subway Ticketing System
2
1.1.0
        Start Of project
3
1.2
        Preliminary   Phase
4
1.2.1
                Developing Project Charter
5
1.2.2
                Project Charter Approved By steering committee
6
1.3
        Planning Phase
7
1.3.1
                                Creating Scope Document
8
1.3.2
                                Scope Document Approved
9
1.3.1.2
                        Managing Requirement Gathering
10
1.3.1.2.1
                                Preparing Research Materials Required
11
1.3.1.2.2
                                Interviewing Client
12
1.3.1.2.3
                                Reviewing Requirement Document
13
1.3.1.2.4
                                Revising Requirement Document
14
1.3.1.2.5
                                Requirement Document Approved
15
1.3.1.3
                        Development Plan
16
1.3.1.3.1
                                Creating Development Plan
17
1.3.1.3.2
                                Approved Development Plan
18
1.3.1.4
                        Managing Test Plan
19
1.3.1.4.1
                                Creating Test Plan
20
1.3.1.4.2
                                Test Plan Approved
21
1.3.1.5
                        Managing Maintenance Plan
22
1.3.1.5.1
                                Creating Maintenance Plan
23
1.3.1.5.2
                                Maintenance of Plan Approved
24
1.4
         Project Execution
24
1.4.1.
                           Manage Design
25
1.4.1.1
                                    Developing Use Case
26
1.4.1.2
                                    Creating Hardware Architecture Model
27
1.4.3
                                    Designing Product
28
1.4.3.1
                                             Designing UI
29
1.4.3.2
                                             Designing Entities
30
1.4.3.3
                                             Designing Business Login Layer
31
1.4.3.4
                                             Designing Database
32
1.4.3.5
                                     Design Approved
33
1.4.1.2
                           Manage Development
34
1.4.1.2.1
                                    Building Prototype Model
 35
1.4.1.2.2
                                    Demo Prototype Showing
36
1.4.1.2.3
                                    Developing Documentation
37
1.4.1.2.4
                                    Developing Product
38
1.4.1.2.4.1
                                           Developing UI
39
1.4.1.2.4.2
                                           Developing Business Logic Layer
40
1.4.1.2.4.3
                                           Developing Relational Database
41
1.4.1.2.4.4
                                    Development Of work Completed
42
1.4.1.2.5
                                   Executing Tests
43
1.4.1.2.5.1
                                           Executing Unit Tests
44
1.4.1.2.5.2
                                           Executing System Tests
45
1.4.1.2.5.3
                                           Executing Integration Tests
46
1.4.1.2.5.4
                                           Creating Test Documentations
47
1.4.1.2.5.5
                                   Testing Completed
48
1.4.1.3
                           Managing Deployment
49
1.4.1.3.1
                                   Making Schedule Of release
50
1.4.1.3.2
                                   Launching Product Live
51
1.5
         Closing Phase
52
1.5.1
                  Managing Maintenance activities
53
1.5.1.1
                           Performing Impact analysis
54
1.5.1.2
                           Checking User Acceptance
55
1.5.1.4
                           Monitoring Defects
56
1.5.1.6
                           Resolving Technical Problems
57
1.5.1.7
                           Establishing Maintenance Procedure
58
1.5.1.9
                           Gathering Requirements for future Enhancements
59
1.6
        End Of the Project


6. Estimation of each task :
Phase
Effort
Estimate (in weeks)
Planning Phase
Scope definition
1-2
Requirement gathering
4-7
Development planning
3-4
Test planning
4-5
Maintenance planning
4-5
Designing Phase
Designing prototype
3-4
Architecture developing
3-4
Designing product
4-7
Execution Phase
Develop product
4-5
Develop and execute tests
2-3
Deployment
2-4
Closing Phase
Maintenance
Will be continued till life time

7. Scheduling task:


1-4
4-8
8-10
10-16
16-20
20-30
30-33
33-35
35 - -

8. Major Milestones:

No
Item
Milestone Date
1
Planning  page
15/9/2016
2
Preliminary Design
15/10/2016
3
Detailed Design
30/10/2016
4
Coding
15/12/2016
5
System testing
31/12/2016



9. Staffing Plan :

Person
Assignment
Backup
Jamil, S.M. Aishwarja
Project Manager
Qaium, Muhammad Abdul
Hossain, Md Tanvir
Developer
Jamil, S.M. Aishwarja
Qaium, Muhammad Abdul
Designer 
Jamil, S.M. Aishwarja
Alam, Sany
Tester
Hossain, Md Tanvir



Role

Project Responsibility

Skills Required
Number of Staff Required
Project Manager
Lead team, report status
Project Management
1
Core Team
Review deliverables, assure quality
Project Management
4
Content Developer
Create framework content
Research and web writing skills
1
Web Designer
Design web-based performance management tool
Web design, web writing skills
1
Web Developer
Build the web-based performance management tool
Web development
1
Review Team
Evaluate deliverables, promote use
Project Management experience
20




10.  Monitoring and Controlling Mechanism
1.      Conduct weekly/biweekly project status meeting.
2.      Compare actual project performance to project management plan.
3.      Assessing performance and deciding if corrective or preventative actions are needed.
4.      Identifying new risks, monitoring project risks and execute risk response plans when needed.
5.      Maintaining an up-to-date information base of the projects products.
6.      Track project schedule and update schedule if needed.
7.      Monitor implementation of approved changes.
8.      Control timing the project with the operational requirements.
9.      Over-seeing resources expenditure.
10.  Control expenses of the project according budget.


11. Risk Management :
The project has identified 2/3 risk for the project as described below.
Risk management, mitigation and monitoring plans are described in the following RIS.(Risk Information Sheet)
Risk ID
Description
Probability
Impact
Risk-1
Software team does not good experience distributed database management
60%
Medium
Risk-2
Requirements Inflation
80%
Medium
Risk-3
Employee turnover. So personnel leave the project taking critical information with them that significantly delays or derails the project.
60%
Medium
Risk-4
Fain timeline of project for poor productivity
80%
Medium

Risk-5
Insignificant  Cost increase
50%
High
Risk-6
Quality degradation barely noticeable
50%
Medium
Risk-7
Project Contain with bug
80%
Medium ( major bug can be high impact )
Risk-8
Project  security system
60%
High
Risk-9
Un understandable for user.
50%
Medium
Risk-10
Weak algorithm
60%
Medium

12.                        List of deliverables:
Following are the list of software S/W deliverables –
No
Item description
Date
1
Detailed requirement document
30 September, 2016
2
Detailed design document
30 October, 2016
3
Software development
30 November, 2016
4
Alpha version of the software executable
30 December, 2016
5
Beta version
30 January, 2016
6
Final version
1 March, 2017
7
User guide
30 April, 2017
8
Installation and maintenance guide
28 May, 2017

13. Defect and Bug Tracking:
A web based database server will be maintained in order to track defects HD quality counter will be used to track defects. We use some software for bug tracking. We will document all this defect and solve with well manner.  


14. Costing
The total development cost is BDT 8,00,00,000 (apx).
Item
Description
Price
Quantity
Time Length
Total (apx)
1
Hardware



50,00,000

Processor dual core 2.6 GHz
-
50
8 months

Hard Disk – 1T
-
50
8 months
RAM – 8 GB
-
50
8 months
Graphics Card – 4 BG
-
50
8 months
Operating System – Windows 10
-
50
8 months
Monitor – 20’’
-
60
8 months
Keyboard
-
70
8 months
Mouse
-
80
8 months
Webcam
-
50
8 months
Card Reader
-
100
8 months




2
Software



20,00,000

Oracle License
-
1
-

Microsoft Visual Studio
-
1
-
QTP
-
1
-
Load Runners
-
1
-
Developing Tool
-
1
-
Testing Tool
-
1
-




3
Personal





Project Manager
2,50,000
1
8 months
20,00,000
Functional Manager
60,000
10
8 months
48,00,000
Engineers
40,000
80
8 months
2,56,00,000
Stuff
25,000
150
8 months
3,00,00,000
Office Rent
60,000

8 months
4,80,000





4
Others
-
-
8 months
1,01,20,000

TOTAL



8,00,00,000































15. Post Mortem:

While doing the project management plan, we have faced different types of problem such as scheduling problem, costing problem and we were not sure to get supplies from supplier timely. There were many risks. We have learned a lot from her. And we made some strategic plan to resolve this risks. We will utilize them in our next project.



No comments:

Post a Comment

Split A String By Coma (,)

Step 1.  create or replace type split_tbl as table of varchar2(32767); Step 2. create or replace function split (     p_list varchar2,...