Analysis and Development of a Use Case Diagram for Swipe Card System

This case study focuses on the development and analysis of a use case diagram for a swipe card transaction system within a transport company. The report begins with an introduction to use case modeling, highlighting its importance in software development for identifying actions and events. The study details the steps involved in collecting information, emphasizing the role of software requirement specifications and various development models. The core of the report presents a use case diagram, identifying actors such as the travel manager, customer, and web service provider, along with their respective use cases, including registration, location tracking, fare imposition, and payment processing. Detailed analyses of the major use cases are provided, outlining preconditions, post-conditions, normal and alternative flows, exceptions, and frequency of use. The conclusion summarizes the key findings, emphasizing the roles of the manager and customer, the importance of considering various assumptions and issues during software development, and the use of software development cycles and tools for gathering information. The report references several academic sources to support its findings.

Case Study 1.

Table of Contents
INTRODUCTION ..........................................................................................................................1
1. Step for collecting information for developing use case diagram......................................1
2. Use Case Diagram for Swipe card transaction system. .....................................................2
Use Case(s).............................................................................................................................3
3. Analysis of major use case identity of the above diagram.................................................5
Use Case(s).............................................................................................................................6
CONCLUSION................................................................................................................................8
REFERENCES................................................................................................................................9

INTRODUCTION
Use case model is considered as one of the essential step of the software system
development process. With the help of this approach actions and events that are involved into
the process can be easily identified. It helps in representing all the function and activities that are
involved into the process effectively (Börger and Fleischmann, 2015). It is mainly consisting of
actors and cases through which associations can be represented. The present report is based on
the use case development process for the swipe card transaction system for a transport company
(Bork and Sinz, 2015). Development of the use case model is considered as one of the
significant step of for the effective development of the software, with the help of this approach
all the actions of various character can be identified. On the basis of that environment is
developed. In the present model the characters are identified as web service provider, user and
the manager. In this process fare charges are imposed on an individual on the basis of traveling
location and zone (Citrigno and et.al., 2014).
1. Step for collecting information for developing use case diagram.
Information gathering is considered as one of the most important step. On the basis of
this process further development procedure depends. In order to effectively complete this process
use case data collection step of considered. It is based on the approach of software requirement
specification. For this various development and requirement analysis cycles are implemented.
Some of them are spiral model, water fall model, evolutionary prototype model and so on. On
the basis of these steps developer is able to effectively understand the needs and requirements of
the clients (Herden, Farias and Albuquerque, 2015). On the basis of their understanding a
dummy model is developed. In the next step the model is presented to the customers if all the
requirements are meet then only development step of the software is implemented. In order to
develop use case model data collecting step is the basic level. With the help of Software
development life cycle tools, all the information are gathered effectively, on the basis of that
actors or characters of the process are identified. In the next step their association into the
process and activities that are completed by them are analysed (Hilken, Hamann and Gogolla,
2014). Once all the identifications process is completed development of the model takes place. In
the present report model is being developed for the transportation .firm. They are trying to
develop a swipe card transaction system, through which they can impose travelling charges on
the user on the basis of their location. Apart from that use case model can be also developed with
1

the help of any other 'model such as object, entity- class, sequential diagram etc (Inukollu and
et.al 2014). Through the help of these model flow of the process can be effectively understand by
the developer on the basis of that necessary development steps can be implemented. On the
basis of that above discussion it is analysed that use case model can be developed with the help
of various software development tools, along with this various types model and approaches can
be effectively used for gathering relevant information for the development (Knapp and et.al.,
2015).
2. Use Case Diagram for Swipe card transaction system.
2

Case ID Primary Actor Use Cases
UC-1 Uid 1 Travel manager
UC-2 Uid 2 Customer
UC-3 Uid 3 Web service provider
Use Case(s)
Use Case ID: Uid 1
3
Illustration 1: Use Case Diagram for swipe card transaction system
Level 1

Use Case
Name:
Swipe card transaction system Level 1
Created By: UML Developer
Actors: Manager
Description: The manager is controlling all the fare calculation and imposing
charges on the user (López-Fernández and et.al., 2015).
Trigger: The user will be providing their information by registration. In the next
step location selection step is considered.
Preconditions
:
In this user will be providing traveling details on the basis of that
manager is tracking their zone in order to impose charges.
Post
conditions:
Once the customer reach the location, on the basis of that manager will
be imposing the fare. The client is making payment with the help of
swipe system.
Normal
Flow:
1. Registration.
2. Login
3. Selecting location
4. Location is being tracked.
5. Once user make the off swipe, travel fare is imposed by the
manager.
6. With the help of swipe system user is making payment.
Alternative
Flows:
If user is considering alternative path.
1. login
2. selecting location
3. tracking zone
4. imposing charges
5. making payment.
If manager is considering alternative path.
1. user login.
2. Tracking selected location
4

3. imposing fare on the basis of provided information.
If web service provider is considering alternative path.
1. considering user history instead of maintaining new records.
Exceptions: System failure occur due to increased access.
Information provided by the user is fake (Mahmoud, Barakat and
Ajjour, 2016).
Includes: Uid1, Uid 2 and Uid 3 all are included into the process.
Using
frequency
As the system is introducing swipe card mechanism, most of the users
are influenced. Therefore, frequency of using is 50 person/ hr.
Other needs Cloud services should be included for effective outcomes.
Assumptions: Transport company should provide user friendly interface so that a non
technical person can also avail these services effectively.
Notes and
Issues:
Various other languages should be provided as a sportive language so
that they do not feel any kind of difficulties in understanding the
process.
5

In the above mentioned UML diagram user, manager and web service provider are
considered as important characters of the entire process. The user is providing travelling details
on the basis of which whole swipe process is taking place (Ribeiro and da Silva, 2014). The next
actor is manager, all the fare charges are imposed by them and the last element of this process is
web service provider. All the tracking and network development is completed by them. The
combinations of theses three element is essential for the completion of the process.
3. Analysis of major use case identity of the above diagram.
6
Illustration 2: Use Case Diagram for swipe card transaction system
Level 2

Case ID Primary Actor Use Cases
UC-1 Uid 1 Travel manager
UC-2 Uid 2 Customer
UC-3 Uid 3 Web service provider
Use Case(s)
Use Case ID: Uid 2
Use Case
Name:
Swipe card transaction system Level 2
Created By: UML Developer
Actors: User
Description: The user is providing information related to their change of location.
On the basis of that travelling charges will be imposed.
Trigger: The user will be providing their personal data by registration. In the
next step location selection step is considered (Ruiz-Rube, Dodero and
Colomo-Palacios, 2015).
Preconditions: In the initial step of the process, user is creating account with the helps
of making registration.
Post
conditions:
In this step user is making swipe off , in order to get the imposed fare
details.
Normal Flow: 1. Registration.
2. Login
3. Selecting location
4. Location is being tracked.
5. Once user make the off swipe, travel fare is imposed by the
manager.
6. With the help of swipe system user is making payment.
Alternative
Flows:
If user is considering alternative path.
1. login
7

2. selecting location
3. tracking zone
4. imposing charges
5. making payment.
Exceptions: System failure occur due to increased access.
Information provided by the user is fake.
Includes: Uid1, Uid 2 are included into the process.
Using
frequency
As the system is introducing swipe card mechanism, most of the users
are influenced. Therefore, frequency of using is 50 person/ hr (Santos
and et.al., 2016).
Other needs Cloud services should be included for effective outcomes.
Assumptions: Transport company should provide user friendly interface so that a non
technical person can also avail these services effectively.
Notes and
Issues:
Various other languages should be provided as a sportive language so
that they do not feel any kind of difficulties in understanding the
process.
In the above mentioned UML diagram the role of manager and user is identified as significant.
The major processing in the system is controlled or completed by them only. It any of them are
not performing their role (UML Use Case Diagram, 2017). It will create huge impact on the
outcome.
CONCLUSION
On the basis of above report it is inferred that transport company is developing effective
swipe card transaction system. In this process manager and customers are identified as most
important actor of the entire process. With the help of this process an outline of the process can
be developed on the basis of that processing of each step can be effectively analysed. Along with
this it helps in determining the loopholes of the process. There are various assumption and issues
are need to be considered while developing the software on the basis of that efficiency of the
process can be enhanced. While developing and gathering information for developing the system
various software development cycles and tools are considered, it helps in having the deep
8

understanding about the needs and requirements of the user. It maintains the productivity and
processing of the system.
9