University Systems Design Report: Travel Swipe Card Use Case Diagram

This report focuses on the development of a Use Case Diagram for a travel swipe card payment system. The report begins with an introduction to the system and the process of gathering information for use case diagram development, emphasizing the importance of software requirement analysis, including both functional and non-functional requirements, and the influence of external factors. The report then provides a detailed implementation of a Use Case Diagram for the travel swipe card system, including a use case list with actors, descriptions, triggers, preconditions, postconditions, normal and alternative flows, exceptions, and special requirements. The report also explains one major use case identity using a template, detailing the manager's role in collecting tracking information for fare calculation. The conclusion summarizes the key findings, highlighting the manager's control over the process and the use of web users to facilitate cashless travel. References to relevant books and journals are provided at the end of the report.

Introduction to Systems
Design

Table of Contents
INTRODUCTION ..........................................................................................................................1
Question 1. Process of gathering information for use case diagram development. ...................1
Question 2. Implement Use Case Diagram for travel swipe card direction................................2
Use Case List...................................................................................................................................2
System Name (Example: Travel swipe card transaction system)...................................................3
Use Case(s)..................................................................................................................................3
Question 3. Explain one major use case identity using template................................................4
Use Case List...................................................................................................................................4
Use Case(s)..................................................................................................................................5
CONCLUSION ...............................................................................................................................5
REFERENCES................................................................................................................................6

Illustration Index
Illustration 1: Use Case Diagram for travel swipe card direction....................................................2
Illustration 2: Use Case Diagram for fare calculation.....................................................................4

INTRODUCTION
This report is based on the Use Case Diagram development process. The transportation
company is trying to implement a travel swipe card payment system , in which cost will be
imposed on the basis of zone (McDade, 2014). The present report contain the transaction
process of all the characters involved into the process.
Question 1. Process of gathering information for use case diagram development.
The requirements are determined with the help of software requirement analysis. In this
process both the functional and non-functional requirements are included (McDermott, 2014).
With the help of functional requirement analyses developer is able to understand the scope, range
and connection with other system (Munn and et.al., 2014). It is considered as basic element for
the growth of company. On the other hand Non- functional is implemented for analysing the
security, maintenance and portability of the products. This determination step is influenced by
various external factors such as political, social and cultural (Ponzanelli, Bacchelli and Lanza,
2013). The transportation company is also gathering effective information for producing better
services.
In order to determine all the requirements effectively following are the steps, identify the
criteria for describing the process, all the considered possibilities must be feasible and accurate
(Salemink, Strijker and Bosworth, 2015). All the ambiguity and data redundancy should be
removed. It helps in increasing productivity of the services. In the next step identify all the
characters of the process (Tarhan and Yilmaz, 2014). On the basis of that their roles and
transactions are also need to be evaluated. On the basis of that effective development of the use
case diagram takes places (Ponzanelli, Bacchelli and Lanza, 2013). In this process all the actors
are represented wit the help of basic human structure on the other hand ovals are use to represent
the process (Ponzanelli, Bacchelli and Lanza, 2013). With the help of effective Use Case
diagram implementation process will become simple and more productive. All the loopholes of
the process, can be determined effectively (Salemink, Strijker and Bosworth, 2015).
1

Question 2. Implement Use Case Diagram for travel swipe card direction.
Use Case List
Use Case
ID
Primary Actor Use Cases
UC-1 Traveler Providing swipe in and off details on the basis of locations
and zones.
UC-2 Web user Collecting and tracking locations of the user for fare
calculations (McDade, 2014).
2
Illustration 1: Use Case Diagram for travel swipe card direction

UC-3 Manager Imposing charges on the basis of zone and locations.
System Name (Example: Travel swipe card transaction system)
Use Case(s)
Use Case ID: UC1
Created By: Travel swipe card transaction system
Date Created: 26th August 2017
Actors: Traveler
Description: The traveler is login into the page and provide their swipe on and off
location. On the basis of that web user will gather data to collect
payment (Ponzanelli, Bacchelli and Lanza, 2013).
Trigger: The user select zone and then locality for providing swipe off and on
place.
Preconditions: User view locations for traveling (McDermott, 2014).
Post conditions: Selected location is saved as the swipe on and off zone , on the basis of
that fare is imposed.
Normal Flow: Registration-> login-> select swipe on and off location-> tracking->
gathering all traveling info-> on the basis of that charges are imposed.
Alternative Flows: Login-> select location-> start traveling. (UC1)
UC2 (collect traveling information of user)
Login-> track location-> draw network (Munn and et.al., 2014).
UC3 (collect traveling information for fare calculation)
Login-> track location-> draw network-> impose charges-> calculate
fare-> delete information.
Exceptions: Exp 1. User selects and feeds the traveling information.
Exp 2. Any system failure takes places, due to which process return on
step 1.
Includes: UC1, UC2 and UC3 are included in the process.
Frequency of Use: 20% of travelers are using for saving swipe card transaction system for
3

making process cashless. Therefore, 20 per hour (Salemink, Strijker
and Bosworth, 2015).
Special Requirements: Security of the system should be maintained due to which swipe
details of the user does not misused.
Question 3. Explain one major use case identity using template.
Use Case List
Use Case Primary Actor Use Cases
4
Illustration 2: Use Case Diagram for fare calculation

ID
UC-1 Traveler Providing swipe in and off details on the basis of locations
and zones.
UC-2 Web user Collecting and tracking locations of the user for fare
calculations (Ponzanelli, Bacchelli and Lanza, 2013).
UC-3 Manager Imposing charges on the basis of zone and locations.
Use Case(s)
Use Case ID: UC1
Use Case Name: Travel swipe card transaction system
Date Created: 26th August 2017
Actors: Traveler
Description: The manager is collection tracking information on the basis of that
fare is calculated. The fare charges are imposed on the basis of zones
(Ponzanelli, Bacchelli and Lanza, 2013).
Trigger: The user select zone and then locality for providing swipe off and on
place, on the basis of that charges are imposed.
Preconditions: Manager collect all the traveling information of user (Salemink,
Strijker and Bosworth, 2015).
Post conditions: Selected location is saved as the swipe on and off zone , on the basis of
that fare is imposed (Salemink, Strijker and Bosworth, 2015).
Normal Flow: Registration-> login-> select swipe on and off location-> tracking->
gathering all traveling info-> on the basis of that charges are imposed.
Alternative Flows: Login-> track location-> draw network-> impose charges-> calculate
fare-> delete information.
Exceptions: Exp 1. User selects and feeds the traveling information (Tarhan and
Yilmaz, 2014).
Exp 2. Any system failure takes places, due to which process return on
step 1.
Includes: UC1 and UC2 are included in the process.
Frequency of Use: 20% of travelers are using for saving swipe card transaction system for
5

making process cashless. Therefore, 20 per hour.
Special Requirements: Data should be effectively managed so that the fare calculations can be
managed properly (Salemink, Strijker and Bosworth, 2015).
CONCLUSION
On the basis of above report it is inferred that manager of the company is able to control
the process. In order to impose charges on an individual they are considering previous traveling
details also. All the information are gathered by the web user. With the helps of this user is able
to travel cashless.
6