SRS Document

COMSATS University Islamabad (CUI)
Software Requirement Specification

(SRS DOCUMENT)
for
Pro Tracking
Version 1.0
By
AHSAN ASHRAF CIIT/SP20-BSE-005.ISB
AREEBA AKBAR CIIT/SP20-BSE-012/ISB

MOHSIN ZARAR CIIT/SP20-BSE-047/ISB
Supervisor
MS LAILMA JAVED
Bachelor of Science in Computer Science (2020-2024)

Revision History
Name Date Reason for Changes Version
Application Evaluation History

Comments (by committee) Action Taken
i
*include the ones given at scope time both in doc and
presentation
Supervised by MS
Lailma Javed
Signature______________
Table of Contents
ii
1. Introduction ........................................................................................................................... 1
1.1 Purpose ........................................................................................................................................ 1
1.2 Scope ........................................................................................................................................... 1
1.3 Modules ....................................................................................................................................... 2
1.3.1 Account management: ................................................................................................................ 2
1.3.2 Driver Management: ................................................................................................................... 2
1.3.3 Vehicles Management: ............................................................................................................... 2
1.3.4 Devices Configuration: ............................................................................................................ 3
1.3.5 Expense Management: ............................................................................................................. 3
1.3.6 History Management: ............................................................................................................... 4
1.3.7 Journey Management: .............................................................................................................. 4
1.3.8 Geofence Management: ........................................................................................................... 4
1.3.9 Alerts and notifications: ........................................................................................................... 5
1.3.10 Driver License Management: .................................................................................................... 5
1.3.11 Vehicles Maintenance: .............................................................................................................. 5
1.4 Overview ..................................................................................................................................... 6
2. Overall Description ............................................................................................................... 6
2.1 Product Perspective ..................................................................................................................... 6
2.2 User classes and characteristics ................................................................................................... 6
2.3 Operating Environment ............................................................................................................... 7
2.4 Design and Implementation Constraints ..................................................................................... 7
3. Requirement Identifying Technique ................................................................................... 7
3.1 Use case Diagram ........................................................................................................................ 7
3.1.1 User Use Case Diagram ..................................................................................................................
7
3.1.2 Admin Use Case Diagram ...............................................................................................................
9
3.2Use case description ..........................................................................................................................
11 3.2.1 User Profile ...................................................................................................................................
11
4. Functional Requirements ................................................................................................... 38
4.1 Login/Register ........................................................................................................................... 38
4.1.1 Register ...................................................................................................................................... 38
4.1.2 Login ......................................................................................................................................... 42
4.1.3 Logout ................................................................................................................................... 45
4.2 User Account................................................................................................................................ 47
4.2.1 Edit Account ..........................................................................................................................
47
4.3 Driver profile .........................................................................................................................
49
4.3.1 Add Driver ..........................................................................................................................
49 4.3.2 Edit
Driver ....................................................................................................................... 51 4.3.3
Remove Driver ................................................................................................................... 54
4.3.4 Search Driver Profile .............................................................................................................
56
iii
4.3.5 View Driver Profile ................................................................................................................
58
4.4 Devices ....................................................................................................................................
59
4.4.1 Add Device ..........................................................................................................................
59 4.4.2 Edit
Devices ..................................................................................................................... 61 4.4.3
Remove Devices .................................................................................................................. 63
4.4.4 Search Device .........................................................................................................................
65
4.4.5 View Device ...........................................................................................................................
67
4.4 Vehicles .................................................................................................................................. 68
4.4.1 Add Vehicles ....................................................................................................................... 68
4.5.2 Vehicles Driver .................................................................................................................
70
4.5.3 Remove Vehicles................................................................................................................. 73
4.5.4 Search Vehicles Profile .......................................................................................................... 74
4.5.5 View Vehicles ........................................................................................................................ 76
4.6 Journey................................................................................................................................... 78
4.6.1 Add Journey ....................................................................................................................... 78
4.6.2 Driver Journey .................................................................................................................
79 4.6.3 Remove
Journey ................................................................................................................. 82
4.6.4 Search Journey Profile ........................................................................................................... 84
4.6.5 View Journey.......................................................................................................................... 86
4.7 Geofence .................................................................................................................................
87
4.7.1 Add Geofence ..................................................................................................................... 87
4.7.2 Geofence Driver ...............................................................................................................
89 4.6.3 Remove
Geofence ............................................................................................................... 91
4.7.4 Search Geofence Profile .........................................................................................................
93
4.7.5 View Geofence .......................................................................................................................
95
iv
4.8 Expense ..................................................................................................................................
96
4.8.1 Add Expense .......................................................................................................................
96 4.8.2 Expense
Driver ................................................................................................................. 98 4.8.3 Remove
Expense............................................................................................................... 101
4.8.4 Search Expense Profile .........................................................................................................
102
4.8.5 View Expense .......................................................................................................................
104
4.9 Contacts ............................................................................................................................... 105
4..1 Add Contacts ......................................................................................................................
105
4.9.2 Driver Contacts ................................................................................................................
107 4.9.3 Remove
Contacts .............................................................................................................. 110
4.9.4 Search Contacts Profile .........................................................................................................
111
4.9.5 View Contacts ....................................................................................................................... 113
4.9.6 View Report ............................................................................................................................ 115
4.9.7 Check History ..........................................................................................................................
115
4.9.8 Check Speed ............................................................................................................................
116
4.9.9 Check Mileage......................................................................................................................... 117
5. Non-Functional Requirements ......................................................................................... 118
5.1 Availability .............................................................................................................................. 118
5.2 Usability .................................................................................................................................. 118
5.3 Performance............................................................................................................................. 118
5.4 Security .................................................................................................................................... 118
6. External Interface Requirements .................................................................................... 119
6.6 Software interfaces .................................................................................................................. 119
6.7 Communications interfaces ..................................................................................................... 122
7. References .......................................................................................................................... 122
v
1. Introduction
Right from when the GPS vehicle tracking software came into existence, it has become quite easy for
fleet operators to comfortably manage their fleet of vehicles. With the advent of this device, investing
in transport, haulage, and logistic business and even ambulance services have become a profitable
venture because the tracking device helps keep the drivers under check, check the fuel consumption,
distance covered and ensures the safety of the vehicle. The fact that you can install GPS vehicle
tracking devices that trigger automated bus stop announcements makes it easier to run a public
transport service company. Much more than buying insurance for personal cars, most people also
choose to buy and install GPS vehicle trackers in their cars to prevent theft. The truth is that with car
tracking devices, even if your car is stolen, it can easily be tracked and recovered.
Global statistics show that the need for GPS vehicle tracking systems in cars is on the increase because
of how efficient it has proven to be and in fact most transport operating companies will not allow their
cars to start plying the roads until they have installed a GPS vehicle tracking system on it. The
Automobile industry of which GPS vehicle tracking services is a part of will continue to experience
growth in all parts of the world, especially in developed countries such as the United States of America,
Canada, United Kingdom, Germany, Australia, and Italy.
1.1 Purpose
The purpose of the GPS Tracking Devices project is to provide businesses with a comprehensive
solution for managing their fleet of vehicles by developing a mobile application and a web-based
dashboard. The project aims to improve communication and increase efficiency by enabling drivers to
manage their journeys, monitor their driving behavior, and providing fleet managers with centralized
tools to analyze the performance of their vehicles. The project also includes the implementation of pro
tracking, which will allow for detailed insights into the driving behavior of the vehicle and the ability
to mark different locations of interest. Overall, the purpose of the project is to provide businesses with
the necessary tools to optimize their fleet management and reduce costs while improving their services.
1.2 Scope
The GPS Tracking Devices project aims to provide businesses with a comprehensive solution for
managing their fleet of vehicles. The project will include the development of a mobile application and
a web-based dashboard to manage and monitor the vehicles. The mobile application will allow drivers
to start and schedule journeys, add stops, and manage their driving behavior. The app will also include
a feature for tracking the location of the vehicle in real-time, which will allow for better coordination
and communication between drivers and dispatchers. The web-based dashboard will provide a
centralized location for fleet managers to monitor and analyze the performance of their vehicles. The
dashboard will include features such as maintenance expense management, journey history, route
optimization, and live tracking of vehicles. Additionally, the project will include the implementation of
pro tracking, which will provide drivers and fleet managers with detailed insights into the driving
behavior of the vehicle. This feature will allow for better management of vehicle performance, and the
identification of areas for improvement. The project will also include the ability to add tags to the map
to mark different locations of interest, and live tracking of these tags using pro tracking. This feature
will be particularly useful for businesses that need to monitor specific locations, such as delivery or
pickup points. Overall, the GPS Tracking Devices project aims to provide businesses with a
1
comprehensive solution for managing their fleet of vehicles, improving communication, and increasing
efficiency.
1.3 Modules
1.3.1 Account management:
Account Management module is designed to manage the accounts of their business users. The module
provides tools to add, remove and edit accounts for the business users. This module is essential for
efficient account management, allowing the business admin to keep track of their business users and
ensure that all the required information is up to date.
FE-1: Create new accounts and provide all the necessary information i.e., names, addresses, contacts.
FE-2: Remove accounts if they are no longer needed or if there is a need to deactivate an account.
FE-3: Edit the information related to the account or changing the account password.
FE-4: Set permissions for different users, giving them access to only certain parts of the system. FE-5:
Add and manage their payment information, such as payment method details.
FE-6: Generate reports related to their account, such as financial statements or user activity logs.
1.3.2 Driver Management:
Driver Management module is designed to manage drivers and ensure that they have a complete record
of all the drivers in their fleet. This module allows business owners to add, edit, and remove drivers
from the system. Driver Management module provides is a simple and effective way to manage their
drivers and ensure that all driver-related information is up to date and accurate.
FE-1: create a new driver account by providing the details such as username, display name, password.
FE-2: Edit the information of existing drivers.
FE-3: Remove a driver from the system.
FE-4: Shows profile of driver.
FE-5: Shows driving history of driver.
1.3.3 Vehicles Management:
The Vehicles Management module is designed to enable the control panel users to manage vehicles of
the users. The module supports adding devices to vehicles to get live location information. This feature
helps in tracking the vehicle's location in real-time. The module allows storing the engine number and
2
chassis number of each vehicle. This information is useful for tracking the vehicle's maintenance
history and repair work.
FE-1: In control panel vehicles will be added and users will be assigned to them.
FE-2: Vehicles can be added by their registration numbers one by one, or a CSV file can be uploaded.
FE-3: In vehicles we add devices to get live location.
FE-4: We can edit vehicle.
FE-5: We can assign them color.
FE-6: We can store their engine number and chases number.
FE-7: We set their fuel mileage.
1.3.4 Devices Configuration:
Devices Management module is designed to help users manage the trackers installed in their vehicles.
Devices Management module provides users with a way to monitor and manage the trackers installed
in their vehicles. By enabling or disabling devices, assigning them to vehicles, and configuring them.
FE-1: Enable or disable devices from the control panel, indicating if the tracker is on or off.
FE-2: Apply filters to navigate through specific device information, such as device type, status,
location.
FE-3: Assign devices to vehicles in which the trackers are installed to get live tracking data.
FE-4: Customize device settings, control the data received from the tracker and manage alerts.
FE-5: Shows the status of each device, whether it is connected or disconnected.
FE-6: Detailed information about each device, including the manufacturer, device model, etc.
FE-7: Provides a history of each device, including any maintenance or repair work done on the device.
1.3.5 Expense Management:
The Expense Management module is designed to help business owners manage their transport system
costs, including fuel, maintenance, and other related expenses. The module also provides filters that
allow the user to navigate through desired results. For example, a user can filter the expenses to display
only the fuel consumption or the maintenance of a specific vehicle.
FE-1: User can check the date of expense.

FE-2: User can check type of expense (Fuel, Maintenance etc.). FE-3:
User can check the vendor.
FE-4: User can check who did that expense.
FE-5: User can check the amount of that expense.
3
FE-6: Expenses can be displayed in both list and graphical format.
1.3.6 History Management:
The History Management module is designed to help user navigate through the travel history of their
vehicles. History Management module provides a comprehensive view of the vehicle's travel history,
allowing users to identify patterns and areas where costs can be optimized. The module also helps in
monitoring driver behavior, ensuring compliance with safety regulations, and improving overall
efficiency.
FE-1: Historical Data of speed.

FE-2: Provides detailed information e.g., Altitude, status, name, and time. FE-3:
Ignition data with time.
FE-4: Provides Odometer readings, traveled distance and fuel consumption.
FE-5: Draw complete history of user or vehicle by clicking on just one option and can play it.
FE-6: Track any events related to the vehicle, such as maintenance, repair work, or accidents.
FE-7: Track the vehicle's fuel consumption and identify any areas for optimization.
1.3.7 Journey Management:

The Journey Management module is designed to help users plan and customize their journeys. The
module allows users to create a journey by inputting a starting point and an ending point. Journey
Management module provides users with a convenient and customizable way to plan and manage their
journeys. Users can easily create a journey, add stops, and schedule the trip, ensuring that they arrive at
their destination on time and with ease.
FE-1: Can create a new journey by adding a starting point and an ending point.
FE-2: Can add stops to their journey, indicating the locations they will be visiting along the way.
FE-3: Users can schedule their journey, indicating the date and time they will be starting the journey.
FE-4: Provides details of their journey, including the duration of the journey, the distance traveled.
FE-5: Provides map view of their current journey.
FE-6: Users can customize their routes, choosing the fastest or shortest route, and avoiding certain
roads.
FE-7: Users can set up alerts and notifications to remind them of upcoming journeys, scheduled stops.
1.3.8 Geofence Management:
4
The Geofencing module is a tool that allows users to create customized geographical boundaries, also
known as Geofence, around specific areas or locations. With this module, users can set different
Geofence according to their customers' needs, allowing them to monitor their vehicles and receive
alerts when they leave or enter a specified area.
FE-1: User can add Geofence.
FE-2: User can add multiple Geofence.
FE-3: User can remove Geofence.
FE-4: User can draw any type of Geofence. FE-5: User can edit Geofence.
1.3.9 Alerts and notifications:
The Alerts Management module allows users to manage and customize the alerts that are generated by
the system. With this module, users can select which type of alerts should be given to the customer and
by which platform. Users can choose from a variety of different alert types, including alerts related to
maintenance tasks, geofencing, vehicle speed, and other relevant information. They can then select
which platforms to use for sending alerts, such as SMS, email, or push notifications.
FE-1: User can choose the type of alerts he wants.

FE-2: User can choose the platform.
FE-3: User can turn on the alerts.
FE-4: User can turn off the alerts.
FE-5: User can set the priority of alerts (Critical, normal and etc.).
1.3.10 Driver License Management:

Driver license management is a system designed to store and manage information about drivers and
their licenses. The system can be used by organizations such as government agencies, employers, and
insurance companies to keep track of driver information, including their license expiry date, license
type, region, and name. Overall, driver license management can help organizations stay on top of their
drivers' licensing requirements and ensure that they are operating legally and safely on the road.
FE-1: Shows profile of driver.

FE-2: Shows driving history of driver. FE-3: Can check the expiry of license.
FE-4: Can store the data of license.
FE-5: Can check the type of license.
FE-6: User will get an alert when the license expires of any diver.
1.3.11 Vehicles Maintenance:
5
The Vehicles Maintenance Management module is designed to help individuals and organizations keep
track of important maintenance tasks related to their vehicles, such as tire and oil changes. The module
allows users to input information about their vehicle, including the date of the last tire or oil change,
the current mileage, and the recommended mileage interval for the next maintenance task.
FE-1: User can maintain their vehicle.

FE-2: User will be notified when the oil of their vehicle needs to be changed.
FE-3: User will automate alerts for service (oil and tire changing). FE-4: User can keep records of
maintenance.
1.4 Overview
This document aims to go into greater detail on the system's features. To get into greater detail we have
used visual displays such as use case diagrams and context diagrams. In addition to that functional and
non-functional requirements, detailed use case description and user interface design details and
operating environment are explained.
2. Overall Description
2.1 Product Perspective
The GPS Tracking Devices project is an innovative solution that empowers businesses to efficiently
manage their fleet of vehicles. Our product comprises a mobile application and web-based dashboard
that enables drivers and fleet managers to monitor and manage their vehicles in real-time. With this
solution, businesses can improve their communication and collaboration, increase efficiency, and
reduce operational costs. The mobile application, designed for drivers, includes features like journey
scheduling, stop management, and driving behavior management. It also provides real-time tracking of
vehicle location, which allows for better coordination between drivers and dispatchers. Additionally,
the app includes pro tracking, which provides detailed insights into vehicle performance and driving
behavior. This feature enables drivers and fleet managers to identify areas for improvement and take
proactive measures to ensure optimal vehicle performance. The web-based dashboard, designed for
fleet managers, provides a centralized location for monitoring and analyzing vehicle performance. It
includes features like maintenance expense management, journey history, route optimization, and live
tracking of vehicles. With this solution, fleet managers can identify areas for improvement, streamline
operations, and reduce operational costs.
2.2 User classes and characteristics
Table 1: User classes and characteristics

User Class Description
6
User User will use the system to check live mapping, add journey, remove
journey, add stops, manage expenses, login and edit information, view
travel history, view license information can add or remove vehicles, view
alerts and notifications.
Admin Admin will use the system for the management of users, management of
devices (adding, removing and configuring devices), management of
vehicles (adding or removing), can add drivers for fleets, manage stops.
Admin can edit and delete the profile of user (Driver and User).
2.3 Operating Environment
OE-1: The web application for this system shall be deployed on Microsoft Azure. OE-2:
The database for this server will be SQL.
OE-3: The System shall operate correctly with Windows Internet Explorer versions 7, 8, and 9; Firefox
versions 12 through 26; Google Chrome (all versions); Apple Safari versions 4.0 through 8.0. OS-3:
The mobile application shall be operational on android 10 or above.
2.4 Design and Implementation Constraints

There are times when a certain programming language must be used, a code library that has already
had time invested to develop it needs to be used, and so forth. Describe any factors that will restrict the
options available to the developers and the rationale for each constraint. Constraints are described
further in Chapter 141, “Beyond functionality.” Example:
CO-1: The system shall use Oracle Enterprise Linux 6 server for tracking.
CO-3: The system will use Apache Tomcat version 6.0.29 server for application.
CO-2: The system shall use flask for the development of REST API’s.
CO-3: The system shall use VANILA JS Technology web framework for Web Frontend.
CO-4: The system shall use React Native for the Development of Mobile Application.
CO-5: The system shall use Python and its libraries to develop the machine learning code.
CO-7: The user needs to have a knowledge of basic computer skills to use the application.
3. Requirement Identifying Technique
7
3.1 Use case Diagram
3.1.1 User Use Case Diagram
8
9
3.1.2 Admin Use Case Diagram
10
11
3.2Use case description
3.2.1 User Profile
Table 2: Description for register user

Use Case ID: CUC-1
Use Case Name: Register User
Actors: Primary actor: User
Description: To create an account, the user will enter the information requested by the system.
Trigger: User enters the required credentials and clicks onto the “Register” button so process can activate.
Preconditions: PRE-1: User has active internet connection. PRE-2:

User has active phone number.
Post Conditions: POST-1: User information will be verified.

POST -2: User receives confirmation message and access to the account.
Normal Flow: 1. User enters name.

2. User enters the email address.
3. User select gender.
4. User enters the password.
5. User re-enters the password to confirm.
6. System checks availability of username.
7. System authenticates.
8. Account Registered Successfully.
Alternative Flows: a) In step 2 of normal flow if email entered by the user is invalid then:
1. The System checks the email.
2. System will prompt user to correct the email.
3. User corrects the email.
b) In step 4 of normal flow if the username entered by the user is already existing then.
1. The System checks the username.
2. System will prompt patient to enter a unique username.
3. Patient re-enters the username.
Exceptions: None
Business Rules The User's information should be kept strictly confidential and secure.
Assumptions: None
Table 3: Description for login user

Use Case ID: CUC-2
Use Case Name: Login User
Description: User logins and accesses the system features
Trigger: User enters login credentials i.e., username/email and password and presses enter.
12
Preconditions: PRE-1: User has an active internet connection. PRE-
2: User has already a registered account.
Post Conditions: POST-1: User logs into the system successfully.

POST-2: User accesses the different app functionalities.
Normal Flow: 1. User enters the email/username and password.

2. System checks for details of user.
3. User is logged in successfully.
Alternative Flows: In step 1 of normal flow if login details entered by the user are incorrect:
1. System prompts the error message.
2. User corrects the details.
3. User is logged in to the system successfully.
Exceptions: 1. System checks for an username in first step of the normal flow
2. Password authentication in the system's database.
3. If the email address is accurate but the password is incorrect, the system will prompt the user to
enter the password again.
4. If the password entered by the user is correct but the username, the system asks the user to provide
a valid email address.
5. If the system does not recognize both the Username and the password, the user is required to
reenter both.
Business Rules Only those users who have a registered account should be allowed to use the system's features.
Assumptions: None
Table 4: Description for edit user profile

Use Case ID: CUC-3
Use Case Name: Edit User profile
Description: User edits his account information.
Trigger: Users logs in and edit his information.
Preconditions: PRE-1: User has an active internet connection. PRE-2:
User has already a registered account.
Post Conditions: POST-1: User logs into the system successfully. POST-2:
User edits the account information.
Normal Flow: 1. User enters the username and password.

2. System checks for details of user.
3. User is logged in successfully.
4. Users edits the account information.
13
Alternative Flows: In step 1 of normal flow if login details entered by the user are incorrect:
1. System prompts the error message.
2. User corrects the details.
3. User is logged in to the system successfully.
4. User edits account information.
Exceptions: System validates the changes that are being made and updates the database. System
authenticates the valid information is being entered by the user.
Business Rules 1. Only those users who have a registered account should be allowed to edit their account information.
2. User cannot edit his/her username.
Assumptions: None
Table 5: Description for add driver

Use Case ID: UCU-4
Use Case Name: Add driver
Actors: Primary Actor: User
Description: User can add multiple drivers and can assign them to vehicles
Trigger: Users click on driver and add drivers
Preconditions: PRE-1: user must have active internet connection.
PRE-2: user must have access to driver’s management.
PRE-3: user must have logged into the system.
PRE-4: user must have access of driver’s management.
Post Conditions: POST-1: Driver will be added.

POST-2: User can assign driver to vehicle.
Normal Flow: 1. Users enter username and password.
2. Users click on drivers.
3. Users add drivers.
4. User will click on ok.
Alternate Flow: 1. Admin can also add the driver
Exceptions: Driver of same username will not be added.
Business Rules This is for large organization who have large number of vehicles and drivers.
Assumptions: None.
Table 6: Description for delete driver

Use Case ID: UCU-5
Use Case Name: Delete driver
Description: User can delete drivers.
Trigger: Users click on driver and delete drivers
14
PRE-4: user must have added a driver first.
Post Conditions: POST-1: Driver will be deleted.
3. Users click on delete button.
4. User should click on ok button.
Alternate Flow: 1. Admin can remove the driver.
Exceptions: First user should unassigned the driver from the vehicle he is assigned to.
Business Rules This is for the user to remove the driver and add new ones.
Assumptions: None
Table 7: Description for edit driver

Use Case ID: UCU-6
Use Case Name: Edit driver
Description: User can Edit drivers.
Trigger: Users click on Edit driver option.
PRE-4 user must have added driver first.
PRE-5: user must have access of driver’s management.
Post Conditions: POST-1: Driver details can be edited
3. User will click on edit drivers.
4. User will click on save button.
Alternate Flow: 1. Admin can also edit the driver.
Exceptions: None
Business Rules This is for user to edit the details of the drivers.
Assumptions: None
Table 8: Description for add geofence

Use Case ID: UCU-7
Use Case Name: Add Geofence
Actors: User
Description: User can add multiple geofences.
Trigger: Users click on geofence management then click on add button.
15
PRE-2: user must have access to geofence management.
Post Conditions: POST-1: Geofence will be added.

POST-2: Geofence can be edited.
POST-3 geofence can be assigned to vehicles.
Normal Flow: 1. User will enter username and password.
2. User will click on Geofence management.
3. User will click on add button.
4. Geofence will be added
Alternate Flow: 1. Admin can also add the geofence
Exceptions: Geofence within the geofence cannot be added.
Business Rules This is for the user to add the boundary limit for the vehicles. After which they will receive the alert.
Assumptions: None
Table 9: Description for edit geofence

Use Case ID: UCU-8
Use Case Name: Edit Geofence
Actors: User
Description: User can Edit geofences.
Trigger: Users click on geofence management then click on edit button.
PRE-4 user must have geofence added first.
Post Conditions: POST-1: new boundary limits will be set.

3. User will click on edit button.
4. Geofence will be edited.
Alternate Flow: 1. Admin can also edit the geofence.
Exceptions: Geofence will be added first.
Business Rules This is for the user to edit the geofemce of the vehicles.
Assumptions: None
Table 10: Description for delete geofence

Use Case ID: UCU-9
Use Case Name: Delete Geofence
16
Description: User can delete geofences.
Trigger: Users click on geofence management then click on delete button.
PRE-4: user must have geofence added first.
Post Conditions: POST-1: User will not receive the alert.

3. User will click on delete button.
4. Geofence will be deleted.
Alternate Flow:
Exceptions: Geofence should have added first.
Business Rules This is for the user who wants to delete the geofence.
Assumptions: None
Table 11: Description for View geofence

Use Case ID: UCU-10
Use Case Name: View Geofence
Actors: User
Description: User can view their geofences.
Trigger: Users click on geofence management then click on add button.
Post Conditions: POST-1: Graphical view of Geofence will be displayed.


3. User will click on view button.
4. Geofence will be displayed
Alternate Flow: None
Exceptions: Geofence should be added first.
Business Rules This is for the user if they want to view the geofence.
Assumptions: None
Table 12: Description of Add expense

Use Case ID: UCU-11
Use Case Name: Add Expenses
Actors: User
17
Description: User can add expenses of their vehicles.
Trigger: Users click on expense management then click on add button.
PRE-2: user must have access to expense management.
Post Conditions: POST-1: Expense can be added.

POST-2: Expense Report can be generated.
2. User will click on Expenses management.

Exceptions: Users have to fill all the details otherwise expense will not be shown properly.
Business Rules This is for those who want to manage the expense of their vehicles.
Assumptions: None
Table 13: Description of Delete expense

Use Case ID: UCU-12
Use Case Name: Delete Expenses
Actors: User
Description: User can delete expenses of their vehicles.
Trigger: Users click on expense management then click on delete button.
PRE-2: user must have access to Expense management.
PRE-4: user must have expense added first.
Post Conditions: POST-1: Expense will be removed.


4. User will click on ok button.
Exceptions: If the user doesn’t click on ok button in step 4 the expense will not be removed.
Business Rules This is for those who want to delete old expense and add new one.
Assumptions: None
Table 14: Description of View expense

Use Case ID: UCU-13
18
Use Case Name: View Expenses
Actors: User
Description: User can view expenses of their vehicles.
Trigger: Users click on expense management.

PRE-2: user must have access to expense management.
Post Conditions: POST-1: Expense can be viewed.

POST-2: Expenses cab be viewed in graphical form.
Exceptions: Users have to add the expenses first.
Business Rules This is for those who want to view the expense of their vehicles. Expense report can also be generated.
Assumptions: None
Table 15: Description of add logins

Use Case ID: UCU-14
Use Case Name: Add logins
Actors: User
Description: User can add logins which can help to open the control panel on multiple places.
Trigger: Users click on Login management to add multiple logins.
PRE-2: user must have access to login management.
Post Conditions: POST-1: different logins can be added.

POST-2: one user can login from multiple control panels.
2. User will click on Login management.

Exceptions: Login of same username cannot be made.
Business Rules This is for those who want to manage their panel from different devices.
Assumptions: None
Table 16: Description of remove logins

Use Case ID: UCU-15
19
Use Case Name: Remove logins
Actors: User
Description: User can remove logins.
Trigger: Users click on Login management to remove logins.
Post Conditions: POST-1: once the login is removed then that person will not have the further access.

3. User will click on remove button.
Exceptions: None
Business Rules This is for the user to remove new logins and add new logins.
Assumptions: None
Table 17: Description of edit logins.
Use Case ID: UCU-16

Use Case Name: Edit logins
Actors: User
Description: User can edit the details of login.
Trigger: Users click on Login management to edit login.
Post Conditions: POST-1: details of the login will be changed once saved.

Exceptions: None.
Business Rules This is for the user to edit their logins.
Assumptions: None
Table 18: Description of view report
20
Use Case ID: UCU-17
Use Case Name: View reports
Actors: User
Description: User can view reports.
Trigger: Users click on reports and view them.
PRE-2: user must have access to reports.
Post Conditions: POST-1: reports can be printed.

2. User will click on reports.

3. User will click on any reports.
4. User will fill details.
5. User can will click ok.
6. User can view report.
Exceptions: Users have to click on the report and fill the details.
Business Rules This is for those who want to view monthly movement of their vehicles.
Assumptions: None
Table 19: Description of Add journey.
Use Case ID: UCU-18

Use Case Name: Add journey
Actors: User
Description: User can add journey.
Trigger: User should click on journey and click on the add button.
PRE-2: user must log on the system.
PRE-3: user should fill the details of journey.
PRE-4: user must have the access.
Post Conditions: POST-1: journey could be assigned to all the vehicles or vehicle
2. User will click on journey.
3. Users click on add button.
4. User will fill the details of journey.
5. User will click the save button and journey will be added.
Alternate Flow: Admin can also add the journey for the user.
21
Exceptions: User must have to assign the journey to the vehicle.
Business Rules This for route management. As large clients demand route management.
Assumptions: None
Table 20: Description of remove journey.
Use Case ID: UCU-19

Use Case Name: remove journey
Actors: User
Description: User can remove journey.
Trigger: User should click on journey and click on the delete button.
PRE-2: user must log on the system. PRE-3:
user should add the journey first, PRE-4:
user must have the access.
Post Conditions: POST-1: user should unassigned the journey first.

3. Users click on delete button.
4. User will click the ok button and journey will be removed.
Alternate Flow: Admin can also remove the journey for the user.
Exceptions: If the journey is assigned it cannot be removed.
Business Rules This will help user to remove old journeys and add new ones.
Assumptions: None
Table 21: Description of edit journey.
Use Case ID: ACU-20

Use Case Name: Add journey
Actors: User
Description: User can add journey.
Trigger: User should click on journey and click on the add button.
PRE-3: user must add journey first.
PRE-4: user must have the access.
Post Conditions: POST-1: user should unassigned the journey first.

3. Users click on edit button.
22
4. User will click the save button and journey will be edited.
Alternate Flow: Admin can also edit the journey for the user.
Exceptions: User must have to assign the journey to the vehicle.
Business Rules This will help user to change the details of the journey.
Assumptions: None
Table 22: Description of check history
Use Case ID: UCU-21

Use Case Name: history
Actors: user
Description: User can check the history of previous days of any vehicle
Trigger: User should click on the history and select he date and vehicle.
PRE-3: user must have access to the history.
PRE-4: old data of that user must be available.
Post Conditions: POST-1: user can check the mileage and speed.
2. User will click on the history.

3. Users select the vehicle.
4. User will select the date.
5. User will click on the search button and history will be available.
Exceptions: If the user doesn’t have any vehicle history will not be available.
Business Rules This will help user to track the previous moment of their vehicles.
Assumptions: None
Table 23: Description of mileage and from user.
Use Case ID: UCU-22

Use Case Name: Mileage and speed
Actors: user
Description: User can check the mileage and speed of previous days of any vehicle
Trigger: User should click on the history and select he date and vehicle them click the mileage.
PRE-5: User must open and draw the history first.
Post Conditions: POST-1: user can check the mileage, odometer and speed of the vehicle.
23
6. User will click on the mileage.
Exceptions: If the user doesn’t have any vehicle mileage will not be available.
Business Rules This will help the user to check the mileage and speed of their vehicles.
Assumptions: None
Table 24: Description of check speed
Use Case ID: UCU-23

Use Case Name: check speed
Actors: user
Description: User can check the speed of previous days of any vehicle
Trigger: User should click on the history and select he date and vehicle them click the mileage.
PRE-5: User must open and draw the history first.
Post Conditions: POST-1: user can check the mileage, odometer and speed of the vehicle.

6. User will click on the speed summary.
Exceptions: If the user doesn’t have any vehicle speed will not be available.
Business Rules This will help the user to check the speed of their vehicles.
Assumptions: None
Table 25: Description of vehicle maintenance alerts license
Use Case ID: UCU-24

Use Case Name: Vehicle maintenance alerts
Actors: user
Description: User can maintain their vehicle with the help of it.
Trigger: User should click on the vehicle maintenance.
24
PRE-3: user must have access to the vehicle maintenance.
PRE-4: vehicle must be added first.
Post Conditions: POST-1: user can generate the automated alerts for the maintenance of vehicle.
2. User will click on the maintenance.
4. User will fill the detail.
5. User will click on the save button.
6. User will get automated alert from the system according on time he fills.
Alternate Flow: Admin can add details and turn on the alerts after getting details from the user.
Exceptions: If the user doesn’t have any vehicles he can not avail this feature.
Business Rules This will help user to maintain their vehicles.
Assumptions: None
Table 26: Description of print report
Use Case ID: UCU-25

Use Case Name: print reports
Actors: User
Description: User can print report.
Trigger: Users click on reports and view them.
PRE-2: user must have access to reports.
Post Conditions: POST-1: reports can be printed.

2. User will click on reports.
3. User will click on any reports.
4. User will fill details.
5. User can will click ok.
6. User can print report.

Exceptions: Multiple reports cannot be generated.
Business Rules This is for those who want to see reports of their vehicles.
Assumptions: None
25
Table 27: Description of logout
Use Case ID: UCU-26

Use Case Name: Logout
Actors: user
Description: User can logout.
Trigger: User should click my profile and click on logout.
Post Conditions: POST-1: user will be logged out.

Normal Flow: 1. User will click on my profile.
2. User will click on logout

Exceptions: None
Business Rules This is for getting logged out of the system.
Assumptions: None
Table 28: Description for search geofence.
Use Case ID: UCU-27

Use Case Name: search Geofence
Actors: User
Description: User can search geofences.
Trigger: Users click on geofence management then click on search Bar.
PRE-4 user must have geofence added first.
Post Conditions: POST-1: User can edit searched geofence.

POST-2: User can remove searched geofence.
3. User will click on Search bar.

Exceptions: None
Business Rules This is for the ease of user to find the geofence.
Assumptions: None
26
Table 29: Description for view geofence.
Use Case ID: UCU-27

Use Case Name: Geofence
Actors: User
Description: User can delete geofences.
Trigger: Users click on geofence management then click on delete button.
Post Conditions: POST-1: User can edit the geofence.

POST-2: User can delete the geofence.
3. User can view geofence.

Exceptions: None
Business Rules This is for users to view their geofences
Assumptions: None
Table 30: Description for search drivers.
Use Case ID: UCU-28

Use Case Name: search Drivers
Actors: User
Description: User can search driverss.
Trigger: Users click on drivers management then click on search Bar.
PRE-2: user must have access to drivers management.
PRE-4 user must have drivers added first.
Post Conditions: POST-1: User can edit searched drivers.

POST-2: User can remove searched drivers.
2. User will click on Drivers management.

Exceptions: None
Business Rules This is for the ease of user to find the drivers.
27
Assumptions: None
Table 31: Description for view drivers.
Use Case ID: UCU-29

Use Case Name: Drivers
Actors: User
Description: User can delete driverss.
Trigger: Users click on drivers management then click on delete button.
PRE-2: user must have access to drivers management.
PRE-4: user must have drivers added first.
Post Conditions: POST-1: User can edit the drivers.

POST-2: User can delete the drivers.
2. User will click on Drivers management.
3. User can view drivers.

Exceptions: None
Business Rules This is for users to view their drivers.
Assumptions: None
Table 31: Description for search expenses.
Use Case ID: UCU-30

Use Case Name: search Expenses
Actors: User
Description: User can search expensess.
Trigger: Users click on expenses management then click on search Bar.
PRE-2: user must have access to expenses management.
PRE-4 user must have expenses added first.
Post Conditions: POST-1: User can edit searched expenses.

POST-2: User can remove searched expenses.

28
Exceptions: None
Business Rules This is for the ease of user to find the expenses.
Assumptions: None
Table 32: Description for view expenses.
Use Case ID: UCU-31

Use Case Name: Expenses
Actors: User
Description: User can delete expensess.
Trigger: Users click on expenses management then click on delete button.
PRE-2: user must have access to expenses management.
PRE-4: user must have expenses added first.
Post Conditions: POST-1: User can edit the expenses.

POST-2: User can delete the expenses.

7. User can view expenses.

Exceptions: None
Business Rules This is for the user to view expenses of there vehicles.
Assumptions: None
Table 33: Description for search journeys.
Use Case ID: UCU-32

Use Case Name: search Journeys
Actors: User
Description: User can search journeyss.
Trigger: Users click on journeys management then click on search Bar.
PRE-2: user must have access to journeys management.
PRE-4 user must have journeys added first.
29
Post Conditions: POST-1: User can edit searched journeys.
POST-2: User can remove searched journeys.
5. User will click on Journeys management.

Exceptions: None
Business Rules This is for the ease of user to find the journeys.
Assumptions: None
Table 34: Description for view journeys.
Use Case ID: UCU-33

Use Case Name: Journeys
Actors: User
Description: User can delete journeyss.
Trigger: Users click on journeys management then click on delete button.
PRE-2: user must have access to journeys management.
PRE-4: user must have journeys added first.
Post Conditions: POST-1: User can edit the journeys.

POST-2: User can delete the journeys.
9. User will click on Journeys management.

10. User can view journeys.

Exceptions: None
Business Rules This is for the user to view journeys of there vehicles.
Assumptions: None
Table 35: Description of Add device.
Use Case ID: ACU-1
30
Use Case Name: Add device
Actors: Admin
Description: Admin can add device.
Trigger: Admin should click on device management to add device.
Preconditions: PRE-1: Admin must have active internet connection.
PRE-2: Admin must fill all the details of the devices.
PRE-3: Admin must log on the system.
Post Conditions: POST-1: Device will be ready for configuration. POST-2:

Device can be assigned to a vehicle.
Normal Flow: 1. Admin will enter username and password.
2. Admin will enter device details in devices.

3. Admin will click the save.
4. Devices will be saved.
Exceptions: Devices cannot be added if the device imei and sim number is already in the system.
Business Rules This is for the tracking of the vehicle which will allow us to track the vehicle through gsm/gps
Assumptions: None
Table 36: Description of Edit device.

Use Case ID: ACU-2
Use Case Name: Edit device
Actors: Admin
Description: Admin can edit device.
Trigger: Admin should click on device management to edit device.
PRE-3: the device should be added first.
Post Conditions: POST-1: Device will be ready for configuration. POST-2:

Device can be assigned to a vehicle.

3. Admin will click the edit button.
4. Admin will click the save button after editing.
5. Devices will be saved.
Exceptions: Devices cannot be edited if the device is not added.
Business Rules This is due the reason if we change a sim in the device we have to change the sim number in the system.
Assumptions: None
Table 37: Description of configure device.
31
Use Case ID: ACU-3
Use Case Name: configure device
Actors: Admin
Description: Admin can configure device.
Trigger: Admin should click on device management and double click on the device.
PRE-3: Device must be added first.
Post Conditions: POST-1: Device will be ready to use.


3. Admin will double click on the device.
4. Device can be configured by sending sms on sim number.
Exceptions: Devices should be in a gsm area.
Business Rules After this the device will be online on our server and send messages there.
Assumptions: None
Table 38: Description of remove device.
Use Case ID: ACU-4

Use Case Name: Remove device
Actors: Admin
Description: Admin can remove device.
Trigger: Admin should click on device management to remove device.
PRE-3: Device should be added first.
Post Conditions: POST-1: Device will deleted from the system.


3. Admin will click on delete option.
4. Admin will click on the ok button device will be deleted.
Exceptions: Devices cannot be deleted if it is assigned to the vehicle.
Business Rules This is to remove the device from the system if it is lost.
Assumptions: None
32
Table 39: Description of Create user ID from admin.
Use Case ID: ACU-5

Use Case Name: Create user ID
Actors: Admin
Description: Admin can create user id
Trigger: Admin should click on user in backend and click on add button.
PRE-2: Admin must fill all the details of the user.
PRE-4: User id must be unique.
Post Conditions: POST-1: user will be created.

POST-1: user name can’t be changed.
Normal Flow: 1. Admin will log on the system.
2. Admin will click on the users.
3. Admin will click the add button.
4. Admin will fill the details.
5. Admin will click the save button.
6. User will be created.
Alternate Flow: User can also register from control panel.
Exceptions: Username must be unique.
If user already exist, user id will not be created.
Business Rules This is to create the user id which can be used by the user.
Assumptions: None
Table 40: Description of Add vehicles:
Use Case ID: ACU-6

Use Case Name: Add vehicle
Actors: User
Description: User can add multiple vehicles.
Trigger: Users click on vehicle management then click on add button.
PRE-2: user must have access to vehicle management. PRE-3:
user must have logged into the system.
Post Conditions: POST-1: Vehicle will be added. POST-2:

User can edit vehicle
2. Users click on vehicle management.
3. Users add vehicles.
33
Exceptions: Vehicles of same registration number will not be added.
Business Rules This is only for large organization who large number of vehicles.
Assumptions: None
Table 41: Description for edit vehicle:
Use Case ID: ACU-7

Use Case Name: Edit vehicle
Actors: User
Description: User can Edit vehicles.
Trigger: Users click on vehicle management then click on edit button.
PRE-2: user must have access to vehicle management.
PRE-4: user must have vehicles added first.
Post conditions: POST-1: Vehicle info will be edited.

2. User will click on vehicle management.

3. User will click on edit button.
4. User will click on ok button.
Exceptions: Vehicle should be added first.
Assumptions: None
Table 42: Description for Delete vehicle.
Use Case ID: ACU-8

Use Case Name: Delete vehicle
Actors: User
Description: User can Edit vehicles.
Trigger: Users click on vehicle management then click on edit button.
PRE-2: user must have access to vehicle management.
Post conditions: POST-1: Vehicle will be deleted.

2. User will click on vehicle management.
34
4. Vehicle will be deleted
Exceptions: Vehicle should be added first.
Assumptions: None
Table 43: Description for Add contacts.
Use Case ID: ACU-9

Use Case Name: Add Contacts
Actors: User
Description: User can add multiple contacts.
Trigger: Users click on Alerts management then click on contacts and then click on add button.
PRE-2: user must have access to contact management.
Post Conditions: POST-1: Contacts can be added.

POST-2: Contacts can be edited.
POST-3: Contacts of different types can add.
2. User will click on Alerts management.

3. User will click on contacts.
Exceptions: None
Business Rules This is for those who want to add contacts on which they receive messages etc.
Assumptions: None
Table 44: Description of edit contacts.
Use Case ID: ACU-10

Use Case Name: Edit Contacts
Actors: User
Description: User can edit contacts.
Trigger: Users click on Alerts management then click on contacts and then click on Edit button.
Post Conditions: POST-1: Contact can be edited
35

Exceptions: None
Business Rules This is for those who want to update their contacts.
Assumptions: None
Table 45: Description of Delete contacts.
Use Case ID: ACU-11

Use Case Name: Delete Contacts
Actors: User
Description: User can Delete contacts.
Trigger: Users click on Alerts management then click on contacts and then click on delete button.
Post Conditions: POST-1: Contact will be deleted.


Exceptions: None
Business Rules This is for those who want to Delete their contacts
Assumptions: None
Table 46: Description of edit alerts.
Use Case ID: ACU-12

Use Case Name: Edit Alerts
Actors: User
Description: User can edit alerts.
Trigger: Users click on Alerts management then click on Settings.
36
PRE-2: user must have access to alerts management.
Post Conditions: POST-1: Alerts can be turned on and turned off. POST-2:
Alerts prioritization can be changed.

3. User will click on settings.
4. User can modify alerts.
Exceptions: Alerts prioritization should be handled with care because it can create a mess.
Business Rules This is for those who want to management alerts.
Assumptions: None
Table 47: Description for search contacts.
Use Case ID: ACU-13

Use Case Name: search Contacts
Actors: User
Description: User can search contactss.
Trigger: Users click on contacts management then click on search Bar.
PRE-2: user must have access to contacts management.
PRE-4 user must have contacts added first.
Post Conditions: POST-1: User can edit searched contacts.

POST-2: User can remove searched contacts.
8. User will click on Contacts management.


Exceptions: None
Business Rules This is for the ease of user to find the contacts.
Assumptions: None
Table 48: Description for view contacts.
Use Case ID: ACU-14
37
Use Case Name: Contacts
Actors: User
Description: User can delete contactss.
Trigger: Users click on contacts management then click on delete button.
PRE-2: user must have access to contacts management.
PRE-4: user must have contacts added first.
Post Conditions: POST-1: User can edit the contacts.

POST-2: User can delete the contacts.
12. User will click on Contacts management.

13. User can view contacts.

Exceptions: None
Business Rules This is for the user to view contacts of there vehicles.
Assumptions: None
Table 48: Description for search devices.
Use Case ID: ACU-15

Use Case Name: search Devices
Actors: User
Description: User can search devicess.
Trigger: Users click on devices management then click on search Bar.
PRE-2: user must have access to devices management.
PRE-4 user must have devices added first.
Post Conditions: POST-1: User can edit searched devices.

POST-2: User can remove searched devices.
11. User will click on Devices management.


Exceptions: None
Business Rules This is for the ease of user to find the devices.
Assumptions: None
38
Table 49: Description for view devices.
Use Case ID: ACU-16

Use Case Name: Devices
Actors: User
Description: User can delete devicess.
Trigger: Users click on devices management then click on delete button.
PRE-2: user must have access to devices management.
PRE-4: user must have devices added first.
Post Conditions: POST-1: User can edit the devices.

POST-2: User can delete the devices.
15. User will click on Devices management.

16. User can view devices.

Exceptions: None
Business Rules This is for the user to view devices of there vehicles.
Assumptions: None
Table 50: Description for search vehicles.
Use Case ID: ACU-17

Use Case Name: search Vehicles
Actors: User
Description: User can search vehicless.
Trigger: Users click on vehicles management then click on search Bar.
PRE-2: user must have access to vehicles management.
PRE-4 user must have vehicles added first.
Post Conditions: POST-1: User can edit searched vehicles.

POST-2: User can remove searched vehicles.
14. User will click on Vehicles management.


39
Exceptions: None
Business Rules This is for the ease of user to find the vehicles.
Assumptions: None
Table 51: Description for view vehicles.
Use Case ID: ACU-18

Use Case Name: Vehicles
Actors: User
Description: User can delete vehicless.
Trigger: Users click on vehicles management then click on delete button.
PRE-2: user must have access to vehicles management.
Post Conditions: POST-1: User can edit the vehicles.

POST-2: User can delete the vehicles.
18. User will click on Vehicles management.

19. User can view vehicles.

Exceptions: None
Business Rules This is for the user to view vehicles of there vehicles.
Assumptions: None
4. Functional Requirements
4.1 Login/Register
40
4.1.1 Register
Table 52: Description of FR-1

Identifier FR-1
Title <Register>
Requirement System shall allow the user to register.
Source User
Rationale To allow the user to register his/her account.
Business Rule (if User should be assigned a unique username.
required)
Dependencies None
Priority High

Identifier FR-2
Title <Account. Register. Username>
Requirement System shall allow the user to enter username for registration.
Source User
Rationale To allow user to enter unique name so that his/her data can be saved against
his/her unique username.
Business Rule (if None
required)
Dependencies None
Priority High

Identifier FR-3
Title <Account.Register.ChoosePassword>
Requirement System shall allow the user to make password for registration.
Source User
Rationale To register the user
41
required)
Dependencies None
Priority High

Identifier FR-4
Title <Account.Register.ConfirmPassword>
Requirement The system shall allow the user to re-enter his/her password.
Source User
Rationale To confirm the password.
required)
Dependencies None
Priority High

Identifier FR-5
Title <Account.Register.Email>
Requirement The system shall allow the user to enter his/her email.
Source User
Rationale To register the user
required)
Dependencies None
Priority Low

Identifier FR-6
Title <Account.Register.PhoneNo>
Requirement The system shall allow the user to enter his/her phone no.
Source User
42
Rationale For contact purposes.
required)
Dependencies None
Priority High

Identifier FR-7
Title <Account.Register.Address>
Requirement The system shall allow the User to enter his/her clinic address.
Source User
Rationale To locate the clinic.
required)
Dependencies None
Priority Medium

Identifier FR-8
Title <Account.Register.Submit>
Requirement The system shall allow the user to submit his/her account details.
Source User
Rationale To register Driver’s account.
required)
Dependencies None
Priority High
Identifier FR-9
Title <Account.Register.Error.MissingField>
43
Requirement The system shall display error message if the user misses any input filed.
Source User
Rationale All the fields are required to collect the Driver data.
required)
Dependencies None
Priority Medium
Identifier FR-10
Title <Account.Register.Error.MismatchPassword>
Requirement The system display error message for mismatch between password field and
renter password field.
Source User
Rationale To confirm the password of user.
required)
Dependencies None
Priority High
Identifier FR-11
Title <Account.Register.Error.Username>
Requirement The system shall display error message, if the username is not unique.
Source User
Rationale To keep the user notified about the registration process.
Business Rule (if Username shall be unique.
required)
Dependencies None
Priority Medium
44
4.1.2 Login
Identifier FR-12
Title <Login>
Requirement User shall be able to login to the system.
Source User
Rationale Allowing the user to access the system.
Business Rule (if Only those users who have a registered account should be allowed to use the
required) system's features.
Dependencies FR-1
Priority Meduim
Identifier FR-13
Title <Login.Authenticate>
Requirement System shall authenticate the user before login.
Source User
Rationale To authenticate that data is entered correctly
Business Rule (if System shall authenticate the user every time when he/she gets logged in.
required)
Dependencies None
Priority High
Identifier FR-14
Title <Login.Authenticate.Successful>
Requirement After authenticating the credentials, System shall give access to the user.
Source User
45
Rationale To inform the user about the status of login.
required)
Dependencies FR-15
Priority Medium
Identifier FR-15
Title <Login.Authenticate.SaveData>
Requirement System shall allow user to save his/her login data.
Source User
Rationale To reduce the number of logins for the user.
required)
Dependencies FR-13, FR-15
Priority Medium
Identifier FR-16
Title <Login.Authenticate.Error.Message>
Requirement System shall display error message if user enters wrong credentials or misses
any information.
Source User
Rationale To let the user notified.
required)
Dependencies FR-15
Priority Medium
46
Identifier FR-17
Title < Login.Authenticate.Error.Register>
Requirement If an unregistered user logins to the system, System shall display error message.
Source User
Rationale To guide the user to register first, before login.
required)
Dependencies FR-1
Priority High
Identifier FR-18
Title <Login.Authenticate.Error.InvalidUsername>
Requirement If the user enters wrong/invalid username, System shall display error message.
Source User
Rationale To update the user that he/she has invalid username.
required)
Dependencies None
Priority Medium
Identifier FR-19
Title <Login.Authenticate.Error.WrongPassword>
Requirement If the user enters wrong password, System shall display error message.
Source User
Rationale To update the user that he/she has entered wrong password.
47
required)
Dependencies None
Priority Medium
Identifier FR-20
Title <Login.Authenticate.Error.ForgotPassword>
Requirement System shall allow user to recover the password.
Source User
Rationale To allow the user, recover his/her password.
required)
Dependencies None
Priority Medium
4.1.3 Logout
Identifier FR-21
Title <Account.Logout>
Requirement System shall allow the user to logout his/her account.

Source User
Rationale To logout the user from the account.
required)
Dependencies FR-13
Priority Medium
48
Identifier FR-22
Title <Account.Logout.ConfirmationMessage>
Requirement System shall confirm from the user if he/she wants to logout.
Source User
Rationale For user’s confirmation
required)
Dependencies FR-24
Priority Medium
Identifier FR-23
Title <Account.Logout.Successful.Redirect>
Requirement System shall redirect the user to the login page after logout is successful.
Source User
Rationale To maintain the consistent flow of the system.
required)
Dependencies None
Priority Medium
Identifier FR-24
Title <Account.Logout.Cancel.Redirect>
Requirement If the user cancels the logout request, the system shall redirect the user to the
home page.
Source User
Rationale To maintain the consistent flow of the system.
required)
49
Dependencies FR-23
Priority Medium
4.2 User Account
4.2.1 Edit Account
Identifier FR-25
Title <Account.Edit>
Requirement User shall be able to edit his/her profile.
Source User
Rationale To allow User to update his/her profile information.
required)
Dependencies FR-1
Priority Medium
Identifier FR-26
Title <Account.Edit.ViewInfo>
Requirement System shall display the profile information that User wants to edit.
Source User
Rationale To modify User’s profile information.
Business Rule (if User cannot edit his/her username, once registered.
required)
Dependencies FR-25
Priority Medium
50
Identifier FR-27
Title <Account.Edit.Update>
Requirement User shall click on to the information he/she wants to edit.
Source User
Rationale Flexibility for the User
required)
Dependencies FR-26
Priority Medium
Identifier FR-28
Title <Account.Edit.SaveUpdate>
Requirement System shall save the changes made by User.
Source User
Rationale To update the information in the database of system.
required)
Dependencies FR-27
Priority Medium
Identifier FR-29
Title <Account.Edit.Confirmation>
Requirement System shall display confirmation message to the User.
Source User
Rationale To keep the User notified about the action.
required)
51
Dependencies FR-28
Priority Medium
Identifier FR-30
Title <Account.Edit.Redirect>
Requirement System shall link the user to the home page after saving changes.
Source User
Rationale To reflect the consistent flow of the system.
required)
Dependencies FR-29
Priority Medium
Identifier FR-31
Title <Profile.Edit.Refresh>
Requirement System shall be able to refresh the page if the information edited is not saved by
User.
Source User
Rationale To reflect the system’s backup.
required)
Dependencies FR-30
Priority Medium
52
4.3 Driver profile
4.3.1 Add Driver

Identifier FR-32
Title <DriverProfile.add>
Requirement System shall add the driver to the system.

Source User
Rationale To add the drivers to the system.
required)
Dependencies FR-1
Priority Medium
Identifier FR-33
Title <DriverProfile.add.details>
Requirement System shall only add driver when user fulfill all the details.
Source User
Rationale System requirements
required)
Dependencies FR-32
Priority High
Identifier FR-34
53
Title <DriverProfile.Error.>
Requirement The system shall display an error on the screen if the user doesnt fulfill all
details.
Source User
Rationale To let the user know about his mistake.
required)
Dependencies FR-33
Priority High
Identifier FR-36
Title <DriverProfile.Add.successful>
Requirement System shall display a message of successfully if the User is added.
Source User
Rationale To help the User know that the driver is added.
required)
Dependencies FR-35
Priority Medium
Identifier FR-37
Title <Driver.Add.incorrect.password>
Requirement System shall display the message of incorrect password if the password doesnt
match.
Source User
Rationale To help the User know about the issue.
required)
Dependencies FR-35
54
Priority Medium
4.3.2 Edit Driver
Identifier FR-38
Title <Driver.Edit>
Requirement User shall be able to edit the driver profile.
Source User
Rationale To allow User to update driver profile information.
required)
Dependencies FR-32
Priority Medium
Identifier FR-39
Title <Driver.Edit.ViewInfo>
Source User
Rationale To modify Driver’s profile information.
Business Rule (if User cannot edit Drivers username, once registered.
required)
Dependencies FR-32
Priority Medium
Identifier FR-40
55
Title <Driver.Edit.Update>
Source User
required)
Dependencies FR-38
Priority Medium
Identifier FR-41
Title <Driver.Edit.SaveUpdate>
Source User
required)
Dependencies FR-40
Priority Medium
Identifier FR-42
Title <Driver.Edit.Confirmation>
Source User
required)
Dependencies FR-41
56
Priority Medium
Identifier FR-43
Title <Driver.Edit.Redirect>
Source User
required)
Dependencies FR-42
Priority Medium
Identifier FR-44
Title <Profile.Edit.Refresh>
User.
Source User
required)
Dependencies FR-43
Priority Medium
4.3.3 Remove Driver
Identifier FR-45
Title <Remove.Driver>
Requirement User shall be able to remove the driver and add the new one.
57
Source User
Rationale To allow User to update driver profile information.
required)
Dependencies FR-32
Priority Medium
Identifier FR-46
Title <Driver.Remove.Error>
Requirement System shall display the error message on the screen if there is an issue in
removing the driver.
Source User
Business Rule (if User will be informed by the system if there is an error in removing the driver.
required)
Dependencies FR-45
Priority Medium
Identifier FR-47
Title <Driver.remove.unsuccessful>
Requirement User shall be informed by the system if the driver is not removed successfully.
Source User
Rationale To let the user know about removing driver.
required)
Dependencies FR-46
Priority Medium
58
Identifier FR-48
Title <Driver.remove.Successful>
Requirement System shall save the changes made by User and let the user know.
Source User
Rationale To update the Driver list in the database of system.
required)
Dependencies FR-45
Priority Medium
4.3.4 Search Driver Profile
Identifier FR-49
Title <DriverProfile.Search>
Requirement System shall display the profile of the specific Driver that User searches for.
Source User
Rationale To keep User and Driver interlinked.
required)
Dependencies FR-32
Priority Medium
Identifier FR-50
59
Title <DriverProfile.Search.assigned>
Requirement System shall only display all those profiles of Drivers that are assigned to the
User.
Source User
Rationale Privacy terms
required)
Dependencies FR-49
Priority High
Identifier FR-51
Title <DriverProfile.Search.ByUsername>
Requirement The User shall be able to search his/her Driver’s profile by entering his/her
name in search bar.
Source User
Rationale To provide ease to the User for the search i.e. to reduce the search effort.
required)
Dependencies FR-50
Priority High
Identifier FR-52
Title <DriverProfile.Search.Error.IncorrectUsername>
Requirement System shall display error message if the User searches for invalid Driver.
Source User
Rationale To help the User understand the state of system.
required)
Dependencies FR-51
60
Priority Medium
Identifier FR-53
Title <DriverProfile.Search.Error.NotExist>
Requirement System shall display error message that the user does not exists.
Source User
required)
Dependencies FR-52
Priority Medium
4.3.5 View Driver Profile
Identifier FR-54
Title <DriverProfile.View>
Requirement User can see the profile of Driver.
Source User
Rationale To let the User access his/her Drivers,to link them.
required)
Dependencies FR-32
Priority Medium
Identifier FR-55
Title <DriverProfile.View.List>
61
Requirement System shall display a list of registered Drivers to the User.
Source User
Rationale To keep and maintain the record of Drivers.
required)
Dependencies FR-54
Priority Medium
Identifier FR-56
Title <DriverProfile.View.Details>
Requirement The User shall view the details of Driver through Driver profile by clicking on it.
Source User
Rationale To keep the User aware of Driver profile.
required)
Dependencies FR-55
Priority Medium
4.4 Devices
4.4.1 Add Device

Identifier FR-57
Title <Device.add>
Requirement System shall add the Device to the system.

Source User
62
Rationale To add the Devices to the system.
required)
Dependencies FR-1
Priority Medium
Identifier FR-58
Title < Device.add.details>
Requirement System shall only add Device when user fulfill all the details.
Source User
Rationale So that user fulfil all the System requirements
required)
Dependencies FR-57
Priority High
Identifier FR-59
Title <Driver.Device.Error.>
details.
Source User
required)
Dependencies FR-58
Priority High

63
Identifier FR-60
Title <Device.Add.successful>
Requirement System shall display a message of successfully if the User is added.
Source User
Rationale To help the User know that the driver is added.
required)
Dependencies FR-69
Priority Medium
4.4.2 Edit Devices
Identifier FR-61
Title <Device.Edit>
Requirement User shall be able to edit the Device profile.
Source User
Rationale To allow User to update Device profile information.
required)
Dependencies FR-59
Priority Medium
Identifier FR-62
Title < Device.Edit.ViewInfo>
64
Source User
Rationale To modify Device’s profile information.
Business Rule (if User can edit Device, once registered.
required)
Dependencies FR-61
Priority Medium
Identifier FR-63
Title < Device.Edit.Update>
Source User
required)
Dependencies FR-62
Priority Medium
Identifier FR-64
Title < Device.Edit.SaveUpdate>
Source User
required)
Dependencies FR-63
Priority Medium
65
Identifier FR-65
Title <Device.Edit.Confirmation>
Source User
required)
Dependencies FR-64
Priority Medium
Identifier FR-66
Title < Device.Edit.Redirect>
Source User
required)
Dependencies FR-65
Priority Medium
Identifier FR-67
Title < Device.Edit.Refresh>
User.
Source User
66
required)
Dependencies FR-66
Priority Medium
4.4.3 Remove Devices
Identifier FR-68
Title <Remove. Device >
Requirement User shall be able to remove the Device and add the new one.
Source User
Rationale To allow User to update Device profile information.
required)
Dependencies FR-67
Priority Medium
Identifier FR-69
Title < Device.Remove.Error>
removing the Device.
Source User
Business Rule (if User will be informed by the system if there is an error in removing the Device.
required)
Dependencies FR-68
Priority Medium
67
Identifier FR-70
Title < Device.remove.unsuccessful>
Requirement User shall be informed by the system if the driver is not removed successfully.
Source User
Rationale To let the user know about removing Device.
required)
Dependencies FR-69
Priority Medium
Identifier FR-71
Title < Device.remove.Successful>
Source User
Rationale To update the Device list in the database of system.
required)
Dependencies FR-70
Priority Medium
4.4.4 Search Device
Identifier FR-72
Title < Device.Search>
68
Requirement System shall display the profile of the specific Device that User searches for.
Source User
Rationale To keep User and Device interlinked.
required)
Dependencies FR-71
Priority Medium
Identifier FR-73
Title < Device.Search.assigned>
Requirement System shall only display all those profiles of Device that are assigned to the
User.
Source User
required)
Dependencies FR-72
Priority High
Identifier FR-74
Title < Device.Search.IMEI>
Requirement The User shall be able to search his/her Device’s profile by entering his/her
name in search bar.
Source User
required)
Dependencies FR-73
69
Priority High
Identifier FR-75
Title < Device.Search.Error.IMEI>
Requirement System shall display error message if the User searches for invalid Device.
Source User
required)
Dependencies FR-74
Priority Medium
Identifier FR-76
Title <DriverProfile.Search.Error.NotExist>
Requirement System shall display error message that the Device does not exists.
Source User
required)
Dependencies FR-75
Priority Medium
4.4.5 View Device
Identifier FR-77
Title < Device.View>
70
Requirement User can see the profile of Device.
Source User
Rationale To let the User access his/her Device s,to link them.
required)
Dependencies FR-56
Priority Medium
Identifier FR-78
Title < Device.View.List>
Requirement System shall display a list of registered Device s to the User.
Source User
Rationale To keep and maintain the record of Devices.
required)
Dependencies FR-75
Priority Medium
Identifier FR-79
Title < Device.View.Details>
Requirement The User shall view the details of Device through Device profile by clicking on it.
Source User
Rationale To keep the User aware of Device profile.
required)
Dependencies FR-78
Priority Medium
71
4.4 Vehicles
4.4.1 Add Vehicles

Identifier FR-80
Title <Vehicles.add>
Requirement System shall add the Vehicles to the system.

Source User
Rationale To add the Vehicles to the system.
required)
Dependencies FR-1
Priority Medium
Identifier FR-81
Title < Vehicles.add.details>
Requirement System shall only add Vehicles when user fulfill all the details.
Source User
required)
Dependencies FR-80
Priority High

72
Identifier FR-82
Title < Vehicles.Device.Error.>
details.
Source User
required)
Dependencies FR-81
Priority High
Identifier FR-83
Title < Vehicles.Add.successful>
Requirement System shall display a message of successfully if the Vehicles is added.
Source User
Rationale To help the User know that the Vehicles is added.
required)
Dependencies FR-82
Priority Medium
4.5.2 Vehicles Driver
Identifier FR-84
Title < Vehicles.Edit>
Requirement User shall be able to edit the Vehicles profile.
73
Source User
Rationale To allow User to update Vehicles profile information.
required)
Dependencies FR-83
Priority Medium
Identifier FR-85
Title < Vehicles.Edit.ViewInfo>
Source User
Rationale To modify Vehicles’s profile information.
Business Rule (if User can edit Vehicles, once registered.
required)
Dependencies FR-84
Priority Medium
Identifier FR-86
Title < Vehicles.Edit.Update>
Source User
required)
Dependencies FR-85
Priority Medium
74
Identifier FR-87
Title < Vehicles.Edit.SaveUpdate>
Source User
required)
Dependencies FR-86
Priority Medium
Identifier FR-88
Title < Vehicles.Edit.Confirmation>
Source User
required)
Dependencies FR-87
Priority Medium
Identifier FR-89
Title < Vehicles.Edit.Redirect>
Source User
required)
75
Dependencies FR-88
Priority Medium
Identifier FR-90
Title < Vehicles.Edit.Refresh>
User.
Source User
required)
Dependencies FR-89
Priority Medium
4.5.3 Remove Vehicles
Identifier FR-91
Title < Vehicles.Remove >
Requirement User shall be able to remove the Vehicles and add the new one.
Source User
Rationale To allow User to update Vehicles profile information.
required)
Dependencies FR-90
Priority Medium
Identifier FR-92
76
Title < Vehicles.Remove.Error>
removing the Vehicles.
Source User
Business Rule (if User will be informed by the system if there is an error in removing the Vehicles.
required)
Dependencies FR-91
Priority Medium
Identifier FR-93
Title < Vehicles.remove.unsuccessful>
Requirement User shall be informed by the system if the Vehicles is not removed successfully.
Source User
Rationale To let the user know about removing Vehicles.
required)
Dependencies FR-92
Priority Medium
Identifier FR-94
Title < Vehicles.remove.Successful>
Source User
Rationale To update the Vehicles list in the database of system.
required)
77
Dependencies FR-93
Priority Medium
4.5.4 Search Vehicles Profile

Identifier FR-95
Title < Vehicles.Search>
Requirement System shall display the profile of the specific Vehicles that User searches for.
Source User
Rationale To keep User and Vehicles interlinked.
required)
Dependencies FR-94
Priority Medium
Identifier FR-96
Title < Vehicles.Search.assigned>
Requirement System shall only display all those profiles of Vehicles that are assigned to the
User.
Source User
required)
Dependencies FR-95
Priority High
78
Identifier FR-97
Requirement The User shall be able to search his/her Vehicles’s profile by entering his/her
name in search bar.
Source User
required)
Dependencies FR-96
Priority High
Identifier FR-98
Title < Vehicles.Search.Error.Reg no>
Requirement System shall display error message if the User searches for invalid Vehicles.
Source User
required)
Dependencies FR-97
Priority Medium
Identifier FR-99
Title < Vehicles.Search.Error.NotExist>
Requirement System shall display error message that the Vehicles does not exists.
Source User
required)
79
Dependencies FR-98
Priority Medium
4.5.5 View Vehicles
Identifier FR-100
Title < Vehicles.View>
Requirement User can see the profile of Vehicles.
Source User
Rationale To let the User access his/her Vehicles,to link them.
required)
Dependencies FR-99
Priority Medium
Identifier FR-101
Title < Vehicles.View.List>
Requirement System shall display a list of registered Vehicles to the User.
Source User
Rationale To keep and maintain the record of Vehicles.
required)
Dependencies FR-100
Priority Medium
80
Identifier FR-102
Title < vehicles.View.Details>
Requirement The User shall view the details of Vehicles through Vehicles profile by clicking on
it.
Source User
Rationale To keep the User aware of Vehicles profile.
required)
Dependencies FR-101
Priority Medium
4.6 Journey
4.6.1 Add Journey

Identifier FR-103
Title <Journey.add>
Requirement System shall add the Journey to the system.

Source User
Rationale User can add the Journey to the system.
required)
Dependencies FR-1
Priority Medium
Identifier FR-104
Title < Journey.add.details>
Requirement System shall only add Journey when user fulfill all the details.
81
Source User
required)
Dependencies FR-103
Priority High
Identifier FR-105
Title < Journey.Device.Error.>
details.
Source User
required)
Dependencies FR-104
Priority High
Identifier FR-106
Title < Journey.Add.successful>
Requirement System shall display a message of successfully if the Journey is added.
Source User
Rationale To help the User know that the Journey is added.
required)
Dependencies FR-105
Priority Medium
82
4.6.2 Driver Journey
Identifier FR-107
Title < Journey.Edit>
Requirement User shall be able to edit the Journey profile.
Source User
Rationale To allow User to update Journey profile information.
required)
Dependencies FR-103
Priority Medium
Identifier FR-108
Title < Journey.Edit.ViewInfo>
Source User
Rationale To modify Journey’s profile information.
Business Rule (if User can edit Journey, once registered.
required)
Dependencies FR-107
Priority Medium
Identifier FR-109
Title < Journey.Edit.Update>
83
Source User
required)
Dependencies FR-108
Priority Medium
Identifier FR-110
Title < Journey.Edit.SaveUpdate>
Source User
required)
Dependencies FR-109
Priority Medium
Identifier FR-111
Title < Journey.Edit.Confirmation>
Source User
required)
Dependencies FR-110
Priority Medium
84
Identifier FR-112
Title < Journey.Edit.Redirect>
Source User
required)
Dependencies FR-111
Priority Medium
Identifier FR-113
Title < Journey.Edit.Refresh>
User.
Source User
required)
Dependencies FR-112
Priority Medium
4.6.3 Remove Journey
Identifier FR-114
Title < Journey.Remove >
Requirement User shall be able to remove the Journey and add the new one.
Source User
Rationale To allow User to update Journey profile information.
85
required)
Dependencies FR-103
Priority Medium
Identifier FR-115
Title < Journey.Remove.Error>
removing the Journey.
Source User
Business Rule (if User will be informed by the system if there is an error in removing the Journey.
required)
Dependencies FR-114
Priority Medium
Identifier FR-116
Title < Journey.remove.unsuccessful>
Requirement User shall be informed by the system if the Journey is not removed successfully.
Source User
Rationale To let the user know about removing Journey.
required)
Dependencies FR-115
Priority Medium
86
Identifier FR-117
Title < Journey.remove.Successful>
Source User
Rationale To update the Journey list in the database of system.
required)
Dependencies FR-116
Priority Medium
4.6.4 Search Journey Profile

Identifier FR-118
Title < Journey.Search>
Requirement System shall display the profile of the specific Journey that User searches for.
Source User
Rationale To keep User and Journey interlinked.
required)
Dependencies FR-103
Priority Medium
Identifier FR-119
Title < Journey.Search.assigned>
Requirement System shall only display all those profiles of Journey that are assigned to the
User.
87
Source User
required)
Dependencies FR-118
Priority High
Identifier FR-120
Requirement The User shall be able to search his/her Journey’s profile by entering his/her
name in search bar.
Source User
required)
Dependencies FR-119
Priority High
Identifier FR-121
Title < Journey.Search.Error.Reg no>
Requirement System shall display error message if the User searches for invalid Journey.
Source User
required)
Dependencies FR-120
Priority Medium
88
Identifier FR-122
Title < Journey.Search.Error.NotExist>
Requirement System shall display error message that the Journey does not exists.
Source User
required)
Dependencies FR-121
Priority Medium
4.6.5 View Journey
Identifier FR-123
Title < Journey.View>
Requirement User can see the profile of Journey.
Source User
Rationale To let the User access his/her Journey,to link them.
required)
Dependencies FR-122
Priority Medium
Identifier FR-124
Title < Journey.View.List>
Requirement System shall display a list of registered Journey to the User.
89
Source User
Rationale To keep and maintain the record of Journey.
required)
Dependencies FR-123
Priority Medium
Identifier FR-125
Requirement The User shall view the details of Journey through Journey profile by clicking on
it.
Source User
Rationale To keep the User aware of Journey profile.
required)
Dependencies FR-124
Priority Medium
4.7 Geofence
4.7.1 Add Geofence

Identifier FR-126
Title <Geofence.add>
Requirement System shall add the Geofence to the system.

Source User
Rationale User can add the Geofence to the system.
90
required)
Dependencies FR-1
Priority Medium
Identifier FR-127
Title < Geofence.add.details>
Requirement System shall only add Geofence when user fulfill all the details.
Source User
required)
Dependencies FR-126
Priority High
Identifier FR-128
Title < Geofence.Device.Error.>
details.
Source User
required)
Dependencies FR-127
Priority High
91
Identifier FR-129
Title < Geofence.Add.successful>
Requirement System shall display a message of successfully if the Geofence is added.
Source User
Rationale To help the User know that the Geofence is added.
required)
Dependencies FR-128
Priority Medium
4.7.2 Geofence Driver
Identifier FR-130
Title < Geofence.Edit>
Requirement User shall be able to edit the Geofence profile.
Source User
Rationale To allow User to update Geofence profile information.
required)
Dependencies FR-125
Priority Medium
Identifier FR-131
Title < Geofence.Edit.ViewInfo>
Source User
Rationale To modify Geofence’s profile information.
92
Business Rule (if User can edit Geofence, once registered.
required)
Dependencies FR-130
Priority Medium
Identifier FR-132
Title < Geofence.Edit.Update>
Source User
required)
Dependencies FR-132
Priority Medium
Identifier FR-133
Title < Geofence.Edit.SaveUpdate>
Source User
required)
Dependencies FR-132
Priority Medium
93
Identifier FR-134
Title < Geofence.Edit.Confirmation>
Source User
required)
Dependencies FR-133
Priority Medium
Identifier FR-135
Title < Geofence.Edit.Redirect>
Source User
required)
Dependencies FR-134
Priority Medium
Identifier FR-136
Title < Geofence.Edit.Refresh>
User.
Source User
required)
94
Dependencies FR-135
Priority Medium
4.6.3 Remove Geofence
Identifier FR-137
Title < Geofence.Remove >
Requirement User shall be able to remove the Geofence and add the new one.
Source User
Rationale To allow User to update Geofence profile information.
required)
Dependencies FR-125
Priority Medium
Identifier FR-138
Title < Geofence.Remove.Error>
removing the Geofence.
Source User
Business Rule (if User will be informed by the system if there is an error in removing the
required) Geofence.
Dependencies FR-137
Priority Medium
95
Identifier FR-139
Title < Geofence.remove.unsuccessful>
Requirement User shall be informed by the system if the Geofence is not removed
successfully.
Source User
Rationale To let the user know about removing Geofence.
required)
Dependencies FR-138
Priority Medium
Identifier FR-140
Title < Geofence.remove.Successful>
Source User
Rationale To update the Geofence list in the database of system.
required)
Dependencies FR-139
Priority Medium
4.7.4 Search Geofence Profile

Identifier FR-141
Title < Geofence.Search>
Requirement System shall display the profile of the specific Geofence that User searches for.
Source User
96
Rationale To keep User and Geofence interlinked.
required)
Dependencies FR-125
Priority Medium
Identifier FR-142
Title < Geofence.Search.assigned>
Requirement System shall only display all those profiles of Geofence that are assigned to the
User.
Source User
required)
Dependencies FR-141
Priority High
Identifier FR-143
Requirement The User shall be able to search his/her Geofence’s profile by entering his/her
name in search bar.
Source User
required)
Dependencies FR-142
Priority High

97
Identifier FR-144
Title < Geofence.Search.Error.Reg no>
Requirement System shall display error message if the User searches for invalid Geofence.
Source User
required)
Dependencies FR-143
Priority Medium
Identifier FR-145
Title < Geofence.Search.Error.NotExist>
Requirement System shall display error message that the Geofence does not exists.
Source User
required)
Dependencies FR-144
Priority Medium
4.7.5 View Geofence
Identifier FR-146
Title < Geofence.View>
Requirement User can see the profile of Geofence.
Source User
98
Rationale To let the User access his/her Geofence,to link them.
required)
Dependencies FR-125
Priority Medium
Identifier FR-147
Title < Geofence.View.List>
Requirement System shall display a list of registered Geofence to the User.
Source User
Rationale To keep and maintain the record of Geofence.
required)
Dependencies FR-146
Priority Medium
Identifier FR-148
Requirement The User shall view the details of Geofence through Geofence profile by clicking
on it.
Source User
Rationale To keep the User aware of Geofence profile.
required)
Dependencies FR-147
Priority Medium
99
4.8 Expense
4.8.1 Add Expense

Identifier FR-149
Title <Expense.add>
Requirement System shall add the Expense to the system.

Source User
Rationale User can add the Expense of their vehicles to the system.
required)
Dependencies FR-1
Priority Medium
Identifier FR-150
Title < Expense.add.details>
Requirement System shall only add Expense when user fulfill all the details.
Source User
required)
Dependencies FR-149
Priority High
Identifier FR-151
100
Title < Expense.Device.Error.>
details.
Source User
required)
Dependencies FR-150
Priority High
Identifier FR-152
Title < Expense.Add.successful>
Requirement System shall display a message of successfully if the Expense is added.
Source User
Rationale To help the User know that the Expense is added.
required)
Dependencies FR-151
Priority Medium
4.8.2 Expense Driver
Identifier FR-153
Title < Expense.Edit>
Requirement User shall be able to edit the Expense profile.
Source User
Rationale To allow User to update Expense profile information.
101
required)
Dependencies FR-149
Priority Medium
Identifier FR-154
Title < Expense.Edit.ViewInfo>
Source User
Rationale To modify Expense’s profile information.
Business Rule (if User can edit Expense, once registered.
required)
Dependencies FR-153
Priority Medium
Identifier FR-155
Title < Expense.Edit.Update>
Source User
required)
Dependencies FR-154
Priority Medium
102
Identifier FR-156
Title < Expense.Edit.SaveUpdate>
Source User
required)
Dependencies FR-155
Priority Medium
Identifier FR-157
Title < Expense.Edit.Confirmation>
Source User
required)
Dependencies FR-156
Priority Medium
Identifier FR-158
Title < Expense.Edit.Redirect>
Source User
required)
Dependencies FR-157
103
Priority Medium
Identifier FR-159
Title < Expense.Edit.Refresh>
User.
Source User
required)
Dependencies FR-158
Priority Medium
4.8.3 Remove Expense
Identifier FR-160
Title < Expense.Remove >
Requirement User shall be able to remove the Expense and add the new one.
Source User
Rationale To allow User to update Expense profile information.
required)
Dependencies FR-149
Priority Medium
Identifier FR-161
Title < Expense.Remove.Error>
104
removing the Expense.
Source User
Business Rule (if User will be informed by the system if there is an error in removing the Expense.
required)
Dependencies FR-160
Priority Medium
Identifier FR-162
Title < Expense.remove.unsuccessful>
Requirement User shall be informed by the system if the Expense is not removed successfully.
Source User
Rationale To let the user know about removing Expense.
required)
Dependencies FR-161
Priority Medium
Identifier FR-163
Title < Expense.remove.Successful>
Source User
Rationale To update the Expense list in the database of system.
required)
Dependencies FR-162
105
Priority Medium
4.8.4 Search Expense Profile

Identifier FR-164
Title < Expense.Search>
Requirement System shall display the profile of the specific Expense that User searches for.
Source User
Rationale To keep User and Expense interlinked.
required)
Dependencies FR-149
Priority Medium
Identifier FR-165
Title < Expense.Search.assigned>
Requirement System shall only display all those profiles of Expense that are assigned to the
User.
Source User
required)
Dependencies FR-164
Priority High
106
Identifier FR-166
Requirement The User shall be able to search his/her Expense’s profile by entering his/her
name in search bar.
Source User
required)
Dependencies FR-165
Priority High
Identifier FR-167
Title < Expense.Search.Error.invalid>
Requirement System shall display error message if the User searches for invalid Expense.
Source User
required)
Dependencies FR-166
Priority Medium
Identifier FR-168
Title < Expense.Search.Error.NotExist>
Requirement System shall display error message that the Expense does not exists.
Source User
required)
107
Dependencies FR-167
Priority Medium
4.8.5 View Expense
Identifier FR-169
Title < Expense.View>
Requirement User can see the profile of Expense.
Source User
Rationale To let the User access his/her Expense,to link them.
required)
Dependencies FR-149
Priority Medium
Identifier FR-170
Title < Expense.View.List>
Requirement System shall display a list of registered Expense to the User.
Source User
Rationale To keep and maintain the record of Expense.
required)
Dependencies FR-169
Priority Medium
108
Identifier FR-171
Requirement The User shall view the details of Expense through Expense profile by clicking
on it.
Source User
Rationale To keep the User aware of Expense profile.
required)
Dependencies FR-170
Priority Medium
4.9 Contacts
4..1 Add Contacts

Identifier FR-172
Title <Contacts.add>
Requirement System shall add the Contacts to the system.

Source User
Rationale User can add the Contacts of their vehicles to the system.
required)
Dependencies FR-1
Priority Medium
Identifier FR-173
Title < Contacts.add.details>
Requirement System shall only add Contacts when user fulfill all the details.
109
Source User
required)
Dependencies FR-172
Priority High
Identifier FR-174
Title < Contacts.Device.Error.>
details.
Source User
required)
Dependencies FR-173
Priority High
Identifier FR-175
Title < Contacts.Add.successful>
Requirement System shall display a message of successfully if the Contacts is added.
Source User
Rationale To help the User know that the Contacts is added.
required)
Dependencies FR-174
Priority Medium
110
4.9.2 Driver Contacts
Identifier FR-176
Title < Contacts.Edit>
Requirement User shall be able to edit the Contacts profile.
Source User
Rationale To allow User to update Contacts profile information.
required)
Dependencies FR-172
Priority Medium
Identifier FR-177
Title < Contacts.Edit.ViewInfo>
Source User
Rationale To modify Contacts’s profile information.
Business Rule (if User can edit Contacts, once registered.
required)
Dependencies FR-176
Priority Medium
Identifier FR-178
Title < Contacts.Edit.Update>
Source User
111
required)
Dependencies FR-177
Priority Medium
Identifier FR-179
Title < Contacts.Edit.SaveUpdate>
Source User
required)
Dependencies FR-178
Priority Medium
Identifier FR-180
Title < Contacts.Edit.Confirmation>
Source User
required)
Dependencies FR-179
Priority Medium
112
Identifier FR-181
Title < Contacts.Edit.Redirect>
Source User
required)
Dependencies FR-180
Priority Medium
Identifier FR-182
Title < Contacts.Edit.Refresh>
User.
Source User
required)
Dependencies FR-181
Priority Medium
4.9.3 Remove Contacts
Identifier FR-183
Title < Contacts.Remove >
Requirement User shall be able to remove the Contacts and add the new one.
Source User
Rationale To allow User to update Contacts profile information.
113
required)
Dependencies FR-172
Priority Medium
Identifier FR-184
Title < Contacts.Remove.Error>
removing the Contacts.
Source User
Business Rule (if User will be informed by the system if there is an error in removing the
required) Contacts.
Dependencies FR-183
Priority Medium
Identifier FR-185
Title < Contacts.remove.unsuccessful>
Requirement User shall be informed by the system if the Contacts is not removed
successfully.
Source User
Rationale To let the user know about removing Contacts.
required)
Dependencies FR-184
Priority Medium
114
Identifier FR-186
Title < Contacts.remove.Successful>
Source User
Rationale To update the Contacts list in the database of system.
required)
Dependencies FR-185
Priority Medium
4.9.4 Search Contacts Profile

Identifier FR-187
Title < Contacts.Search>
Requirement System shall display the profile of the specific Contacts that User searches for.
Source User
Rationale To keep User and Contacts interlinked.
required)
Dependencies FR-172
Priority Medium
Identifier FR-188
Title < Contacts.Search.assigned>
Requirement System shall only display all those profiles of Contacts that are assigned to the
User.
115
Source User
required)
Dependencies FR-187
Priority High
Identifier FR-189
Requirement The User shall be able to search his/her Contacts’s profile by entering his/her
name in search bar.
Source User
required)
Dependencies FR-188
Priority High
Identifier FR-190
Title < Contacts.Search.Error.invalid>
Requirement System shall display error message if the User searches for invalid Contacts.
Source User
required)
Dependencies FR-189
Priority Medium
116
Identifier FR-191
Title < Contacts.Search.Error.NotExist>
Requirement System shall display error message that the Contacts does not exists.
Source User
required)
Dependencies FR-190
Priority Medium
4.9.5 View Contacts

Identifier FR-192
Title < Contacts.View>
Requirement User can see the profile of Contacts.
Source User
Rationale To let the User access his/her Contacts,to link them.
required)
Dependencies FR-172
Priority Medium
Identifier FR-193
Title < Contacts.View.List>
Requirement System shall display a list of registered Contacts to the User.
Source User
117
Rationale To keep and maintain the record of Contacts.
required)
Dependencies FR-192
Priority Medium
Identifier FR-194
Requirement The User shall view the details of Contacts through Contacts profile by clicking
on it.
Source User
Rationale To keep the User aware of Contacts profile.
required)
Dependencies FR-193
Priority Medium
4.9.6 View Report

Identifier FR-195
Title < Report.view>
Requirement User can see the report.
Source User
Rationale To keep the User aware of all incidents.
required)
Dependencies FR-193
Priority Medium
118
Identifier FR-196
Title < Report.View.List>
Requirement System shall display a list of reports to the User.
Source User
Rationale To keep and view the reports.
required)
Dependencies FR-192
Priority Medium
4.9.7 Check History

Identifier FR-197
Title < History.Check>
Requirement User can check the history of activities.
Source User
Rationale To keep the User aware of all activities.
required)
Dependencies FR-193
Priority Medium

Identifier FR-198
Title < History.check.list>
Requirement System shall display a list of activities to the User.
Source User
Rationale To keep and view list of all activities.
required)
Dependencies FR-192
119
Priority Medium
4.9.8 Check Speed

Identifier FR-199
Title < Speed.Check>
Requirement User can check the speed of vehicles.
Source User
Rationale To keep the user aware of his speed.
required)
Dependencies FR-193
Priority Medium
4.9.9 Check Mileage

Identifier FR-200
Title < Mileage.Check>
Requirement User can check the Milelage of vehicles.
Source User
Rationale To keep the user aware of mileage of their vehicles.
required)
Dependencies FR-193
Priority Medium
120
5. Non-Functional Requirements
5.1 Availability
AVAIL-1: The system shall be available all the time i.e. 24/7.
5.2 Usability
USA-1: The system shall allow a user to retrieve the travel history with a single interaction. USA-2:
The system shall be easy to use and intuitive.
5.3 Performance
PER-1: 95% of webpages generated by the system shall download completely within 4 seconds from
the time the user requests the page over a 20 Mbps or faster Internet connection.
5.4 Security
SEC-1: The system shall prevent unauthorized access by assuring data of the user i.e. username and
password.
SEC-2: The system shall keep data of the users and drivers safe.
SEC-3: The user shall receive an email on the modification of profile.
5.5 Reliability
REL-1: The system shall be highly reliable, with a low failure rate and a fast recovery time (15 sec) in
the event of system failures or errors.
REL-2: The system shall be highly available 24/7.
5.6 Maintainability
MAIN-1: The system shall be easily maintainable, with well-organized and well-documented code.
MAIN-2: The system shall be updated, with clear and well-documented code.
5.7 Interoperability
INT-1: The system shall be interoperable, with the ability to integrate with other systems and services
using industry-standard protocols and APIs
121
6. External Interface Requirements
6.1Software interfaces
122
123
124
6.2Hardware Interfaces
HI-1.1: System shall use tracking devices to get gps data and send it to system.
HI-1.2: Tracking devices will use sim cards to fetch cellular data.
6.3Communications interfaces
CI- All types of web browsers are accepted by the system.

CI-System shall send notification message to the user, in case of any update.
7. References
Book
Author(s). Book title. Location: Publishing company, year, pp.
Example:
W.K. Chen. Linear Networks and Systems. Belmont, CA: Wadsworth, 1993, pp. 123-35.
Article in a Journal
Author(s). “Article title”. Journal title, vol., pp, date.
Example:
G. Pevere. “Infrared Nation.” The International Journal of Infrared Design, vol. 33, pp. 56-99, Jan. 1979.
Articles from Conference Proceedings (published) Author(s).

“Article title.” Conference proceedings, year, pp.
Example:
D.B. Payne and H.G. Gun hold. “Digital sundials and broadband technology,” in Proc. IOOC-ECOC, 1986, pp.
557-998.
World Wide Web

Author(s)*. “Title.” Internet: complete URL, date updated* [date accessed].
M. Duncan. “Engineering Concepts on Ice. Internet: www.iceengg.edu/staff.html, Oct. 25, 2000 [Nov. 29, 2003].
125

SRS Document

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

SRS Document

Uploaded by

Copyright:

Available Formats

COMSATS University Islamabad (CUI)

Software Requirement Specification

AREEBA AKBAR CIIT/SP20-BSE-012/ISB

Bachelor of Science in Computer Science (2020-2024)

Application Evaluation History

1.3.1 Account management:

1.3.2 Driver Management:

1.3.3 Vehicles Management:

1.3.4 Devices Configuration:

1.3.5 Expense Management:

FE-1: User can check the date of expense.

1.3.6 History Management:

FE-1: Historical Data of speed.

1.3.7 Journey Management:

1.3.8 Geofence Management:

1.3.9 Alerts and notifications:

FE-1: User can choose the type of alerts he wants.

1.3.10 Driver License Management:

FE-1: Shows profile of driver.

1.3.11 Vehicles Maintenance:

FE-1: User can maintain their vehicle.

2.2 User classes and characteristics

Table 1: User classes and characteristics

2.3 Operating Environment

2.4 Design and Implementation Constraints

3.1.1 User Use Case Diagram

3.2.1 User Profile

Table 2: Description for register user

Preconditions: PRE-1: User has active internet connection. PRE-2:

Post Conditions: POST-1: User information will be verified.

Normal Flow: 1. User enters name.

Table 3: Description for login user

Post Conditions: POST-1: User logs into the system successfully.

Normal Flow: 1. User enters the email/username and password.

Table 4: Description for edit user profile

Normal Flow: 1. User enters the username and password.

Table 5: Description for add driver

Post Conditions: POST-1: Driver will be added.

Table 6: Description for delete driver

Table 7: Description for edit driver

Table 8: Description for add geofence

Post Conditions: POST-1: Geofence will be added.

Table 9: Description for edit geofence

Post Conditions: POST-1: new boundary limits will be set.

Table 10: Description for delete geofence

Post Conditions: POST-1: User will not receive the alert.

Table 11: Description for View geofence

Post Conditions: POST-1: Graphical view of Geofence will be displayed.

2. User will click on Geofence management.

Table 12: Description of Add expense

Post Conditions: POST-1: Expense can be added.

Alternate Flow: None

Table 13: Description of Delete expense

Post Conditions: POST-1: Expense will be removed.

2. User will click on Expenses management.

Table 14: Description of View expense

Trigger: Users click on expense management.

Post Conditions: POST-1: Expense can be viewed.

Table 15: Description of add logins

Post Conditions: POST-1: different logins can be added.

2. User will click on Login management.

Table 16: Description of remove logins

2. User will click on Login management.

Table 17: Description of edit logins.