Information Systems Development: A Case Study of Kangaroo Taxi

This case study explores the information systems development process for Kangaroo Taxi, an online taxi service. It includes use case diagrams, entity relationship diagrams, class diagrams, sequence diagrams, and activity diagrams.

Case Study 2
Assessment 3

Table of Contents
Introduction......................................................................................................................................3
Overview of case study..........................................................................................................3
Use case Diagram...................................................................................................................3
Use Case diagram...................................................................................................................6
Entity relationship diagram....................................................................................................7
Class diagram.........................................................................................................................8
Sequence Diagram..................................................................................................................9
Activity diagram...................................................................................................................13
Conclusion.....................................................................................................................................15
References......................................................................................................................................16

Introduction
Information systems development is defined as a process in which work activities or
organisational settings are being facilitated by introduction of new information system for
modification or expansion of existent one. System development approaches are being referred to
steps which are being utilised for forming, planning as well as controlling processes for
development of information system for driving towards computerised methods (Awasthi and
Omrani, 2019). The process associated with creation of data models to store data within the
database is referred to as data modelling. There are wide concepts which are being used while
formulating a system, they are user and system interfaces, system testing, deployment,
maintenance and many other. T o understand this concept Kangaroo Taxi is into account which
is a new firm and have started delivering online taxi services around the country. This report
comprises of different use case diagrams, entity relationship diagram, class, sequence along with
activity diagrams to furnish adequate and in-depth knowledge about these aspects.
Overview of case study
Kangaroo Taxi has started delivering their services across Australia for their users. They
have opted to furnish online taxi services. They have made a website which can be accessed
through smart phones of users. Users have to make registration when they will use it for the first
time and enter essential details like name, contact number, etc. This has to be done only one time
and next time when user wants to have services they can directly login into the system by
making use of their credentials. The system will render them with estimated cost associated with
their trip. Along with this, users can check for available taxis, details of drivers and also make
online payments for the same. Basically, a system is designed by them to render as system to
their user to furnish them with ease while looking for travelling from one point to other.
Use case Diagram
The graphical illustration associated with interaction that takes place among distinct entities of
system is referred to as use case diagram. Generally, this implies a methodology that can be used
for determining, clarifying as well as organising system needs. System denotes something that is

being developed or operated like sending a mail associated with details related with trip
(Beratan, 2019). Here, unified modelling language is being utilised that implies standard notation
for modelling of objects along with systems. UML is a standardised modelling language that is
liable for enabling developers to furnish specifications, visualisations, construction along with
document artefacts related with software system. For an instance, with reference to Kangaroo
Taxi, the details of customers in terms of what they have to enter within the website will be
furnished in a visual manner. By this developer can have insight into if everything is alright like
all the essential details have been entered or some new fields or entities must be added. A clear
picture illustrates better understanding of entire systems which s being developed. This involves
justification of hardware designs, overall planning requirements, software debugging as well as
their testing in context of service oriented aspects of tasks (De Rooij, Mannak and Janowicz-
Panjaitan, 2019).
With reference to Kangaroo Taxi, the use case diagram has been illustrated below:
Illustration 1: Case diagram for User registration
The diagram illustrates registration process which is being shown to user while they enter
into website of Kangaroo Taxi for the first time. Here, users have to enter details like their name,

address, contact number and payment options. All the option are clear but it is crucial to illustrate
payment option as it do not illustrate what exactly it is. By clicking on this text box a drop down
list will be shown to user in which different methods for making payment will be illustrated like
credit card, PayPal, debit card, cash, transaction from account or any other method. It does not
imply that if user has opted for one method then it has to be utilised always, they can change it as
per their requirements. The admin will verify all the details that are filled up by user and provide
them with appropriate credentials; they are username and password through which they can login
into the system when they use it for next time.
Illustration 2: Bookings
This illustration depicts the bookings that can be made by user by the use of system
furnished by Kangaroo Taxi. When user will enter the details about where they have to go like
destination, then they will forwarded or navigated to next page which will illustrate them with
details of taxi whether they want to travel alone or in sharing. Along with this, details about
vehicle will also be provided and by clicking on any peculiar vehicle, they can have information
related with driver, their contact number, vehicle number and type of vehicle. Customer id will
be generated and as per the anticipated amount, they will make payments depending upon option
they have chosen. The admin will confirm the information along with pick up location and
destination where user wishes to travel.

Use Case diagram
The simplest representation related with interaction of user with system which will
illustrate relationship among user as well as different use cases that are involved within the
system is referred to as use case diagram (Fadillah, and Fitriana, 2019). This section will show
graphical illustration of overall use case diagram for Kangaroo Taxi.
Illustration 3 Use Case
The above figure depicts overall system diagram with reference to ways in which user
and admin will interact with each other along with essential details related with travelling or trip

are being illustrated. The user will login into the system and will be validated by agent whether
they are authenticated or not. If credentials are not adequate then they won’t have access to the
system. The above figure shows actor, system user is connected with use cases like login, search
bus, tickets and many others. Furthermore, they are extended to other use cases like login has
been further extended to validate username and password so that user can be verified and if users
do not exist then they can sign up into the system. Now, user will check for the availability of the
car as per their requirements and if it is in sharing then they will also look for seats that are
available. If their requirements are not fulfilled then they can further search for car by providing
details related with date and seats they are looking forward for.
Furthermore, they can book the car, make payment and have a confirmation. Along with
this, if they don’t want to go then they also have option to cancel the bookings. Agent is
responsible for validating user as well as maintaining package details for their regular customers.
Admin will also validate user to ensure that they are authenticated and not a bot. They will also
maintain database wityh respect to how many cars are available and for which date, by whom
and to what place bookings have been made. They can add car, route through which their
vehicles will travel while going any peculiar location, assign a driver for the same and update
database as per alterations or bookings which have made by users. This involves the entire
service provider system of Kangaroo Taxi which will accomplish all the probable requirements
of their users by providing them ease to travel from one place to other.
Entity relationship diagram
The data modelling technique which graphically depicts information related with system
entities along with relationship which prevails among them is referred to as entity relationship
diagram. It is a representational as well as conceptual model of data which is being utilised for
representation of entities framework infrastructure (Genta and Morello, 2019). The major
elements of this are entities, relationship and their attributes. Attributes illustrates characteristics
of entities like if entity is user then its attributes will be user id, name, address, contact number
and many other aspects.

Illustration 4: Entity Relationship Diagram
The figure depicts ERD for Kangaroo Taxi like users have two options in which they can
register as well as login. Customer has different attributes and are associated with support staff
with relationship of 1:M from support_staff to customers. Similarly there are many entities like
city, payment, driver, car and many others and each have relationship with one or the other, and
it has been clearly illustrated within the diagram. Kangaroo Taxi has provided their customers
with an option for feedback in which they can share their experience along with any kind of
problems which are experienced by them. Along with this they can also give recommendations
through which overall performance of system can be enhanced.
Class diagram
The representation of overview of target system by furnishing description related with
classes as well as objects is referred to as class diagram (Haberfellner and et. al, 2019). This also
illustrates relationship which prevails among different entities.

Illustration 5: Class Diagram
Sequence Diagram
The interactive diagram which renders details related with ways in which operations are
being conducted is referred to as UML sequence diagram. Here, interaction between different
objects takes place with reference to collaboration which takes place among them (Mullarkey
and Hevner, 2019). They aim at furnishing time along with order according to that
communication take place through usage of vertical axis diagram to represent to time when
details are sent as well as what it is all about. They comprises of two major aspects, they are as:
 Interaction takes place in collaborative manner which either realizes operations carried at
particular use case or activity.
 Higher level of interaction occurs in between system as well as users who make use of
these systems as Kangaroo Taxi will provide adequate details to their customers.
These diagrams can be organised vertically or horizontally according level of interaction
between active objects in system along with their instances.

Illustration 5 Sequence Diagram for Admin

Illustration 6 Sequence diagram for Agent

Illustration 7 Sequence diagram for Customer
The diagram describes sequence diagram for distinct use cases, admin, and agent along
with customers. The horizontal axis depicts elements that are concerned in carrying out
communication. Operations that are illustrated from left to right depict message sequence.
Vertical axis implies proceedings down page or time progressing. The arrow among user
interface as well as admin illustrates message that represents lifelines for interaction as well as
invocation of target lifelines. Furthermore, a thin rectangle which is present below admin as well

as other use cases imply period through which operations have been completed and they are
aligned from initiation until their completion.
Activity diagram
This is essential diagram in UML for describing dynamic aspects related with system.
Generally, it is a flowchart that implies flow of information from one activity to another (Oshana
and Kraeling, 2019). It demonstrates message flow for construction of executable system by
making use of reverse as well as forward engineering techniques. Activities executed from
initiation and their representation within sequential order for conduction peculiar activities.
Illustration 9: Activity Diagram
The black circle within above diagram illustrates initiation of workflow and circular
edges rectangle depicts actions that have been performed within them. Diamond is liable for
illustrating decisions along with alternatives a system or users have. The customer or users are

associated with website of Kangaroo Taxi which is further linked with their database so that their
system can be updated as per bookings which have been made.
Conclusion
From above it can be concluded that unified modelling language plays critical role within
formation of different modelling language for illustrating a standard way to visualise ways
according to which segments have been designed. This visual language is liable for depicting
structure along with behaviour of system. Basically, they are being used for modelling, designing
and analysing system architecture. In context of Kangaroo Taxi, use case, activity diagram, ERD,
sequence diagrams and class diagrams have been illustrated. Basically, it illustrates the ways in
communication takes place between systems and users. These diagrams are liable for illustration
of each and every aspect related with system to ensure that it accomplish all the requirements.

References
Books & Journals
Awasthi, A. and Omrani, H., 2019. A goal-oriented approach based on fuzzy axiomatic design
for sustainable mobility project selection. International Journal of Systems Science:
Operations & Logistics, 6(1), pp.86-98.
Beratan, K.K., 2019. Improving problem definition and project planning in complex natural
resource management problem situations using knowledge brokers and visual design
principles. Ecology and Society, 24(2).
De Rooij, M.M., Mannak, R.S. and Janowicz-Panjaitan, M., 2019. Dataset on performance
management systems' design in project-based organizations. Data in brief, 25, p.104185.
Fadillah, A.P. and Fitriana, D., 2019, November. Design of Project Data Management
Information System. In IOP Conference Series: Materials Science and Engineering (Vol.
662, No. 2, p. 022014). IOP Publishing.
Genta, G. and Morello, L., 2019. The automotive chassis: volume 2: system design. Springer
Nature.
Haberfellner, R. and et. al, 2019. Systems engineering. Springer International Publishing.
Mullarkey, M.T. and Hevner, A.R., 2019. An elaborated action design research process
model. European Journal of Information Systems, 28(1), pp.6-20.
Oshana, R. and Kraeling, M. eds., 2019. Software engineering for embedded systems: Methods,
practical techniques, and applications. Newnes.