• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
WBS bus ticketsystem
 

WBS bus ticketsystem

on

  • 2,988 views

 

Statistics

Views

Total Views
2,988
Views on SlideShare
2,988
Embed Views
0

Actions

Likes
1
Downloads
75
Comments
0

0 Embeds 0

No embeds

Accessibility

Upload Details

Uploaded via as Microsoft Word

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    WBS bus ticketsystem WBS bus ticketsystem Document Transcript

    • Work Breakdown Structure Project Name: Bus Ticks Product/Process: online system for tickets booking Prepared By Document Owner(s) Project/Organization Role Angel Gruev Ina Ivanova Stefan Grigorov Project Closure Report Version Control Version Date Author Change Description 1.0 14.06.2010 Owners Created document. 2.0 15.06.2010 Owners Finalized and reviewed document. Confidential wbsbusticketsystem-100615134641-phpapp02.doc Last printed 4/6/2004 13:07:00 a4/p4
    • Work Breakdown Structure Work Breakdown Structure Purpose and Limitations The purpose of this worksheet is to: • Identify the work to be done. • Identify the types of resources required for the work. • Develop estimates for each work element. • Identify storage locations. This worksheet does not address: • Who will perform the work. • When the work will be completed. Confidential Page 2 6/15/2010
    • Work Breakdown Structure Work Breakdown Structure Organization Chart Work ID Work Name Description Estimated Estimated Dependency 1.0 Cost Effort Bus Ticks (Euro) (ManDays) System 1.0 Bus Ticks System A system that contains two modules BTMS and OTSS. You can easily manage bus tickets selling in a centralized system with BTMS and also tickets are sold online with OTSS. 1.1 Develop a simple prototype Develop a simple prototype. It will illustrate the base functionalities and 2100 210 1.1.1, 1.1.2, 1.1.3 1.2 show common workflow use 1.3 cases. The prototype should clearly 1.4 1.5 1.1 demonstrate the benefits of using such software Development of the System delivery and Arrange meetings with Provide Develop a simple 1.1.1 Prototype implementation the bosses of big is the step when the real System This implementation happens. 300 integration 30 system prototype transport companies support 1.1.2 Promoting to a couple of companies Show the prototype to a couple of companies and collect their feedback. 1200 120 1.1.3 Detailed prototype Using the collected feedback from the previous step implement a more 600 60 detailed prototype of the system. 1.2 Arrange meetings with the bosses of big transport Show them the prototype, explain the benefits of using the system, 600 60 1.1.1 companies 1.1.2 1.1.3 discuss their reqiurments, explain them the delivery and installation and 1.3.1 1.3.2 1.3.3 1.3.4 1.4.1 1.4.2 Prototype Promoting to a Detailed Develop the Develop the also the support process for the system. Integration of Additional Installation, Training Implementation couple of prototype BTMS OTSS both systems services 1.3 Development of the system Develop the fully functional system containing both main modules: Bus 8000 800 configuration, 1.3.2, 1.3.3, 1.3.4 1.3.1, companies testing of the Ticket Management System and The online ticket selling system. system 1.3.1 Develop the BTMS (Bus Ticket Management Create the module for 1.3.2.1 management, designed for the bus 4000 tickets 1.3.2.2 400 System) companies. This module will provide synchronization between different payment Creating web Integration with portal portals offices of the bus companies and also a centralized point for all the data. Creating different reports for the managers. 1.3.2 Develop the OTSS (Online ticket selling system) Create the module for online ticket 1.3.2.1.2 reservation. It will 1.3.2.2.1 3800 1.3.2.1.1 selling and be web- 380 1.3.2.2.2 1.3.2.1, 1.3.2.2 based portal with and services such Google Design user friendly autorizationCreate interactive as: interactive bus seats ePay scheme, different payment methods and schemevoting, forum, etc interface bus seats ratings, checkout 1.3.2.1 Creating web portal Create the web-based system with autorization and services. Contains a 1200 120 1.3.2.1.1, 1.3.2.1.2 Confidential Page 3 6/15/2010
    • Work Breakdown Structure Estimated Estimated Cost Effort Work ID Work Name Description (Euro) (ManDays) Dependency module for communication with the BTMS system. 1.3.2.1.1 Design user friendly interface Gather information and feedback from different future clients of the 500 50 system for creating an easy to use and friendly user interface that allows the base activities to be easily achievable. 1.3.2.1.2 Create interactive bus seats scheme Create a web based scheme of the bus seats and allow the users to 260 26 book/purchase the desired seat. This will require a real time synchronization with the bus ticket management system in the bus companies. 1.3.2.2 Integration with payment portals Integrate the application with the most popular payment methods 400 40 1.3.2.2.1, 1.3.2.2.2 available for the bulgarian online market. Research of these methods. 1.3.2.2.1 Google checkout Integrate a google checkout in the system. Research 150 15 1.3.2.2.2 ePay Integrate the ePay payment system. Research. 150 15 1.3.3 Integration of both modules Integrate and test the synchronization of the both modules (The BTMS 220 22 and the OTSS). 1.3.4 Additional services Create additional services for the web portal: 400 40 - Voting for the media to be played in the bus - Rating of companies - Forum 1.4 System delivery and integration The next step will be the system delivery and integration for each of the 3500 350 1.4.1, 1.4.2 client companies. At this point we expect to receive payments that will cover our expenses made so far. 1.4.1 Installing, configuring, testing of the system Make the needed customizations in order to setup the system client side 2000 200 and perform testing in order to validate that everything works as expected. 1.4.2 Training Train the customer’s emploeeys how to use our system. 1500 150 1.5 Provide system support The rest concerning the TMS system is providing system support for the 8000 800 negotiated period of time. Confidential Page 4 6/15/2010
    • Work Breakdown Structure Confidential Page 5 6/15/2010