Tram System Travel Swipe Card Transaction

This assignment delves into the intricacies of a tram system's travel swipe card transaction process through a comprehensive use case analysis. It outlines the normal flow of passenger interaction with the system, including entry and exit procedures. Alternative flows, such as top-up transactions, are also considered, along with potential exceptions like card reader errors. The assignment emphasizes the need for robust error handling and highlights specific requirements for system development, such as independent transaction and fare calculation modules. It further explores assumptions about passenger behavior and technology performance.

Running head: ICT TECHNICAL SUPPORT
ICT Technical Support
Name of the Student
Name of the University
Author’s Note

1
ICT TECHNICAL SUPPORT
Answer to Question 1:
For obtaining the information about the development of the use case model for the travel
swipe card transaction system different papers, journals and books are studied. The available
automatic payment processing system are also studied for the proposal of the use case solution.
Internet was used as the major source of information and gather real time data about the real
world.
Answer to Question 2:
Use case Diagram
Figure 1: Use case for Travel swipe card payment service for tram service
(Source: Created by author)

2
ICT TECHNICAL SUPPORT
Use Case List
Use
Case ID
Primary
Actor
Use Cases
UC-
1
Passenger Swipe on entry
UC-
2
Tram
Gateway system
Authentication of the card
UC-
3
Tram gateway
system
Create Transaction
UC-
4
Passenger Swipe on Exit
System Name: Travel Swipe Card Transaction System
Use Case(s)
Use Case ID: UC- 1
Use Case Name: Swipe on Entry
Created By: Enter your name and student ID
Date Created: 01/09/2017
Actors: The primary actor attached with the use case swipe on entry is the
passenger and the secondary actor is the tram gateway system.

3
ICT TECHNICAL SUPPORT
Description: When the passenger swipes the card on the entry point of the tram and
the car is required to be authenticated because a minimum balance is
required for travelling using the tram service. If the balance is low on
the card a message is popped out that the passenger needs to top up the
card from the counter.
Trigger: On successful authentication of the card the gate is opened and the
passenger can enter into the platform for riding the tram.
Preconditions: The passenger should have a card for entering into the system and the
card should have a minimum balance for using the service.
Postconditions: On entering the system the passenger can use the tram for travelling in
different pace and for exiting the system the passenger needs to swipe
on the exit point and the balance on the card gets deducted
automatically.
Normal Flow: The passenger swipes the card on the entry point and the system
analyzed the card and updates the information system by recording the
card number and a transaction is opened with a transaction ID. When
the passenger leaves the station the entry point is analyzed and a fare is
calculated and gets deducted from the card.
Alternative Flows: The passenger can top up the card and thus the transaction module is
required to be developed independent and the fare calculation module
is also required to be separately developed for the accommodation of
the future change of the fare.
Exceptions: The errors generated from the card reader while scanning the card of
the passenger is required to be eliminated and a master card is required
to be available to the gatekeeper for handling the emergency situation.
Includes: It includes calculation of the fare after the passenger after the
passenger swipes the card on the exit point. The transaction ID is
closed and the details are stored in the database for future

4
ICT TECHNICAL SUPPORT
correspondence.
Frequency of Use: The use case is designed with relevant information and analyzing the
current framework of the tram service. It is required to be used at 20
per hour for designing the database.
Special Requirements: The main requirement for the development of the use case is that the
functionality of the system is required to be analyzed and the effect of
the action taken is required to be analyzed.
Assumptions: For the development of the use case for travel swipe card transaction
system it is assumed that the passengers understand English language
and able to develop the system. The card readers are fast and it can
respond to the user at a faster rate.
Notes and Issues: Additional issues associated with the development of the information
system is creation of tables and developing the core modules
separately. The fare calculation module and the payment module is
required to be developed separately for increasing the efficiency of the
system.

5
ICT TECHNICAL SUPPORT
Answer to Question 3:
Use case Diagram
Figure 2: Use case for Fare calculation
(Source: Created by author)
Use Case ID: UC- 2
Use Case Name: Calculate Fare
Created By: Enter your name and student ID

6
ICT TECHNICAL SUPPORT
Date Created: 01/09/2017
Actors: The primary actor attached with the calculation of the fare is the admin
Description: When the passenger swipes the card on the exit point of the tram the
fare is calculated and deducted from the smart card.
Trigger: On completion of the transaction procedure the gate is opened and the
passenger can leave the platform.
Preconditions: The passenger should have the swiped at the entry point and should
have a minimum balance for using the service.
Postconditions: On entering the system the passenger can use the tram for travelling in
different place and for exiting the system the passenger needs to swipe
on the exit point and the balance on the card gets deducted
automatically.
Normal Flow: The passenger swipes the card on the entry point and the system
analyzed the card and updates the information system by recording the
card number and a transaction is opened with a transaction ID. When
the passenger leaves the station the entry point is analyzed and a fare is
calculated and gets deducted from the card.
Alternative Flows: The passenger can top up the card and thus the transaction module is
required to be developed independent and the fare calculation module
is also required to be separately developed for the accommodation of
the future change of the fare.
Exceptions: The errors generated from the card reader while scanning the card of
the passenger is required to be eliminated and a master card is required
to be available to the gatekeeper for handling the emergency situation.
Includes: It includes calculation of the fare after the passenger after the
passenger swipes the card on the exit point. The transaction ID is
closed and the details are stored in the database for future
correspondence.

7
ICT TECHNICAL SUPPORT
Frequency of Use: The use case is designed with relevant information and analyzing the
current framework of the tram service. It is required to be used at 20
per hour for designing the database.
Special Requirements: The main requirement for the development of the use case is that the
functionality of the system is required to be analyzed and the effect of
the action taken is required to be analyzed.
Assumptions: For the development of the use case for travel swipe card transaction
system it is assumed that the passengers understand English language
and able to develop the system. The card readers are fast and it can
respond to the user at a faster rate.
Notes and Issues: Additional issues associated with the development of the information
system is creation of tables and developing the core modules
separately. The fare calculation module and the payment module is
required to be developed separately for increasing the efficiency of the
system.