Sky Bus Design @2005

INSTITUTE OF TECHNOLOGY (IOT) SCHOOL OF INFORMATICS PROJECT TITLE: - ONLINE SKY BUS TICKETING RESERVATION SYSTEM

GROUP MEMBER NAME IDNO ABDISA DEMISSIE IS/007/02 TUCHA KEDIR IT/497/02

Advisor Name Vinod ChandranTable of ContentsCHAPTER ONE11. INTRODUCTION11.1 Background21.2 statement of problems21.3 objective21.3.1 General objectives31.3.2 Specific objective31.4 scope of the project31.5 Limitation of the project41.6 Significance of project51.7 Methodology51.8 System design and development61.9 Development and Enviroment programming tools81.10 Schedule of project9CHAPTER TWO132. SYSTEM REQUIREMENT AND SPECIFICATION DOCUMENT (SRS)132.1 Purpose132.2 Description of the existing system132.3 Stake holders in Existing system132.4 Problem of existing system142.5 Comparison between Manual and Computerized ticketing system152.6 Feasibility study152.7 Application of the project18 CHAPTER THREE193. SYSTEM STUDY AND ANALYSIS193.1 Description of the Proposed System193.2. SYSTEM REQUIREMENTS203.2.1 Functional Requirements203.2.2 Non-Functional requirement213.3 Use case253.4 Class Responsibility and Collaboration Domain353.5 Sequence Diagram363.6 Class diagram403.7 User Interface Flow Diagram423.8 Activity Diagram43CHAPTER FOUR464. SYSTEM DESIGN464.1 Deployment modeling474.2 Database Design474.3 Relationship of the Database534.4 INTERFACE DESIGN564.5.1 Navigation Tree564.5.2 User Interface58CHAPTER FIVE685. CONCLUSION AND REFERENCE685.1 Conclusions685.2 Reference68

LIST OF FRIGURESFig 1: waterfall model----------------------------------------------------------------8 Fig 2: use case model for online Sky Bus Ticketing Reservation system---------------------26Fig 3: Member and Non Member customer ticketing reservation system Use case model-----27Fig 4: Class Responsibility and collaboration Domain----------------------------------- 36Fig 5: sequence diagram for journey reservation--------------------------------------- 37Fig 6: Sequence diagram for ticket withdraw------------------------------------------ 38Fig 7: Sequence diagram for choose seat number-------------------------------------- 39Fig 8: Class diagram for online Sky Bus Ticketing Reservation system --------------------------------41Fig 9: User Interface Flow Diagram---------------------------------------------------43Fig 10: Ticket Reservation System activity Diagram------------------------------------ 44Fig: 11 Ticket Cancellation activities Diagram ---------------------------------------- 45Fig 12: Deployment Diagram of Ticket Reservation-------------------------------------47

CHAPTER ONE1. INTRODUCTION Traveling is a large growing business in Ethiopia. It becomes very difficult to keep records for large number of items, customers and calculating bills. Sky Bus is one of the travels but not much developed in Ethiopia. This is the project on the online ticketing system of express sky Bus Company, which in most cases; the company has problems with their ticketing and scheduling process. This project intends to computerize its semi- computerized ticketing system to provide better customer service. Because of that, the company can provide the easier way of travelling to the customer or passenger. The system is sky Bus Ticket Reservation System. We observed the working of the sky bus ticketing reservation system and after going through it, we get to know that there are many operations, which have to do manually. It takes a lot of time and cause many errors. Due to this, sometimes a lot of problems occur and they were facing many disputes with customers. To solve the above problem, and further maintaining records of items, seat availability, price of per/seat, bill generation and other things, we offering this proposal of sky bus reservation system. This project is modularized a sky Bus ticketing system consists of all the activities involved in producing a ticket which includes:- Enquire the availability of seats in particular bus at particular date. Producing tickets Total tickets produced for a trip Booking ticket cancelation of the tickets

1.1 Background Sky Bus transport system is an intercity coach or share company based in Addis Ababa, Ethiopia. It is organized in 2000 according to E.C. Which is owned by Share Company registered with the Federal Ministry of Trade and Industry under the Ethiopian commercial code ,Headquartered in Addis Ababa, Bole Area, friendship building. It can hold 3,000 share holders and started by having different branches like Gondar, Bahirdar, Jimma, Hawassa, Dire-Dawa, Harar, Dessie and Jijiga, sky bus proudly transports the most precious creature on Earth to those destinations.1.2 Statement of problemsSystem that are using by the staff at the counter currently is an internal system and just used to sell the sky bus ticket at the counter (totally it is manual systems). Customer has to go to the counter to buy sky bus ticket or ask for bus schedule. Furthermore, customers need to pay cash when they buy the sky bus ticket and sometimes needs to queue up long time to get the sky bus ticket. Besides that, customer also not allowed buying sky bus ticket through telephone and the sky bus company's telephone always-busy line and there is also a punishment when the customer wants to reschedule or cancel their travel. The method to solve this problem is to create an online buying sky bus ticket system. Customer can buy the sky bus ticket over the Internet, 24 hours a day, 7 and the sky bus ticket can't be lost, stolen or left behind. In addition, the online system lets the customers check the availability of the bus ticket before they buy the sky bus ticket.The counter clerk has to manually calculate the total amount of the ticket sold and send the daily report to the management. The daily ticket sale accounts form must fill by the clerk daily and passed to officers on duty for verification.1.3 ObjectiveThe main purpose of the online buying sky bus ticket system is to provide another way for the Transnationals customer to buy sky bus ticket.

1.3.1 General objectives To develop online reservation and ticketing system that have been replaced the manual ticketing system. 1.3.2 Specific objective To provide anytime anyplace service for the customer. Customer can buy sky bus ticket 24 hours a day, 7 days a week over the Internet. To enable customer to check the availability of the sky bus ticket online. Customer can check the time departure and arrival for every Transnationals bus through the system. To minimize the number of staff at the ticket box. The numbers of staff at the counter can be reducing after the online buying sky bus ticket system launch. To implement the new developed system and increase the customer satisfaction It replaces all the paper work To Reduced search time 1.4 Scope of the project The online sky bus system is an easy-to-use self-service system which enables the customer to buys sky bus ticket online. Customer has to check the availability of the sky bus ticket before they buy the sky bus ticket. After process buys sky bus ticket is successfully, the customer can get the sky bus ticket by print out the sky bus ticket and give the sky bus ticket to the sky bus driver when he/she wants to take bus.Besides departure place, arriving place, departure date, departure time and ticket number, the sky bus ticket also wills states the seat number that assigned by the system automatically. Generally the scope of our projects includes the following pointsA person should be able to:1. Registered to the system through the first page of the application2. See his/her current reservations on different sky buses along with the details.3. Register to the system through the application4. View current travel plans of the sky bus transport systems5. Make reservation.6. See his/her current reservation from the details.7. Withdraw reservation.8. Able to choose the seats9. A message should be sent to the concerned person about the confirmation of the ticket to the specified system.10. A calendar should be there which helps the person to select dates. It should also show the public and nation holidays.11. The system should automatically show the schedule for the corresponding seat and amount of money needs to be pay for selected seats.12 Upon payment the clerk should be able to use the system to update the status of reservation1.5 Limitation of the projectTo develop an online sky bus reservation system all the needed requirements need to be fulfilled. In the context of this project there are restrictions and drawbacks which can be considered as limitations of the project. In general the limitations are: Expensiveness when we say expensiveness, to use our website we have to get an accessories and materials like computer, internet access, etc so for those materials they are expensive. Limited access when we use the website, there must be an internet access. The place whose does not have an internet connection, there is no chance to use our website. Skill ability the website user or consumer who does not have knowledge and skill ability how to use internet, so it does not consume our service. Shortage of equipments There may be a power fluctuation in the lab; this may cause not to finish the project in the estimated schedules. Our files and documents may be affected by a virus and worms. This limitation is as a result of less budget allocation and shortage of time. Interruption of the information while we are asking some workers in the company for collecting information because of crowded of customer when they come to the sky bus company for buying sky bus ticket. 1.6 Significance of projectThe online sky bus is very important company for customer, sky Bus Company and all. It is important to customer because customer can check availability of the sky bus ticket, buy sky bus ticket. Electronic ticket is different with traditional paper ticket because electronic ticket is safer, faster, reliable and cheaper. Besides that, this concept can be used by others sky bus company so that their customers will be easier. The profit for the sky bus company will be increased because the online system will attract more customers and no need to hire many staffs at the counter to sell sky bus ticket because ticket can be sold efficiency online. 1.7 Methodology Method of data collectionVarious methods can be adopted to gather information from a variety of sources. The following methods are used in our projects.

OBSERVATION Observation is the first method used to gather information regarding the development of an online sky bus reservation system. For this project we were visit to observe the buying habit of passengers and also observe the selling of tickets by the sky bus branch which is found in Hawassa. From the observation, we found that the human traffic is extremely high. INTERVIEW Interview is the second method used to gather some information regarding an online sky bus reservation system. Interview was conducted with the sky bus personnel in Hawassa branch office. 1.8 System design and developmentThere are many methodologies to carry out our system (project) but we have chosen to implement the object oriented approach because of the following few reasons: It is one of the widely accepted method The object-oriented approach combines data and processes (called methods) into single entities called objects which can be easy to show necessary operations. Object-oriented approach makes system elements more reusable, thus improving system quality and the productivity of systems analysis and design. Describes the real world by its objects, the attributes, services, and relationships Improved communication among users, analysis ,designer and programmers The ability to tackle more achieving problem domain Increased consistency among analysis ,design and programmers

Waterfall Development MethodologyThe Waterfall software development methodology is one of the most widely known and recognized methodologies and it is a software development life-cycle. Using the Waterfall software development life cycle, the implementation of the system is preceded by requirements definition, analysis, design and development. The online Sky Bus Ticketing reservation system is the project that done through a sequence steps that is from concepts to the through design, implementation, testing, installation, troubleshooting, and ends up at operation and maintenance and which follows the sequence of registering first before coming to reserving tickets and seats so the system is clear and obvious to the customer because of the reason that waterfall have advantages of:- Easy to use. It is simple and easy to explain to the user. The project requires the fulfillment of one phase, before proceeding to the next.

Fig 1: waterfall model

1.9 Development and Environment programming toolsA. System Development ToolsAnalysis tools Use case diagram Collaboration class diagram (CRC) Sequence diagram Class diagram User interface flow diagram Deployment Diagram Gant chart

Design tool Activity diagram Class Modeling Database design B. system Development EnvironmentSoftware Requirements Programming languages : PHP MS Office tools : MS-Word, PowerPoint Script : CSS Java script Data base or data retrieval quarries : MYSQL Notepad ++ Adobe Photoshop Microsoft Visio E Draw max trial version1.10 Schedule of projectThis project is expected to be completed in two semesters of this year. Some parts of the project component to be completed in the first semester are up to design and rest activities such as implementation, testing and maintenance would completed in the next semester including other minor activities. Schedule achievability is also making sure whether the potential time frames and Completion date can be met or not. We expect this Project to be completed on time as much as possible by reducing delay. On the Gantt chart below we have fitted the time given in a possible manner to bring about successfully completed system as scheduled. The Schedule for software development in the given months of the weeks which represents the estimate completion dates with the key project milestones.

Project schedule and Milestones Activity Start dateLast dateOut put

1.Briefing,complete project title Week1Week1List of title

2.Submit proposed title to supervisor Week1Week1Complete project suggestion form.

3.project description Week1 1Week1Describing about the project title and its features with advisor

4.data collection Week2Week3Gathering data from organization and different sources

5.project proposalWeek2Week3Writing project proposal

6.Mid term presentation Week4Week4Presenting what we have proposed

7.system designWeek 5Week7Designing

8.presentation on the system designWeek 8Week8Final report project or presenting the designed system

9.ImplementationWeek9Week12Implementing

10.TestingWeek 13Week14Analysis the existing system

11.Final document submissionWeek 15Week16Submitting the written document to advisor

12.Final presentationWeek 17Week17Elaborating the all designed system to final

MonthDecemberJanuaryFebruaryMarchAprilMayJune

WeakWeakWeakWeakWeakWeakWeak

Activity123 4123412341234123412341234

project proposal

system design

presentation on the system design

Implementation....

Testing

Final document submission

Final presentation

COST OF THE PROJECTThe project takes some costs to develop and implement some basic tasks. Our projects have been taking all the costs as the following table to summary. No ItemsPrice (In birr)Quantity

1paper50.00200

2CD10.002

3Pen7.002

4Transportation25.00Group

5Call phone10.002 times

6Print15.0015 pages

7Miscellaneous cost35.005 times

Total7152.00228.00

CHAPTER TWO2. SYSTEM REQUIREMENT AND SPECIFICATION DOCUMENT (SRS) 2.1 PurposeThe purpose of the software requirements specification document is to maintain all the functions and the Online Sky Bus Ticket Reservation system. Besides, it contains the detailed descriptions of all the requirements specified before.2.2 Description of the existing systemExisting system refers to the system that is being followed till now. Now a day in Ethiopia there is no online ticket reservation system. All of the ticketing systems in Ethiopia are conducted manually. Before tickets are sold to customers, trip to particular destination has to be scheduled which is fixed by the management of each bus operators. The destination and price are printed on the tickets for particular trips. The counter will manually reserve the tickets for the customers, which means the ticket sales counter clerk will put the ticket aside. The customer has to come personally to the ticket counter one day before the actual trip to collect the reserved ticket. Failing to do so, the ticket will then be released to other passengers.The ticket sales counter clerk has to manually calculate the total amount of the ticket sold and send daily report to the top management. Matter becomes complicated when several branches conduct the ticketing selling task for the same bus at the time. The ambiguities let the management face operation and accounting problems. 2.3 Stake holders in existing systemThe main users of this product are those who have the right to access this software. These users are sure to be literate with the computers.The user types that would use the online sky bus reservation system are as follows:Clerk: Clerk shall usually do anything on the site, in all pages. Clerk is also responsible for updating of the web site content such as adding/removing information about the company, adding/removing links onto the main bar, adding/removing Medias in the content menu, adding/removing/updating links on the calendar and the menu changing the logo.Customer: customers are people who shall use online sky bus reservation system. To use this service people have the basic computer using ability. They shall see the sky buses information which is belong to current time.Manager The manager can access all the functions in this system, which includes the bus operator information, view comment, member and staff account, and reports. 2.4 Problem of existing systemThe current sky bus reservation has the following limitation The passenger must wait for their required bus which is time consuming process, as it possible that sometimes there would be no buses available to the desired place for a long period of time. The passenger must reserve tickets directly. So they have to wait in long queue and reserve tickets. This will be time consuming Most of the records are maintained on paper. Existing system is totally on book and thus a great amount of manual work has to be done. The amount of manual work increases exponentially with increase in sky bus services Needs a lot of working staff and extra attention on all the records. More man power is required, so it is costly. Over price tickets to the same destination. The seller of paper tickets does not collect important information about the passengers Lack of security of data (anyone is able to see, change or deleting existing data).2.5 Comparison between Manual and Computerized ticketing systemAfter analyzing the manual and computerized ticketing system, a summary of comparison between both systems had been prepared as the following:-A. SYSTEM ORGANIZATIONIn the manual sky bus ticketing systems, the sale counter clerk has to write the price, source, destination, departure date, departure time and other ticket information manually on the ticket to be issued. This is prone human errors. Computerized system will alert if there is such errors. There will not be ticket forgery in the computerized systems because the system is updated on real-time basis and keeps track on all the transactions occurred.B.TICKET AVAILABILITIY The manual system is not organized compared to computerized system. The manual system is less efficient in identifying ticket availability compared to computerized system. Computerized system has clear view on the seat availability with the latest.2.6 Feasibility StudyFeasibility analysis begins once the goals are defined. It starts by generating broad possible solution, which are possible to give an indication of what the new system should look like. This is where creativity and imagination are used.Feasibility of a new system means ensuring that the new system, which we are going to implement, is efficient and affordable. There are various types of feasibility to be determined:- Technical feasibility Operational feasibility Economic feasibilityTECHINCAL FEASIBILITYThis evaluation determines whether the technology needed for the new system is available and how it can be integrated within the organization. The projects were going to expected greater return on their development; technical risks were also valuable tool to understand the sources and types of risks as well as their management.Risk Name Risk Management

-Failure to attain expected benefits from the project-Reviewing /Feedback mechanism of the project procurers

-Inaccurate project cost estimates-Allocating budgets for each task

-Inaccurate project duration estimates-Breaking tasks into section

-Failure to achieve adequately system performance levels.-Applying new/modified procedure

-Failure to integrate with the existing hardware, or software-Using the version of them

OPERATIONAL FEASIBILITYOperational feasibility covers two aspects. One is a technical performance aspects and the other is acceptance within the organization. Technical performance includes issues such as determining whether the system can provide the right information for the organization personnel, and whether the system can be organized so that it always delivers this information at the right place and on time.Operational feasibility must determine how the proposed system will fit in with the current operations and what, if any, job restructuring and retraining may be needed to implement the system.ECONOMIC FEASIBILITYThis evaluation looks at the financial aspects of the project. It determines whether the investment needed to implement the system will be recovered. Economic feasibility concerns returns from the investments in a project. It determines whether it is worthwhile to invest the money in the proposed project or whether something else should be done with it. To carry out economic feasibility study, it is necessary to place actual money values against any purchase or activities needed to implement the project. 2.7 Application of the project This project has great assumption to generate online sky bus reservation system in Share Company of sky bus. This project connects people like customer and company. Any people can investigate any online categorized services in his home, working place or any where using internet including mobile internet. The passenger goes to office personal when they want to travel to buy sky bus ticket, check availability of seat and cancel or reschedule their travel. Our proposed solution would eliminate those problems and make the system to be present online.

CHAPTER THREE 3. SYSTEM STUDY AND ANALYSIS INTRODUCTIONSystem Analysis is a phase which is conducted before the development of the Online Sky Bus Ticketing System web. System Analysis shows the requirement or a description of the needs and desires for an information system. A requirement may describe functions, features, and constraints. Thus, system requirement defines the services provided by the system and prescribes constraints for its operation.3.1 Description of the Proposed SystemThe proposed system is recommended that an online sky bus ticket reservation system a solution that attempts to solve many of the existing problems in the current sky bus ticketing system. The system provides proper security and reduces the manual work and it will help the user to reduce the workload and mental conflict.The objective of this system is to provide the organization a new system that provides all the functionality specified by the organization, that is more users friendly and less complex.In effort to improve the existing sky bus ticket over the counter, observation on the problems had been conducted. Therefore, the goal of the online sky bus ticket reservation system is to provide a revolutionary way to interact effectively.Effectives of online sky Bus Ticketing reservation system Online sky bus ticket reservation is more efficient compared to buying a sky bus ticket over the counter Online sky bus is user friendly It is more convenient It is relatively fast approach to know timing Relatively simple to use Is highly reliable, unless for network failure 3.2. SYSTEM REQUIREMENTS 3.2.1 Functional requirementsFunctional requirement is a function or feature that must be included in an information system to satisfy the business needs and user acceptance or descriptions of activities and services a system must provide. These requirements describe the interactions between the system and its environment independent of its implementation. The environment includes the user and any other external system with which the system interacts. Each is a statement of exactly what the system must do. A clear and detail functional system requirements for this system of the manger section, clerk and Customer section are described as following.The following are the Functional requirements associated with the new system. Allow someone to register to become a member. The system will send out automated emails to validated users. The user signup form should test that the form is filled in by a human and not a computer program. Customers buy tickets online by simply sitting in their house. Allow manager/clerk view

3.2.2 Non-functional requirementNon-functional requirement is a description of the features, characteristics, and attributes of the system as well as any constraints that may limit the boundaries of the proposed solution. These requirements do not directly affect the performance of the system but they are nonetheless important.The Online sky Bus Ticketing System must ensure certain web application qualities such as ease of use, user-friendliness, correctness, functionality, reliability, response time, security, robustness as well as maintainability. The following lists the non-functional requirement of the system:- A EASE OF USEThe system should be simple and easy to use. Documentation and user manual should be provided to the users, to ensure that the users are able to use and operate the system by themselves. Help sections or user instructions should also be provided throughout the system in order to guide users when they encounter any problems. B MAINTAINABILITYMaintainability is the ease with which a program can be corrected if an error is encountered, adapted if its environment changes, or enhanced if the customer desires a change in requirement . C RELIABILITYReliability is the extent to which a program can be expected to perform its intended function with requirement precision.This system should perform all its services and functions accurately and in timely manner. This quality is essential as it indicates how far users will have confidence in the implementation of this online sky Bus Ticketing System. D RESPONSE TIME / SPEEDThe system should be able the process any transaction at the highest speed and avoid unnecessary interaction. As a low response time, the users may feel frustrated and decide not use this system. E SECURITYThis system should have security measures to minimize the risk of data exposure to unauthorized people. Only the authorized users with the correct login and password are allowed to access and manipulate the data kept in the database. F USER-FRIENDLYA user-friendly interface enables the users who are with or without technical background able to operate and use this system. A user-friendly system will satisfy users and allow interaction with this website and able to utilize this system to the maximum.Online Sky Bus Ticket Reservation System provides a group of works with interface environments. Also there will be a database which will keep all the records that done by user while visiting the page. SYSTEM INTERFACESThe Online Sky Bus Ticket Reservation system is connected with company server database, thus no more connection with other systems is needed. No system interface is needed during the development of this project. USER INTERFACESThe Online Sky Bus Ticket Reservation system shall be designed as a web based that has a main user interface. Format of main screen shall be standard and flexible. The system shall be user friendly designed.Pages shall be connected each other in a consistent way. Operations can be done with the system shall be repeatable. GOALS OF USER INTERFACE When considering Human Computer Interaction factor in designing the framework for Online sky Bus Ticketing System there are several goals of user interface needs to be achieved as listed below: Learn abilityThe interface is easy to learn by the users so that even a first time users can learn it with minimal time frame. FlexibilityThe design of the Online Bus Ticketing system supports the flexibility to add any new features in future. Forcing functionForcing function is essential for certain functions in order to avoid incorrect input from the users. HARDWARE INTERFACESome of the hardware interfaces for OSBTRS to be used are: PC computer, Hard Disk and etc. SOFTWARE INTERFACESThere are 2 product options for viewingA. Name: Microsoft Internet Explorer, Mozilla FirefoxMicrosoft Corporation, the interface of Online Sky Bus Ticket Reservation System is well documented purpose: the web browser specified above is required as the container of the client software at the client site in order to execute the client site of Online Sky Bus Ticket Reservation System.Definition of the interface: the Microsoft Internet Explorer and Mozilla Firefox are the software; provide a flexible and reliable browsing experience with enhanced web privacy features for all users.Name: HTTP ServerPurpose: in order to execute the client the site of Online Sky Bus Ticket Reservation System, the web server specified above is required as the provider of the client software at the server site.Definition of the interface: the apache HTTP server project is an effort to develop and maintain an open-source HTTP server for modern operating systems. The goal of this project is to provide a secure, efficient and extensible server that provides HTTP service with the current HTTP standards. Name: PHP (Hypertext Preprocessor)Hypertext Preprocessor (PHP) is an Open Source and cross-platform which is widely-used as general-purpose scripting language and it is used to build web pages which work with MYSQL database and server.Definition of the interface: PHP is a widely-used general-purpose scripting language that is especially suited for web development and can be embedded into HTML. MYSQLIt is required as data base server and it is the worlds most popular open source database software. With superior speed, reliability, and ease of use, MYSQL has become the preferred choice of corporate IT managers because it eliminates the major problems associated with downtime, maintenance, administration and support. COMMUNICATION INTERFACESThe default communication protocol for data transmission between server and the client is Transmission Control Protocol/Internet protocol (TCP/IP). At the upper level hypertext transfer protocol (HTTP, default port=80, default of apache port=8080) will be used for communication between the web server and client. 3.3 Use caseUse case defines set of interaction between actors and use case models considerations. It is a tools used in system analysis to identify, clarify and organize all system activities that have significations to the project. Use case diagrams are diagrams used for capturing for functional requirements of the system. Each use case diagram describes a behaviorally related sequence of transaction in a dialogue between the user and the system.

Fig 2: use case model for online Sky Bus Ticketing Reservation system

Fig 3: Member and Non Member customer ticketing reservation system Use case model

Use case Documentation Use case description Registration

Use case nameRegistration

ActorsPassenger

DescriptionAllow someone to register to become a user.

Pre-conditionThe user must know how to register to the system.

Post-condition

Basic course of action1 the users must fill their personal info2 data bases connection terminated.3 the user registered to the system successfully.

Alternative courses1.1The users might miss to fill their personal info.A 1.2 Error message appearsA 1.2 Continue with step 1 in the normal course events.A 2.1 the system may failed to connect to databaseA 2.2 Shows error messages.

Table of use case for Registration

Reservation

Use case nameReservation

ActorsPassenger and Clerk

DescriptionsUser reservation

Pre-conditionsThe user must be registered to the system.

Post- conditions

Basic course of actions1. The passenger wants to reserve.2 The passenger enter name and password3 The system check availability of Ticket4 The system allow for passenger to reserve.5 The system display availability of Ticket.6 The passenger enters his/her information.7 The system verifies the entered information.8 The system checks validity of Ticket. 9 Validity of message displayed to passenger10. The passenger reserve ticket.

Alternative coursesA 2.1users can enter their names wrongly.A 2.2 Error massage appearsA 2.3 Continue with step 2 in the normal course events.

Table of Use case of Reservation functionSeat

Use case nameSeat

ActorsPassenger

DescriptionsVerify availability of seat


Post-condition

Basic course of Action1 the passenger first registered to the system2 the system verify as passenger registered3 the passenger reserve the ticket4 Passenger must choose Ticket type.5 Passenger chooses the seat number.6The system verifies seat status.7 Seat number is selected.8 The system is end.9 Passenger seat information sent to the system

Alternative coursesA 2.1users entered seat id wronglyA 2.2 Error message appears.A 2.3 continue with step 5 in the normal course events

Table of Use case of seat ReservationUpdate Passenger info

Use case nameUpdate Passenger information

Actorsclerk

DescriptionUpdating Passenger information

Pre-conditionsThe user must log in to the system.

Post- conditions

Basic course of action1 The user must be registered on the system.2 The user clicks on themselves.3 The system retrieves the desired person information from data base.4 The system shows the persons information in new page.5 The user clicks on update profile link.6 The user can update his/her profile in desired information field.7. The user clicks on save button.8. The user profile is updated.

Alternative course of actionA5.1 The user clicks on update profile wrongly.A 5.2 Error message displayed.A 5.3 continue with step 6 in the normal course events

Table of Update Passenger informationView Company informationUse case nameView buses information

Actorsclerk and passenger

DescriptionViewing the company information.


Post-condition

Basic course of action1 The user must be registered on the system which is defined on use case 1.2 The user clicks on desired time and destination.3 The system retrieves the desired company information from data bases.4 The system shows the company information in new page.5. The system shows the available seats from the selected sky bus.

Alternative coursesA 3.1 The system cannot access to the data bases.A 3.2The system puts a message on the top of the window about the problem.A 3.3 continue with step 2 in the normal course events.

Table of use case view company information function PaymentTable of use case payment functionUse case namePayment

ActorsPassenger

DescriptionsPaying money for available (selected) seat(s)

Pre-conditionsThe passenger must be registered to system.

Post-condition

Basic course of action1 The user must be registered to the system which is defined on use case 1.2 The user clicks on the desired time and the destination.3 The system retries the desired sky buses information from data bases.4 The system shows the sky buses information in new pages.5. The system shows the available seats from the selected sky bus.6. The system shows the details of the payment.7. The system sent message to the customer for informing.

Alternative coursesA 3.1 The system cannot access to the data bases.A 3.2 The system puts a message on the top of the window about the problem.A 3.3 continue with step 2 in the normal course events.

LoginTable of use case description for loginUse case Name Login

Actors All system Users(Manager ,clerk, Member)

precondition Login screen must active to enter username and password

Basic course action

ActorSystem

1.Fills the following details: User name password3.sends filled from

2.Displays form

4.Verifies username and password5.use case ends

Post conditionUser access to the system close window or logout

Alternative course of action

1.If password correct go to main menu2.If password is wrong display error message3.user can cancel login return to the Home page

3.4 Class Responsibility and Collaboration DomainDomain modeling is the task of discovering class that they represent things and the concepts to the problem space for the project.Class Responsibility Diagrams are a collection of standard index that represent classes. The intent of CRC cards is to develop an organized representation of classes, responsibilities and operations that are relevant for the class. Three different types of classes exist .Those are actor class, UI class, Business class from the above types of class we try to include three of them in our projects as follow.

Fig 4: Class Responsibility and collaboration Domain3.5 Sequence DiagramA sequence diagram shows an interaction arranged in time sequence .Sequence diagrams are used to display the interaction between users, screens, objects and entities within the system. Frequently these diagrams are placed under Use Casesin the model to illustrate the use case scenario - how a user will interact with the system and what happens internally to get the work done. Often, the objects are represented using special stereotyped icons.SEQUENCE DIAGRAM FOR JOURNEY RESERVATION

Fig 5: sequence diagram for journey reservationSEQUENCE DIAGRAM FOR TICKET WITHDRAW

Fig 6: Sequence diagram for ticket withdraw

SEQUENCE DIAGRAM FOR CHOOSE SEAT NUMBER

Fig 7: Sequence diagram for choose seat number3.6 Class diagram Classes are show as boxes with three sections, the top one indicates the name of the class, the middle one lists the attributes of the class, and the third one lists the process of the activity in this class.The class Diagram below shows the class of our system, their inter relationship (including inheritance and association) and the operations and attributes of each classes.

Fig 8: Class diagram for online Sky Bus Ticketing Reservation system 3.7 User Interface Flow DiagramUser Interface is communication channel that end-user can interact with a system. All knowledge against a system occurs in compliance with the interaction of the user and interface. Therefore, according to development environment of the application changes rapidly, we became to need interface design to support complex interaction between human and computer. In this documentation, we suggest user-centered design models to standardize user interface prototype and supports flexible development in by customizing it.

Fig 9: User Interface Flow Diagram3.8 Activity DiagramActivity diagram shows the conditional logic for the sequence of system activities needed to accomplish a business process. It clearly shows parallel and alternative behaviors that can be used to show the logic of a use case. In our system, we identified some activity diagrams to clearly show the activities in the system. The following activity diagrams show activity diagrams, registration and which are the main tasks of the system.

Fig 10: Ticket Reservation System activity Diagram

Fig: 11 Ticket Cancellation activities Diagram CHAPTER FOUR4. SYSTEM DESIGNSystem design is the transformation of the analysis model into a system design model. The purpose of this document is to provide an overview as to how to actually build the proposed system and to obtain the information needed to derive the actual implementation of our system. During the last phase we, the team has extensively worked on the system analysis to understand what will be built. In many ways, this is a continuation of that work, only here we draw the system closer towards implementation. In this part of the document, we have used include the following diagram to understand our system. Goals of DesignThe goal of the system design is to manage complexity by dividing the system in to smaller manageable piece. Some of the goal is listed below:Security: - the system should be securing an authorized user.Modification: - the system should be modifiable to modify different services depending on the need of the institute.Flexibility: the system is able to change to suit new condition or situationEfficiency: the system must be doing what it is supposed to do efficiency without any problem.

4.1 Deployment modelingDeployment modeling is used to show the hardware of the system the software that is installed in the hardware and also the middleware that is used to connect the disparate machines to one and other. It also shows how the software and the hardware components work together.

Fig 12: Deployment Diagram of Ticket Reservation

4.2 Database DesignThe design of the DB is portrayed as a special model, database schema. It is the physical model or blueprint for a DB, which represents the technical implimentations of the logical data model. A relational DB schema defines the DB structure interms of tables, keys,indexs and integrity rules. A DB schema specifieces details based on the capablities, terminologies, and constraints the chosen DBMS.

Data Dictionaryi. Table Name: Schedule

Field Type sizeconstraintsDescription

IdInt9 Primary keyBus ID

fld_bustypevarchar20NullBus Type

fld_busregnumbervarchar15Foreign keyBus registration number

fld_originvarchar25NOT NullBus Origin

fld_destinationvarchar25NOT NullBus destination

fld_seatsInt10NullNumber of seats

fld_soldInt10NullNumber of seats sold

fld_available Int10NOT NullNumber of seats available

fl_adultfarevarchar15NoTNullAdult fare

fld_child varchar15Not NullChild fare

fld_roriginvarchar15Not NullBus return origin

fld_rdestinationVarchar15Not NullBus return destination

fld_rdatevarchar15Not NullBus return journey date

fld_rtimevarchar 10Not NullBus return journey time

fld_rseatsInt10NullBus return journey seats

fld_ rsoldsvarchar10NullBus return journey sold

ii. Table Name: seat status

FieldTypesizeconstraintsDescription

IdVarchar9Primary keySeat ID

totalseatsVarchar10NullTotal number of seats

selectedseatsVarchar10NOT NullSelected seats

iii .Table Name: Manager(Admin) FieldTypesizeconstraintsDescription

IdVarchar9Primary keyCompany ID

fld_companynameVarchar20NullCompany name

fld_usernameVarchar20NOT NullCompany Username

fld_passwordvarchar20NOT NullCompany Password

iv. Table Name: Feedback

FieldTypesizeconstraintsDescription

IdInt9Primary keyID

Fld_usernamevarchar10Not NullUsername

Fld_subjectvarchar10NullSubject

Fld_messagevarchar20Not NullMessage

v. Table Name: NewsFieldTypeSizeconstraintsDescription

IdInt9Primary keyID

Fld_subjectvarchar20NOT NullSubject

Fld_messagevarchar20NOT NullMessage

Vi. Table Name: PlacesFieldTypeSizeconstraintsDescription

place_id Int6Primary keyDestination ID

PlacesVarchar15Not NullDestination

Vii Table Name: Reply feedbackFieldTypeSizeconstraintsDescription

IdInt9Primary keyID

Fld_usernamevarchar25Not NullUsername

Fld_subjectvarchar25NullSubject

Fld_messagevarchar25Not NullMessage

Viii Table Name: Member

FieldTypeSizeconstraintsDescription

idInt9Primary key ID number

fld_usernamevarchar25Not NullUsername

fld_passwordvarchar25Not NullPassword

fld_ageInt10Not NullAge

fld_addressvarchar15Not NullAddress

fld_contact_numbervarchar15Not NullContact number

emailvarchar25Not NullE- Mail address

Ix Table Name: SalesFieldTypeSizeconstraintsDescription

idInt9Primary keyID number

fld_ticketnumbervarchar20Primary keyTicket number

fld_busnumbervarchar20Primary keyBus number

fld_usernamevarchar25Not NullUsername

fld_originvarchar20Not NullBus origin

fld_destinationvarchar20Not NullBus destination

fld_returnadultsInt10NullBus return number of adults

fld_returnchildsInt10NullBus return number of children

fld_addressvarchar25Not NULLAddress

fld_totalamountvarchar25Not Null Total amount

fld_contactvarchar25NULLContact

fld_returnjdatevarchar25NOT NULLBus return date

fld_returnjtimevarchar25NOT NULLBus return time

fld_paymentvarchar25NOT NULLPayment

4.3 Relationship of the DatabaseThe following are some of the entity used in our projects. Those are: Passenger, Reservation, Reserved journey, and Journey.

4.4 INTERFACE DESIGN 4.5.1 Navigation treeThe Structure Design of Online sky Bus Ticketing System web portal shows a birds eye view of the entire system. Generally the Online Sky Bus Ticketing System web portal allows easy accessibility to obtain information. Customer can browse the web portal to obtain various types of information such as bus schedule information, promotions, latest news, forums, feedback and star rating for bus operators. On the other hand the Administrator would be able to assess the system to update the portal on bus schedule information, promotions, latest news, forums, feedback, and report generation.

OSBTR MAIN SYSTEMFEEDBACKUSER INSTRUCTIONFAQBOOKING CANCELLATIONABOUT USCONTACT US HOME

VIEW FEEDBACKREPLY FEEDBACKUPDATE JOURNEYVIEW FEED BACKADDING JOURNINGSEARCH REPORTPRINT PAGEVIEW DAILY REPORTREGISTER CLERKSKY BUS INFORMATIONSELECT DESTINATIONSEARCH DESTINATIONSELECT SEATPURCHASE TICKETPRINT TICKETCLERKPASSENGERLOGINMANAGER

ADD SKY BUS SCHEDULEMODIFY/UPDATE SKY BUS SCHEDULEDELETE SKY BUS SCHEDULE4.5.2 User Interface

HOMECONTACT US ABOUT USBOOKING CANCELLATIONFEEDBACKUSER INSTRUCTION FAQ

LOGIN PAGE

Single ReturnDeparture:

Arrival:

Departure Journey Date:

Return Journey Date:

search

Welcome to online Sky Bus Ticketing reservation system

LOGIN HERE! First name

Password

Are you a New UserCreate Account Here:


Welcome to online Sky Bus Ticketing reservation system Registration Form

User Name

password

Confirm password

E-mail

Address

Contact Number

submit

Reset


Welcome to online Sky Bus Ticketing reservation system Login Here!

Passenger ID

First Name

password

Register

cancel


Welcome to online Sky Bus Ticketing reservation system Ticket Reservation Form

Passenger ID

First Name

Last Name

Postal code

city

Contact Number

Email

Age

Sex

source

Destination

Price

Date

submit

cancel


Welcome to online Sky Bus Ticketing reservation system Reserve a Seat Number Here Reserve a Seat Number

source

Destination

Travel Date

Seat Number

Next


Welcome to online Sky Bus Ticketing reservation system Customer booking cancellation page Ticket Details Enter Ticket Number:

submit


Welcome to online Sky Bus Ticketing reservation system Customer Ticket Cancellation Details Page Passenger IDFirst NameLast NamePostal codeCitySourceDestinationEmailPriceAge

cancel


Welcome to online Sky Bus Ticketing reservation system Print This Page Passenger IDFirst NameLast NamePostal codeCitySourceDestinationEmailPriceAge


Welcome to online Sky Bus Ticketing reservation system Manager Login Form

User Name

Password

Login


Welcome to online Sky Bus Ticketing reservation system Ticket Booking Happy Journey

Date

Origin Destination Departure timeAdult FareChild Fare Status No. of AdultsNo. of ChildsBus NumberOnward Date

Please select the seats required

1A2C3C4C5C6C7C8c9c

1B2B3B4B5B6B7B8B9B

9D

1A2A3A4A5A6A7A8A9A

Buy

CHAPTER FIVE 5. CONCLUSION AND REFERENCE 5.1 conclusions After literature review, research and case study on the proposed system, we found that sky Bus Ticket Reservation System is a potential system in Ethiopia.The application software Online sky Bus Ticketing Reservation System has been prepared with great excitement and enthusiasm. It required a lot of efforts and hard work, which was possible only by team work. The characteristics of this software which make it more effective and efficient from existing system are as follows: It provides an efficient security system to the software All work is computerized, so, no man power is required It is easily understandable and reliable The users requirement is fulfilled The application provides platform independent software 5.2 reference 1. Stephen, R. (2005) Object Oriented and classical Software Engineering 2. Essential System Analysis and Design, 2nd Edition, Joseph s. valacita. 3. Manual Documents From the sky bus share company. 4. Software engineering text book and object oriented software engineering book. 5. Fundamentals of database system 4th edition.

5 | Page

Accounting

Subtitle

Title

Company Name/Title

System

Title

Title

Title

Page

Page

Title

System

Manager

Edit sky bus info

Generate Reports

Admin login

Reply feedback

Cancel Ticket

MEMBER

NON MEMBER

Member login

Check seat Availability

Check sky Bus schedule

Select seat

Send feedback

Make Registration

View Sky bus info

System

Choose seat number

passenger

Ticket

Reserve Ticket

Registration form

seat

Administrator

1.Register

2. verifies

3. reserve

4. select Ticket

5. choose seat Number

6. verifies

7. seat No is selected

1.The passenger must register to the system

2. The system verifies as the passenger registered

3. The passenger reserve the ticket

4. The passenger select the ticket type

5. The passenger choose seat No.

6. The system verifies seat status.

7. The passenger select seat No.

8. The use case is end.

+getTicket int:1()+insertDetail string:name()+insertDetail string :password()+insertPrice int:345()

-passenger name-passenger id-passenger address-passenger sex-passenger phone-passenger birth date-passenger age

PassengerStatic Structure

+displayDuration date:moday()+displayDuration time:6pm()

-journey date -journey time-from Journey -to journey

Journey+insertTicket int:1()

-Reserve amount-Reserve date-Reserve time-Ticket amount-Seat number-seat status-passenger id

Reservation+identifyPassenger string :amount()

-payment amount-payment id-payment status-payment date

Paymentreserve

reserve

Paid for

pay

+getPhone int:0910834549()

-Country-Region-City-Phone number-E-mail

Address1

1

*

*

*

1

*

1

*

Static Structure

-

Main Menu

Static Structure

-

Clerk

-

Passenger

-

Manager

Get:Button

[Clicked]

prepare:Button [Clicked]

cancel:Button [Clicked]

get: Button [Clicked]

-

Passenger Detail

-

Daily Report

-

Daily Report

-

Ticket

Clerk:Icon [double clicked]

-

Ticket

Passenger detail:Icon[double clicked]

Manager:Icon [double clicked]

view:Button [cliked]

Display:Button

Home pageStatechart

withdrawEnter detailDisplay error

Update DB

User name andpassword

withdraw iscompleted

Start(withdrawal)

verification

If not

verified

Check detail

incorrect

stop

Activity Diagram withdraw Ticket

Correct

Deployment

Web serverDatabase serverApplication serverRegister

Passenger Database

Ticket form

Passenger Computer

Msql server

Deployment Diagram

Sky Bus Design @2005

Documents

Transcript of Sky Bus Design @2005