CIS Vehicle Transaction Actions

System Requirements Specification

Road & Transport Authority

Information Technology Department
 Statement of Confidentiality

All information presented in this document or shared with the addressee, as part of the proposing
process is considered strictly confidential. As such, the addressee should not disclose this document
or any attachments in whole, or in part to any third party without the prior written consent of Roads
and Transport Authority (RTA).

The addressee also acknowledges that information shared here within is the intellectual property of
Roads and Transport Authority and is subject to a disclosure agreement as recognized by the
copyright and intellectual property protection regulations.

RTA System Requirements Specification CIS Vehicle Transaction Actions Page 2 of 10

 Document Control Sheet

Document Information
Document Title: CIS Vehicle Test - Transactions Follow up - SRS
Owner: RTA
Document Reference: SRS – CIS

Revision History
Version Date Description of Change Author
0.2 2015/9/9. First publication of this SRS Maie Rashad

-
-
-
-

Approval History
Version Date Person Role Comments
1.0
1.0
1.0

RTA System Requirements Specification CIS Vehicle Transaction Actions Page 3 of 10

 Table of Contents
1 Introduction 5
1.1 Purpose 5
1.2 Scope 5
1.3 Definitions, Acronyms and Abbreviations 5
1.4 References 5

2 Use Case Model 6

2.1 Use Case Diagram 6
2.2 Use Case Model Overview 6

3 Use Case Specification 6

3.1.1 Transactions summary 6

4 Logical Data Model 10

RTA System Requirements Specification CIS Vehicle Transaction Actions Page 4 of 10

 1 Introduction
The Centralized Inspection System (CIS) consolidates under RTA's, central authority all vehicle inspection
activities in Dubai. CIS aims at centralizing consistent management practices, cohesive policies, guidance, and
processes for vehicle inspection service provision. Vehicle Transaction actions is a module that enables various
managers and supervisors to review transaction actions, cancel the transaction or re-print the token.

1.1 Purpose
This document captures the available Vehicle Transaction Actions system requirements - It describes system-
actor interaction in terms of basic and alternate flows, and it describes system rules, the user experience, and
the logical data model related to Transaction Actions.

1.2 Scope
The scope of this document is to capture the system requirements for Vehicle Transaction Actions.

1.3 Definitions, Acronyms and Abbreviations

This is a list of definitions, acronyms and abbreviations to aid readers of this document.
See CIS Glossary in References.

1.4 References
References to the following documents were made in defining the system requirements:
• Vehicle Inspection Management System (VIMS) – CIS System Requirements Specification.
• CIS Glossary.
• CIS Actor Catalog.
• CIS Business Domain Model.

RTA System Requirements Specification CIS Vehicle Transaction Actions Page 5 of 10

 [CIS-3575]

2 Use Case Model

This section presents a UML model that depicts CIS system boundaries and identifies Actors and their use cases
within scope of Vehicle Transaction Actions.

2.1 Use Case Diagram

CIS Vehicle Transaction Actions use case model.

2.2 Use Case Model Overview

The above use-case model represents the use-cases, actor, and use-case-actor associations used to describe CIS
within Vehicle Transaction Actions scope. This use case will be used in exactly the same way by: VTP Admin,
VTC Site Manager, VTC Supervisor, VTP Inspector. RTA Admin will have a different interaction with the system.

3 Use Case Specification

The following use cases describe Vehicle Transaction Actions functionality

3.1.1 Transactions summary

Use Case ID UC3.1.1

Use Case Name Search Transactions Summary
Business Activity
Use Case Description A n authorized user searches for the transaction status of a vehicle in all the

RTA System Requirements Specification CIS Vehicle Transaction Actions Page 6 of 10

 steps, even before results generation
Primary Actor RTA Admin, VTP Admin, VTC Site Manager, VTC Supervisor, VTP Inspector
Actor Goal Find available vehicle transaction actions details
Triggering Event The actor initiates the search
Secondary Actors None
CIS successfully authenticated the user.
Pre-conditions
User role is authorized in CIS to initiate use-case scenarios.
Post-conditions List of records found displayed with link to details
Extends None.
Includes None.
Priority/Criticality Medium
Frequency of Use Low.
1. System should not allow a VTP User to search for transaction not done under
his VTP or the other VTPs his VTP had access on.
2. System should not allow user to cancel a service result which is a part of a
test transaction record (only allow cancel the whole transaction record)
3. System should not allow user to enter more than 30 days date range in the
created by search field criteria if user entered only any of the following
search criteria
a. Service name
b. Partner Name
c. VTC Name
d. Date Range
4. System should mandate entering the full plate details in order to be able to
System Rules
search using the vehicle plate details.
5. At least one search criteria must be entered in order to perform the search
action.
6. System should not allow cancelling a transaction if the cancellation reason is
not entered.
7. System should allow canceling a non-paid transaction.
8. System should allow cancelling a transaction canceled or paid transactions
9. System shall not enable booth operator to reprint token unless it has been
generated before
10. System should not allow reprinting the token if the vehicle is not dispatched.
11. System shouldn’t allow the user to reprint token for a cancelled or paid
transaction
Special Requirements /
None.
Constraints
1. User clicks “Transaction Summary” from expandable side menu appears
when mouse hover on “Test Information” , or from “Test Information” page
user clicks the acquired icon
2. System to open the search page defaulted with the current system date
transactions for the current VTC
3. User to search for the transactions by providing one or more of the following
Basic Flow
info (Table 4.1):
 Chassis number
 Plate details
o Plate Source (default value = “Dubai”)
o Plate Category
o Plate code

RTA System Requirements Specification CIS Vehicle Transaction Actions Page 7 of 10

 o Plate Number
 Token number
 VTP (mandatory)
o If the user type is RTA, display the list for the user to select a
VTP.
o Else if the user type is VTP, display the partner name as
disabled for the logged in user VTP name.
o Other user types hide the VTP selection field.
 VTC (mandatory)
o If the user type is RTA, display the full list for the user to select
a VTC filtered according to the selected VTP above.
o Else if the user type is VTP, display the list of VTCs filtered
according to the logged in user VTP name.
 Test Transaction Number
 Date (date range (configurable , Max 30 days), default by current
system date)
4. If user entered any of the following search criteria, system should not
validate on the date range selected even if not entered at all.
 Test Transaction Number
 Chassis Number
 Plate Details
o Plate Source
o Plate Category
o Plate Code
o Plate Number
5. If user entered only any of the following search criteria, system should
mandate user to enter the date range and system should not allow user to
enter a date range greater than 30 days
 Partner Name
 VTC Name
6. If the user entered “Token number” as search criteria, system should
mandate the user to enter:
 VTP name
 VTC name
 Date (user should select a specific date and not allow the user to enter a
date range.
7. System displays the search result as following:
a. One record per vehicle test transaction along with the services
under this transaction as a collapsible list.
b. Transaction record to contain the following columns:
 Test Transaction Number
 Chassis number
 Plate Details
 VTP
 VTC
 transaction Date and time
 Status (all transaction status)
 Cancel transaction button (appears for all transaction status
except canceled or paid transactions)
 View Details button

RTA System Requirements Specification CIS Vehicle Transaction Actions Page 8 of 10

  re-print Token button (appear if the transaction status not
equal under inspection, or in queue, or inspection completed,
or Canceled, or paid)
 “View Transaction Flow” Button to open a pop up with all
action records linked to this transaction.
c. Transaction Actions record to contain the following columns:
 User
 User role
 Action name
 Date/time

5.1 Cancel Test transaction

1. Granted User selects to cancel a test transaction record for a specific
vehicle.
2. System to display a mandatory text field for the user to enter the
cancelation reason.
3. User enters the cancelation reason and confirm.
4. System to update the transaction status as cancelled.
5. System to hide action buttons; Cancel Transaction and Reprint Token
6. System logs cancelation action:
a. Action type: cancel transaction
b. User
c. User role
d. date/time

5.2 View Details

1. User selects to view transaction details
2. System expands the transaction record to display the services records
Alternative Flows linked to this transaction, for each service record system display
 Service Name
 Attempt Number
 Service Fees

5.3 Reprint Token

3. User selects to reprint a token
4. System display a mandatory text field for the user to enter the reprint
reason
5. User enter the reprint reason and confirm
6. System to print the token and log the transaction details.

5.4 No matches found

 CIS displays “no transactions found with the entered criteria” message.

5.5 One transaction only retrieved in the search result

 System to automatically expand the retrieved transaction services
Exceptions
Events None.
Assumptions

RTA System Requirements Specification CIS Vehicle Transaction Actions Page 9 of 10

 4 Logical Data Model
Logical Data Model and business domain model are described in other documents,

Table 4.1

ID Entity Name Attributes Comment

Search Test transaction No
1 Params Chassis Number Text box, 21 digits
Plate Source
Plate Code
Plate Number
Plate Category
Service Name
Token Number
Test Partner Mandatory
Test Centre Mandatory
Test date time from
Test date time to

RTA System Requirements Specification CIS Vehicle Transaction Actions Page 10 of 10