Fatih University Department of Computer Engineering

Software Engineering Project

BUS AUTOMATION SYSTEM

Ahmet lker Yaman Ali Bayraktar Hakan Demir Mehmet Zeki Kr mer Faruk Sker

Requirement Analysis Document December 29th, 2008

TABLE OF CONTENTS 1. INTRODUCTION.3 1.1. Purpose of the system.3 1.2. Scope of the system3 1.3. Objectives and success criteria of the project.3 1.4. Definitions, acronyms, and abbreviations .3 1.5. Overview 4 2. CURRENT SYSTEM....4 3. PROPOSED SYSTEM..4 3.1. Overview4 3.2. Functional Requirements4 3.3. Nonfunctional Requirements.5 3.3.1. Usability..5 3.3.2. Reliability5 3.3.3. Performance5 3.3.4. Supportability.5 3.3.5. Implementation...5 3.3.6. Interface..5 3.3.7. Packaging6 3.3.8. Legal6 3.4. System Models...6 3.4.1. Scenarios.6 3.4.2. Use Case Model..7 3.4.3. Object Model12 3.4.4. Dynamic Model13 4. CONCLUSION16 5. GLOSSARY16 6. REFERENCES16

1. INTRODUCTION 1.1. Purpose of the system In Turkey most of the people travel overland route, and most of these travels made by buses. So people have to go to the travel agencies to make reservations or buy a ticket. At least they have to call a phone to make reservations or ask about departure time etc. While internet spreads over world also over Turkey, so to adapt travel agencies use of internet to make reservations or sell ticket is main purpose of the system. Also make people to have travel agencys card (become a member) is also important to make loyal customers, of course by giving some advantages to them. 1.2 Scope of the system The system can be used by customers via internet to help them about their journeys neither using a phone nor having to come travel agency. There is three main usage of system: Query the system about travel routes, departure-arrival stations and time Make reservation Buy ticket Cancel reservations

1.3 Objectives and success criteria of the project: The objectives of the project are to: provide people who are not member of the travel agency query the necessary info for their travels and buy a ticket with their credit card info provide people who are member of the travel agency the preceding facilities and also make reservation, and give extra points to them

The success criteria of the project is to make travel agency a leading agency and also make customers loyal to agency by providing extra points and discounts. 1.4 Definitions, acronyms, and abbreviations BAS : Bus automation system that provides facilities to passengers Member Passenger: The passenger who is registered to system and also who have the travel agency card Non-member Passenger: The passenger who is unregitered to system or who does not have travel agency card Salesperson : The represantative of travel agency who sells ticket or make reservation for travel agency in a terminal Administrator: The user who has the rights to create new travel routes and add travels to he system 3

1.5 Overview BAS is a system which makes easy the job of travel agencys work by providing reservations or selling ticket over internet. 2. CURRENT SYSTEM The BAS project is a greenfield engineering project. There is no current system to replace and the tasks of BAS are not accomplished by now. 3. PROPOSED SYSTEM 3.1. Overview: The proposed system will help the travel agencies to control the reservations and ticket services by both the passenger side and the salesperson side. In passenger side users can easily query the travels as from their departure stations, arrival stations and date. They can easily make reservation or buy ticket by their credit cards. Also in salesperson side user can easily sell ticket to passengers and cancel the tickets by system facilities. 3.2. Functional Requirements The functional requirements of the system are: The member passengers , the administrators and the salespersons must be able to log on the system by their user ids and passwords The users and also the people who are not user of the system must be able to query the travels The member and non-member passengers must be able to buy ticket by providing credit card info but only member passengers should be able to make reservation The administrators must be able to add new travel routes The administrators must be able to add new travels from existing travel routes The salesperson must be able to sell ticket in terminal by using system but passengers credit card info is not needed to enter in the system because payment is collected by hand or by credit card using POS machine The salesperson must be able to cancel the ticket which passenger wants to cancel 4

If a travel is delayed or canceled the passengers will be called by phone by travel agency

3.3. Nonfunctional Requirements 3.3.1. Usability Users who can browse internet with a web browser can easily adapt the usage of system. Since there are usually buttons, hyperlinks and lists are used most people familiar with them. Users will be notified if there is a warning or something necessary to inform users by the system or by sending e-mail. 3.3.2. Reliability System maintains the user accounts in an encrypted format no one can access the users info. The transactions made by credit card is also encrypted and no credit card info is stored in system. The transactions use SSL. Data backup can be made by travel agency by manually while transaction number is low. If the connection breaks during transaction users will be notified by e-mail if the transaction is completed or not. 3.3.3. Performance Performance will be depend on the users internet speed. Since our system is designed for concurrent usage the web server is sufficient to complete concurrent transactions. The server is able to handle 1000 concurrent connections at the same time. If needed the web server can be replicated. 3.3.4. Supportability The system is supported by a web server installed on it an IIS server. So it can be easily ported to any web server which has an IIS servr on it. There can be extensions to the system in request of customers , like providing a bus scheduling system. 3.3.5. Implementation The system is implemented with Visual Studio .NET platfrom using ASP.NET with C# language. The database management system is Microsoft SQL Server but it can interchangeable by customers need. 3.3.6. Interface Interface is an easy web site browseable by any unexperienced user that provides good usability. Data imports and exports made by SQL queries under the system.

3.3.7. Packaging System needs no installation on neither travel agency side nor passenger side. Since system is web based new versions can easily be uploaded to travel agency web server and needs no installation. 3.3.8. Legal System license term aggrements will be made between our side and travel agency side. Travel agency can not give the system to any third party or person. 3.4. System Models 3.4.1. Scenarios These are the possible scenarios that a user can accomplish using this system: I. Querying a travel: The user browse the query travel page ,then he enters info about search like departure station, arrival station and date of travel. After search system gathers possible travels and lists. II. Making a reservation: After selecting appropriate travel, user determines appropriate seat for passenger and system makes the reservation. III. Buying a ticket: After selecting appropriate travel, user determines appropriate seat for passenger then does the payment with credit card info. IV. Converting a reservation to a ticket: After passenger selects the reservations which he wants to convert a ticket, then does the payment with credit card info. V. Selling a ticket: The salesperson selects the travel and seat according to the passenger request then enters the system the seat is sold. Since payment is by hand no system interaction. VI. Canceling a ticket: The salesperson searches then selects the ticket which passenger wants to cancel after enters the system the ticket is cancelled. 6

VII. Creating a new travel route The administrator creates a new travel route by adding departure, destination and middle stations and also reaching time to stations. VIII. Creating a new travel The administrator creates a new travel by selecting from available travel routes and adding date, time, bus, quota of travel. 3.4.2. Use Case Model

Figure 1: Use Case Diagram The use cases are explained below in detail: I. Use Case Name Initiating Actor Participating Actor Entry Condition Flow of Events : QueryTravel : Passenger or Salesperson or Administrator : none : The actor logged into system or actor browsing our site without login : 1) User browse the query travel page 2) User selects the departure station 3) System brings in the arrival stations according to the departure station 4) User selects the arrival station 7

Exit Condition II. Use Case Name Initiating Actor Participating Actor Entry Condition Flow of Events

5) User selects the date of the travel from calendar 6) User clicks the query travel button 7) System collects the travels according to departurearrival stations and date, then it lists the travel number and name ,departure time and price of the travel : The user observes the result of his query

: MakeReservation : Member Passenger or Salesperson : none : User is logged into system : 1) User use the QueryTravel use case 2) User selects the appropriate travel for passenger 3) System shows the bus schema with selectable seats 4) User selects the appropriate seat for passenger from selectable seats 5) The selected seat is blocked for passenger 6) User clicks the make reservation button 7) System notifies user the reservation is made for passenger Exit Condition : User has received an acknowledgement that reservation has been made Quality Requirements :* Reservation will be canceled by the system if passenger will not convert his reservation to ticket before 24 hours from departure time * If the connection breaks during the transaction; passenger will receive an e-mail if the reservation is completed in server side otherwise no e-mail will be sent : BuyTicket : Passenger : none : User logged into the system : 1) User use the QueryTravel use case 2) User selects the appropriate travel for passenger 3) System shows the bus schema with selectable seats 4) User selects the appropriate seat for passenger from selectable seats 5) The selected seat is blocked for passenger 6) User clicks the buy ticket button 7) User use the PayWithCreditCard use case : *System acknowledges passenger that passenger has bought the ticket 8

III. Use Case Name Initiating Actor Participating Actor Entry Condition Flow of Events

Exit Condition

*System acknowledges passenger that passenger has not bought the ticket because invalid credit card info Quality Requirements : *Credit card info is collected by a secure system * If the connection breaks during the transaction; passenger will receive an e-mail if the transaction is completed in server side otherwise no e-mail will be sent IV. Use Case Name Initiating Actor Participating Actor Entry Condition Flow of Events : PayWithCreditCard : System : Passenger : System redirects passenger to fill credit card info : 1) System represents a form to passenger to fill credit card info 2) Passenger fills the form then sends to system 3) System make validation control of credit card info Exit Condition : System notifies passenger according to validation result Quality Requirements : Credit card info is collected by secure system : ConvertReservationToTicket : Member Passenger : none : Member Passenger logged into system and clicks his reservations : 1) System lists the reservations made by passenger 2) Member Passenger selects the reservations which he wants to convert to ticket 3) Member Passenger use the PayWithCreditCard use case :*Reservations are changed into ticket if Member Passengers credit card info is validated *Reservations are not changed into ticket if Member Passengers credit card info is not validated *Reservations are canceled if the remaining time to departure time becomes less than 24 hours : AddTravelRoute : Administrator : None : Administrator logged into system and browse the add travel route page : 1) Administrator adds the departure station 2) Administrator adds the middle stations and rest places and also add the approximate minute how are they far away from departure station 9

V. Use Case Name Initiating Actor Participating Actor Entry Condition Flow of Events

Exit Condition

VI. Use Case Name Initiating Actor Participating Actor Entry Condition Flow of Events

3) Administrator adds the arrival station and the arrival minute for the arrival station 4) Administrator clicks the add travel route button 5) System names the travel route as the departure station-the arrival station and adds the database 6) System notifies the administrator that the travel route has been added Exit Condition :* System notifies the administrator the new travel route has been added *System notifies the administrator the travel route has not been added because it already exists Quality Requirements : Travel route names must be unique by naming them as departure station-arrival station VII. Use Case Name Initiating Actor Participating Actor Entry Condition Flow of Events : AddTravel : Administrator : none : Administrator logged into system and browse the add travel page : 1) Administrator selects the travel route from existing travel routes which is related with new travel 2) Administrator enters the date and departure time of travel 3) Administrator selects the bus type and enters the number of seats 4) Administrator clicks the add travel button 5) System notifies the administrator the new travel has been added : New travel has been added to the system : SellTicket : Salesperson : Passenger : Salesperson logged into the system and browse sell ticket page : 1) Salesperson use the QueryTravel use case 2) Salesperson selects the appropriate travel for passenger 3) System shows the bus schema with selectable seats 4) Salesperson selects the appropriate seat for passenger from selectable seats 5) The selected seat is sold to the passenger : *The ticket is sold to the passenger *The ticket is not sold to the passenger because of no available seat 10

Exit Condition VIII. Use Case Name Initiating Actor Participating Actor Entry Condition Flow of Events

Exit Condition

IX. Use Case Name Initiating Actor Participating Actor Entry Condition

: CancelTicket : Salesperson : Passenger : Salesperson logged into the system and browse cancel ticket page Flow of Events : 1) Salesperson enters the id of the ticket which the passenger wants to cancel to the system 2) System shows the ticket to salesperson 3) Salesperson clicks the cancel ticket button 4) System notifies the salesperson the ticket is canceled Exit Condition : *The ticket is canceled *The ticket is not canceled because of the remaining time to the departure becomes less than 6 hours Quality Requirements : The ticket can only be canceled if the remaining time to the departure is more than 6 hours

11

3.4.3. Object Model 3.4.3.1 Class Diagram

Figure 2 : Class Diagram of Bus Automation System

12

3.4.4. Dynamic Model 3.4.4.1 Sequence Diagrams

Figure 3 : Sequence Diagram of Query Travel

Figure 4 : Sequence Diagram of Make Reservation

13

Figure 5 : Sequence Diagram of Create Travel Route

Figure 6 : Sequence Diagram of Add Travel

14

Figure 8 : Sequence Diagram of Convert Reservation to Ticket

Figure 8 : Sequence Diagram of Buy Ticket

15

4. CONCLUSION The rapidly developing internet technology provides facilities to people in order to ease their lives. Our project is a system that provides people who can easily make reservation or but ticket for their travels. There is no need to any installation or any requirements to the users of the system except the usage of internet. The user interface is also so easy for anyone who browse the internet. This project will be very useful for both people who want to travel easily and for travel agencies by reducing their expenses and reaching to more people. 5. GLOSSARY Travel Route : Travel route is the route of travel which consists of stations mainly departure and arrival stations, there can be also middle stations and rest places. Travel : Travel consists of the travel route with a determined date and time Internet Information Services (IIS) : Formerly called Internet Information Server - is a set of Internet-based services for servers created by Microsoft for use with Microsoft Windows. The servers currently include FTP, SMTP, NNTP, and HTTP/HTTPS. Secure Sockets Layer (SSL) : Secure Sockets Layer is cryptographic protocol that provide security and data integrity for communications over TCP/IP networks such as the Internet. Several versions of the protocols are in wide-spread use in applications like web browsing, electronic mail, Internet faxing, instant messaging and voice-overIP (VoIP). Microsoft Visual Studio : Microsoft Visual Studio is an Integrated Development Environment (IDE) from Microsoft. It can be used to develop console and Graphical user interface applications along with Windows Forms applications, web sites, web applications, and web services in both native code together with managed code for all platforms supported by Microsoft Windows, Windows Mobile, Windows CE, .NET Framework, .NET Compact Framework and Microsoft Silverlight. Microsoft SQL Server: Microsoft SQL Server is a relational database management system (RDBMS) produced by Microsoft. Its primary query languages are MS-SQL and T-SQL. 6. REFERENCES I. Bernd Bruegge, Allen H. Dutoit; Object-Oriented Software Engineering; PrenticeHall; 2004. II. http://en.wikipedia.org/wiki/Main_Page III. http://wwwbruegge.informatik.tu-muenchen.de/twiki/bin/view/OOSE/WebHome IV. http://msdn.microsoft.com/tr-tr/default.aspx 16