Sydney Traveler Information System Architecture Project

This project presents a comprehensive design and architecture for a traveler information system, addressing the challenges of transportation in Sydney. The project begins with an introduction outlining the need for such a system, followed by a detailed breakdown of its architecture, including use cases and a data-flow diagram. Section 2 focuses on the conceptual design of the user interface, showcasing interfaces for various devices. Section 3 provides a sequence diagram illustrating user interactions, while Section 4 outlines system test plans. Section 5 discusses a cloud-based architecture, covering software, platform, and infrastructure demands. The project continues with functional solutions (Section 6) and system processes and work practices (Section 7). The system includes features like client registration, login, update searches, transport selection, and payment processing. The architecture incorporates cloud services (SaaS, PaaS, and IaaS) to ensure scalability and efficient resource management. The project also includes diagrams and tables to illustrate the user interfaces, system components, and test plans. The overall goal is to provide real-time transport updates and optimal route suggestions to travelers, improving their commuting experiences.

A TRAVELER INFORMATION SYSTEM
[Student Names]
(School Name)
(Professor Name)
(Date)

Table of Contents
INTRODUCTION...........................................................................................................................................3
Section 1: Architecture of the System.........................................................................................................3
Use cases.................................................................................................................................................3
Travelers Information System Architectural Design................................................................................5
Flow chart Level 0 diagram for the traveler information systems............................................................6
Section 2: Conceptual design of user interface...........................................................................................7
Section 3: Sequence diagram....................................................................................................................11
Section 4: System Test Plans......................................................................................................................12
Section 5: Cloud based Architecture..........................................................................................................15
Software demand...................................................................................................................................15
Platform demand...................................................................................................................................15
Infrastructure demand............................................................................................................................16
Section 6: Functional Solutions.................................................................................................................16
Section 7: System Processes and Work Practices......................................................................................18
Reference...................................................................................................................................................20

INTRODUCTION
The transport is one of the activities that are used by every person in Sydney where people go to
work place, recreation places, and shopping centers and also to other avenues.
However there are various incidences that happen in each day which could cause difficulties in
the transport of various people depending on the locations.
Some of the incidences could be long hours traffic jam, load damages, heavy
rains ,flooding ,incidences of fogs ,falling of trees that could block the roads among the others
calamities which could endanger the lives of the people who are traveling or even cause
inconveniences and time wastage.
In order to overcome all these challenges there had been proposed system that will be notifying
the travelers on the incidences that had happened on a certain area that they intend to travel to or
passing by while returning to their residential places.
This application will be sending the notifications to all members who had installed the
application in their computers or their mobile devices, and they also provide a proposal of the
most appropriate means of transport to use which could be either roads, railways, air flight or
even the water transport.
Section 1: Architecture of the System.
The system architecture is used to is used to show the various components of the system, which
entails the subsystems ,hardware, software and the people involved this is implemented using the
data-flow diagram which can be developed from the below list of use cases [9].
Use cases.
The below are the various use case of the system.
Use case Description Actors
1. Client Registering in the system The clients now create an account
after they access the system to be
able to login.
clients
2. Admin approve client registration After the registration the system Admin

admin approves the client within
five minutes.
3. Clients pay monthly subscription fee The client then the initial
subscriptions fees to be able to
receive daily updates.
Client, accountant
4. Clients Login into the system Client login in system using the
password and username used in
registrations.
client
5. Client Searching the updates The client searches the sent
transport status.
client
6. Client Searching for best transport The client now searches for the
transport to use if the updates have
some transport problems.
client
7. Client select the means of transport Client now select the best transport
to use .
client
8. admin update the transport status The admin keep on updating the
various regions transport
conditions.
admin
9. admin update the best transport
available
The admin update the best optional
means of transport to use.
admin
10. accountant receive the payments The accountant receives the
payments from the clients.
accountant
11. accountant send invoice to the client The accountant validates the
payments and sends the invoice to
the clients.
Accountant

Travelers Information System Architectural Design
Below is the traveler information system architectural design that shows the components,
hardware, software and the people in the entire system.

6.0
Creating monthly invoice
D2 Transport
ADMIN/STAFFS
CLIENTS/DEVICE
ACCOUNTANT/
PAYMENTS
D12 Clients
2.0
Client login
1.0
Client’s registration
3.0
Searching for
the updates
5.0
Selecting the transport to use.
D4 Staffs
4.0
Searching for transport available
D3 Monthlyinvoices
D5 Transport status
7.0
Making
Monthly payments
8.0
Admin/
staffs logins
9.0
Updating status and best transport available
Workers logs in the system
Verifying staffs details
Admin preparing to update status
Admin updating the status
Client
Register
Into system
Clients
Log in
Client search any new update
System check the update table
System confirming the updates System accepting the transport search.
Transport is selected
Creating the monthly invoice
Clients invoice
Client’s Payments details
client’s Payments details
Confirmation of the Payments detail
Flow chart Level 0 diagram for the traveler information systems.

LOGO
ABOUTUS
CONTACT Us
LOGIN
REGISTER
THE SYDNEY TRAVELER INFORMATION SYSTEM
LOGIN
LOGIN BELOW
USERNAME
PASSWORD LOGIN
REGISTER
Section 2: Conceptual design of user interface.
The conceptual diagram is design to illustrate the various user interfaces of the system; this is
because the system will be used by various users who use various devices which includes the
computers or the mobile devices like the laptops, tablets and smart phones [7].
Below are the devices user interfaces.
i. Home interface.
ii. Login interface.
THE SYDNEY TRAVELER INFORMATION SYSTEM
Logo ABOUT US||CONTACT Us||LOGIN||REGISTER
LOGIN REGISTER
Enter username
Enter password

REGISTRATION
Please fill your details below. REGISTRATION
Please fill your details below.
Register Exit Register Exit
SEARCH FOR UPDATES BELOW
SEARCH FOR UPDATES BELOW
iii. Registration interface.
iv. Updates interface.
Password
Confirm password
Location
Address
Contacts
Username
Password
Location
Address
Contacts
Enter location
SEARCH
LOCATION:…………………………………………..
STATUS:…………………………………………………
AVAILABLE TRANSPORT:………………………..
……………………………………………………………….
SEARCH TRANSPORT EXIT
Enter location
SEARCH
LOCATION:…………………………………………..
STATUS:…………………………………………………
AVAILABLE TRANSPORT:………………………..
……………………………………………………………….
SEARCH FOR TRANSPORT EXIT

SELECT YOUR AREA AND TRANSPORT TO USE
SELECT YOUR AREA AND TRANSPORT TO USE
CHECK MONTHLY INVOICE
CHECK MONTHLY INVOICE
v. Transport selection interface.
vi. Invoice interface.
SELECT LOCATION
SELECT ONE OF AVILABLE TRANSPORT:
AIRLINE.
BUS
TRAIN
BOATS
SELECT
SELECT EXIT EXIT
SELECT ONE OF AVILABLE TRANSPORT:
AIRLINE.
BUS
TRAIN
BOATS
SELECT LOCATION
MONTH GENERATE
BELOW IS YOUR MONTHLY BILL.
AMOUNT:…………………………………………
PREVIOUS BALANCE:…………………………
OVER PAYMENT:………………………………..
GROSS BILL:…………………………………………
DUE DATE;………………………………………
MAKE PAYMENTS EXIT
BELOW IS YOUR MONTHLY BILL.
AMOUNT:…………………………………………
PREVIOUS BALANCE:…………………………
OVER PAYMENT:………………………………..
GROSS BILL:…………………………………………
DUE DATE;………………………………………
MAKE PAYMENTS EXIT
Enter Month GENERATE

MAKE YOUR MONTHLY PAY
MAKE YOUR MONTHLY PAY
vii. Monthly payment interface.
MONTH
TOTAL AMOUNT
SELECT PAYMENT MODE:
VISA CARD
MASTER CARD
PAYPAL
CONFIRM PAYMENT EXIT
PAYMENT DETAILS
Select the month
Enter the amount to pay
SELECT PAYMENT MODE:
VISA CARD
MASTER CARD
PAYPAL
Enter payment details
Confirm Payment Exit

Section 3: Sequence diagram.
The sequence diagram in this case illustrates how the users who include the admin, clients and
the accountants are able to interact with the system.
Traveler information system Sequence diagram
[6]
ADMIN CLIENTS SYSTEM ACCOUNTANT
ADMIN LOGIN AND UPDATE SYSTEM
CLIENT REGISTER
SYSTEM SEND UPDATES TO CLIENT
ADMIN CONFIRM CLIENT
CLIENT LOGIN AND SEARCH UPDATES
SYSTEM GIVE CLIENT UPDATES
CLIENT SEARCH FOR TRANSPORT
SYSTEM PROVIDES AVAILABLE TRANSPORT
CLIENT SELECT THE TRANSPORT
CLIENT REGUEST FOR INVOICE
THE ACCOUNTANT SEND INVOICE TO THE CLINET THROUGH SYSTEM
SYSTEM REQUEST CLIENT INVOICE
CLIENT SELECT PAYMENT MODE AND
MAKE PAYMENT SYSTEM PROCESS PAYMENT
THE ACCOUNTANT CONFIRM PAYMENTS RECEIVED AND UPDATE BALANCE

Section 4: System Test Plans.
The traveler system require to be tested before it is fully deployed tom the use by the clients ,this
is achieved by following the various tests of the system requirements and functionality which are
in the below test plan table.
Test
number
Test’s name Descriptions Scenario Pre-condition Input Expected outputs
1 Client
registration
The client
required to
register to
use the
system.
Client enter
personals
details
Client should
have a laptop
or mobile
device
Username, password,
confirm password, location,
address and contacts
Registration
successful
waiting
confirmation
2 Client login The client
require to
login first
Client enter
username
and
password
Client Should
be registered
Username and password Welcome and
redirected to
updates form.
3 Client
updates
search
The client
had been
sent updates
so he can
search his
area
Client enter
location and
click
generate
button
Client Should
be registered
and paid
monthly
charges
Location Transport updates
generated and
provided with
available
transport to use
4 Client
transport
search
Client can
search from
available
transports
Client enter
location and
search
Client Should
be registered
Client’s location or
destination.
The client gets all
the available
transport in the
selected
locations.
5 Client
selecting
transport
Client is
able to
select the
transport he
wants to
Client select
one of the
listed
available
Client Should
be registered
Select transport type. Client successful
select the
transport.

use. transport
6 Client
generating
monthly
invoice
The client
require
invoice to
know
amount to
pay.
Client enter
the month
and click on
generate
button.
Client Should
be registered
and used
system for a
month
Month Client receives
the amount,
previous balance
and the total
amount to pay
7 Client
selecting
payment
mode and
making
payment
The client
requires
making
previous
month
payment to
continue
getting
updates.
Client
selects one
of the
payment
modes, enter
the amount
and click
pay button.
Client should
be registered
for the past
one month.
Payment mode and
The amount.
The client gets
the payment
acknowledgement
message.
8 Accountant
login ,recei
ve and
confirm
payments
The
accountant
requires
confirming
the
payments
from the
clients and
sending
confirmation
message.
Accountant
enters the
username
and
password to
login then,
check the
payments
received and
send
confirmatio
n message
to the
clients.
Accountant
should be a
staff member
and given
logins details.
Username, password and
confirmation message.
The accountant
gets the message
sent success
message.
10 Admin
login and
The admin
is the one
The admin
login, then
The admin
should be
Username, password,
Reject or approve client.
The admin give
the client ability

confirm
client’s
registration.
who
confirms the
clients
registration
approve or
reject all the
clients who
had
registered.
part of
system
management
team.
to login.
12 Admin
update the
system
information
.
The admin
is the one
who update
transport
status from
various
locations.
The admin
receives
updates
from various
agents in
various
locations
and update
them on the
system
which send
the
notification
to active
clients
The admin
must be
registered,
and receive
transport
status from
various
locations.
Username, password,
location, transport
status and best
Transport to use.
The system
updates the
transport status in
various locations

Section 5: Cloud based Architecture.
The system implementation will require to be supported by the software, platforms and some
infrastructures; this is to enable the hosting of the system to the cloud architectures.
Below are the respective requirements of the system.
Software demand
The traveler information system will require some software that will enable its development and
maintenance, however it will make use of the SaaS services of the cloud computing.
The software as a service will use the web services and will enable the delivery of the system to
the users; however this system will be managed by the vendors and the system interfaces will
then be accessed by the clients, accountants and the system administrator.
Therefore the software to be required will be:
i. Clients webs browsers.
ii. Vendors webs browsers.
iii. The vendor’s software as service.
Platform demand
The development of the travelers information system require use of various tools ,however while
using the cloud architecture the PaaS service will be employed to enable the development of the
system where all the required development components will be provided [5] .
Therefore the PaaS will provide the system developers with the necessary platform to develop,
test and deploy the system in a simply and cost effectively.
The following are the platform provided by the platform as a service:
i. Operating system i.e. OSe.
ii. Virtualizations.
iii. Development server.
iv. Storage space.
v. Networking infrastructure and
vi. Platform as a service itself.

Infrastructure demand
The implemented and deployed will require to be managed together with the resources to ensure
there is smooth running; however this will be implemented by use of the IaaS service of the
cloud architecture.
However this cloud infrastructures service called infrastructure as a service (s) is a model that
will assist in access, monitory and the management of the datacenter infrastructural facilities that
are remotely located which includes virtual compute, storage spaces, network infrastructures and
networks service like firewall .However this will be used as a computer instead of buying the
computers and servers locally.
The Iaas therefore will play a great role in management of applications, the data, storage spaces
and network services like firewall.
Therefore below are some of the infrastructure requirements.
i. Cloud infrastructure as a service.
ii. Client’s computer/mobile devices which can access internet.
iii. Staff’s computers or mobile devices which can access internet.
Section 6: Functional Solutions.
The system has various uses since it is used by range users who include the admin, clients, and
accountants and thus the system has provided them with various uses cases and functionality
where they are able to interact with the system using respective user interfaces.
Below are the various functional requirements and solutions.
Functional requirements solutions
i. The system should allow the clients to register.
The client will require submitting his registration details to be able to start using the system,
these details are then verified by the admin to allow client to login into the system.
ii. The system should allow the admin to login and approve client’s registration.

The admin of the system login to do the verification of the client’s details and if they are accurate
and correct the admin approve the client as one of the system users and is bale to login else he
rejects the registration [4].
iii. The system should allow the clients to login.
Upon admin approval the client logins into the system using the username and password that he
used during the registration process.
iv. The system should allow the client to search for updates.
After the client login in the system he search for updates sent to him according to the location he
is interested in or he is at.
v. The system should enable the clients to search for the best available means of
transport.
In case there is any transport challenge the system enables the client to search for the available
transport means which are appropriate to use in such locations.
vi. The system should enable the client to select the means of transport to use.
The system will generate all the available means of transport and then the user will be able to
select one that he feels best to use to travel.
vii. The system should enable the client to check his monthly bill invoices.
The client after a month use of the services he is supposed to pay some fixed changes thus he
first search for the invoice which is generated by the system as it is updated by the accountant.
viii. The system should enable the client to make payments.
Upon receiving the invoice the client is supposed to select the mode of payment to use ,enter the
amount and make the payments.
ix. The system should allow the accountant to receive and confirm client’s payments.

After the clients make the payments the accountants login the system and confirm payment
received from the clients, and a notification message should be sent to the client [3].
Section 7: System Processes and Work Practices.
In the system development there are various processes that are required to be offered by the
system and in order to ensure all those processes are fully observed and the system is well
implemented there are various work practices that require to be followed which includes the
following:
i. Analyzing, planning and understanding system and its requirements.
This is the initial work practice in the system implementation process where the system’s
business requirements and processes are reviewed which are then be done mapping on the
project’s plan for further implementations.
ii. Designing, developing and building system.
The project plan that was initially developed in the stage I, the pilot system or prototype is
developed using the appropriate technology in order to do the validation of the identified
business process and the system’s functionalities that are specified in the plan of system’s project
[2].
iii. Training, testing and accepting the system.
This is the next type of work practices after the development o the pilot system where some test
data is used, in this stage the workers and the clients are then engaged and be trained on the use
of the system where they are shown the best practice and procedure to enable the system in
delivery of needed system functionalities.
However the review is done on the results obtained during the test and trainings sessions and this
will show the level of acceptance to all users to ensure the overall system goal is achieved.
iv. Implementing and launching the system.

The information gathered in the stage ii and iii is used to complete the system and all loop holes
are sealed, then the relevant data is transferred to the system and now the system is transited to
the cloud or the appropriate hosting facility.
v. System maintenance and On-going support.
After the implementation and launching of the system in the cloud architecture the service
provider’s vendors will be providing the necessary system support, however the system
management will also set up a help desk for the client’s consultation and also can host a webinar
that will be used to train all the targeted system users groups [1].

Reference
[1] A.Goyal, Systems Analysis and Design Paperback .INDIA: Prentice Hall India Learning
Private Limited, 2011, PP. 232.
[2] B.Gupta, Power System Analysis and Design, New Delhi: S Chand & Company, 2015, PP.
669.
[3]B.Singh, Systems Analysis and Design, Delhi: New Age International Private Limited, 2016,
PP.260.
[4] D.Wixom, Systems Analysis and Design, New Jersey: Wiley, 2016, PP. 448.
[5] E.Award, Systems Analysis and Design, Delhi: Galgotia Publications Pvt Ltd, 2013,PP. 538.
[6] I.Singh, System Analysis and Design, Delhi: Khanna Publishers, 2014, PP. 632.
[7] N.Karumanchi, Peeling Design Patterns: For Beginners and Interviews, New York:
CareerMonk Publications, 2012, PP. 266.
[8] P.Laplante, Real-Time Systems Design and Analysis: Tools for the Practitioner, New Jersey:
Wiley, 2013, PP. 584.
[9] S.Jain, A Level Made Simple Structured System Analysis and Design, New Delhi: Bpb, 2010,
PP. 689.