Chapter One

1. Introduction

1.1 Background

Selam Bus Transport Share Company was established by the Tigray Development Association
(TDA) in 1996 to alleviate the prevailing nation-wide shortage of public transportation.
The aim of Selam Bus Transport Company is “to render reliable, safest, comfortable & modern
public transport service in Ethiopia”.  To this effect and in order to raise a capital that would
enable it realize its mission and vision as well as have more service coverage.

Selam Bus is committed to maintain the ease and convenience as well as the comfort of its
passengers by regularly making arrangements of efficient and standard reception.

Our project is to computerize ticketing system, so that the service becomes fast. It replaces all the
paper work it keeps records of all bills also, giving to ensure successful implementation of the
computerized selam bus reservation system.

1.2 Literature Review

A literature review is a text which includes the current knowledge including substantive
findings, as well as theoretical and methodological contributions to a particular topic.

This review of the literature organizes the previous research in the light of the work we are
doing. This review groups research studies and other type of literature which includes theoretical
articles and case studies according to their objective and chronology.

Writing this review let us gain and demonstrate skills in areas:

 Information seeking
 The ability to scan the literature related to our application.
 The ability to scan using manual or computerized method to identify a set of useful
articles and books critical appraisal.
 Makes us to place our study in the context of other work that has already been done in the
field.
  Define terminology and concepts drawn up on in our study.
 It explains the basis of the chosen research strategy.

This literature review shows and demonstrates how prevailing ideas fit in to our own study, and
how our study agrees or differs from other studies.

The first question we have asked about is what is known in the field of the application we do.
Our question answered by bus ticket reservation system which is done by Wang Kang Li in the
school of Arts and Science Tunku Abdul Rahman College in the Campbell university which is
found in USA.

1.3. Statements of the problem

Description of the existing system

Selam bus is one of the company giving transportation services in our county. It is established in
Addis Ababa. At the moment it is giving services for different Ethiopian cities such as Jimma,
Gondar, Mekele, Bahir dar, Harar, Dire dawa, shire, jijiga and so like.

Problems in the existing system

There is no automat recording of passengers or user information in their organization.

They have not been completed system in their organization until now.

In selam bus transportation system, manual system require a lot of resource like, man power ,
paper, pen, difficulty of updating information timely, file control mechanism is very tedious and
not secured, difficulty in conducting consistent reports, on good follow of information between
employees and so forth.

In this system, a loss of data might be occurred. For example, passenger may loss his or her
ticket also technical problems may occur
The system is not providing equal service to all cities in Ethiopia. That means there are a lot of
cities which are not getting service from them.

1.4. Objective

1.4.1 General objective

The general objective of this project is to develop computerized system for Selam bus
organization.

1.4.2 Specific objective

 Identify the problems of the existing system.

 Analyzing the current manual system and changed into a computerized new system.

 To propose a new business process that has been automated.

 To implement the new developed system and increase the customer satisfaction.

1.5. Methodologies

1.5.1. Method of Data Collection

For the first time we have met the sub branch of the organization of the selam bus transportation
system in Harar, we used data collection method like interview and observation.

1.5.1.1. Interview: We have used this meth

od to collect the data using direct asking the manager of that organization and then exchanged
some ideas of this system how it have been working and the structure of this organization have in
its implementation also the aim of they have to change the current or manual system to an online
system. As a general, we gathered so many data in order to prepare our project by interviewing
them.
1.5.1.2. Observation: We have used this method to collect the data using direct observing the
current activities of the organization. At that time we have gone around that organization by
which techniques this organization use to succeed its function.
1.5.2 System development methodology
We are not well experienced to do this project and we will submit the project Step by step. So
progress of the project is measurable by advisor. Waterfall model is a sequential development
process where development flows steadily downwards through the various phases of analysis,
design, implementation, testing, integration and maintenance.
We preferred Waterfall approach for the following advantages: -

 Simple and easy to understand and use.

 Ideal for supporting less experienced project teams
 Easy to manage due to the rigidity of the model – each phase has specific
deliverables and a review process.
 Phases are processed and completed one at a time.
 Works well for smaller projects where requirements are very well understood.

The main reason of selecting waterfall model is:-

 The Project has clear objectives and solution
 Pressure does not exist for immediate implementation
 Project requirements are stable or unchanging during the system development life
cycle
 Team members are inexperienced

1.5.3 System implementation tools

For this project system development we will be using PHP and HTML because these languages
are easy for us relative to Asp.NET, for the front end as means of communication between
system and the user. This enables the system to be friendly interactive and MY_SQL server as a
back end tool to define the structure of the system for storing all the records.
 1.6. Scope and limitation of the study

1.6.1 Scope
We are going to study problems that exist in the selam bus ticket reservation and how specific
road assign for specific bus.

The functionality of our project is to give Reservation systems, Ticketing system, Customer
service system, Building web application for the users, Security in the form of account and
password

1.6.2 Limitation
Limitation is element of factor or subsystem it restricts the system decision making from
achieving potential goal of the system. There are many constraints within our proposed system
that limit their effectiveness of performance. Our system is limited in the process of selam bus
online ticket reservation and the payment status.

1.7. Significance of the project

Today, more than any time the success of an organization depends on its ability of acquiring
accurate and timely data about its operation .Also information plays an indispensable role in the
organization. Therefore once we implement our project the existing problems selam bus
organization will be solved. Like reduce man power & material budget allocations: in manual
system much amount of power and materials are lost. But our project solves the problem, to
shorten data-processing time: it will not consume much time to process, reduce errors: through
this system, errors will be avoided because the system will be easy to use, improve the accuracy
of input: it will help the user to avoid mistakes regarding the data that they will give to the
clients. There will be accurate information, give information easily and efficiently: it will make
easier to give information for the user, data reliability: it gives users the assurance that the
information they see is reliable, data security: it ensures that data is kept safe from corruption
and that access to it is suitably controlled. Thus data security helps to ensure privacy. It also
helps in protecting personal data.
1.8. Work break down
The project team composed of three (3) members where each member has specified
work. The following are the types of tasks and as well as the responsibility each of us can
have.

Group members

Activities Wondale

Wondale

Demessis
Yirgalem

Shumeta
Matiyas
Kitaw

Kitaw

All
All

Data
Collection
Introduction
SRS

System Modeling

Design
Implementation
Typing
Table 1

1.9 Cost break down

Material Amount Price per unit Total price

No
1 A4 size paper 3 Destin 95 Birr 285Birr
2 Pen 6 5Birr 30Birr
3 Flash disk 3 300 Birr 900Birr
4. For Print 100 sheet 1 Birr 100Birr
5 CD 8 8 Birr 89 Birr
6 Dell computer 1 10,000 Birr 10,000 Birr
7 Microsoft - - free
office 2007
8 Microsoft - - free
office 2010
9 Micro soft - - free
Visio 2008
10 Apache wamp - - free
server
11 Notepad++ - - free
Total 11,404.00 birr

Table 2
 Chapter Two

2. System Requirement and Specification

Introduction

At this stage we are going to determine the system requirement and specification (SRS). It helps
user to understand his or her needs and working environment and to determine system
requirement and it include:

 Users do not always know their needs and analyzed by system analyst.
 Must analyze and understand the potential.
 The requirement process helps clarify needs.
 SRS provides a reference for validation of the final product.
 Clear understanding about what is expected.
 Validation is software satisfies the SRS.

2.1. Existing System

The existing system refers the manual system that is available currently. The existing system
forces customers come over to the selam bus station personally.

2.2. Proposed System

The newly proposed system needs a web based system that customers can access the webpage
wherever they are by using Internet to get tickets, to know journey schedules & to get
information about the bus station in detail and the has enormous database to control the record
keeping & to generate bus distribution schedule. Generally, the new proposed system gives the
following advantages:-

 Customer’s don’t have to waste time & money

 Ticket sellers exhaustive work will be reduced by the system
 Resources that spent on the newly proposed systems are less costly & efficient
 Records will be handled correctly
  Loss of records is unimaginable unless the system crashes with some reasons

2.2.1. Overview

Overview of proposed system

The system is aimed to make improvement on the area of reserving the ticket.

2.2.2. Functional Requirement

Functional requirements are descriptions of activities and services a system must provide.

The following are the functional requirements associated with the new system

Admin

 View daily report

 Manage activity
 Assign routine
 View comment

Customer

 Registration
 Reservation
 Update account
 Payment
 Add comment
 View company information
Clerk
 Update information
 View comment

2.2.3. Nonfunctional requirement

Nonfunctional requirements describe user-visible aspects of the system that are not directly
related with the functional behavior of the system. These requirements do not directly affect the
performance of the system but are nevertheless important. They are concerned with: -

Error Handling Exception– the system is able to handle any exceptions (like input mismatch
exception)

Security – the system is secured from unauthorized access by any means (for example from
unauthorized access)

Performance – the system gives service with maximum performance

Accuracy – the system is accurate and error free

Reliability – the system is reliable all the time the users accesses the system

No redundancy – the system avoids repetition of data on the database

Availability – all the data on the system are available all the time

Efficiency – the system gives service using minimum cost, memory storage, time and human
power as much as possible

User friendly interface – the system targets users need and user friendly

2.3. Feasibility Study

Feasibility study is used to investigate the proposed system in multiple dimensions. It used to
indicate whether the system feasible or not. Our system can be seen according to the following
literals.

2.3.1 Economic Feasibility

The project that we are going to develop is economically feasible than the manual system that the
selam bus station currently use. After finishing online selam bus ticket reservation system so
many resources are feasible. The manual system use large amount of document for ticket this
implies economically infeasible, our System changes this into computerized manner so no
wastage of resource for ticket booking.
2.3.2 Operational feasibility

The new system can be easily operated and accessed by the users anywhere who interact to the
system. It contains user friendly commands which leads users interact to the system interfaces.

It is a measure of how well a proposed system solves the problems and takes advantage of the
opportunities identified during scope definition and how it satisfies the requirements identified in
the requirements analysis phase of system development. Process-in an online ticketing system,
first the passengers data should be gathered like address, name, depart time, depart date, from
location, to location and etc. Evaluation –by comparing the previous system, the new online
ticketing system can satisfy all the customers need.

 Implementation- to implement an online ticketing system, we need to know the

hardware recourses we have also customers suggestions.
 Résistance – try to omit or avoid systems that make customers ambiguous or
confuse.
 Strategies – here, our aim of developing these systems rather than the previous is
to make all customers applicable or fully satisfied with it.
 Adapt and review- developing the system in a simple way with which every
customers can understand that can have instructions and so he/she can register on
it within a short time.

2.3.3 Technical feasibility

Technical feasibility is the measure of practicality of the specific technical solution and the
availability of technical resources and expertise. Our system can be easily maintained and
repaired without requiring high Experts or technical assistants.

2.3.4 Political feasibility

 The system we are going to develop has no harm effect or problem to any human being. It is free
from any political issue that is related with it. Ideology toward the establishment of the system is
only giving the transportation service for any human being without any discrimination.

2.3.5 Risk feasibility

The system should be kept from danger. That means the activities and situation that can because
for the failarity of the system must be known and materials needed to overcome such problem
must be identifies.

2.3.6 Schedule feasibility

Schedule feasibility is making sure whether the potential time frames and Completion date can
be met or not .The project team members expected the Project to be completed on time without
any delay.

2007
No. Task Name
 Nov 20 – Nov 27 Nov 28 – Dec 08 Dec 09 – Dec 25 Dec 26 – Jan 08
1 Introduction
i

2 SRS

3 Object Design
&Analysis
4 System Design
5 Implementation
Gantt chart

Legend: - Job is complete completed

Job is not complete

Table 3

Chapter Three
3.1 System Model

 System model is the conceptual model that describes and represents a system. System

modeling is the interdisciplinary study of the use of models to conceptualize and construct
systems. And also models are used to express complex matters in the context of software
development projects. Modeling is the vocabulary of a system involves making a decision about
which abstractions is a part of the system under consideration and which fall outside its
boundaries. System modeling’s are used to improving understanding of a situation; identifying
problems or formulating opportunities and supporting decision making.

3.1.1 Use Case Model

A use case diagram specifies what the system does (behavior) for the actors. Use case diagram
plays a key role in modeling the behavior of a system or subsystem or a class. Each use case
diagram consists of a set of use cases, actors and their relationships.

A use case is a sequence of action that provides a measurable value to an actor another way to
look at it is that a use case describes a way to which a real world to interacts with the system.
The use case models are used to document the behavioral (functional) requirement of a system.

1 Use cases: is a symbol that describes a sequence of actions that provide something of
measurable value to an actor and is drawn as a horizontal ellipse.

Actors: An actor is a person, organization, or external system that plays a role in one or more
interactions with your system. Actors are drawn as stick figures.

Actor identification
Actors: An actor is a person, organization, or external system that plays a role in one or more
interactions with your system.

In our system the following actors are involved:-

Manager

Clerk

Customer
The following diagram is essential use case our project

view
company
information
manage activity

Registration

Reservation View report

Customer
Manager

Login

Add Information
clerk

Update Information

figure 1:Essential Usecase diagram

 fi
gure 2:Usecase diagram
Login

Use case name Login

Actors Manager, Clerk and Traveller
Description Users enter to the system.
Pre-condition The users must have valid user name and
password
Post-condition The user is login in the system
Basic course of action 1. The user wishes to enter to the
system.
2. The system displays the login
dialog box.
3. The user fills and submits the
username and password.
4. The system checks the login
information.
5. The system displays Main Form.
6. Use case ends

Alternative courses 1. If entered username and password

are not correct.
2. The system determines the
invalidity of username and
password
3. The system determines invalidity to
enter to the system.
4. The system informs the user to
reenter username and password
5. The use case resumes at step 3 of
flow of events.
 6. Use case ends.

Table 4

Registration
Use case name Registration
Actors Customer
Description User Registered
Pre-condition The user must know how to register to the system.

Post-condition The use is register

Basic course of action 1 the users must fill their personal info
2 data bases connection terminated.
3 the user registered to the system successfully.

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

Table 5

Reservation

Use case name Reservation

Actors Customer
Descriptions User reserve services
Pre-conditions The user must be registered to the system.
Post- conditions The user is reserved in the system
Basic course of actions 1. The passenger wants to reserve.
2 The passenger enter name and password
3 The system check availability of reservation
4 The system allow for customer to reserve.
5 The system display availability of reservation.
6 The customer enters his/her information.
7 The system verifies the entered information.
8 The system checks validity of reservation by
their information id.
9 Validity of message displayed to customer
10. The customer get reservation.

Alternative courses A 2.1users can enter their names wrongly.

A 2.2 Error massage appears
A 2.3 Continue with step 2 in the normal course
events.

Table 6

Update account

Use case name Update account

Actors Customer
Descriptions Customer update their profile
Pre-conditions The customer must be having an account.
Post- conditions Customer account will be update
Basic course of actions 1. The customer requests their profile
2 The system display the profile of customer
3 The customer set account that she or he
want to update
4 The system allow for customer to update
profile
5 The customer update his or her account
6 use case end
Alternative courses

Table 7

Update information
Use case name Update information
Actors Clerk
Descriptions Verify availability of information

Pre-conditions The clerk must be registered to the system.

Post-condition The clerk is update the information

Basic course of Action 1 Clerk wants to update information
2 Enter user name and password
3 Select clerk operation
4 select the targeted information
5 Enter information ID
6Search
7 Enter update information
8 Update

Alternative courses A 2.1Clerk entered wrong user name and

password
A 2.2 Error message appears.
A 2.3 Go back to step 2
Table 8

View Company information

Use case name View company information

Actors Customer
Description Viewing the company information.
Pre-conditions The user must be registered to the system.
Post-condition The customer view company
Basic course of action 1 The user must be registered on the system.
 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.

Alternative courses A 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 9

View daily report

Use case name View report

Actors Manager
Descriptions
Pre-conditions The manager must be login
Post-condition
Basic course of action 1 The manager wants to view report
 2 Enter user name and password
3 Login
4 Select report by their respective id
5 Search
6 See the Report

Alternative courses A 2.1 The filled Information is wrong

A 2.2 Error Message appear
A 2.3 Go back into step 2.
Table 10

Search

Use case name Search

Actors All
Descriptions
Pre-conditions All have account
Post-condition The actors get in to
Basic course of action 1 All the actors enter searched id
 2 System cheak
3 System display conformation
4 use case end

Alternative courses A 3.1 If the searched information does not

exist
A 3.2 Go back to step 1
Table 11

3.1.2 Object and class diagram

Object

Object diagrams are also closely linked to class diagrams. Just as an object is an instance of a
class, an object diagram could be viewed as an instance of a class diagram. Object diagrams
describe the static structure of a system at a particular time and they are used to test the accuracy
of class diagrams. The purpose of a diagram should be understood clearly to implement it
practically. The purposes of object diagrams are similar to class diagrams.
Fig 3:Object diagram

Class diagram

Class diagram is static model that shows the classes and the relationships among classes that
remain constant over the time. Class is the main building block of class diagram, which stores
and manages information in the system.
Fig 4:Class diagram

Sequence Diagram

A sequence diagram is an interaction diagram that emphasizes the time ordering of

messages.Sequence diagrams are used to depict the interaction among objects during certain
periods of time. It is a part of use case, such as the logic described by the basic course of action
or a portion of the basic course of actions plus one or more alternate course of actions. It consists
of activation: used to denote the time period during which an object performs an operation and
messages: means by which objects communicate with each other.
Fig 5
fig 6
Fig 7
fig 8
fig 9
Fig 10
Fig 11:Sequence Diagram for Update Account
fig 12

2.6.4. Activity diagram

Activity 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, reservation and which are the main tasks of the system.
 Enter User Name and
Password

Login
Incorrect

Verify

Correct

Login success

Activity Diagram for Login

Fig 13
 Customer
Regisetration

Enter Attributes

verify
Invalid
input

Valid Input

Successfully
Registered

Activity Diagram for Customer Registration

Fig 14
 Enter user
name&password

Invalid

Login

View report check

Valid validity

Activity Diagram for View Report

Fig 15
 Enter user name
and password

Login

check validity
Invalid

Valid

Information form
display

Activity Diagram Update Information

Enter information
id

Search
Invalid

Valid

Enter update
Update
value

fig 16
Fig 17

State chart diagram

A diagram that captures the behavior of an object by specifying the sequence of states it goes
through during its lifetime in response to events; together with the responses to those events
describe changes in state.
 Login page

pass
Enter user
Login
name and
confirm
password

fail
complete

state chart diagam for login

Fig 18
 Home
page

yes
enter
search update
value

no

update

complete

state chart diagam for update information

Fig 19
Fig 20

3.2 Data Dictionary

Data Dictionary is dictionary which contain contains a list of all files in the database. Basically
that consists of records in each file, and the names and types of each field.

Database name: Selam Bus

Tables are:

 Customer table
 Registration table
 Journey table
 Payment table
 Reservation table
User Interface

Fig 21:User Interface

 Chapter four

4. System Design

4.1. Introduction

System design is the transformation of the analysis model into a system design model. Up to now
we were in the problem domain. System design is the first part to get into the solution domain in
a software development.

The purpose of designing is to show the direction how the system is built and to obtain clear and
enough information needed to drive the actual implementation of the system. It is based on
understanding of the model the software built on. The objectives of design are to model the
system with high quality. Implementing of high quality system depend on the nature of design
created by the designer.

4.1.1. Overview of System Design

The purposes of this selam bus system are:

 Develop simple and suitable environment

 To minimize work load company workers and customers
 To minimize both the wastage of resources and time.

4.1.2. Design goals

The objectives of design are to model the system with high quality. The design goals are derived
from non-functional requirements that means non-functional requirement is the description of the
feature characteristics and attribute of the system as well as any constraints that may limit the
boundary of the proposed solution.

Design goals describe the qualities of the system that the developers should consider.

 Reliability: system should be reliable.

 Fault Tolerance: system should be fault tolerant to loss of connectivity with the service.
 Security: should be secured, i.e., not allow other users or unauthorized users to access data
that has no the right to access it.
 Modifiability: online selam bus ticket reservation is modifiable for further modification and
enhancement of the application.
 Performance: - The system should respond fast with high throughput, i.e. it should perform
the task quickly as much as possible.
 End User Criteria: - The system should have simple and understandable graphical user
Interface such as forms and buttons, which have descriptive names. It should give reliable
response for each user request at least before the session expires. All the interfaces, forms
and buttons are written or designed in a simple language or common language so that the
user can access it without any difficult.

4.2. System Decomposition with Services

System decomposition is the way of separate complex system into its sub components in order to
reduce the complexity of the system. Our project has the following subsystems

Storage subsystem

This subsystem will encapsulate the database providing a common interface to other subsystems.

It is responsible for getting system-related data from different subsystems and issuing DBMS
specific calls for information storage and retrieval

Customer management subsystem

This subsystem is responsible for managing different customers of the system that is before
registration the customer does not allow to access detail information. Customer subsystem
manages the username and password of all customers of the system for security purpose.
Payment subsystem

This subsystem emphasis on the customer paying money in order to get services.

4.3. Current Software architecture

Before this period selam bus company use manual system.

4.4. Proposed Software Architecture

4.5Hardware/software Mapping

One of the major task in system design deals with hardware/software mapping. This deals with
which components would be part in which hardware and so on. Our proposed system has a
physical connectivity to web server and database server.

4.5.1 Hardware Mapping

The hardware used for selam bus ticket reservation is personal computer, computer server, CD
(compact disk), flash and papers etc.

4.5.2Software Mapping
Software mapping is defined as the use of the software in the system at the time of development.
The system uses Microsoft Windows 8 Operating System. The proposed system uses HTML,
PHP and JAVA Script to develop the system. Whereas Microsoft Office 2007 for documentation
purpose. The system uses wamp server and MYSQL to store data into the database.

4.5 Persistence Data Management

Persistent data management describes the persistent data stored by the system and the data
management infrastructure required for it. This section typically includes the description of data
schemes, the selection of a database, and the description of the encapsulation of the database.
Persistence data model or Entity relationship (ER) models are used to communicate the design of
a database, usually a relational database, to both users and other developers. Persistence are used
the schema of database. The strength of persistence data models is that data entities are
conceptually the same as the table of relation data base and that attributes are the same as table
columns.

Persistent data management also, deals with how the persistent data (like file, database) are
stored and managed and it out lives a single execution of the system information related to ticket
reservation persistent data, hence stored on a database management system.

4.6 Database Design

Databases are the store houses of data used in the software system. A database is a collection of
stored data organized in such a way that the data requirements are satisfied by the database. The
data is stored in tables inside a database. The general theme of database design is to handle
information as an integrated whole, with a minimum redundancy and improved performance.
Regardless of the type of data structure used, the objectives of the database are accuracy and
integrity and successful recovery from failure, privacy and security of data, and good overall
performance.
A table is designed as a collection of rows and columns, which are in turn called as tuples and
attributes. Tuple is nothing but a record in the table. A record is a collection of one or more inter-
related fields. The table is an object of Relational Database Management System (RDBMS),
which is used to store and retrieve the data much easier and faster. The tables should be carefully
designed because the efficiency of the software is based on the effective table design.
Two essential settings for a database are
 Primary key - The field that is unique for all the record occurrences.

 Foreign key - The field used to set relation between tables.

Some tables in our project
 Customer Table

Field name Data type Size Primary key Foreign key

Customer id int 67 

Customer fname varchar 77

Customer lname varchar 66
Sex varchar 54
E_mail varchar 23

Phone_no int 23

Table 12
Reservation Table

Field name Data type Size Primary key Foreign key

Reserve id int 67 

Reserve date varchar 77

Reserve time varchar 66
Reserve amount varchar 54

Table 13
Journey Table

Field name Data type Size Primary key Foreign key

Journey id int 67 

Journey date varchar 77

Journey time varchar 66
Journey source varchar 54
Journey destination varchar 23
Table 14
 Payment Table

Field name Data type Size Primary key Foreign key

Payment id int 67 

Payment date varchar 77

Payment time varchar 66
Payment amount varchar 54

Table 15
 ER Diagram

reservation id
reserve amount

reserve time
reserve date
*
l_name
birth date reservation
sex
f_name destination joureny time
name
source
email reserve
customer reserve
address joureny date

city paymnt id journey

phone pay for

country ccustomer id pay

region

journey id
payment

date time
amount

Fig 22:ER diagram

4.7. Access control and Security

This part of design phase describes who could access data and who control the data access by
different users, as it is information has to be protected from using by unauthorized users. In this
system, different classes have access to different functionality and data. For example a system
manager have unlimited access to system data base and to other users data.
 4.8. Global control flow

There are two global control policies used in selams bus online ticket reservation.

A. Event driven control flow: in this policy it shows what is gone happen when we do external
events. Event driven control flow waits for an external event and when the event occurs, it will
be dispatched to the appropriate object based on information associated. For example when we
select the save button all available data should be stored in the database that the given criteria are
fulfilled.

A. Procedural driven control flow: user of the system should enter his/her username and
password and waits until the system gives response before getting any benefit of the
system. For example when user enter their user name and password the system control by
the following policy:
 User wants to access.
o User enter username
o User enter password
 System check validity of username and
Password
o If [username and password==correct]
User can access the data
Else
Incorrect username and password error message will display.

4.9. Boundary Condition

Boundary conditions are limitations or conditions that are out of the services given by the system
but which have direct or indirect impact on the system. So this proposed system considers the
following three boundary conditions: shut down, start up, maintainability.