h

Saturday, May 2, 2015

Operating A bus Rapid Transit System final froject of software Engineering


Operating A bus Rapid Transit System

  
         This Recommended Practice provides guidance for operational
Considerations for bus rapid transit system
In recent years, public transportation systems have been            implementing and studying a wide variety of technological and service innovations. Curiously enough, these innovations have generally been considered essentially independently of each other:              

(a)  Information systems to enhance fleet management and passenger information, often under the general category of “Advanced Public Transportation Systems”, APTS;
(b)  fully-automated guide way transit (AGT) systems, including automated metro operations;
(c)  high-occupancy vehicle (HOV) lane operations on freeways, separating buses, vanpools and carpools from the more congested traffic on the general mixed-flow lanes;
(d)  light-rail transit (LRT) deployments in smaller and less dense urban areas than have previously been considered candidates for rail transit services;
  
2-Background and Justification:

      The purpose of this document is to provide guidance to planners, transit agencies, local governments, developers and others interested in operating a BRT systems or enhancing existing BRT systems. This Recommended Practice is part of a series of APTA documents covering the key elements that may comprise a BRT system. Because BRT elements perform best when working together as a system, each Recommended Practice may refer to other documents in the series. Agencies are advised to review all relevant guidance documents for their selected elements.

3-Project Methodology:

 Automated fare collection (AFC) system
       Automatic Fare Collection (AFC) System is a travel ticketing system                                                                                 which allows collection & management of fare for public transport in a prompt and accurate manner, through the deployment of information technology systems. This system allows the automated collection of payment through PDAs and Ticket Vending Machines (TVMs). AFC system reduces the need for ticket checking staff and helps to prevent fraud. OFF-Board ticketing system is provided for collection of fare on all MBS route.


Bus scheduling system (BSS)
      The BSS system helps to manage and control the route scheduling and bus route operation via state of the art Operations Control Centre being established at the ARFA Software Technology Park, Lahore.


Vehicle tracking system (VTS)
VTS System allows tracking of the bus, and conveying real time bus information to the bus station, control center and for telemetry. The VTS System uses a Driver Console for the exchange of textual information between the driver and control center.
·        We use iterative process for our project.
·        For designing use HTML/CSS, J-query, java script.
·        PHP use for navigation between pages for data recorded (teachers, students, assignments, plagiarism detection).
·        Use Algorithm or PHP code for plagiarism detection in student’s assignments.

          Combining the OBRT information technologies with BRT service should be relatively straightforward because these are naturally complementary to each other and the risks are low. However, some more dramatic opportunities arise when combining BRT service with AGT-like automation technology and HOV lane operations. The transit industry has the advantage of having already developed a substantial body of design and operating experience with driverless automated vehicles operating on their own guide ways in applications such as Vancouver’s Sky train, Lille’s VAL Metro, London’s Docklands Light Railway, Lyons’ MAGGALY Metro and Paris’ Meteor Metro. Millions of passengers use these systems safely every week, and the technology for designing and verifying their safety has been developed over the past two decades. Combining that body of technology with the emerging and parallel developments in collision warning and
Avoidance systems for road vehicles provides the technological basis for automated BRT operations
Constraints
1. In our project problem may be occurring due to lack of education of      common man.
2. Problem in loading page.
3. Problem occurs during online booking.

Assumptions
Our project provides the facility to customer that they buy their tickets from everywhere on internet.

FUNCTIONAL REQUIREMENTS

Bus Scheduling Module

 v Add new schedule
ü The system has a function that allow the administrator to add the new schedule and destination to the driver
ü The system will check on the same time , same day and the same driver that already have the schedule or not, if yes then then the system will not allow the administrator to add the new schedule for the particular driver on the same time , day and place.
ü If not then the administrator can assign the new schedule for the particular driver
v Edit Schedule Detail
ü  The system has a function that allows the administrator to edit the schedule that already assigned. If have any happen occur  so that the administrator need to reassign the schedule for the driver
v View Schedule Detail
ü The system has a function that allow the driver to view the schedule that assign by the administrator according to their name so the driver can know when and what time they should drive the bus from one destination to another
v Delete Schedule Detail
ü The system has a function that allows the administrator to delete a schedule for the particular driver if they feel that the schedule not suitable for particular driver on that time.
Repairing Module

v Add new Service
ü The system has a function that allow the administrator to add new service detail for bus if have bus send for service and detail will insert into the database
v Edit Service Detail
ü  The system has a function to allow administrator to edit service details such as update the maintenance fees for the bus service when the bus send back from service company
v Vie Service Detail
ü  The system has a function to allow administrator to view the service details such as which bus still under maintenance


Reservation Module

v Add Reservation
ü  The system has a function that allows member to add reservation via online. When the member click the next button then will go to online payment form to make payment.
v Add Reservation Payment
ü  The system has a function that allows the member to add reservation payment via online
ü  When the member click the next button then will go to online payment form and the member will key in all the information in the payment form then the system will check the credit card no and credit card expire date whether is valid or not.


Maintenance Module

Ø Staff Maintenance
 v Add new Staff
ü  The system has a function to allow administrator to add new staff for the company.
ü  The system will check the staff IC whether already exist in the database or not, if the IC for the staff already exist then the administrator cannot add the new staff and the details to the company database. If the IC does not exist in the database so that the administrator can add the new staff for the company database.
v Edit Staff Details
ü  The system has a function that allows the administrator to edit the staff details for the company if those staff has change the personal information so they will inform the administrator and the administrator will help them to update the details for them so there details will become updated.
v View Staff Details
ü  The system has a function that allows the administrator to view the staff details in the company database.
ü  Administrator can search their details based on ID and staff name. After select the staff ID from the system then click the search button then the details for that particular staff ID will list out in the form to let the administrator to view.
v Delete Staff
ü  The system has a function that allows the administrator to delete the staff the in the company database if the staff resign from the company and no longer belong to the company.

Ø Member Maintenance
 v Add New Member
ü  The system has a function that allows the administrator to add new member for company.
ü  The system will check the member IC whether already exist in the database or not, if the IC for the member already exists then the administrator cannot add the new member and the details to the company database. If the IC does not exist in the database so that the administrator can add the new member for the company database.
v Edit Member Details
ü  The system has a function that allows the administrator to edit the member details for the company if those members have change the personal information so they will inform the administrator and the administrator will help them to update the details for them so there details will become updated.
v View Member Detail
ü  The system has a function that allows the administrator to view the member details in the company database.
ü  Administrator can search their details based on ID and member name. After select the member ID from the system then click the search button then the details for that particular member ID will list out in the form to let the administrator to view.
v Delete Member
ü The system has a function that allows the administrator to delete the member the in the company database if the member wish to withdraw the membership from the company so they can inform the administrator

Bus Maintenance
v Add new Bus
ü  The system has a function that allows the administrator to add the new bus for company if the company buys anew bus.
v Edit Bus Detail
ü  The system has a function that allows the administrator to edit the bus details such as the driver name, engine modal, transmission modal, color and so on.
v View Bus
ü  The system has a function that allows administrator to view the bus details inside the company database so that can know how many busses belong to the company.
v Delete Bus
ü The system has a function that allows the administrator to delete the bus inside the company database if the bus already used many years and cannot use anymore for the company to carry the passenger.


NON-FUNCTIONAL REQUIREMENTS
vConvenient
ü  Creating this new system can bring a lot of convenient to customer and staff for example , If customer need to book the bus ticket, they no need to go to the bus station to booking or buying the bus ticket especially the person who is staying very far away from the bus station. They can directly use this system via internet; it can bring a lot of convenient to the customer who driving to the bus station for buying bus ticket. It also bring convenient to the people who are busy, so they can online booking at any time.
ü  Beside that the system brings a lot of convenient to the staff when they are able to search the information for customer such as search the bus available time and the seat. It also enables the staff to maintain the data easier.
ü  This system also can bring the convenient to the manger such as enables the manger to view the report easier and this system can use to summarize the top sale or provide the daily, monthly or yearly report and so on. So manager no need to expand a lot of time to view the hard copy report.
v Improve Efficiency
ü  The process time of the current system are time consuming because the current system are using paper work to record down all information. Its take a lot of time to serve customer when the staff searching the available time and seat. The purpose of creating this system is to improve the efficiency time of process. It can let the staff search the information faster and easier and maintain the data faster and reduce the paper work.
v Increase Income
ü  Made reservation using online method can attract more customers because made reservation online can save a lot of time for the customer. If can let the customer feel convenient, so that they will come to our company buy the bus ticket more often when they went go to somewhere around the country so we can earn more income from them.
v Bus And Ticket Information
ü  This system can let the customer know the information about the bus schedule and ticket. Nowadays, online is very common issue to everyone so that checking information using online can save a lot of time to the customer. Customer no need go to the counter to asking about the information of the bus schedule and the schedule.
v Reduce Error Data
The purpose of creating this system is let the staff to reduce key in wrong data, because system are using the computer to key in the data, there got some validation to check when staff key in the data wrongly and system will provide some selection to let staff direct choose the data. It also reduce the paper work to record all information, so it bring the benefit for reduce

                  SYSTEM DESIGN

FUNCTIONAL MAODAL


                                Context level diagram for bus ticketing system


     Level 1 DFD for bus ticketing system


   Level 2 DFD for bus ticketing system


                                   
USE CASE DIAGRAM


Use case Description

Actor
1.      Passenger
User case
  1. Login
  2. Check Availability
  3. Booking Pass details
  4. Seat Selection
  5. Window
  6. Non Window
  7. Payment
  8. Cheque
  9. Credit card
  10. Cancellation
  11. Cancel Receipt Generated
  12. Payment Deduction
 Description
  1. Login: It allows the existing user to login.
  2. Check Availability: It verifies the user login against the password.
  3. Booking Pass details: It allows the user to enter the passenger details.
  4. Seat Selection: It allows the user to select the passenger seat.
  5. Window: It allows the user to select the window seat.
  6. Non Window: It allows the user to select the non-window seat.
  7. Payment: It allows the user to make the payment according to the selected mode.
  8. Cheque: It allows the user to make the payment.
  9. Credit card: It allows the user to make the payment by credit card.
  10. Cancellation: It allows the user to make cancellation.
ACTIVITY DIAGRAM
      Activity diagram models the logic from workflow to use cases to methods. It borrows most of the notations from the flowchart but has added the concept of concurrency to support many modern applications. The arrow traces the flow from beginning to end through decision and loops, while identifying each logic steps in the process
Activity diagrams represent the business and operational workflows of a system. An Activity diagram is a dynamic diagram that shows the activity and the event that causes the object to be in the particular state Activity modeling focuses on the execution and flow of the system, rather than how it is implemented. They are applicable to any type of behavioral modeling. Activity diagrams captures activities that are made up of smaller actions. When used for software modeling activities typically represents a behavior invoked as a result of a method call.
      Activity diagrams are typically used for business process modeling, for modeling the logic captured by a single use case or usage scenario, or for modeling the detailed logic of a business rule.  Although UML activity diagrams could potentially model the internal logic of a complex operation it would be far better to simply rewrite the operation so that it is simple enough that you don’t require an activity diagram. In many ways UML activity diagrams are the object-oriented equivalent of flow charts and data flow diagrams (DFDs) from structured development.
       The easiest way to visualize an Activity diagram is to think of a flowchart of a code. The flowchart is used to depict the business logic flow and the events that cause decisions and actions in the code to take place
     So, what is the importance of an Activity diagram, as opposed to a State diagram? A State diagram shows the different states an object is in during the lifecycle of its existence in the system, and the transitions in the states of the objects. These transitions depict the activities causing these transitions, shown by arrows.
  
 ACTIVITY DIAGRAM


Sequence Diagram
Sequence diagram is one kind of interaction diagrams, which shows an interaction among a set of objects and their relationships. The purpose of the Sequence diagram is to document the sequence of messages among objects in a time based view. The scope of a typical sequence diagram includes all the message interactions for a single use case.
The sequence diagram is used primarily to show the interactions between objects in the sequential order that those interactions occur. Much like the class diagram, developers typically think sequence diagrams were meant exclusively for them. However, an organization's business staff can find sequence diagrams useful to communicate how the business currently works by showing how various business objects interact. Besides documenting an organization's current affairs, a business-level sequence diagram can be used as a requirements document to communicate requirements for a future system implementation. During the requirements phase of a project, analysts can take use cases to the next level by providing a more formal level of refinement. When that occurs, use cases are often refined into one or more sequence diagrams


                                                  Sequence Diagram for login



                                             Sequence Diagram for Reservation




                                                Sequence diagram for Cancellation


                             
Class Diagram
Class diagram, one of the most commonly used diagrams in object-oriented system, models the static design view for a system. The static view mainly supports the functional requirements of a system – the services the system should provide to the end users. We will see from our practical experience that lots of fun comes out when modeling out system with class diagrams.
A class diagram shows a set of classes, interfaces, and collaborations and their relationships.
Class diagrams involve global system description, such as the system architecture, and detail aspects such as the attributes and operations within a class as well. The most common contents of a class diagram are:
Classes
Interfaces
Collaborations
Dependency, generalization, and association relationships
Notes and constraints


Class Diagram

                                                  Class diagram for Bus ticketing system