03 NS Ia SRS V1.0

Software Requirement Specification
Project: Interconnection Agreement

Version no. 1.0
Document Control Sheet
Current Version 1.0
Project Code NS_InterconnectionAgreement_04102021
Project Name Development of Interconnection agreement
Document Type SRS Document
Author Nakul
Reviewed By Amol
Frequency of Document Review Next Revision of Standards Documents
Document Creation Date 08/11/2021
Revision History
Version Date Name Comments
1.0 08/11/2021 Nakul SRS Document.

1. Purpose of this Document
This document specifies the functional specifications for the Development of Interconnection
agreement that needs to be developed. The document helps the business stakeholders to
understand what to expect out of the project & technical stakeholders to understand what to
deliver.
The Functional Requirements Specification will:
- Define the scope of business objectives, business functions and organizational units
covered for the project
- Identify the business processes that the solution must facilitate
- Facilitate a common understanding of what the functional requirements are for all
parties involved in the project
- Establish a basis for defining the acceptance tests for the solution to confirm that what
is delivered meets requirements.
Summary
Client (CITC) wants to design and develop a web application for Interconnection agreement
where CITC internal users will be accessing the proposed platform Examiner user, wholesale
manager & department user, and on the other side operator users are service provider admin
and service provider user. Service provider users (operators) will be able to upload an
agreement against the raised request or upload any new agreement request from their side.
CITC wholesale manager will act as an admin on the proposed system where wholesale
manager will be able to manage the service provider admin and Examiner user along with the
roles and permissions. And service provider admin will be able to manage the service provide
users.
CITC users-
Examiner User: These types of users will be created by the wholesale interconnection manager
(super admin), and can log in through valid login credentials. The examiner will be able to raise
an agreement upload request to the operator once it's been asked by the wholesale manager.
They will be able to receive the newly assigned agreement request for review and can take the
necessary action (Save, reject or cancel). Furthermore, they will be able to ask for amendment
(amend on data or amend on agreement) and receive the updated agreement (form or
agreement) from the operators. The examiner will also be able to view the saved listing where
all the agreements will be displayed for which outcome has been determined.
Wholesale Interconnection manager- This type of user can log in to the proposed system
through valid credentials. The wholesale manager (super admin) will be able to view and
manage Examiner user and service provider admin. Admin can view all the new agreement
requests, raise agreement upload request, assign examiner to raise agreement request,
Agreements under review, pending agreement requests, saved agreement request, manage
department users, inbox, keyword and advance search, re-allocation of the agreement request,
reports, timeline configurable, my account and manage content.
External users-
Service provider admin- These types of users will be created by the super admin and can log in
through valid login credentials. The service provider admin will be able to create service
provider users and can manage the permissions. The service provider admin will be able to view
all the agreements uploaded by him and service provider users. They will be able to view
received agreement upload requests from the wholesale manager and Examiner. They will be
able to upload an agreement from their panel and can ask the operator user to upload an
agreement against the raised request.
Service provider users- These types of users will be created by the service provider admin and
can log in through valid credentials. The service provider user will be able to receive the
agreement upload requests from the service provider admin and can upload an agreement
from their panel. They will be able to view ongoing/under review agreement from their side
and can receive the amendment request from the examiner or wholesale manager against it.
Once the upload agreement is saved/rejected/canceled, it can be viewed in the saved
agreement listing.
2. Scope of the Functional Requirement specifications
Entities Features Interaction mode
 Login
 Forgot password
 View Profile
 Keyword search (Predictive) and advance
search
 Agreement request (from CITC)
 Agreement upload request (to SP user)
Service provider admin  Upload agreement
 Agreements under review
 Logs
 Manage service provider user
 Manage roles & permissions
 Saved agreements Web application
 Inbox
 Reports
 Login
 Forgot password
 View Profile
 Keyword search (Predictive) and advance
search
 Agreement request (from service provider
Service provider user admin)
 Upload agreement
 Logs
Web application
 Saved agreements
 Inbox
 Reports
Examiner user  Login
 Forgot password
 Raise agreement upload request
o Make a decision on an application
o Request agreement upload (one's
assigned by WIM)
o Raising violation
o Ask from manager to raise for
inquiry (inquiries and sharing)
 Inbox
Web application
 Reports
 Advance search
 My profile
 Reports
 Login
 Forgot password
 Manage all entities
o Examiner user
o Service provider admin
 Manage department user
 Raise agreement upload request
 Assign examiner to raise request
 New agreement requests
o Raising violation
Web application
Wholesale manager user o Sharing with other departments
(inquiries and sharing)
 Pending requests
 Inbox
 Re-allocate the agreement request
 Reports
 Timeline configurable
 Manage content
 Manage profiles
 Login
 Forgot password
 New inquires
o Details of inquires Web Application
Department user o Provide comments
 Previous inquires
o Details of inquires
 My profile
3. Target Platforms for User type
User types Target platform End user capacity
Web based Portal As per user assigned role

Agreement Examiner
Wholesale Manager Web based Portal Unlimited

(Super Admin)
Service provider Web based Portal Unlimited

Admin (Operator)
Service provider User Web based Portal As per user assigned role
(Operator)
Web based Portal As per user assigned role

Department user
4. Wireframe Links for Interconnection agreement:
 Service provider admin: https://o1ulnt.axshare.com

 Service provider user : https://5m15cf.axshare.com
 Examiner:
 Wholesale interconnection Manager: https://a6wmqu.axshare.com
5. Functional requirement:
5.1. Introduction page
Actors Visitor user

Requirement Definition The use case will allow visitor users to view the informational content
and option to access the platform.
Pre - Condition 1. Users should be on existing CITC website and clicked on
interconnection agreement.
2. There should be proper internet connectivity.
Post - Condition Users will be able to view the information content on the page along
with option to login.
Business Rules / Logic
Whenever user clicks on interconnection agreement in the existing

CITC website, they will be re-directed to this page where they will be
able to view below details.
 Introduction page
o Header
 Logo and name
o Menu
o Keyword search and advance search
o Service provider login
 Service provider admin (refer to UC_5.2)
 Service provider user (refer to UC_6.2)
o Examiner user (refer to UC_7.2)
o Change theme (color and design scheme will be changed on
click)
o Informational content
o Switch Language: English(Default), and Arabic
o Footer
 FAQs
 Privacy policy
 Description-
 A static page will be created and provided to CITC (so that they can
integrate with CITC exiting website) where users can view
information content about Interconnection agreement. Moreover,
there should a button named Access Interconnection agreement
and on click of it users will be redirected to this page.
 Visitor users will be able to login based on their role such as
internal users (Examiner) and Service provider side users (Service
Provider Admin, and service provider user).
 FAQs: User will be redirected to “FAQs” page where user can read
the info related to application.
 Privacy Policy: User will be redirected to “Privacy policy” page
where user can read the info related to application.
5 Service provider Admin (Operator)

5.1 New user accessing Interconnection agreement
Actors Visitor user
Requirement Definition This use case is used to define the process to access the
Pre - Condition 1. The user account should be created by the super admin.
2. The user should have proper internet connectivity.
Post - Condition Users should be able to view the process to access the
Service provider admin will be created by the super admin, and login
credentials will be shared over registered email.
The received credentials would be following:

 Email ID
 Mobile number
 Dummy password
 URL to access
On click of URL they will be asked to enter the email ID, mobile
number, dummy password and captcha. Hereafter, users will receive
an OTP on their registered mobile number (for validation).
Moreover, users will be asked to change the password where below

fields will be shown:
 Enter old password

 New password
 Confirm password
 Submit>>
Now users will be able to login on the proposed system. (refer to

UC_5.2)
Third-party services  SMS (TBD)

 Email (TBD)
Fields and Validation Validation:
1. Once new user created they should receive an email over
registered email ID.
2. Users should enter valid email ID.
3. Users should enter valid mobile number.
4. Users should enter dummy password.
5. Users should be able to enter the captcha. And captcha should
be matched with the shown image.
6. Users have to enter the valid OTP which they will receive on
their registered mobile number.
7. Users should be able to change their dummy password.
8. Below are the types of licenses for which Service providers will
raise the agreement on the platform:
a. Provide Facilities-Based Fixed Telecommunication
Services
b. Facilities-Based Unified Telecommunication Services
License
c. Provide telecommunication facilities leasing service
(CSP)
d. License Mobile Virtual Network Operator (MVNO)
services
e. Provide wholesale infrastructure services
f. Provide Internet of Things Virtual Network Operator
(IoT-VNO) services
g. And other if required in the future.
Email ID Text Field (should accept alphanumeric
with max limit of 40-50 chars)
mandatory
Dummy Password Text Field (should accept alphanumeric
mandatory
Mobile number Text Field (should accept numeric values
with max 10-12 digits) mandatory
Enter captcha Text field (should be same as shown
picture)
Login Button
OTP Text field (should accept numeric with

max limit of 8-10 digits) mandatory
Change password
Old password Text field (Should match with dummy

password ) Mandatory
New password Text Field (should accept alphanumeric
mandatory
Confirm password It should match the entered password
5.2 Login page
Actors Service provider admin
Requirement Definition This use case is used to define the Login process for the Visitor users
Pre - Condition 1. The user should already have an account with the platform to log
in.
Post - Condition When user enters valid login credentials they should be able to
access the proposed system.
Whenever user clicks on the Login button, they will be asked to
enter their registered mobile number and enter the received OTP.
For general login through Mobile – Users can enter their
1. Mobile number
2. OTP
3. Enter captcha
4. Submit>>
5. Forgot password
On click of submit button, the system will look a match in their

respective DB and if the match is found they will be logged in as
registered user. If no match is found, users can either try again with
their credentials or they can use forgot password flow.
Password expiry- user password will be auto expiry after 90 days

and the system will force to change the password.
Third-party services  SMS (third-party service TBD)

1. Registered mobile number must be relevant and matched with
the interconnection agreement database.
2. OTP must be correct.
3. In case of incorrect the system will show a message that “you
have entered incorrect OTP”
4. Mobile number field must be filled.
5. OTP field must be filled.
7. If an invalid mobile number is entered then the web portal shall
notify the user that mobile number is incorrect.
8. There will be a two factor authentication where users can login
through mobile and OTP.
Mobile number Text field, (Mandatory, and allow

numeric digits only)
OTP Text field, (Mandatory, and allow
Login Button
Forgot password? Button

picture)
5.3 Forgot password?
Requirement Definition This use case is used to define forgot password flow for the Visitor
user.
Pre - Condition 1. User should be on the Login Page
2. User should already have an account with the platform.
3. Proper Internet connectivity should be there.
Post - Condition Users should be able to reset their password.

This use case starts when the registered user clicks on the “Forgot
Password” button.
Once they will click on forgot password button, they will be asked to
enter their registered email ID and click submit. The system will look
for a match in the database and if a match is found, they will be
displayed a message that a reset password link has been successfully
shared on your registered email id, please use the link to generate a
new password.
When a user clicks on the link from their email, they will be asked to
enter a password and confirm the password in 2 different fields. All
validations will be the same as used while registration. Once they set
their new password, redirect them to the login page directly.
In case the entered email id does not match with the DB, then they
will be shown a message to check the entered email id or register
with us first.

1. If the user does not enters email ID and clicks on “send email”
button it must show that “please write the email ID”
2. If the user enters invalid email and clicks on “send email” button
it must show that “wrong email ID”
3. If the user enters an email that does not correspond with the
Interconnection agreement database the website shall notify the
user with the text, “Record not found.”
4. If the user enters a valid email and selects “Send Email” the
website shall notify the user with the text “Please check your
email.” below the “Send Email” button.
Enter registered email ID Text field
Submit Button
5.4 Home Page
Actors Service provider Admin

Requirement Definition Users will be re-directed to the home page of the web application and view
available elements.
Pre - Condition 1. User should be logged-in on the existing CITC platform and clicked on
Interconnection agreement.
Post - Condition User will be able to view all the available functionality on the platform.
Whenever user successfully logged-in on the platform they will be

navigated to this page where below details will be displayed.
 Landing page/Home page

o Header
 Logo and name
o Tiles
 Agreement request
 Agreement request (from CITC)
 Agreement upload request (to SP user)
 Upload agreement
 Agreements under review
 User management
 Saved agreements
 Inbox
 Reports
 My profile
 Advance search
o Content zoom twice (in/out)
click)
o Footer
 FAQs
 Privacy policy
 Description-
 On the home page, users will be able to view above details.

 On click of any tile, users will be redirected to the particular page
where they can view details about respective sections.
 Agreement request- Users will be able to view two tiles in
agreement request i.e. Agreement upload (to SP user) and
Agreement upload request from CITC (refer to UC_5.5)
 Agreement upload request- Users will be able to send the upload
agreement request to the service provider user. (refer to UC_5.7)
 Upload agreement- Users will be able to upload an agreement on
the platform. (Refer to UC_5.8)
 Agreements under review - Service provider admin will be able to
view list of submitted requests (Uploaded) by different service
provider Users. (refer to UC_5.9)
 Manage service provider user- Users will be able to manage
(create/edit/delete) operator user from this section.
 Manage permissions- Users will be able to manage
(view/write/modify) the user (service provider user) permission.
 Inbox- All reminders for an application (based on timeline / SLA)
will be sent to the respective users through the inbox
feature. (refer to UC_5.19)
 Saved agreements- Users will be able to view all the agreement
there outcome has been determined (cancelled, rejected and
withdrawn) and saved agreement just by clicking on tabs. (Refer to
UC_5.13)
 Reports- Different types of reports will be displayed in this section.
Fields and Validation  On click of above tiles users should be re-directed to the respective
page. Example- on click of Agreements under review, users will be re-
directed to the listing page.
 On click of zoom in/out icon, users will be zoom in twice 125% and
150% from neutral/default 100% of the page and in zoom out 75%
and 50%.
 On click of profile icon, users will be re-directed to the account
page.
 On click of dark and bright mode, users will be able to switch the
color mode of the website.
 The default language would be English however, users will be able
to switch to Arabic language.
 Users will be able to view advance search on the home page,
whenever users click on it an advance search pop-up will
appear (Refer to UC_5.17) and in this search, users will be able to
find both types of agreement together (open and closed).
5.5 Agreement requests (List view)
Requirement Definition Users will be able to view the agreement request sent by examiner
or wholesale manager.
Pre - Condition 1. Users should be successfully logged-in on the Interconnection
agreement.
2. Users should be clicked on agreement request on home page.
Post - Condition Users should be able to view the list of agreement requests.
Business Rules / Logic This use case will start when user clicks on agreement requests,
hence they will be able to view two tiles i.e. Agreement upload
request (to SP user) (refer to UC_5.7) and Agreement Requests from
CITC.
In agreement request from CITC, users can view list of raised request
from CITC (by examiner and WSIM) and below listing will be shown:
o Request ID
o Name of agreement
o Date of signing the agreement
o Agreement Due date
o Request date
o Parties of agreement
o Request type
 New request
 Modification request
o Action
 View details (refer to UC_5.6)
 Assign to service provider user (Pop-up)
 On click of view details, users will be re-directed to the detail

page where all the information will be shown.
Users will be able to filter out the agreement by selecting/entering

the parameters in listing. Following parameters would be there
 Keyword search to enter the request ID
 Keyword search to enter the name of the agreement
 Sorting for newest and oldest for date of signing the agreements
 Sorting for newest and oldest for agreement due date
 Sorting for newest and oldest for request date
Also, users can view keyword search option where they can
manually enter the agreement related keyword and get the desired
outcome.
Process:
 On click of agreement request tile, users will be re-directed to
the listing page where all the newly received agreement request
and modification request will be shown.
page of a selected agreement (refer to UC_5.6)
 All the modification request raised by the CITC on saved
agreement will be sent only to service provider admin. Then, he
will assign SP user or update by their own.
 On click of assign service provider user, a pop-up will appear
where users can select the service provider user, add comment,
upload document (if any) and submit.
o On click of submit, the request will be sent to the service
provider user.
 Users will be able to view Keyword search as mentioned above
to get the desired result.
 Searches/filters will be shown in the listing parameters.
Fields and Validation:

Validation  Operator can view the received agreement request from the
examiner or wholesale manager.
 Amendment raise by the examiner in the ongoing agreement will
be sent to the operator user only. However, Modification
initiated by CITC i.e. modification post an agreement was saved
once will be first sent to SP admin, who will the assign it to a SP
user.
 Nomenclature of the request Number shall be decided at the
time of development to help in tracking as well.
 The system sends notification and email to service provider at
the beginning of each day till the deadline to upload the
agreement once request is raised.
o This is a reminder that CITC must be provided with (Name
of agreement) noting that in case of failing to provide the
required agreement within (number of days changes
based on remaining period) days from today, regulatory
procedures will be taken.
 After the deadline, the system sends notification and email to
service provider stating that-
o Kindly be informed that the deadline set for providing
CITC with the agreement has expired, noting that CITC
will take necessary procedures against entities that failed
to provide CITC with the requirements within the set
deadline.
 The timeline allowed for uploading the agreement is 10 days
configurable (Default timeline is 10 days).
 All the modification request raised by the CITC on saved
agreement will be sent only to service provider admin. Then, he
will assign SP user or update by their own.
View detail Button

Assign service provider A pop-up will appear
user
Select service provider Dropdown (mandatory, single selection)
user
Add comment Text box, Mandatory, (Allow
alphanumeric with word limit 800 char)
Upload document PDF, Word, optional (size limit 20 MB)
Submit Button
Wireframes:
5.6 Agreement request details
Requirement Definition Users will be able to view the agreement request details raised by
the examiner or wholesale manager.
agreement.
2. Users should be clicked view detail in agreement requests.
Post - Condition Users should be able to view the raised agreement request details.
Business Rules / Logic This use case will start when user clicks on view detail in agreement
requests, hence they will be able to view the details of the specific
agreement request and below details will be displayed.
 Details
o Request ID
o Name of agreement
o Request date
o Request type
 New request
o Attachment & Annexes
 Upload pdf files
o Added comment (by examiner or wholesale manager)
o Action
 Assign service provider user
Process:
 Users will be able to view the details of requested upload
agreement and can take upload the agreement.
 On click of upload agreement, users will be re-directed to the
upload agreement page. (Refer to UC_5.7)
 Users will be able to assign service provider users to upload an
agreement against the raise agreement.
 On click of assign service provider user, a pop-up will appear
where users can select the service provider user, add comment,
upload document (if any) and submit.
o On click of submit, the request will be sent to the service
provider user.
Request Type:
 New- When new agreement upload request sent by the
examiner or wholesale interconnection manager.
 Amend on data- when examiner user raises the amendment
request on (data) the particular agreement which operator has
uploaded in past.
 Amend on agreement- when examiner user raises the
amendment request on (agreement itself) the particular
agreement which operator has uploaded in past.

 Operator can submit the agreement on its own or CITC can
request the operator to submit the agreement.
 Operator should have upload an agreement to view that in
above listing.
 Users should be able to view all the attachments uploaded
against a particular agreement. Also, CITC uploaded files should
be highlighted in different colour/format so that it will be earlier
for them to understand.
Assign SP user
Select SP user Dropdown (mandatory), single selection
option
Add comment Text box, Mandatory, (Allow
Submit Button
Upload agreement Button
5.7 Agreement upload requests (to SP user)
Requirement Definition Users will be able to send the agreement upload request to the
service provider user.
agreement.
2. Users should be clicked on agreement upload requests.
Post - Condition Users should be able to fill-up the form and send the agreement
request.
Business Rules / Logic On click of agreement upload request (to SP user) tile, users will be
re-directed to this page where they can view list of agreement
request raised by the SP admin to SP user and following information
will be shown.
 Agreement upload requests (To SP user)

o Request ID
o Name of agreement
o Service provide user
o Date of signing
o Request type
 Modification
 New request
o Status
 Assigned
o Action
 View
 In details, users can view added comment and
uploaded document along with above
attributes.
 Cancel
SP admin can cancel the assigned request hence SP user won’t be
able to take further actions.
Also, users can view a button named “raise agreement request” and
on click, users will get a pop-up where assign SP user form will be
shown to enter below information.
 Select SP user
 Name of agreement
 Date of signing
 Add comment
 Upload document
 Submit>>
 On click of submit, the request will be sent to the SP user to
upload an agreement from their side.
Description:
 Users will be able to view the list of agreement request raised by
the operator admin.
 Users will be able to view the button to raise agreement request
to operator user and on clicking, a pop-up will appear to enter
above details and submit.
 Users will be able to view above form and can enter the
necessary details.
 On click of submit, agreement request will be sent to the specific
service provider user.
 Service provider admin will be able to raise agreement request in
agreement under review listing by entering the request ID.
 Assigned operator user will receive the upload agreement
request. (refer to UC_6.5)
Fields and  Users can also view the assigned modification request to
Validation operator user in this listing. And once operator user raise the
modification will be visible in agreement under review listing.
Select service provider Dropdown, (mandatory) single selection

Date of signing Georgian calendar (mandatory)
Name of the agreement Text field to enter keyword (mandatory),
20-25 alphanumeric char
Comment Text box, Mandatory, (Allow
Submit Button
5.8 Agreement upload
Requirement Definition Users will be able to view the option to upload an agreement
requests.
agreement.
2. Users should be clicked on upload agreement on home page.
Post - Condition Users should be able to view the option to upload an agreement.
Business Rules / Logic This use case will start when user clicks on agreement upload
requests. Therefore, they will be able to view the list of drafted
agreements and below details will be shown.
o Request ID
o Type of agreement
o Parties to the agreement
o Date of signing
o Submission date
o Name of agreement
o Status
 Draft
o Action
 Remove
 View
 On click of remove, an agreement that’s in drafted stage will be

removed from the list.
 On click of view, they will be re-directed to the detail page where
drafted details will be shown to them along with the option to
remove, edit and submit.
 Users will be able to view the upload agreement button on the
listing page and on click of it agreement form will open-up.
On click of upload agreement, a pop-up will appear where users can

fill-up the form and submit.
o Name of agreement
o Date of singing
o Submission date
o Agreement termination
 Date of termination
 Renewed agreement
 Other (checkbox)
o Type of license
o Other (The field is displayed when user selects “Other”
from “Parties of agreement” List)
o Involved or affected parties
o Type of agreement
from “Type of agreement” List)
o Type of service
from “type of services” List)
o Currency list
from “Currency” List)
o Fees (repetition based on the need of requester)
 Fees description
 Fees values
 Fees currency
 Upload pdf file
o Add note/comment
o Submit>>
 On click of submit, agreement form will be submitted to the

wholesale and interconnection services.
Process:
 On click of upload agreement, users will be re-directed to this
page where they can view the agreement form.
 They should be able to upload different type of agreement from
this section.
 On click of submit, the agreement request will be submitted to
the CITC (wholesale manager).
 Users won’t be able to make the amendment/delete after the
submission of the agreement. Unless it will be asked from the
CITC.
 Once agreement is uploaded, it should be removed from this
page and can be viewed in agreement under review page.

 Agreements will be uploaded by service provider within 10 days
from signing the agreement, where it reviewed by CITC
Wholesale and Interconnection Services and appropriate
decision is made.
 Post submission of the agreement, users won’t be able to make
the changes unless it’ll be asked from the CITC.
 The system must save name of requester (operator), date and
time of submission
 Request status upon submission will be (Under Review).
 Users should be able to add a comment and this comment could
be written in Alphabetic format with a 1000 character limit.
 In case without entering comment users click on submit then
system should display a message that “please add the
comment”.
 Also, users can upload additional documents and these
documents will be shown when the outcome is determined
(saved/rejected/amendment) in the saved agreement and
Agreements under review. Moreover, all these documents' names,
sent by, date, and time will be in approval logs during the
approval process.
 On click of submit, a pop-up will be shown to the users stating
“are you sure you want to submit?” “yes or no”
 Post submission, wholesale manager will receive an email about
the new agreement upload.
 The file cannot be amended/deleted after submission. It can only
be edited when it’s been asked by the examiner or wholesale
manager.
 Once all the fields are entered of the agreement, the system
should identify if similar kind of agreement uploaded earlier so
that users can raise change/modification request. Hence, a
warning/alert will be shown to them.
 In case no similar agreement found then they should continue
with the existing agreement.
 In case any mandatory fields are not filled then the system
should throw the error.
 Services will be shown based on the selection of license as they
are associated with specific licenses. For example if operator
selects ABC license then while selecting services they can view all
the associated services with that license and can select multiple
or one of them.

View agreement button
Remove Button
Date of signing Gregorian calendar (Mandatory)
Date of termination Check box (Gregorian calendar) Only one
field can be selected
Renewed agreement
Checkbox, for other (text)
Other -In case of selecting “Date of
termination”, the user must define the
date
Type of license Dropdown List, Mandatory
Parties of agreement -Multiple choices (Mandatory)
-The list is filtered based on type of
license
-User can search inside the list
Other Text, (Mandatory) The field is displayed
when user selects “Other” from “Parties
of agreement” List
Involved or affected Text, optional
parties
Type of agreement Dropdown list, (Mandatory) The list:
-New
-Amended
when user selects “Other” from “Type of
agreement” List
Type of service Dropdown list, (Mandatory)
-Multiple choices
service” List
Currency Dropdown list, (Mandatory) The list:
-SAR
-USD
-Other (insert text)
when user selects “Other” from
“Currency” List
Fees description Text, (mandatory)
Fees value Number (mandatory)
Fees currency Text (mandatory)
Upload attachment PDF format (mandatory) (size limit 20
MB)
Upload Annexes PDF format (optional) (size limit 20 MB)
Submit Button
5.9 Agreements under review (List view)
Requirement Definition Users will be able to view all the ongoing agreement.

agreement.
2. Users should be clicked on Agreements under review
Post - Condition Users should be able to view the list of Agreements under review or
ongoing agreements.
Business Rules / Logic In this use case users will be able to view list of ongoing agreements
requests created by them, or service provider user and following list
view will be displayed.
o Request ID
o Name of agreement
o Submission date
o Type of agreement
o Request type
 New request
o Status
 Requested
 Request update
 Under review
 Amendment (on data or agreement)
 Saved
o Action

page where all the associated details of the request will be
shown.
 Sorting for newest and oldest for signing the agreement
 Dropdown for type of agreement
 Dropdown for type of license
Also, users can view keyword search and advance search option
where they can manually enter the agreement related keyword and
get the desired outcome.
Process:
 On click of Agreements under review, on the home page, users
will be re-directed to the listing page where all the open/ongoing
and newly created agreements will be displayed.
 Users can also view the agreements on which amendment raised
by the CITC.
 Filters will be shown in the listing parameters as well as the
advance search button.
Request type Description:

 New request- When service provider assigns a new agreement
request (to upload an agreement) to the service provider user.
 Request update- When service provider raise a modification
request in the existing agreement then the status would be
request update.
 Amend on data- when examiner or wholesale manager raise an
amendment request on the agreement data.
 Amend on agreement- When examiner or wholesale manager
raise an amendment request on the agreement itself (in
agreement document).
Status description
 When user drafts the agreement upload request then the status
would be “draft”
 When user uploaded the agreement then status would be
“agreement under review”.
 When user assigns operator user to upload an agreement then
status would be “assigned”
 When user receives amendment on data on application
submitted by him then status would be “amend data”
 When user receives amendment on agreement on application
submitted by him then status would be “amend on agreement”
 When application approved by the CITC then status would be
“saved”
 When IA agreement rejected by the CITC then status would be
“rejected”
Note: Reject happens only after approval of WSIM
 When IA agreement cancelled by the CITC then status would be
“cancelled”
Note: Cancel happens only after approval of WSIM
 When change request initiated by operator then status would be
request update.
 When change request approved by the CITC then status would
be “Saved”
 When user received CITC initiated a modification request then a
status would be “amendment on data or agreement ”
 For modification request, the status will be similar to mentioned
above just the request type would be changed from “new
request” to “modification request”

 Users should be able to view all newly created agreements.
 Amendment on data and amendment on agreement request will
be viewed in this section. (amend request which is raised by the
examiner)
 Users will be facilitated to search for the records using the
keywords. The entered keyword would be searched in agreement
forms and will display the result based on it.
 When user revert on amendment (data) - Rules for checking
whether all mandatory fields have been filled or not will be put
in place. Error will be thrown if mandatory fields are not filled.
View detail Button

Keyword search Search bar (to enter the keyword in
alphanumeric char)
Advance search Button
Wireframes:
5.10 Agreement under review details
Requirement Definition Users will be able to view the details of the ongoing agreements.

agreement.
2. Users should be clicked view detail in Agreements under review
Post - Condition Users should be able to view details of the particular ongoing/active
agreement.
Business Rules / Logic This use case will start when user clicks on view detail in Agreements
under review, hence they will be able to view the details of the
specific agreement and below details will be displayed.
o Details
o Request ID
o Name of agreement
o Agreement submission date
o Request type
 New request
 Request update/Modification
o Progress status
 Requested
 Under review
 Amendment on Data/agreement
 Saved/rejected/cancelled (final outcome)
o Type of license
o Type of agreement
o Type of service
o Fees values
 Upload pdf file
o Action
 Logs
Description:
 Users will be able to view the details of the uploaded agreement.
 Users can view the progress status based on the current status
of the agreement.
 Users will be able to view logs icon on this page and on clicking,
they will be navigated to the logs page. (Refer to UC_5.16)
 Users will be able to view send reminder icon, which will help
them to send reminder manually to CITC (for their own
agreement requests). Hence, they can simply write the message
and submit. Then, reminder will be sent to the examiner user.
Request Type:
 New Request- When new agreement upload request sent by the
uploaded in past.
Progress status:-
 Requested- when service provider user drafted the agreement
but not submitted.
 Agreement Under review- when application has been submitted
to the CITC.
request update.
 Amendment- When any type of amend request raised by the
CITC could be amend on data or amend on agreement.
above listing.
 The Operator will see Rejected/Cancelled status only after
approval from Wholesale and Interconnect Manager.
Logs Button
Send reminder Icon
5.11 Manage users
Requirement Definition This use case is used to define the elements available in User
Management.
agreement.
2. Users should be clicked on user management.
Post - Condition Users will be able to view created users and manage it from this section.

From this section service provider admin would be able to view and
manage Service provider users. The use case will define the process
for the management.
View all user
Service provider admin can click on the section to view all the users
on this platform created by them. They have option to filter user
type
1. Search by
1.1. Username
1.2. Email ID
1.3. Mobile number
 Users will be able to search for the service provider users by

entering the name, email ID or mobile number.
2. List view of service provider user

2.1. Name
2.2. Email
2.3. Phone number
2.4. User rights (read only or modify)
2.5. Status (Active/inactive)
2.6. View password
2.7. Action
2.7.1. Edit
2.7.2. Delete
2.7.3. Reset password
2.7.4. Block/unblock user
Edit User
Clicking on “Edit” button user will be displayed with the Edit User
page having below details:
 User Name
 Email ID
 Mobile number
 User Role
 Password
 Status
Clicking on “Save” button user will be displayed with success

message and made change will be saved and reflecting in system.
Default user listing will be shown for all the latest added users.
Manage role button will be shown on internal user listing page.
Service provider admin will be able to create Service provider user

from this section. And once created email would be trigged to the
service provider user along with password credentials. Example-
Email will be a welcome email having login credentials:
 Email id
 Password
Password will be an auto generated password which can be used by
service providers to login to application for first time.
Add User: (Service provider User)
Clicking on “Add User” button, user will be redirected to user
creation page with below capture fields
 Enter User Name
 Phone Number
 Email ID
 User role (view only access or modify rights)
o View
o Modification
 Status (Default Checked)
 Create>>
Process for roles assignment-

 Once user selects the user role, modification then all the default
features will be auto-selected and assigned for that specific user.
 On selection of view role, then users can select the activities or
features that they want to assign for particular user.
 On selection of respective menu, all the associated sub-menus
will be auto-assigned to them. For example- assignment of
agreement upload, users can creation different type of
agreement type, view all the fields of the agreement, and submit
agreement form.
 On click of save, user will be created along with given rights.
Pagination
User will be displayed with default top 20 records in listing page and
user will be able to view rest records by clicking on the pagination.

 Service provider Admin needs to click on action icon to perform the
edit, delete, reset password and block/unblock users.
 Post editing, clicking on “Save” button user will be displayed with
success message and made changes will be saved in system.
 Once service provider admin create service provider users then he can
view their details in list view.
 Users can also see search bar where they can enter keyword and
search for it.
 Users can also search for user types by entering email ID, mobile
number or user name.
Add User
User Name User Name (text field with alphabetic

char with 20-25 limit ) Mandatory
Email ID (text field with alphanumeric char with

20-25 limit ), Mandatory
Phone Number Numeric, Mandatory
User Role Dropdown, Mandatory
Submit Button
Back Button
Search
Search Icon Button
View Icon
Edit Icon
Search bar Keyword search
5.12 Manage Roles
Actors Service Provider Admin
Requirement Definition 1. User will be able to add roles of the system.

2. User will be able to edit roles of the system.
3. User will be able to delete roles of the system.
4. User will be able to grant/revoke access to modules.
Pre - Condition 1. Users should be successfully logged-in on the Interconnection agreement.
2. Users should be clicked on manage roles.
Post - Condition User will be able to view roles created.

Whenever user clicks on Manage roles, they will be re-directed to this
page where user roles listing will be displayed and be able to perform
below activities
 Add Roles
 Edit Roles
 Search Roles
Role Listing:
Users will be displayed with all roles created so far in the system. Users
will also be able to search using search bar available on page
Search:
Users will be able to search records using keywords.
Add Role:
Clicking on “Add Role” button, user will be redirected to role creation
page with below capture fields
 Role name
 Status
 Access Rights
User will be facilitate to select the access rights to modules and its
permission (view and modify).
Clicking on “Save” button, user will be displayed with a success message

“Roles created successfully”
Edit Role
Clicking on “Edit” button user will be redirected to edit role page, with
below fields
 Role ID/Code
 Role name
 Status
 Access Rights
Clicking on save button the updates will be saved in the system.
View Role
Clicking on edit icon, user will be redirected to view role page, with below
fields
 Role ID/Code
 Role name
 Status
 Access Rights
Fields and Validation
Add Role
Role Name Text Field, Mandatory
Status Checkbox (Default checked)
Save Button
Back Button
View Role
Role ID Label
Status Checkbox
Edit Button
Back Button
Edit Role
Role ID Label
Status Checkbox
Save Button
Back Button
5.13 SAVED AGREEMENTS (LIST VIEW)
Requirement Service provider admin will be able to view list of all saved agreements
Definition
Pre - Condition  Users should be successfully logged-in on the Interconnection

agreement.
 Users has clicked on saved agreement tile from home page.
 User has proper internet connectivity.
Post - Condition Users will be able to view all the approved agreements under saved
agreement section.
Whenever user clicks on saved agreements user will be displayed with the
agreements that are saved by user.
The listing will include below details:

 Request ID
 Operator user Name (if uploaded by operator user)
 Parties to the agreement
 Date of signing
 Date of submission
 Name of agreement
 saved date
 Status
o Saved
 Action
o View details (refer to UC_5.14)
o Modification
On click of view details, users will be re-directed to the detail page of the
agreement.
All (cancelled/rejected/withdrawn) and Saved tabs

Users will be able to view a tab named “all agreements” where all type of
agreement will be shown such as cancelled, rejected and withdrawn. And
in saved tab users can view only saved agreements for that user.

 Request ID
 Date of signing
 saved date
 Status
o Rejected
o Cancelled
o Withdrawn
 Action
o Modification
Search
Search By Keyword :
Users will be facilitated to search for the records using the keywords. The
entered keyword would be searched in agreement forms and will display
the result based on it.
If the data does not matches or there is no data available user will be
displayed with message “ no record found”
Users will be able to filter out the agreement by selecting/entering the

parameters in listing itself. Following parameters would be there
 Sorting for newest and oldest for saved agreements
 Dropdown for service provider user
 Dropdown for type of agreements
Pagination
User will be displayed with default top 20 records in listing screen and user
will be able to view rest records by clicking on the paginations.
Advance search
Clicking on “View” button user will be redirected to page displaying details
of the agreements.(refer UC_5.17)
Fields and Validation Validation-
 In case entered parameters matches with the database then users can
view the result in a form of listing.
 If the data does not matches or there is no data available user will be
 Manager can toggle between saved and all agreements where in saved
listing only saved/approved agreement will be shown and in all
cancelled/withdrawn and rejected agreement will be shown.
 On selection of all, users can view all the agreement with different
status types such as cancelled, rejected, withdrawn and on click of
saved, only saved agreement will be shown.
 Once a CITC users (examiner and wholesale manager)
approves/rejects/ cancelled the particular agreement it will notify on
the system and will receive an email to all the associated users. (For
amendment request as well)
Status description
 When user raises modification request then status would be

 When user assigns operator user to raise modification request then
 When user receives amendment on data on modification application
 When user receives amendment on agreement on modification
application submitted by him then status would be “amend on
agreement”
 When modification application approved by the CITC then status
would be “saved”
 When IA modification agreement rejected by the CITC then status
would be “rejected”
 When IA modification agreement cancelled by the CITC then status
would be “cancelled”
request update.
 When change request approved by the CITC then status would be
“Saved”
 When user received CITC initiated a modification request then a status
would be “amendment on data or agreement ”
 For modification request, the status will be similar to mentioned above
just the request type would be changed from “new request” to
“modification request”
All Tab
Saved Tab
Search
Search Text field, optional
Request ID Text field, optional
Type of agreement Dropdown, optional
Name of agreement Text field, optional
Operator name Dropdown, Optional
Advance Search Button
Date of saved agreement Sorting (oldest/newest)
View Icon Button
alphanumeric char)
5.14 VIEW SAVED AGREEMENTS
Requirement Definition Service provider admin will be able to view details of the agreements
saved
agreement.
 Users has clicked on view detail on saved agreement.
Post - Condition Users will be able to view details of the saved agreement.

Clicking on the view icon user will be redirected to view agreements
screen where user will be able to view entire details of the agreement.
It will be having below details:
 Request ID
 Date of signing
 Submission date
 Renewed Agreement
 Date of termination
 Operator
 Type of License
 Agreement Parties
 Others
 Type of agreement
 Others
 Type of services
 Others
 Currency Type
 Others
 Involved and affected parties
 Notes
 Fees Currency
 Fee Description
 Fees Value
 Uploaded Documents
 Attachments listing (if any)
 Progress Status
o Requested
o Under review
o Amendment on Data/agreement
o Saved (final outcome)/cancelled/withdrawn
 Action
o View Logs (Refer to UC_5.16)
o Change/modification request
o Assign modification (to SP user)
 Clicking on “View Logs” users will be displayed with the logs of
the agreements. (Refer UC_5.16)
 On click of change/modification, users will be able to view the
agreement form in edited version where all the earlier entered
data will be shown and users can make the changes in the
fields. (only saved agreement will be modify) Also users can
upload the new agreement document.
o Users can see the marked amended fields of the
agreement.
 On click of assign modification, a pop-up will appear on this
page where user can select the service provide user, add
comment and submit.
Progress status:-
 Agreement Under review- when application has been
submitted to the CITC.
 Requested- when service provider user drafted the agreement
but not submitted.
 Request update- When service provider raise a modification
request update.
 Amend on data- when examiner or wholesale manager raise
an amendment request on the agreement data/form.
 Amend on agreement- When examiner or wholesale manager
 Saved- When IA agreement is approved/saved by the CITC.
 Rejected- When IA agreement is rejected by the CITC and send
back due to issues.
 Cancelled- When CITC is not getting the response within
certain time stamp then CITC can close the agreement.
Fields and Validation Validations-

 All the agreements there outcome is determined by the CITC users
(examiner and wholesale manager) will be shown in this section.
approves/rejects the particular agreement it will notify on the
system and will receive an email to all the associated users.
 Users should be able to view all the attachments uploaded against
a particular agreement. Also, CITC uploaded files should be
highlighted in different colour/format so that it will be earlier for
them to understand.
 Submitting an agreement amending request is not allowed, if
there is another unfinished amendment request on the same
agreement
 Once assign modification request is raised by the user, it can be
viewed in agreement under review listing. (refer to UC_5.7)
 Modification requester name, date and time of submission will be
saved.
 On click of modification submit, a pop-up will be shown to the
users stating “are you sure you want to submit?” “yes or no”
the modification agreement.
submission of the modification. Unless it will be asked from the
CITC.
View Logs Button

Change modification Button
Comments Free Text field, Mandatory
Assign modification request (To SP user)
Select SP user Dropdown list (single selection )
Add comment User Name (text field with alphabetic
char with 400-500 limit )
Submit Button
Wireframes:
5.15 AMENDMENT TYPES
Requirement Definition Service provider admin will be able to make the changes/modification
raised by the examiner or wholesale manger.
agreement.
2. Users has received the amendment request from CITC.
3. User has proper internet connectivity.
Post - Condition Users will be able to make the amendment changes asked by the CITC
on a specific agreement.
Whenever service provider admin uploads an agreement request and
CITC (examiner or wholesale manger) identified the issues/concerns in
the agreement then CITC can raise two types of amendment requests.
 Amendment on data
 Amendment on agreement
 Amendment on data- Amendments will be raised when the

service provider entered data is incorrect hence, the wholesale
manager/examiner will be able to add a comment related to that
data (fields) and send it back to the service provider.
o Users can view the received feedback from CITC in a
form of comment. Hence, users can view two options
edit and create new agreement.
o On click of edit, the exiting agreement form will open-
up including previous filled data in editable version
where users can input/edit the form. Also they can
upload new agreement pdf if required.
o On click of create new agreement, a new agreement
form will open where they can start agreement from
scratch.
 Amend on agreement- Amendments will be raised when any
major regulations are not met, clauses of the agreement are not in
line with the regulation, or any other issues with the agreement
document.
o Users can view the added comments along with the
uploaded pdf (if any) from CITC.
o Users can view two options edit and create new
agreement.
upload new agreement pdf.
scratch.
Description-
 In case of amend on data-
 When CITC raised the amendment on data request then service
provider will receive the notification related to it and users will be
able to make the changes in the agreement form.
 Post making the changing in the requested fields, service provider
users can re-submit the agreement to the CITC. And changed fields
will be highlighted so that CITC users can understand.
 Amend on data provided by the CITC in the form of comments
where all the data that needs to change will be shown.
 In case of amend on agreement-
 When CITC raised the amendment on agreement request then
service provide will receive the notification related to it and users
will be able to upload new version of agreement document.
 The system won’t be able to track the changes inside the new
version of document however the document versions will be
maintained.
 Amend on agreement provided by the CITC in the form of
comments and document where all the changes will be
mentioned.
Note: Users will not be able to view the versioning of the documents,
instead to check the changes or modifications user will have to go
through the pdf line by line.
Fields and Validation  In case of amend on data, Users will be able to make the changes
in the below parameters of agreement form.
o Name of agreement (non-editable)
o Date of signing agreement (editable)
o Date of submitting agreement ( editable)
o Renewed Agreement (editable)
o Date of termination (editable)
o Operator (non-editable)
o Type of License (editable)
o Agreement Parties (editable)
o Others (editable)
o Type of agreement (editable)
o Others (editable)
o Type of services(editable)
o Others(editable)
o Currency Type (editable)
o Others (editable)
o Involved and affected parties (editable)
o Notes (editable)
o Fees Currency (editable)
o Fee Description (editable)
o Summary of Fees (editable)
o Upload Documents (editable)
 The operator won’t be able to make the changes during the
approval process hence changes can only be raised once it’s asked
by an examiner or wholesale manager.
 Operator will be able to upload new agreement pdf in case of
amend on agreement and system will maintain the version of the
agreements. However, the system won’t be able to track the
changes inside the new version of document.
 On clicking of submitting the amendment request, a pop-up will
be shown to the users stating “are you sure you want to submit?”
“yes or no”
agreement.
Status description
 When user receives amendment on data on application submitted

by him then status would be “amend data”
 When amendment on data/agreement request approved by the
CITC then status would be “saved”
 When amendment on data/agreement request rejected by the
CITC then status would be “rejected”
 When amendment on data/agreement request cancelled by the
CITC then status would be “cancelled”
Feedback Button
Edit Button
Create new agreement Button
5.16 Logs
Requirement Definition Users should be able to view all the logs against the agreement.
Pre - Condition 1. Users should be successfully logged-in on the interconnection

agreement.
2. Users should be clicked on logs.
Post - Condition Users should be able to view work logs and Saved Workflow Logs for a
particular agreement.
Whenever users click on logs on saved agreement detail page, then a
pop-up will appear having options named work log, and Saved
Workflow Logs.
 Process:
 On click of logs a pop will appear where work log, and Saved
Workflow Logs button will be shown.
 On click of work log, users will be able to view all logs starting
from drafting the agreement, submitted to CITC for approval and
CITC under review.
 Here users can view following details:
o Operator name/CITC
o Previous status
o Current status
o Email
o comment
o Date and time
o Attached file (if any) along with date.
 Also there would be two buttons named all, and change log. On
click of any button users will be re-directed to the specific detail
page.
 On click of change logs, users will be able to view the list of
changes in the specific agreement and users can see the name of
changes in the fields, previous agreement, current agreement, and
date & time. Also users can select the request ID to view the
specific changes.
 On click of Saved Workflow Logs, users will be re-directed to the
page where they can view all the information related to the
approval journey, and below details will be shown.
 Saved Workflow Logs will display both side communication
(CITC and operator user) on agreement.

 In work logs, internal and external discussion will be listed.
 In change logs, users will be able to view the changes made from
initial submission of the agreement to modification suggested by
the CITC.
 In Saved Workflow Logs below details will be shown
o CITC user details
o Image
o CITC user
o Previous status
o Current status
o Approval date and time
o Comment
o Email ID
o Supporting documents by the user along with the date and
time.
 Work log will contain following tabs
o All
o Change logs
 Following details will be shown in Work logs
o Image
o CITC user
o Previous status
o Current status
o Date and time
o Comment
o Email ID
o Supporting document by the user along with date and
time.
 Change logs will contain following information
o Request ID
o Fields
o Previous agreement
o Current agreement
o Date & time
Saved Workflow Logs Button

Work logs Button
All Button
Change logs Button
5.17 Advance search
Requirement Definition Service provider admin should have the option where they can enter
different parameters to get the exact match.
agreement.
2. Users should be clicked on advance search.
Post - Condition Service provider admin should be able to advance search by
entering/selecting different parameters.
This use case will allow users to enter different parameters in
advance search and get desired result. When user clicks on advance
search on home page, an advance search pop-up will appear where
they can enter following parameters:
 Advance search
o Request ID
o Name of agreement
o Date of agreement
o Type of license
o Type of agreement
o Type of service
o Currency
o Fees
o Search >>
o Reset>>
Process:
 Users will be able to view above parameters in advance search.
 Users will be able to enter and select above parameters can
click on search to view the result (Refer to UC_5.18).
 On click of reset, users will be able to re-enter and re-select the
given parameters.
Alternate Flow Different ways to reach advance search page:

 On click of advance search button on Agreements under review
listing page (Refer to UC_5.10)
 On click of advance search button on saved listing. (Refer to
UC_5.13)
On click of advance search on Agreements under review listing, an

advance search pop-up will appear where they can enter the above
parameters and get the desired result. However, the searching of
different agreements would be done within ongoing and requests
under review agreements only. (agreements created by the service
provider users and service provider admin)
In a similar manner, on click of advance search in saved listing, an

different agreements would be done within saved agreements (or
for which outcome is determined cancelled, rejected, withdrawn).
Fields and Validations Validation:

 There is no limitation or restriction of entering the minimum or a
maximum number of parameters. Hence, there is no such rule
where users need to enter/select all the parameters to get the
outcome.
 On click of reset, all the entered parameters should become
natural or reset.
 Post entering the parameters, the user needs to hit enter or click
on search to view the result listing.
 In case no appropriate result is found in the database, then the
system should display a message stating that “no data found
please try again”
 Following are the + add options in the filter and fields
information:
o Request ID
o Name of agreement
o Date of agreement
o Type of license
 Other (The field is displayed when user selects
“Other” from “Parties of agreement” List)
o Type of agreement
“Other” from “Type of agreement” List)
o Type of service
“Other” from “type of services” List)
o Currency list
“Other” from “Currency” List)
 Fees values
 Fees currency
Request ID Text box with Alphabetic with 40

character limit
Date of agreement Date range from (format
DD/MM/YYYY )
Date of termination Date range to (format

DD/MM/YYYY)
Type of license Dropdown list (only single selection

option)
Parties of agreement Dropdown list (multiple selection
option)
Involved or affected parties Text, optional
Type of agreement Dropdown list (only single selection
option)
Type of service Dropdown list (multiple selection
option)
-SAR
-USD
Search Button
Reset Button
5.18 Searched Result page
Requirement Definition Service provider admin should be able to view searched results on this
page.
agreement.
2. Users should have searched for the agreement.
Post - Condition Service provider admin should be able to view the searched results.

Once user enters the advance search parameters and hit enter, they
will be re-directed to this page where result listing would be
displayed.
 List view
o Request ID
o Name of agreement
o Date of agreement
o Type of agreement
o Status
o Action
 View details
 Process:
o On the result listing page, users can view a number of results
found based on the entered parameters.
o On click of view, users can view the details similar to the
agreement details of the agreement along with the
current/final status.
o In case entered parameters does not match with the
database then a message will be shown as “no data found,
please try again”

 On the result listing page, users can view number of results
 In case entered parameters does not match with the database
then a message will be shown as “no data found, please try
again”
View details Button
5.19 Inbox
Actors Service provider Admin
Requirement Definition Service provider Admin should be able to view inbox where
they can view remainders and notifications.
Pre - Condition 1. Users should be successfully logged-in on the
2. Users should be clicked on inbox tile/section from home
page.
Post - Condition Service provider admin should be able to view inbox section
where they can reminders and notifications.
Whenever user clicks on inbox, they will be re- directed to the
page where users can view below separate sections:
 Inbox
 Reminders
 Notifications
Reminders & Notifications:
 Users will be able to receive reminders and notifications in

this section.
 These reminder & notifications will related to the delay in
submitting the agreement, uploaded agreement by service
provider user, amendment on data and agreement, and
violation related.
 Users will be able to view all the received reminders &
notifications and below information will be shown:
 List of reminders/notifications
 Title (agreement name)
 Sender name (if any, for reminders only)
 Type of Agreement
 Description
 Date and time
Users will be able to view notifications on below events

 New agreement upload request from CITC
 Delay in submitting the agreement
 Uploaded agreement by service provider
 Status change on any agreement
 Deadline/Reminder auto notifications to decide on an
agreement
 Modification request initiated by the CITC and modification
request raised by the service provider user.
 On final decision by wholesale manger
(saved/rejected/cancelled)
User will be able to view all latest reminders & notifications on
top and past one in the bottom.
Fields and Validation  Validation:

 All reminders for an application during approval process
(based on timeline / SLA) will be sent to the respective
users through the inbox feature.
 Users will be able to send the reminders on the
uploaded/ongoing agreement details page only.
 Reminders and notifications should be highlighted in
different colour so that users can easily identified that they
have received the reminder or notification.
 Service provider admin can view reminders and
notification for all the agreement created by the service
provider users.
 Auto and manual (both) type of reminders will be sent to
the operator users.
5.20 My Profile
Requirement Users will be able to maintain his/ her profile from here.
Definition

agreement.
2. User should be clicked on profile.
3. Users should have proper internet connectivity.
Post - Condition Users will be able view and manage profile details.
Business Rules / On click of “My Profile” user will be navigated to view profile page
Logic where they will be able to view following fields:
 Service provider name
 User name
 Email ID
 Phone Number
 Profile Photo
 Date of birth
 Profile Creation date
Users will be able to edit the mobile number and upload profile photo
from this section.
Users will be able to change the password:

 Change password
o New password
o Confirm password
o Submit>>
Third-party services  (TBD)
Fields and NA
Validation Back Button
Edit mobile number Text filed (numeric values not more
than 15 digits)
Upload image Upload button (format could be jpeg,
raw image and .PNG)
Change password
New password Text field (Mandatory), Should be
alphanumeric with at-least 1 number
and 1 uppercase character, and length
should be minimum of 8 characters
Confirm password Text field, (Mandatory) It should
match the entered password.
Submit Button
5.21 Reports
Requirement Definition Service provider admin should be able to view all the different reports
from this section.
agreement.
2. Users should be clicked reports landing page.
Post - Condition Service provider admin should be able to view different kinds of
reports such as KPI.
This use case will allow users to view different kinds of reports on
this section such as KPI.
Draft message Text field to draft the message and

should allow alphanumeric with 800 to
900 characters.
Send Button
6 Service provider User (Operator)

Actors Visitor user
Pre - Condition 1. The user account should be created by the service provider
admin.
Service provider user will be created by the super admin, and login
 Email ID
 Mobile number
 Dummy password
 URL to access


 New password
 Submit>>

UC_6.2)

 Email (TBD)
8. Below are the types of licenses for which Service providers will
raise the agreement on the platform:
a. Provide Facilities-Based Fixed Telecommunication
Services
b. Facilities-Based Unified Telecommunication Services
License
c. Provide telecommunication facilities leasing service
(CSP)
d. License Mobile Virtual Network Operator (MVNO)
services
e. Provide wholesale infrastructure services
f. Provide Internet of Things Virtual Network Operator
(IoT-VNO) services
g. And other if required in the future.
mandatory
mandatory
picture)
Login Button

Change password

mandatory
6.2 Login page
Actors Service provider user
Requirement Definition This use case is used to define the Login process for the Visitor users
Pre - Condition 1. The user should already have an account with the platform to log
in.
1. Mobile number
2. OTP
3. Enter captcha
4. Submit>>
5. Forgot password

registered user. If no match is found, users can either try again with
their credentials or they can use forgot password flow.

Third-party SMS (third-party service TBD)


Login Button

picture)
user.
Pre - Condition 1. User should be on the Login Page.

Password” button.
Once they will click on forgot password button, they will be asked to
enter their registered email ID and click submit. The system will look
for a match in the database and if a match is found, they will be
displayed a message that a reset password link has been successfully
shared on your registered email id, please use the link to generate a
new password.
When a user clicks on the link from their email, they will be asked to
enter a password and confirm the password in 2 different fields. All
validations will be the same as used while registration. Once they set
their new password, redirect them to the login page directly.
with us first.

2. If the user enters invalid email and clicks on “send email” button
it must show that “wrong email ID”
Interconnection agreement database the website shall notify the
user with the text, “Record not found.”
Submit Button
6.4 Home Page

Requirement Definition Users will be re-directed to the home page of the web application and view
available elements based on the user role.
Post - Condition User will be able to view all the available features based on the user role.


o Header
 Logo and name
o Tiles
 Agreement upload requests (sent by the service
provider admin)
 Agreements under review (ongoing)
 Inbox
 Reports
 Advance search
 My profile
click)
o Footer
 FAQs
 Privacy policy
 Description-

 Agreement upload request- Users should be able to able to view
the option to upload an agreement. (refer to UC_6.5)
 Agreement upload- Users will be able to upload different types of
agreement from this section. (refer to UC_6.7)
 Agreements under review - Service provider user will be able to
view list of submitted requests (Uploaded) and ongoing
agreements. (refer to UC_6.8)
UC_6.10)
and 50%.
page.
whenever users click on it an advance search pop-up will
appear (refer to UC_6.14) and in this search, users will be able to
6.5 Agreement upload requests (by SP Admin)
Actors Service provider User
Requirement Definition Users will be able to view the agreement upload request sent by
service provider admin.
agreement.
Post - Condition Users should be able to view the list of agreement upload requests
came from service provider admin.
requests sent by the service provider admin, hence they will be able
to view the listing on this page.
o Request ID
o Name of agreement
o Request date
o Added Comment (to view comment they need to click on
view detail )
o Uploaded document
o Request type
 New request
o Action
 Upload agreement (refer to UC_6.7)
shown.

outcome.
Process:
 On click of agreement upload request on the home page, users
will be re-directed to the listing page where all the new assigned
agreements by the service provider admin will be displayed.
 Users can view filters/searches in the listing parameters.

 New request- When service provider assigns a new agreement
request (to upload an agreement) to the service provider user.
request update.

 Operators should be able to view all the new requests sent by
the service provider admin.
 Amendment raise by the examiner in the ongoing agreement will
be sent to the operator user only. However, Modification
initiated by CITC i.e. modification post an agreement was saved
once will be first sent to SP admin, who will the assign it to a SP
user.
configurable (Default timeline is 10 days).
 SP admin can assign the modification request and new upload
request.
 In case SP admin cancel the request then SP users won’t be able
to take further actions.

View details Button
Wireframes:
6.6 Agreement request details
Requirement Definition Users will be able to view the application request details sent by the
agreement.
Post - Condition Users should be able to view the raised agreement request details.
 Details
o Request ID
o Name of agreement
o Request date
o Added Comment (to view comment they need to click on
view detail )
o Uploaded documents
 Upload pdf file
o Action
Process:
 Users will be able to view the details of requested upload
agreement and can take upload the agreement.
 On click of upload agreement, users will be re-directed to the
upload agreement page. (Refer to UC_6.7)

 Comments will be visible on this page.
6.7 Agreement upload
Requirement Definition Users will be able to view the option to upload an agreement
requests.
agreement.
2. Users should be clicked on upload agreement on home page.
Post - Condition Users should be able to view the option to upload an agreement.
requests. Therefore, they will be able to view the list of drafted
agreements and below details will be shown.
o Request ID
o Type of agreement
o Date of signing
o Submission date
o Name of agreement
o Status
 Draft
o Action
 Remove
 View
 On click of remove, an agreement that’s in drafted stage will be

removed from the list.
 On click of view, they will be re-directed to the detail page where
drafted details will be shown to them along with the option to
remove, edit and submit.
 Users will be able to view the upload agreement button on the
listing page and on click of it agreement form will open-up.
On click of upload agreement, a pop-up will appear where users can

fill-up the form and submit.
o Name of agreement
o Date of agreement
o Type of license
from “Parties of agreement” List)
o Type of agreement
from “Type of agreement” List)
o Type of service
from “type of services” List)
o Currency list
from “Currency” List)
 Fees values
 Fees currency
 Upload pdf file
o Add note
o Submit>>
 On click of submit, agreement form will be submitted to the

wholesale and interconnection services.
Process:
 On click of upload agreement, users will be re-directed to this
page where they can view the agreement form.
 They should be able to upload different type of agreement from
this section.
 On click of submit, the agreement request will be submitted to
the CITC (wholesale manager).
submission of the agreement. Unless it will be asked from the
CITC.
 Once agreement is uploaded, it should be removed from this
page and can be viewed in agreement under review page.

 Agreements will be uploaded by service provider within 10 days
from signing the agreement, where it reviewed by CITC
Wholesale and Interconnection Services and appropriate
decision is made.
 Post submission of the agreement, users won’t be able to make
the changes unless it’ll be asked from the CITC.
time of submission
 Request status upon submission will be (Under Review).
 Users should be able to add a comment and this comment could
be written in Alphabetic format with a 1000 character limit.
 In case without entering comment users click on submit then
system should display a message that “please add the
comment”.
(saved/rejected/amendment) in the saved agreement and
Agreements under review. Moreover, all these documents' names,
sent by, date, and time will be in approval logs during the
approval process.
“are you sure you want to submit?” “yes or no”
 The file cannot be amended/deleted after submission. It can only
be edited when it’s been asked by the examiner or wholesale
manager.
 In case any mandatory fields are not filled then the system
should throw the error.
 Services will be shown based on the selection of license as they
are associated with specific licenses. For example if operator
selects ABC license then while selecting services they can view all
the associated services with that license and can select multiple
or one of them.

View agreement button
Remove Button
Date of agreement Gregorian calendar (Mandatory)
Date of termination Check box (Gregorian calendar) Only one
field can be selected
Renewed agreement
Checkbox, for other (text)
Other -In case of selecting “Date of
termination”, the user must define the
date
Type of license Dropdown List, Mandatory

Parties of agreement -Multiple choices (Mandatory)
license
when user selects “Other” from “Parties
of agreement” List
Involved or affected Text, optional
parties
-New
-Amended
agreement” List
Type of service Dropdown list, (Mandatory)
-Multiple choices
service” List
-SAR
-USD
when user selects “Other” from
“Currency” List
Fees description Text, (mandatory)
Upload attachment PDF format (mandatory)
Upload Annexes PDF format (optional)
Submit Button
6.8 Agreements under review (List view)

Requirement Definition Users will be able to view the ongoing agreement requests.

agreement.
2. Users should be clicked on Agreements under review
Post - Condition Users should be able to view the list of active/ongoing agreement
created by them.
Business Rules / Logic In this use case users will be able to view list of ongoing agreements
requests created by them and following list view will be displayed.
o Request ID
o Name of agreement
o Submission date
o Type of agreement
o Request type
 New request
o Status
 Requested
 Request update
 Under review
 Amendment (on data or agreement)
 Saved
o Action

shown.

outcome.
Process:
 On click of Agreements under review on the home page, users
will be re-directed to the listing page where all the open/ongoing
and newly created agreements will be displayed.
 Filters will be shown in the listing parameters as well as the
advance search button.

 New request- When service provider admin assigns a new
agreement request (to upload an agreement) to the service
provider user.
request update.
Progress status:-
to the CITC.
but not submitted.
request update.
amendment request on the agreement data/form.
Status description
 When user drafts the agreement upload request then the status
would be “draft”
 Once agreement request is uploaded by operator user then
status would be “agreement under review”
 When user receives upload request from admin then status
would be “assigned”
 When user receives amendment on data on agreement
 When application approved by CITC then status would be
“saved”.
 When IA agreement rejected by the CITC then status would be
“rejected”
 When IA agreement cancelled by the CITC then status would be
“cancelled”
Note: cancel happens only after approval of WSIM
 When change request initiated by the operator then status
would be “request update”
 When change request approved by the CITC then status would
be “saved”
 When user receives a CITC initiated modification after admin
assigns then status would be “assigned”

 Users should be able to view all newly created applications.
 Amendment on data and amendment on agreement request will
be viewed in this section. (amend request which is raised by the
examiner)
 The system sends a notification and email to service provider
once agreement is submitted by agreement examiner.
 Users will be facilitated to search for the records using the
 Once operator revert post making the changes asked by the
examiner then they can view all the changed fields.
 When user revert on amendment (data) - Rules for checking
whether all mandatory fields have been filled or not will be put
in place. Error will be thrown if mandatory fields are not filled.
View detail Button

alphanumeric char)
Wireframes:
6.9 Agreement under review details

agreement.
2. Users should be clicked view detail in Agreements under review
Post - Condition Users should be able to view details of the particular active
agreement.
under review, hence they will be able to view the details of the
specific agreement and below details will be displayed.
 Details
o Request ID
o Name of agreement
o Request type
 New request
 Request update
o Progress status
 Requested
 Under review
 Saved/rejected/cancelled (final outcome)
o Type of license
o Type of agreement
o Type of service
 Upload pdf file
o Action
 Logs
 Reminder
Description:
 Users will be able to view the details of the uploaded agreement.
 Users can view the progress status based on the current
situation of the agreement.
them to send reminder manually to CITC (for their own
agreement requests). Hence, they can simply write the message
and submit. Then, reminder will be sent to the examiner user.
Request Type:
uploaded in past.
Progress status:-
but not submitted.
to the CITC.
request update.

above listing.
Logs Button
Send reminder Button
Requirement Service provider user will be able to view list of all saved agreements
Definition

agreement.
 Users has clicked on saved agreement tile from home page.
agreement section.
Whenever user clicks on saved agreements user will be able to view all the
agreements for which outcome has been determined on the platform.

 Request ID
 Date of signing
 saved date
 Status
o Saved
 Action
o Modification/change
 On click of view details, users will be re-directed to the detail page of

the agreement.
 In case SP admin ask SP user to raise the modification then only users
will be able to raise the modification/change request.


 Request ID
 Date of signing
 saved date
 Status
o Rejected
o Cancelled
o Withdrawn
 Action
o Modification
Search
Search By Keyword :

 Dropdown for type of status
Pagination
Advance search
of the agreements.(Refer UC_6.14)
approves/rejects/cancelled the particular agreement it will notify on
the system and will receive an email to all the associated users. (For
amendment request as well)
Status description
 When user draft the modification request then the status would be
“draft”
 When user raised modification request then status would be
 When user assigns operator user to raise modification request then
 When user receives amendment on data on modification application
 When user receives amendment on agreement on modification
application submitted by him then status would be “amend on
agreement”
 When modification application approved by the CITC then status
would be “saved”
 When IA modification agreement rejected by the CITC then status
would be “rejected”
 When IA modification agreement cancelled by the CITC then status
would be “cancelled”
request update.
 When change request approved by the CITC then status would be
“Saved”
 When user received CITC initiated a modification request then a status
would be “amendment on data or agreement ”
All Tab
Saved Tab
Search
View Icon Button
alphanumeric char)
Requirement Definition Service provider user will be able to view details of the agreements
saved
agreement.

 Details
 Request ID
 Date of agreement
 Operator
 Type of License
 Others
 Others
 Others
 Currency Type
 Others
 Notes
 Fees Currency
 Fee Description
 Fees Value
 Progress Status
o Requested
o Under review
o Amendment on Data/agreement
o Saved (final outcome)
 Action
o Change/modification request
 Clicking on “View Logs” users will be displayed with the logs of

the agreements.
 On click of change/modification, users will be able to view the
agreement form in edited version where all the earlier entered
data will be shown and users can make the changes in the
fields. Also users can upload the new agreement document.
o Users can see the marked amended fields of the
agreement.
Progress status:-
 Agreement Under review- when application has been
submitted to the CITC.
but not submitted.
request update.
 Amend on data- when examiner or wholesale manager raise
an amendment request on the agreement data/form.
 Saved- When IA agreement is approved/saved by the CITC.
 Rejected- When IA agreement is rejected by the CITC and send
back due to issues.
 Cancelled- When CITC is not getting the response within
certain time stamp then CITC can close the agreement.

approves/rejects the particular agreement it will notify all the
associated users.
agreement
them to understand.
 Modification requester name, date and time of submission will be
saved.
 On click of modification submit, a pop-up will be shown to the
users stating “are you sure you want to submit?” “yes or no”
the modification agreement.
submission of the modification. Unless it will be asked from the
CITC.
 In case SP admin ask SP user to raise the modification then only
users will be able to raise the modification/change request.
View Logs Button

Change modification Button
Wireframes:
6.12 AMENDMENT TYPES
Requirement Definition Service provider user will be able to make the changes/modification
raised by the examiner or wholesale manger.
agreement.
2. Users has received the amendment request from CITC.
Post - Condition Users will be able to make the amendment changes asked by the CITC
on a specific agreement.
Whenever service provider user uploads an agreement and CITC
(examiner or wholesale manger) identified the issues/concerns in the
agreement then CITC can raise two types of amendment requests.

service provider entered data is incorrect hence, the wholesale
manager/examiner will be able to add a comment related to that
data (fields) and send it back to the service provider.
o Users can view the received feedback from CITC in a
form of comment. Hence, users can view two options
edit and create new agreement.
upload new agreement pdf if required.
scratch.
major regulations are not met, clauses of the agreement are not in
line with the regulation, or any other issues with the agreement
document.
o Users can view the added comments along with the
uploaded pdf (if any) from CITC.
o Users can view two options edit and create new
agreement.
upload new agreement pdf.
scratch.
Description-
 When CITC raised the amendment on data request then service
provider will receive the notification related to it and users will be
able to make the changes in the agreement form.
 Post making the changing in the requested fields, service provider
users can re-submit the agreement to the CITC. And changed fields
will be highlighted so that CITC users can understand.
service provide will receive the notification related to it and users
will be able to upload new version of agreement document.
maintained.
mentioned.
Note: Users will not be able to view the versioning of the documents,
instead to check the changes or modifications user will have to go
through the pdf line by line.
Fields and Validation  In case of amend on data, Users will be able to make the changes
in the below parameters of agreement form.
o Name of agreement (non-editable)
o Date of signing agreement (editable)
o Date of submitting agreement ( editable)
o Renewed Agreement (editable)
o Date of termination (editable)
o Operator (non-editable)
o Type of License (editable)
o Agreement Parties (editable)
o Others (editable)
o Type of agreement (editable)
o Others (editable)
o Type of services(editable)
o Others(editable)
o Currency Type (editable)
o Others (editable)
o Involved and affected parties (editable)
o Notes (editable)
o Fees Currency (editable)
o Fee Description (editable)
o Summary of Fees (editable)
o Upload Documents (editable)
 The operator won’t be able to make the changes during the
approval process hence changes can only be raised once it’s asked
by an examiner or wholesale manager.
 Operator will be able to upload new agreement pdf in case of
amend on agreement and system will maintain the version of the
agreements. However, the system won’t be able to track the
changes inside the new version of document.
 On clicking of submitting the amendment request, a pop-up will
be shown to the users stating “are you sure you want to submit?”
“yes or no”
agreement.
Status description
 When user receives amendment on data on application submitted

by him then status would be “amend data”
 When amendment on data/agreement request approved by the
CITC then status would be “saved”
 When amendment on data/agreement request rejected by the
CITC then status would be “rejected”
 When amendment on data/agreement request cancelled by the
CITC then status would be “cancelled”
Feedback Button
Edit Button
Create new agreement Button
6.13 Logs
Requirement Definition Users should be able to view all the logs against the agreement.

agreement.
Workflow Logs.
 Process:
from drafting the agreement, submitted to CITC for approval and
CITC under review.
o Operator name/CITC
o Previous status
o Current status
o Email
o comment
o Date and time
page.
specific changes.
 Approval logs will display both side communication (CITC
and operator user) on agreement.

the CITC.
o CITC user details
o Image
o CITC user
o Previous status
o Current status
o Comment
o Email ID
time.
o All
o Change logs
o Image
o CITC user
o Previous status
o Current status
o Date and time
o Comment
o Email ID
time.
o Request ID
o Fields
o Current agreement
o Date & time
Work logs Button
All Button
Change logs Button
6.14 Advance search
Requirement Definition Service provider user should have the option where they can enter
agreement.
Post - Condition Users should be able to advance search by entering/selecting
different parameters.
 Advance search
o Request ID
o Name of agreement
o Date of agreement
o Type of license
o Type of agreement
o Type of service
o Currency
o Fees
o Search >>
o Reset>>
Process:
given parameters.

UC_6.10)

under review agreements only. (agreements created by the service
provider users)


outcome.
natural or reset.
please try again”
information:
o Request ID
o Name of agreement
o Date of agreement
o Type of license
o Type of agreement
o Type of service
o Currency list
 Fees values
 Fees currency

character limit
DD/MM/YYYY )

DD/MM/YYYY)

option)
option)
option)
option)
-SAR
-USD
Search Button
Reset Button
Requirement Definition Service provider User should be able to view searched results on this page.

agreement.
Post - Condition Users should be able to view the searched results.

displayed.
 List view
o Request ID
o Name of agreement
o Date of agreement
o Type of agreement
o Status
o Action
 View details
Description:
 On the result listing page, users can view a number of results
 On click of view, users can view the details similar to the
agreement details of the agreement along with the current/final
status.
again”

again”
View details Button
6.16 Inbox

Requirement Definition Service provider user should be able to view inbox where they can
view remainders and notifications.
agreement.
2. Users should be clicked on inbox tile/section from home page.
Post - Condition Service provider user should be able to view inbox section where they
can reminders and notifications.
Whenever user clicks on inbox, they will be re- directed to the page
where users can view below separate sections:
 Inbox
 Reminders
 Notifications
 Users will be able to receive reminders and notifications in this

section.
submitting the agreement, upload agreement request,
amendment on data and agreement, and violation related.
 Description
 Date and time

 New agreement upload request from service provider admin
 Delay in submitting the agreement
 Deadline/Reminder auto notifications to decide on an agreement
 Modification request initiated by the CITC.
 On final decision by wholesale manger (saved/rejected/cancelled)
User will be able to view all latest reminders & notifications on top
and past one in the bottom.

 All reminders for an application during approval process (based on
timeline / SLA) will be sent to the respective users through the
inbox feature.
 Users will be able to send the reminders on the uploaded/ongoing
agreement details page only.
 Reminders and notifications should be highlighted in different
colour so that users can easily identified that they have received
the reminder or notification.
 Service provider admin can view reminders and notification for all
the agreement created by the service provider users.
 Auto and manual (both) type of reminders will be sent to the
operator users.
Inbox (reminder and Inbox (reminder and notifications)

notifications)
6.17 My Profile
Definition

agreement.
 Service provider name
 User name
 Email ID
 Phone Number
 Profile Photo
 Date of birth
from this section.

 Change password
o New password
o Confirm password
o Submit>>
Fields and NA
than 15 digits)
raw image and .PNG)
Change password
Submit Button
6.18 Reports
Requirement Definition Service provider user should be able to view all the different reports from
this section.
agreement.
Post - Condition Service provider user should be able to view different kinds of reports
such as KPI.
This use case will allow users to view key performance indicators
(KPIs) below:
 Number of created agreements on the platform
 Number of approved agreements
 Number of rejected agreements
 Number of cancelled agreements
 Number withdrawn agreements
Draft message Text field to draft the message and should

allow alphanumeric with 800 to 900
characters.
Send Button
7 Agreement Examiner
Actors Visitor user
interconnection agreement system.
Pre - Condition 1. The user account should be created by the wholesale manager.
Examiner users will be created by the wholesale manager, and login
 Email ID
 Mobile number
 Dummy password
 URL to access


 New password
 Submit>>

UC_7.2)

 Email (TBD)

mandatory
mandatory
picture)
Login Button

Change password

mandatory
7.2 Login page
Actors Visitor
Requirement Definition This use case is used to define the Login process for the Visitor
users
Pre - Condition 1. The user should already have an account with the platform to
log in.
1. Mobile number
2. OTP
3. Enter captcha
4. Submit>>
5. Forgot password

registered user. If no match is found, users can either try again
with their credentials or they can use forgot password flow.


Login Button
Actors Visitor user
user.
Password” button.
Once they will click on forgot password button, they will be asked
to enter their registered email ID and click submit. The system will
look for a match in the database and if a match is found, they will
be displayed a message that a reset password link has been
successfully shared on your registered email id, please use the link
to generate a new password.
When a user clicks on the link from their email, they will be asked
to enter a password and confirm the password in 2 different fields.
All validations will be the same as used while registration. Once
they set their new password, redirect them to the login page
directly.
with us first.

2. If the user enters invalid email and clicks on “send email”
button it must show that “wrong email ID”
Interconnection agreement database the website shall notify
the user with the text, “Record not found.”
Submit Button
7.4 Home page
Actors Examiner user

Requirement Definition Users will be re-directed to the home page of the web application and
view available elements based on the user role.
Pre - Condition 1. User should be logged-in on the interconnection agreement and
clicked on Interconnection agreement.
Post - Condition User will be able to view available elements based on the user role.

 Home page
o Header
 Logo and name
o Tiles
 Request agreement upload (to operator)
 Agreement request (from WIM)
 Agreement under review
 Inbox
 Reports
 Advance search
 My profile
click)
o Footer
 FAQs
 Privacy policy
 Description-
 On the home page, users will be able to view above mentioned
details.
 Raise agreement request- Users will be able to send the upload
agreement request to the service provider. (refer to UC_7.15)
 Agreement request- Users will be able to receive the agreement
upload request from the WIM. (refer to UC_7.5)
 Agreements under review – Examiner will be able to view the
active agreements (newly assigned requests) (refer to UC_7.7) and
pending request from WSIM side in this section. (refer to UC_7.9)
 Saved agreement- Users will be able to view all the agreement
withdrawn) and saved agreement just by clicking on tabs. (refer to
UC_7.13)
and 50%.
page.
whenever users click on it an advance search popup will
7.5 Agreement requests (List view)
Requirement Definition Users will be able to view the agreement upload request sent by the
wholesale interconnection manager.
agreement.
2. Users should be clicked on agreement request on home page.
Post - Condition Users should be able to view the list of agreement upload request
sent by the WIM.
Business Rules / Logic This use case will start when user clicks on agreement requests,
hence they will be able to view the listing of agreements requests
sent by the wholesale manager and following details will be
displayed.
o Service provider names (from which request will be

raised)
o Submission due date
o Date of signing
o Request type
 New request
 Modification
o Action


 Sorting for newest and oldest for date of signing the agreements
 Sorting for newest and oldest for submission date
outcome.
Process:
 On click of agreement request on the home page, users will be
re-directed to the listing page where all the agreement upload
request will be displayed. (sent by the WIM)
 Searches will be shown in the listing parameters.
Fields and
Validation
Wireframes:
7.6 Agreement request details (sent by WIM)
Requirement Definition Users will be able to view the agreement request details raised by
the wholesale manager.
agreement.
Post - Condition Users should be able to view the details of the agreement request
sent by the WIM.
 Details
o Service provider names (from which request will be
raised)
o Request type
 New request
 Modification
o Attachments
 Uploaded pdf files
o Added comment (wholesale manager)
o Requested on
o Action
 Raise agreement upload request (Refer to
UC_7.15)
Process:
 Users will be able to view the details of agreement request sent
by the WIM.
 Users will be able to read the comment added by the WIM.
 On click of raise agreement upload request, users will be re-
directed to the raise agreement upload page. (Refer to UC_7.15)
Request Type:
 New request- When new agreement upload request sent by the
wholesale manager to the examiner user.
 Modification request- When examiner user will receive raise
modification request for existing IA agreement.

 Modification request will be sent to the same examiner user who
has worked earlier on the agreement approval.
 Post receiving the modification request, examiner user can raise
the modification request from saved agreement (refer to
UC_7.14)
Raise agreement upload Button

request
7.7 AGREEMENTS UNDER REVIEW (ACTIVE AGREEMENTS)
Actors Examiner User
Requirement Examiner user will be able to view list of active agreements that are
Definition assigned for review.

agreement.
2. Users has clicked on active agreements.
Post – Condition Examiner will be able to view details of the agreements that are
under review. (active)
Whenever user clicks on Agreements under review tile user will be
redirected to the page where active agreements and pending
agreements tile (refer to UC_7.9) will be shown to them.
On click of active agreement tile, users will be re-directed to this

page where all active agreements that are assigned to examiner for
review will be displayed.

 Request ID
 Tracking Number
 Operator Name
 Parties to the Agreement
 Date of Signing Agreement
 Date of submitting Agreement
 Name of Agreement
 Request type
o New request
o Modification request
 Status
o Agreement under review
o Sent back by manager
o Amendment (on data or agreement)
o Requested other department review
 Action
o View
o Violation
o Raise Flag/lower flag
Search (Keyword)
Users will be facilitated to search for the records using the keywords.
The entered keyword would be searched in agreement forms and
will display the result based on it.
Pagination
User will be displayed with default top 20 records in listing screen
and user will be able to view rest records by clicking on the
paginations.
Description:-
 Clicking on “View” button user will be redirected to page
displaying details of the agreements. (refer UC_7.8)
 Clicking on “Violation” Icon, an agreement will be marked as
violated and further actions would be taken in detail page.
 Clicking on “Flag” icon, the flag can be turned off and on for all
the agreement. The flag will include number of days since
deadline was lapsed.
o Users can also switch off the flags if required.
Tracking logic
 Examiner users and WSIM can view tracking number that is

combination values for date of signing, amount, and associated
party’s code. For example- 101221-300-0203
 To check/view if both parties have uploaded the agreement or
not users can follow the below process
o WSIM can view the list of new agreements uploaded by
different operators.
o Once a user clicks on any specific agreement they can
view details of the agreement.
o On this detail page, WSIM can view a drop-down tab
named “other parties” and on click of that users can view
a list of associated parties.
o Therefore, in case the other party has uploaded the
agreement then it will show a green dot else red (if
another party has not uploaded the agreement).
 CITC can also search for the agreement uploaded parties by
entering the tracking number. Hence, they can view list of
parties uploaded the document.
Status description
 When user raises the agreement upload request to the operator
then the status would be “requested”
 When Agreement Request gets assigned by WSIM then status
would be “agreement under review”. He will only see this
application once assigned by WSIM
 When user saves an agreement then status would be
“agreement saved by examiner”
 When user rejects an agreement then status would be “rejected
by examiner”
 When user cancels an agreement then status would be
“cancelled by examiner”
 When user send back application to operator then status would
be “amend on data/amend on agreement”
 When user sends agreement to other department then status
would be “request other department review”
 Rejects request of examiner to send to other department then
 When user receives application back from WSIM then status
would be “agreement under review.”
 When user receives modified application from Operator, after
assigned from WSIM then status would be “agreement under
review”. He will only see this application once assigned by WSIM.
Third-party services Violation system (TBD)

 Examiner will be able to view all the newly received agreement
from WIM.
 From the date of request assignment to the examiner, the
system sends reminders (every five days) and over email, to the
examiner to whom the request is assigned.
 Users can also view ongoing (under review) amendment
agreements.
 Once decision made by the WSIM the decision agree
(saved/rejected/cancelled) the agreement will be removed from
this listing.
 Flag will include number of days since deadline was lapsed. By
clicking/unclicking, the flag can be turned off and on for all the
applications
 Flag will be raised by the tool if the difference between the date
of signing the agreement and date of submitting the agreement
is more than 10 days (default)
 There will be no automatic triggering of the violation system.
User has to click manually on violation icon.
 However, if CITC has raised a request to an operator to submit
the agreement and changed the timeline. Then the revised
timeline will be considered for flagging off this particular
operator’s submission (i.e. if 10 days was changed to 15 days,
then in that case the flag will be shown when the difference is
more than 15 days)
 The examiner and the wholesale & Interconnect manager should
be allowed to switch off the flags mentioned above.
 The system verifies from delay of uploading the agreement by
service provider, as follows:
o Deadline for uploading the agreement = 10 days
(configurable)
o Date of uploading the agreement – date of agreement <
deadline for uploading the agreement
 In case of exceeding the deadline, the system identifies service
provider as “delayed” and submit the case to the examiner.
 Flagged can be raised in below scenarios:
o There is a delay in submitting the agreement by the
operator (i.e. beyond 10 days of signing the agreement).
operator after predefined timeline set by the CITC user
(first time upload or amendment)
o In all the cases the CITC user should be able to switch off
the flag if required.
 When WSIM sent back the agreement for review then an email
will be triggered to them.
Search
View Icon Button
Violation icon Button
Flag Icon Button
7.8 VIEW AGREEMENT DETAILS
Requirement Examiner user will be able to view details of the agreements

Definition assigned for review.

agreement.
2. Users has clicked on view detail in agreement under review.
Post - Condition Examiner will be able to update the status of the agreements for
review.
screen where user will be able to view entire details of the
agreement.
 Request ID
 Operator
 Type of License
 Others
 Others
 Others
 Currency Type
 Others
 Notes
 Fees Currency
 Fee Description
 Fees Value
 Added Comments
 Action
o Add comment and upload document
o Save
o Reject
o Cancel
o Violation
o Amend
 On Data
 On agreement
o View Logs
o Request other department review
Description-
 User will be able to add comments, in comment section, upload
document and take further actions.
 Clicking on “save” button the agreement will be approved and an
agreement will be sent to the manager for final approval process.
 Clicking on “Reject” Button agreement will be rejected and
agreement will be sent to WSIM for final decision. Post WSIM
decision the agreement will be deemed as rejected.
 Clicking on “cancel” Button agreement will be cancelled and
agreement will be sent to WSIM for final decision. Post WSIM
decision the agreement will be deemed as cancelled.
 Users need to checkmark the “Violation” option if they want to
raise violation on any particular agreement and take further
necessary actions (save, reject, and cancel). They can write the
reason in the comment section as to why violation was raised.
o When the application reaches the Wholesale and
Interconnect Manager for review, the manager will be
able to see in the detailed view of application if a
violation was flagged by Examiner or not.
 Clicking on “Amend” button and a pop-up will appear where two
kinds of amendment will be shown. Amend on data and amend
on agreement based on the selection user will be re-directed.
(refer to UC_7.9)
the agreements. (refer UC_7.10)
them to send reminder manually to operator user. Hence, they
can simply write the message and submit. Then, reminder will be
sent to the service provider user and service provider admin.
Request to other department review process

Examiner user will be able to raise the request to other departments
review from this page however, this request will be sent to the
wholesale interconnection manager, and after that manager can
send it to the department else manager can respond to the
examiner directly (if not required for other departments) if he has
the answer for the examiner query.
In case WSIM shared the agreement with other departments then

the examiner will get the direct revert from the department and
WSIM will be notified for the same.
Fields and Validation  While user reject the agreement, the system should check if they
have added a comments to comments section. If not then user
will be displayed with message “ Kindly add rejection reason in
comments area”
 Comments should be mandatory only when sending back
(internally or to operator) or rejecting.
(save/rejected/amend) in the saved agreement. Moreover, all
these documents' names, sent by, date, and time will be in
approval logs during the approval process.
 Any request submitted by the service provider can be rejected or
cancelled by CITC. These 2 statuses are defined as follows
 Rejected - If an IA agreement submitted by operator is incorrect
and is not aligned with the IA regulations. CITC may choose to
reject it. In this case the operator will have to re-initiate the
entire process and submit the agreement again.
 Cancelled - If an IA agreement has been submitted by the
operator but there is no traction on it since a long time due to
some reasons (these reasons may be from operator's end or
CITC's end). In such cases, CITC may want to cancel the
submission. Post cancellation, the operator will have to re-
initiate the entire process and submit the agreement again
 The system sends a notification and email to service provider
once agreement is submitted by agreement examiner.
 Once the examiner rejects a request, it is sent to the Wholesale
and Interconnect Manager
 The wholesale and interconnect manager will need to accept the
rejection. Post approval or acceptance, the request is rejected
and sent to Operator.
 When examiner makes a decision to reject an application, the
status changes from Agreement under Review to Rejected by
Examiner/Cancelled by Examiner and after the Wholesale and
Interconnect Manager agree (approval).
 Wholesale and Interconnect Manager will trigger the violation
system if he accepts the reasoning of violation.
 In case user has already marked the agreement as violated then
on this page they can proceed with the further actions such as
adding the comment and “save, reject, and cancel the
agreement”.
 The request for amendment needs to be sent directly from the
examiner to the service provider.
Approve Button
Reject Button
Violation Checkbox
Amend Button
View Logs Button
Send reminder Button
7.9 PENDING AGREEMENT
Requirement Examiner user will be able to view list of agreements that are
Definition pending from WSIM for final outcome.
agreement.
2. Users has clicked on pending agreement.
Post - Condition Examiner will be able to view all the agreement that are pending
from WSIM.
Whenever user clicks on pending Agreements tile user will be
redirected to the listing page where all the pending agreement from
WSIM will be shown.

 Request ID
 Tracking Number
 Operator Name
 Parties to the Agreement
 Date of Signing Agreement
 Date of submitting Agreement
 Name of Agreement
 Request type
o New request
o Modification request
 Status
o Saved/reject/cancelled by examiner
 Action
o View
Search (Keyword)
Users will be facilitated to search for the records using the keywords.
The entered keyword would be searched in agreement forms and
will display the result based on it.
Pagination
paginations.
Description:-
displaying details of the agreements. (refer UC_7.10)

 Examiners can view all the requests that are pending from WSIM
for final outcome.
 Post final decision of the WSIM the agreement will be pushed to
the saved agreement (all/saved).
 When WSIM sent back the agreement to the examiners it can be
viewed in active agreements.
Search
View Icon Button
7.10 VIEW PENDING AGREEMENT DETAILS
Requirement Examiner user will be able to view details of the pending

Definition agreements.

agreement.
2. Users has clicked on view detail in pending agreement.
Post - Condition Examiner will be able to view the details of the pending agreements
on this page.
Clicking on the view icon (in pending agreement) user will be
redirected to view detail agreement page where user will be able to
view entire details of the agreement.

 Request ID
 Operator
 Type of License
 Others
 Others
 Others
 Currency Type
 Others
 Notes
 Fees Currency
 Fee Description
 Fees Value
 Added Comments
 Action
o View Logs
Description-

View Logs Button
7.11 AMEND AGREEMENTS

Requirement Examiner user will be able to ask for amendment from this
Definition section.

agreement.
2. Users has clicked on agreement under review tile from home
page.
Post - Condition Examiner will be able to view the option to ask for two kinds of
amendment on the agreement. (Amendment on data and
amendment on agreement)
The use case will allow examiner user to ask for the amendments
on specific agreement request. Clicking on “Amend” button user
will be displayed with the popup having two options :

service provider entered data is incorrect hence, the
wholesale manager or examiner will be able to add a
comment related to that data (fields), select timeline and
send it back to the service provider.
major regulations are not met, clauses of the agreement are
not in line with the regulation, or any other issues with the
agreement document.
Description-
 When CITC raised the amendment on data request, then
service provider will receive the notification related to it and
users will be able to make the changes in the agreement form.
 Post submission of the changed form, users can view marked
changes data/fields.
o Also, examiner can view which fields (all the fields)
have been changed after the amendment. Hence,
previous fields values/info and new fields values/info.
service provide will receive the notification related to it and
users will be able to upload new version of agreement
document.
maintained.
mentioned.
Note: Users will not be able to view the versioning of the

documents, instead to check the changes or modifications user
will have to go through the pdf line by line.
Fields and Validation  Validate the file size and file type.
time of submission amendment.
 Amendment request will be sent to the same examiner user
who has raised the amendment.
configurable (Default timeline will be of 30 days unless
changed by CITC examiner or wholesale interconnect
manager)
 The request for amendment needs to be sent directly from
the examiner to the service provider
 While sending for amendments the examiner can configure
the timeline on a case-to-case basis. The timeline can also be
configured by the wholesale and interconnect manager.
Raise amendment request

Select timeline in days Select submission date from
calendar
Add comment Text field to enter keyword
(mandatory), 400-500
alphanumeric char
Upload attachment PDF format (mandatory) (size
limit 20 MB)
Submit Button
7.12 VIEW LOGS
Requirement Examiners will be able to view all the agreements logs that are
Definition added by the CITC users.

agreement.
2. Users has clicked on inbox tile/section from landing page.
Post - Condition Examiner will be able to view the logs.

Clicking on “Logs” user will be displayed with pop-up displaying
two types of the Logs:
 Work Logs
 Saved Workflow Logs
Clicking on “Work Logs” user will be displayed with the work logs
that will include the trail of internal and external communication
in a form of logs that are exchanged during the agreement
approval process. This will include below details:
 Process:
from received/assigned new agreement request, sent to an
amendment request and final approval from wholesale
manager. (internal and external)
o Operator /CITC
o Previous status
o Current status
o Email
o comment
o Date and time
 Also there would be two buttons named all, and change log.
On click of any button users will be re-directed to the specific
detail page.
changes in the specific agreement and users can see the name
of changes in the fields, previous agreement, current
agreement, and date & time. Also users can select the
request ID to view the specific changes.
 On click of Saved Workflow Logs, users will be re-directed to
the page where they can view all the information related to
the approval journey, and below details will be shown.
 Saved Workflow Logs will display both side
communication (CITC and operator user) on
agreement.
Clicking on cross icon the pop-up will be closed and user will be
redirected to view amendment screen.

 In change logs, users will be able to view the changes made
from initial submission of the agreement to modification
suggested by the CITC.
o CITC user details
o Image
o CITC user
o Previous status
o Current status
o Comment
o Email ID
o Supporting documents by the user along with the date
and time.
o All
o Change logs
o Image
o CITC user
o Previous status
o Current status
o Date and time
o Comment
o Email ID
time.
o Request ID
o Fields
o Current agreement
o Date & time
Work logs Button
All Button
Change logs Button
7.13 SAVED AGREEMENTS
Requirement Examiner user will be able to view list of all saved agreements
Definition

agreement.
2. Users has clicked on saved agreement tile from landing page.
Post - Condition Examiner will be able to view details of the agreements that are
under review.
Whenever user clicks on saved agreements user will be able to
view all the agreements for which outcome has been determined
on the platform.

 Request ID
 Tracking number
 Operator submitting the agreement
 Parties to the agreement
 Date of signing
 Date of submission
 Name of agreement saved date
 Status
o Saved
 Action

Users will be able to view a tab named “all agreements” where all
type of agreement will be shown such as cancelled, rejected and
withdrawn. And in saved tab users can view only saved agreements
for that user.

 Request ID
 Date of signing
 saved date
 Status
o Rejected
o Cancelled
o Withdrawn
 Action
Search
Search By Keyword :
Users will be facilitated to search for the records using the
If the data does not matches or there is no data available user will
be displayed with message “ no record found”
Pagination
paginations.
Clicking on “View” button user will be redirected to page displaying

details of the agreements.(refer UC_7.10)
Status description
 When user raises the agreement upload request to the
operator then the status would be “requested”
 When user ask examiner to raise agreement modification
request to operator the status would be “requested”. (only in
case of asked by WSIM)
 When examiner raised the modification agreement request
then status would be “amend on data/agreement”
 When examiner receives the modification agreement from
operator then status would be “agreement under review”
 When examiner raised the amendment against the
modification request then status would be “amend on
data/agreement”
 When user approve the modification request then status would
be “saved”
 When user rejects the modification request then status would
be “rejected by the examiner”
 When user cancels the modification request then status would
be “cancel by the examiner”
would be “request other department review”
 Rejects request of examiner to send to other department then
 When examiner receives agreement back from WSIM then
 Receives modified application from Operator, after assigned
from WSIM the status would be “agreement under review”
Fields and Validation Validation:-

 In case entered parameters matches with the database then
users can view the result in a form of listing.
 Manager can toggle between saved and all agreements where
in saved listing only saved/approved agreement will be shown
and in all cancelled/withdrawn and rejected agreement will be
shown.
 If the data does not matches or there is no data available user
will be displayed with message “ no record found”
 On selection of all, users can view all the agreement with
different status types such as cancelled, rejected, withdrawn
and on click of saved, only saved agreement will be shown.
 Users will be able to view a list of saved agreements and by
clicking on any agreement they will be able to view the details.
 The agreement should contain all the associated files (word,
pdf, and excel).
 Upon saving the agreement, the system numbers the
agreement file as follows:
Year of saving + 4 sequential numbers
 Users will be able to raise modification request once it’s asked

by the WSIM.
All Tab/button
Search
Keyword search Search bar (to enter the keyword
in alphanumeric char)
View Icon Button
Requirement Examiner user will be able to view details of the agreements saved
Definition

agreement.
2. Users has clicked on agreement under review tile from landing
page.
Post - Condition Examiner will be able to view logs of the saved agreements

page where user will be able to view entire details of the agreement.
 Details
o Request ID
o Name of agreement
o Date of agreement
o Renewed Agreement
o Date of termination
o Operator
o Type of License
o Agreement Parties
o Others
o Type of agreement
o Others
o Type of services
o Others
o Currency Type
o Others
o Involved and affected parties
o Notes
o Fees Currency
o Fee Description
o Fees Value
o Add Comments
o Upload Documents
o Attachments listing (if any)
o Action
 View Logs
Descriptions:

View Logs Button
7.15 RAISE UPLOAD REQUEST
Requirement Examiner user will be facilitated to raise a request for uploading an

Definition agreement.

agreement.
2. Users has clicked on raise request button in the Agreement
listing screen.
Post - Condition Examiner user will be able to view request details

Clicking on “Raise Request” button user will be displayed with a pop
where user will be facilitated to provide below inputs:
 Request ID
 Select Service Provider
 Date of signing
 Message
 Timeline
 Upload Document
 Submit>>
User will be able to select the service provider from dropdown.
Description
 Clicking on “Submit” button the request to upload agreement
will be raised to respective service provider.
 Post submitting the request, users can view it in agreement
request listing and details. (refer to UC_7.16)

 In case WIM asked to raise an agreement request, then they can
raise an agreement upload request from this section.
 Only service provider admin will receive the agreement upload
request and later they can assign or upload the agreement
accordingly.
 On click of submit, a pop-up will appear where users will be
asked to confirm “yes” or “no”?
 On click of yes, the request will be submitted.
 On click of no, users will be re-directed to the drafted page.
Request ID Auto generated, Numeric

Service Provider Dropdown, Mandatory
Name of agreement Text box, optional
Date of signing the Gregorian Calendar, optional
agreement
Email ID Text field, mandatory
Message Text area, Mandatory
Timeline Date picker
Upload Document Button, Max size 20 MB (PDF)
Submit Button
7.16 AGREEMENT REQUEST LISTING
Requirement Examiner user will be able to view details of the agreements request
Definition list.

agreement.
2. Users has clicked on agreement request listing.
Post - Condition Examiner will be able to view the listing of agreement which they
have raised on the platform.
page where user will be able to view entire details of the agreement.

 Request ID
 Operator name
 Requested on
 Days left
 Time changed
 Action
o View
o Violation
o Flag Raise Flag/lower flag
Search (Keyword)
Users will be facilitated to search for the records using the
If the data does not matches or there is no data available user will
be displayed with message “ no record found”
Description:
 Users will be able to view raise request button on this page and
on click of it, a pop-up for raise request agreement screen.(refer
UC_7.15)
displaying details of request agreements.(refer UC_7.17)
 Clicking on “Violation” Icon, an agreement will be triggered with
the violation system of CITC.
 Clicking on “Flag” icon, the flag can be turned off and on for all
the agreement. The flag will include number of days since
deadline was lapsed.
Raise Request Button
View Button
Violation Button
Flag Button
7.17 VIEW RAISE REQUEST DETAIL
Requirement Examiner user will be facilitated to view agreement request.

Definition

agreement.
2. Users has clicked on agreement request listing screen.
Post - Condition Examiner user will be able to view agreement request

Clicking on view icon user will be displayed with request details and
will include below details
 Request ID
 Operator name
 Requested Date
 Days Left
 Message (message content)
 Uploaded documents
Clicking on back button, popup will be closed and user will be

redirected to previous screen.

Request ID Auto generated, Numeric
Service Provider Name Dropdown, Mandatory
Message Text area, Mandatory
Timeline Date picker
Upload Document button
Submit Button
7.18 Reports
Requirement Definition Examiner should be able to view all the different reports from this section.

agreement.
Post - Condition Examiner user should be able to view different kinds of reports such
as KPI.
This use case will allow users to view different kinds of reports on this
section such as KPI.
7.19 Advance search
Requirement Definition Examiner user should have the option where they can enter
agreement.
 Advance search
o Request ID
o Name of agreement
o Date of agreement
o Type of license
o Type of agreement
o Type of service
o Currency
o Fees
o Search >>
o Reset>>
Process:
given parameters.

 On click of advance search button on active agreement listing
page (Refer to UC_7.7)
UC_7.13)
On click of advance search on agreement under review listing, an

under review agreements only. (agreements that are assigned to
them)

outcome.
natural or reset.
please try again”
information:
o Request ID
o Name of agreement
o Date of agreement
o Type of license
o Type of agreement
o Type of service
o Currency list
 Fees values
 Fees currency
o Date range from (format DD/MM/YYYY)
o Date range to (format DD/MM/YYYY)

character limit
DD/MM/YYYY )

DD/MM/YYYY)

option)
option)
option)
option)
-SAR
-USD
Search Button
Reset Button

Requirement Definition Examiner User should be able to view searched results on this page.

agreement.

displayed.
 List view
o Request ID
o Name of agreement
o Date of agreement
o Type of agreement
o Status
o Action
 View details
Description:
status.
again”

again”
View details Button
7.21 INBOX
Requirement Examiners will be able to view inbox where they will be displayed
Definition with reminders. They will also be able to exchange messages with
operators.
agreement.
2. Users has clicked on inbox tile/section from home page.
Post - Condition Examiner should be able to view inbox section where they can
exchange messages and view reminder.
where users can view below tabs:
 Reminder & notification
 Deliberations (receive messages)

section.
approving the agreement, raise agreement request, updated
agreement (amendment on data and agreement), and final
decision by wholesale manager (violation/rejected/saved by
wholesale manager).
 Description
 Date and time

 New request to raise an upload request from service provider
admin
 Delay in approving the agreement
 Updated agreement on amendment (data and agreement)
 On saved agreement by wholesale manager
 On rejection by wholesale manager
 When wholesale manager will ask to raise an modification
request.
 When examiner receives the response from the department user.
 When wholesale manager sends back the agreement.
 When manager violate ongoing/assigned agreement request.

 All reminders for an application during approval process (based
on timeline / SLA) will be sent to the respective users through
the inbox feature.
 Examiner can receive the remainder and notification on the
assigned agreements.
operator users.

should allow alphanumeric with 800
to 900 characters.
Send Button
7.22 My Profile
Actors Examiner
Definition

agreement.
 Examiner name
 User name
 Email ID
 Phone Number
 Profile Photo
 Date of birth
from this section.

 Change password
o New password
o Confirm password
o Submit>>
Fields and NA
than 15 digits)
raw image and .PNG)
Change password
Submit Button
8 Wholesale Interconnection Manager (Super admin)

8.1 Login page
Actors Visitor
Requirement Definition This use case is used to define the Login process for the
Visitor users
Pre - Condition 1. The user should already have an account with the
platform to log in.
Post - Condition When user enters valid login credentials they should be able
to access the proposed system.
Whenever user clicks on the Login button, they will be asked
to enter their registered mobile number and enter the
received OTP.
1. Mobile number
2. OTP
3. Enter captcha
4. Submit>>
5. Forgot password
On click of submit button, the system will look a match in

their respective DB and if the match is found they will be
logged in as registered user. If no match is found, users can
either try again with their credentials or they can use forgot
password flow.
Password expiry- user password will be auto expiry after 90

days and the system will force to change the password.
Third-party services SMS (third-party service TBD)

1. Registered mobile number must be relevant and matched
with the interconnection agreement database.
3. In case of incorrect the system will show a message that
“you have entered incorrect OTP”
6. Users should be able to enter the captcha. And captcha
should be matched with the shown image.
7. If an invalid mobile number is entered then the web
portal shall notify the user that mobile number is
incorrect.
8. There will be a two factor authentication where users can
login through mobile and OTP.
Mobile number Text field, (Mandatory, and

allow numeric digits only)
OTP Text field, (Mandatory, and
allow numeric digits only)
Login Button
Actors Visitor user
Requirement Definition This use case is used to define forgot password flow for the
Visitor user.

This use case starts when the registered user clicks on the
“Forgot Password” button.
Once they will click on forgot password button, they will be

asked to enter their registered email ID and click submit. The
system will look for a match in the database and if a match is
found, they will be displayed a message that a reset
password link has been successfully shared on your
registered email id, please use the link to generate a new
password.
When a user clicks on the link from their email, they will be
asked to enter a password and confirm the password in 2
different fields. All validations will be the same as used while
registration. Once they set their new password, redirect
them to the login page directly.
In case the entered email id does not match with the DB,
then they will be shown a message to check the entered
email id or register with us first.

1. If the user does not enters email ID and clicks on “send
email” button it must show that “please write the email
ID”
3. If the user enters an email that does not correspond with
the Interconnection agreement database the website
shall notify the user with the text, “Record not found.”
Submit Button
8.3 Home page
Actors Wholesale manager

Requirement Definition Wholesale manager to re-direct to the home page of the web application and
view available elements.
Post - Condition User will be able to view all the available features on the platform.

navigated this page where below details will be displayed.

o Header
 Logo and name
o Tiles
 Agreement requests
 Raise agreement upload request (to
operator)
 Assign examiner to raise request
 New agreement requests (from operator)
 Active agreements
 Pending requests
 User management
 Manage department users
 Inbox
 Reports
 Timeline configurable
o My account
click)
o Footer
 FAQs
 Privacy policy
 Description-

 Agreement request: WSIM will be able to view two tiles i.e. raise
agreement upload request from Operator and assign examiner to
raise request.
o Raise agreement upload request- Manager will be able to
raise the agreement upload request to specific service
provider from this section. (Refer to UC_8.6)
o Assign Examiner to raise request- Manager will be able to
assign a particular examiner to raise an agreement upload
request from this section. (Refer to UC_8.7)
 New agreement requests. Managers will be able to receive new
agreement requests uploaded by the operators. (refer to UC_8.4)
 Agreements under review- Managers will be able to view
ongoing/under review agreements on which examiner users are
working. (Refer to UC_8.8)
 Pending Agreement - These are the agreements that are seeking
for a final decision from wholesale manager.(refer to UC_8.10)
 Manage service provider and Examiner user- Users will be able to
manage (create/edit/delete) operator and examiner users from this
section.
 Manage permissions- Users will be able to manage
(view/write/modify) the user (service provider user) permission.
 Manager Department users- Manger will be able to create
department users and provide view rights to them from this
section.
UC_8.15)
 Timeline configurable- Manager will be able to manage the default
timeline for various events.
page. Example- on click of agreement under review, users will be
re-directed to the listing page.
and 50%.
page.
 Users will be able to view advance search on the landing page,
whenever users click on it an advance search popup will
find both types of application together (open and closed).
8.4 New Agreement Requests (List view)
Requirement Definition Wholesale manager will receive a new agreement requests created
by the operator.
agreement.
2. Users should be clicked on new agreement requests.
Post - Condition Users should be able to view the list of new agreement requests.
Business Rules / Logic This use case will start when user clicks on new agreement requests,
hence they will be able to view the listing of new agreements
created by the operator and following details will be shown.
o Request ID
o Tracking number
o Operator name
o Name of agreement
o Agreement submitted date
o Request type
 New request
o Status
 Assignment pending
o Action
 Assign to examiner user
 Raise flag/lower flag

 Keyword search to enter the tracking ID
 Sorting for newest and oldest for submitted agreements
outcome.
Process:
 On click of new agreement request on the home page, users will
be re-directed to the listing page where all the newly received
agreement request and modification request will be shown.
 Advanced search will be shown in the listing parameters as well
as the advance search button.
Status description
 When user raises agreement upload request to operator the
status would be “requested”.
 When user assigns Examiner to raise agreement upload request
then status would be “assigned”
 When user receives uploaded agreement from operator then
status would be “assignment pending”
 When user assigns agreement request to an examiner then
 When user agrees to decision of examiner then status would be
“saved/rejected/cancelled”
 When user disagrees to decision of examiner then status would
be “agreement under review”
 Modification
 When user raises modification request on saved agreement then
status would be “amend data/agreement”
would be “other department review”
 When user rejects request of examiner to send to other
department then status would be “agreement under review”
 When user sends back application to Examiner to send
application back to Operator then status would be “agreement
under review”
 When user receives modification request from Operator then
Note: Pending clarification from CITC, if they want to see
operator/CITC initiated modification separately or similarly.
Fields and Validation-

Validation  Manager can assign the new modification request and new
agreement request to the examiner user.
 The assignment to an examiner is done on a manual basis by the
wholesale and interconnect manager. However, this assignment
needs to be in line with K2 system.
 The wholesale and interconnect team has external sources
through which they can know when an agreement has been
signed or not)
 Flagged can be raised in below scenarios:
operator (i.e. beyond 10 days of signing the agreement).
operator after predefined timeline set by the CITC user
(first time upload or amendment)
 In all the cases the CITC user should be able to switch off the flag
if required.
 Manager will receive any agreement upload details over email.
 Manager will receive an email if they have not assigned
examiner user. (SLA)
View detail Button
Assign to examiner Button
Raise flag Button
Wireframes:
8.5 New Agreement request details
Requirement Definition Users will be able to view the details of a particular agreement.

agreement.
2. Users should be clicked view detail in new agreement requests.
Post - Condition Users should be able to view the details of the newly received
agreement.
Whenever user clicks on view detail in new agreement listing, they
will be re-directed to this page where they can view the details in
below format.
 Details
 Request ID
 Agreement submission date
 Request type
o New request
o Modification/change request
 Annual renewal
 Date of saving agreement
 Parties of agreement
 Other
 Involved or affected parties
 Other
 Type of service
 Other
 Currency
 Fees (repetition based on the need of requester)
 Fees Description
 Other
 Fees Value
 Fees Currency
 Attachment & Annexes
 Notes (if any)
 Action
o Assign to Examiner user
o Share with internal department
o Violation
o Raise flag/lower flag
Description:
 Users will be able to view the details of new agreement and
based on the provided information manager can take further
action (assign to examiner user or share with internal
department)
 Assign agreement to examiner user- wholesale manager needs
to follow below process.
o Select examiner user
o Add comment
o Upload document
o Submit>>
 Manager can share the agreement request for inquiry (to
internal department) and below process will be followed.
 On click of share, a pop-up will appear on this page where user
can select the department, enter the email ID, add comment and
submit.
 On click of submit, application will be sent to the department
manager who can view and add the comment and re-send to the
same user.
 On click of violation an agreement will be marked as violated
and further action can be taken.
Tracking logic
 WSIM can view tracking number that is combination values for

date of signing, amount, and associated party’s code. For
example- 101221-300-0203
 To check/view if both parties have uploaded the agreement or
not users can follow the below process
o WSIM can view the list of new agreements uploaded by
different operators.
o Once a user clicks on any specific agreement they can
view details of the agreement.
o On this detail page, WSIM can view a drop-down tab
named “other parties” and on click of that users can view
a list of associated parties.
o Therefore, in case the other party has uploaded the
agreement then it will show a green dot else red (if
another party has not uploaded the agreement).
 CITC can also search for the agreement uploaded parties by
entering the tracking number. Hence, they can view list of
parties uploaded the document.
Third-party services Violation system (provided by the client)

 Manager will receive both type of agreement requests, revert on
the agreement request raised by the CITC and new agreement
request from operator.
 There will be no automatic triggering of the violation system.
User has to click manually on violation icon.
 Wholesale Interconnection manager allows to change the
request assignment from one examiner to another, provided
that no decision has been made on such request.
 Amendment agreement will be directly send to the assigned
examiner user.
 Wholesale and Interconnection Services manager selects one
examiner to whom the request is sent.
 Examiner and operators will be timelines bounded to take the
certain action described below:
o Agreement study for examiner -10 calendar days.
o Review and save the agreement (wholesale and
interconnection manager) -5 calendar days.
o Reply to the inquiry- 5 calendar days
 The internal inquiries will be sent to the concern department
manager.
 The system sends reminders to Wholesale and Interconnection
Services manager till the request is assigned to an agreement
examiner. “Kindly be informed that the request <request
number> has not been assigned yet”
 Manager can mark the agreement request as violated and assign
examiner user to take necessary actions (save, amend (on data
and agreement), reject, and cancel).
Assign to examiner user

Select examiner user Dropdown (mandatory, and single
selection option)
Add comment Text field to enter keyword (mandatory),
Upload document PDF or word format, optional, (Max limit
20 MB)
Submit Button
Share with internal department
Share Button
Select department Dropdown, (mandatory, and single
selection option)
Enter email ID Text field, mandatory (alphanumeric
char is allowed)
Add comment to share Text field to enter keyword
(mandatory), 20-25 alphanumeric char
Submit Button
8.6 Raise Agreement upload requests
Requirement Definition Users will be able to send the agreement upload request to the
agreement.
Post - Condition Users should be able to raise a request to upload an agreement.
Business Rules / Logic WSIM will be able to view two tiles inside agreement request i.e.
raise agreement upload request (to operator) and ask examiner to
raise request (refer to UC_8.7).
On click of raise agreement upload request on the tile, manager will

be re-directed to this page where they can view the agreement
upload request listing and option to raise agreement upload request
and below details will be displayed.
 Listing
o Name of agreement
o Request type
o Requested on
o Timeline
o Operator
o Days left
o Action
 View
 In view, users can view added comment and
uploaded document along with above attributes.
 Cancel
WSIM will be able to cancel the sent request to service provider

admin and then SP admin will no longer be able to take further
actions on the same.
 Raise request
o Select service provider admin
o Name of agreement
o Timeline
o Comment
o Upload document
o Submit>>
Description:
 Users will be able to view above form and can enter the
necessary details to raise the agreement request.
 On click of submit, agreement request will be sent to the specific
operator admin.
Fields and  When user raises agreement upload request to operator the
Validation status would be “requested”.
Select service provider Dropdown, (mandatory) single selection

Timeline Gregorian calendar (Mandatory)
Parties of agreement -Multiple choices (Optional)
license
-New
-Amended
- modification
Comment Text box, Mandatory, (Allow
Submit Button
8.7 Assign examiner to Raise Request
Requirement Definition Manager will assign a specific examiner user to raise the agreement
request.
agreement.
2. Users should be clicked on assign examiner to raise request.
Post - Condition Manager will assign an examiner user to raise the agreement
request.
Business Rules / Logic This use case will define the process to assign the examiner user to
raise an agreement request. Hence, manager will be able to view the
listing of raised requests and option to request examiner by filling up
below form.
 Listing
o Examiner name
o Request type
o Requested on
o Submission date of the agreement
o Operator
o Status
o Action
 View
 In view, users can view uploaded document and
added comment along with the above attributes.
 Cancel
WSIM will be able to cancel the sent request to examiner user and
examiner will no longer be able to take further actions on the same.
 Examiner request
o Select examiner user
o Enter the service provider names (from which request
will be raised)
o Name of agreement
o Select request type
 New request
o Attachment
o Add comment
o Submit>>
 On click of submit, agreement request will be sent to the

examiner user.
Process:
 Manager can assign specific examiner to raise an agreement
request.
 On click of submit, the request will be sent to the examiner user.
 Hereafter, examiner is responsible to raise the agreement
request.
Fields and Validation  While raising request to the operator :-

o The wholesale and interconnect manager can directly
raise the request to the operator to submit the
agreement.
o The wholesale and interconnect manager can assign an
examiner to raise the request to the operator to submit
the agreement.
o Therefore assignment can happen twice, once at the
beginning while raising the request and once while
reviewing the request.
Enter service provider Text field to enter keyword (optional),

names 20-25 alphanumeric char
Select examiner user Dropdown List, Mandatory
Name of agreement Text box, optional
Submission due date Gregorian Calendar, optional

Date of signing the Gregorian Calendar, optional
agreement
Upload attachment PDF format (mandatory) (size limit 20
MB)
Submit Button
8.8 Agreements under review (Active Agreement List view)
Requirement Definition Users will be able to view all the ongoing agreement which are
assigned to different examiners.
agreement.
2. Users should be clicked on agreement under review.
Post - Condition Users should be able to view the list of agreement under review.
Business Rules / Logic In agreement under review, WSIM can view two tiles i.e. Active
agreements and pending agreements (refer to UC_8.10). And on
click of active agreement they will be re-directed to this page where
list of ongoing agreements requests on the platform and following
list view will be displayed.
o Request ID
o Name of agreement
o Submission date
o Assigned examiner name
o Operator name
o Request type
 New request
o Status
 Amend on data
 Amend on agreement
 Other department review
o Action

shown.

outcome.
Process:
 On click of active agreement tile, users will be re-directed to the
listing page where all the open/ongoing assigned agreement will
be shown.
 Filters/search will be shown in the listing parameters as well as
the advance search button.
Status:
 When WISM raises the agreement upload request to operator
then status would be “requested”
 Modification
under review”

 When agreement is assigned to any examiner user, then it
should be visible in this section.
 When agreement is approved/rejected by the examiner user it
will be shown in pending requests. (refer to UC_8.10)
View detail Button
alphanumeric char)
Wireframes:
8.9 Agreement under review details (active agreement)

agreement.
2. Users should be clicked view detail in Agreements under review.
Post - Condition Users should be able to view details of the particular active
Agreements.
Business Rules / Logic This use case will start when user clicks on view detail in active
Agreement, hence they will be able to view the details of the specific
agreement and below details will be displayed.
 Details
o Request ID
o Name of agreement
o Request type
 New request
 Request update
o Progress status
 Agreement Under review
 Saved (final outcome)
o Type of license
o Type of agreement
o Type of service
 Uploaded pdf file
o Action
 Logs
 Re-allocate the agreement
Description:
 Users will be able to view the details of the agreement and can
check the current status of the agreement.
 Manager will be able to re-allocate the agreement request from
one examiner to another.
o User needs to select the new examiner user
o Add comment
o Upload
o Submit>>
Request for other department by examiner

When request sent by the examiner user for other department,
WSIM can review the details such as
 Added Comment
 Uploaded document
 Action
o Send to other department>>
o Reject (user needs to enter the comment to reject)
In case request sent to other department then examiner will directly

receive the response and WSIM will receive the notification. If WSIM
already know the concern raised by the examiner then he can add
the comment and reject the request.
Request Type:
 Request update- When modification/change request sent by the
operator in the existing agreement.
Progress status:-
to the CITC.
 Saved- when agreement is saved by the examiner user and
wholesale manager.

above listing.
 Users can view the comments in the logs section.
 Once user re-allocate the agreement from one examiner to
another then first examiner won’t be able to take further action.
“are you sure you want to Re-allocate?” “yes or no”
Logs Button
Re-allocation of agreement
Select new examiner Dropdown, (mandatory, single selection
only)
Upload document PDF, optional
Submit Button
8.10 Pending agreement requests

Requirement Definition Users will be able to view all the agreement requests coming from
examiner user. (pending listing)
agreement.
2. Users should be clicked on pending requests.
Post - Condition Users should be able to view the list pending agreement seeking for
final decision from manager.
Whenever user clicks on pending request tile, they will be re-
directed to this page where they can view following information.
o Request ID
o Name of agreement
o Submission date
o Type of license
o Type of agreement
o Assigned examiner name
o Request type
 New request
 Request update
o Status
 Saved by Examiner
 Rejected by Examiner
 Cancelled by examiner
 Request other department review
o Action

shown.

outcome.
Process:
 Whenever agreement request saved/rejected by the examiner
user, the request will be sent to wholesale manager for final
decision.
 Filters/searches will be shown in the listing parameters.
Status:
 Saved by examiner- When IA agreement is saved by the
examiner user.
 Rejected by examiner- When IA agreement is rejected by the
examiner.
 Cancelled by examiner- When IA agreement is cancelled by the
examiner due to not getting response from the operator on
certain timeline.

 Post decision made by the examiner user, the request will be
send to the wholesale manager for final decision.
 Once examiner made the decision of the agreement, then the
agreement will be sent to the manager user and listing in
pending requests.
Status:
 When user raises agreement upload request to operator the
status would be “requested”.
 Modification
under review”
View detail Button
Wireframes:
8.11 Pending Agreement details
Requirement Definition Users will be able to view the details of the pending agreements.

agreement.
2. Users should be clicked view detail in pending agreement.
Post - Condition Users should be able to view details of the particular pending
agreement and take the final decision.
Business Rules / Logic Once user click on view detail in pending agreement they will be re-
directed to this page where details will be viewed.
 Details
o Request ID
o Name of agreement
o Request type
 New request
 Request update
o Progress status
 Agreement Under review by examiner
 Saved by examiner
 Saved (final outcome)
o Type of license
o Type of agreement
o Type of service
 Uploaded pdf file
o Action
 Add comment and upload document
 Agree (users can agree for below events)
 Save
 Reject
 Cancel
 Request other department review
 Violation (trigger to violation system)
 Send back to examiner
 Share with internal department
 Logs
Description:
 Post decision of the examiner user, the agreement request will
be sent to wholesale manager where above details can be
viewed.
 On click of agree, the agreement will be deemed as final decision
on the agreement. (whether the examiner decision would be
saved, cancelled or rejected)
 On click of send to examiner, then agreement will be send back
to the same examiner for further review.
 WSIM can view if an agreement is marked as “Violated” by
examiner or not, along with the reasoning and decision
(saved/rejected/cancelled). Hence, WSIM can agree with the
examiner decision or he can send back to examiner for further
clarification.
 On clicking of “Violation” an agreement will be marked as
violated and post final decision it will be triggered to the violated
system.
 On click of share, user will be able to share the agreement with
internal department for review.
Request Type:
 New Request- When new agreement request send by the
service provider admin or service provider user.
 Request update- When modification/change request sent by the
operator in the existing agreement.
Progress status:-
to the CITC.
 Amendment- When any type of amendment request raised by
the CITC could be amend on data or amend on agreement.
 Saved- when agreement is saved by the examiner user and
wholesale manager.

 In case without entering comment users click on save or rejected
then system should display a message that “please add the
comment”.
(approved/rejected/return) in the saved agreement. Moreover,
all these documents' names, sent by, date, and time will be in
approval logs during the approval process.
 On click of saved or rejected, a pop-up will be shown to the users
stating “are you sure you want to save/reject?” “yes or no”
 Users can view the comments in the logs section.
 The Wholesale & Interconnect manager should not be allowed
to overwrite the decisions of the examiner. In case of any
disconnect, the Wholesale & Interconnect manager shall send
back the request to the examiner.
 Wholesale and Interconnect Manager will trigger the violation
system if he accepts the reasoning of violation.
 Post approval of WSIM system should display a message that
“Saving (name of agreement) of Request (request number) is
approved”.
Logs Button
Agree Button
Send back to examiner Button
Violation Check box
Share with internal Button
department
8.12 Manage users
Management.
agreement.
2. Users should be clicked on user management.
Post - Condition Users will be able to view created users and manage it from this section.

From this section wholesale manager would be able to view and
manage examiner user. The use case will define the process for the
user management.
View all user
Wholesale manager can click on this section to view all the examiner
and service provider admin. They have option to filter user type
1. Filter by
1.1. User type
1.1.1. Examiner user
1.1.2. Service provider admin
2. Search by
2.1. User name
2.2. Mobile number
2.3. Email ID
 Users will be able to filter out the examiner and service provider
admin user.
 Users will be able to search for the users by entering the name,
email ID or mobile number.
3. List view of service provider admin

3.1. User Name
3.2. Operator name
3.3. Email
3.4. Phone number
3.6. View password
3.7. Action
3.7.1. Edit
3.7.2. Delete
4. List view of Examiner user
4.1. Name
4.2. Email
4.3. Phone number
4.4. User role
4.4.1. View
4.4.2. Modify
4.6. View password
4.7. Action
4.7.1. Edit
4.7.2. Delete
Pagination
Third-party services  ERP integration (for operator admin)

 Identification number (for CITC)
 AD
 Wholesale manager needs to click on action icon to perform the
 Manager will be able to filter out the users.
 The IA management tool needs to be integrated to the employee
database for ease of role creation and sharing with other
departments.
 Details of the employee (department user) will be fetch through
the integration and will show the fetched users details only.
Search
Search Icon Button
View Icon
Edit Icon
8.1.10 Edit & Add users
Management.
agreement.
2. Users should be clicked on edit ot add users.
Post - Condition Users will be able to edit and add new users on the platform.

Wholesale manager will be able to edit and add new users on the
platform.
Edit Service provider

Clicking on “Edit” button user will be displayed with the Edit service
provider admin page having below details:
 User Name
 Operator name
 Email ID
 Mobile number
 Password
 Status
Edit Examiner
Clicking on “Edit” button user will be displayed with the Edit
examiner user page having below details:
 User Name
 Email ID
 Mobile number
 User role
 Password
 Status
Clicking on “Save” button user will be displayed with success

message and made change will be saved and reflecting in system.
Default user listing will be shown for all the latest added users.
Wholesale manager will be able to create Service provider admin

and examiner user from this section. And once created email would
be trigged to the service provider user along with password
credentials. Example- Email will be a welcome email having login
credentials:
 Email id
 Password
 Login URL
Password will be an auto generated password which can be used by
service provider admin and examiner to login to application for first
time.
Add User: (Service provider admin)

 Enter User Name
 Operator name
 Phone Number
 Email ID
 Create>>
Add User: (Examiner)

 Enter User Name
 Phone Number
 Email ID
 User role (view only access or modify rights)
o View
o Modification
 Create>>
Process for roles assignment-

 Service provider admin will get the full user rights on the
platform where they can created service provider user and
manage agreements.
 For examiner user, wholesale manager needs to select the user
modification role, then all the default features will be auto-
selected and assigned for that specific user.
 On selection of view role, then users can select the activities or
features that they want to assign for particular user.
o On selection of respective menu, all the associated sub-
menus will be auto-assigned to them. For example-
assignment of agreement upload, users can creation
different type of agreement type, view all the fields of
the agreement, and submit agreement form.
 On click of save, user will be created along with given rights.
Pagination

 Wholesale manager needs to click on action icon to perform the edit,
delete, reset password and block/unblock users.
 Once wholesale manager can create service provider admin can
examiner user then created users details will be shown in user
management list view page.
 Manager can also see search bar where they can enter keyword and
search for it.
 Manager can also search for user types by entering email ID, mobile
Add User
User Name User Name (text field with alphabetic
char with 20-25 limit ) Mandatory
Email ID (text field with alphanumeric char with

20-25 limit ), Mandatory
Phone Number Numeric, Mandatory
User Role Dropdown, Mandatory
Submit Button
Back Button
Search
Search Icon Button
View Icon
Edit Icon
8.13 Manage Roles
Requirement Definition 1. User will be able to add roles of the system.

2. User will be able to edit roles of the system.
3. User will be able to delete roles of the system.
4. User will be able to grant/revoke access to modules.
Pre - Condition 1. Users should be successfully logged-in on the Interconnection agreement.
2. Users should be clicked on manage roles.
Post - Condition User will be able to view roles created.

Whenever user clicks on Manage roles, they will be re-directed to this
page where user roles listing will be displayed and be able to perform
below activities
 Add Roles
 Edit Roles
 Search Roles
Role Listing:
Users will be displayed with all roles created so far in the system. Users
will also be able to search using search bar available on page
Search:
Users will be able to search records using keywords.
Add Role:
Clicking on “Add Role” button, user will be redirected to role creation
page with below capture fields
 Role name
 Status
 Access Rights
User will be facilitate to select the access rights to modules and its
permission (view and modify).
Clicking on “Save” button, user will be displayed with a success message

“Roles created successfully”
Edit Role
Clicking on “Edit” button user will be redirected to edit role page, with
below fields
 Role ID/Code
 Role name
 Status
 Access Rights
Clicking on save button the updates will be saved in the system.
View Role
Clicking on edit icon, user will be redirected to view role page, with below
fields
 Role ID/Code
 Role name
 Status
 Access Rights
Add Role
Status Checkbox (Default checked)
Save Button
Back Button
View Role
Role ID Label
Status Checkbox
Edit Button
Back Button
Edit Role
Role ID Label
Status Checkbox
Save Button
Back Button
8.14 Manage Department user

Requirement Definition This use case is used to view & manage the department users.

agreement.
2. Users should be clicked on department user.
Post - Condition Users will be able to view & manage the department user.

From this section wholesale manager would be able to view and
manage department user. The use case will define the process for
the user management.
View all department user
Wholesale manager can click on this section to view all the created
department users. They have option to search option
1. Search by
1.1. User name
1.2. Mobile number
1.3. Email ID
 Users will be able to search for the users by entering the name,
email ID or mobile number.
2. List view of department user

2.1. Name
2.2. Email
2.3. Phone number
2.4. User role
2.4.1. View only
2.6. View password
2.7. Action
2.7.1. Edit
2.7.2. Delete
Edit Department user
Clicking on “Edit” button user will be displayed with the Edit
department user page having below details:
 Name
 Email ID
 Mobile number
 User role (view only)
 Password
 Status
 Clicking on “Save” button user will be displayed with success

message and made change will be saved and reflecting in
system.
 Default user listing will be shown for all the latest added users.
Wholesale manager will be able to create department users from

this section. And once created email would be trigged to the service
provider user along with password credentials.
Example- Email will be a welcome email having login credentials:
 Email id
 Password
 Login URL
Password will be an auto generated which can be used by to login to

application for first time.
Add User: (Department user)

 Enter User Name
 Phone Number
 Email ID
 View role (Default checked)
 Create>>
Department user will have a default view role, which will be
assigned to the department user.
Pagination

 Wholesale manager needs to click on action icon to perform the
 Manager will be able to filter out the users.
 Employee database needs to be accessed to implement the
functionality. Discussions need to be done with CITC IT on this. In
case of any changes, the same shall be communicated.
Search
Search Icon Button
View Icon
Edit Icon
Requirement Wholesale manager will be able to view list of all saved agreements
Definition

agreement.
2. Users has clicked on saved agreement tile from home page.
agreement section.
Whenever user clicks on saved agreements user will be displayed with the
agreements that are saved by user.

 Request ID
 Tracking number
 Date of signing
 saved date
 Status
o Saved
 Action
o Violation
o Raise Modification
On click of view details, users will be re-directed to the detail page of the
agreement.


 Request ID
 Tracking number
 Date of signing
 saved date
 Status
o Rejected
o Cancelled
o Withdrawn
 Action
o Violation
o Raise Modification
Search
Search By Keyword :

 Dropdown for type of agreements
On click of raise modification, a pop-up will appear where user can add the
comment, upload document (if any) and submit. Thereafter, the request
will be sent to service provider admin.
Pagination
Advance search
of the agreements.(Refer UC_8.19)
Modification
 When user ask examiner to raise agreement modification request to
operator the status would be “requested”.
 When user sends agreement to other department then status would
be “other department review”
 When user rejects request of examiner to send to other department
then status would be “agreement under review”
 When user agrees to decision of examiner on modification request
then status would be “saved/rejected/cancelled”
 When user disagrees to decision of examiner on modification then
 When user sends back application to Examiner to send application
back to Operator then status would be “agreement under review”
 When user receives modification request from Operator then status
would be “assignment pending”
Note: Pending clarification from CITC, if they want to see operator/CITC
initiated modification separately or similarly.

 Users will be able to view a list of saved agreements and by clicking on
any agreement they will be able to view the details.
 The agreement should contain all the associated files (word, pdf, and
excel).
 Upon saving the agreement, the system numbers the agreement file
as follows:
o Year of saving + 4 sequential numbers
 Violation integration:
 Violation system is a system through which penalties can be issued to
the operator.
 A separate icon needs to be available which will be used to trigger the
violation system to issue the penalty.
 The examiner and the wholesale interconnect manager will be able to
manually click on this icon and trigger the request to the violation
system
 There will be no automatic triggering of the violation system. It needs
to be manually clicked and then only the request will be sent.
 The icon to trigger the violation system will be available on the
detailed view of the agreement submitted and on the listing page
(which shows the list of requests which have been received & under
review)
 Apart from the violation system, the employee database also needs to
be linked to the IA management tool. No other system will be linked to
the IA management tool.
 Modification request is only raised by the WSIM.
 Modification request sent by the operator user will be received by the
WSIM only and later they can assign it to examiner user.
All Tab/Button
Search
View Icon Button
Raise modification request
Add comment Free Text field, (Mandatory) with
word limit of 400-500 char.
Submit Button
Actors Wholesale manger
Requirement Definition Wholesale manager will be able to view details of the agreements
saved.
agreement.

 Request ID
 Operator
 Type of License
 Others
 Others
 Others
 Currency Type
 Others
 Notes
 Fees Currency
 Fee Description
 Fees Value
 Progress Status
o Agreement Under review
o Amendment (data/agreement)
o Other department review
o Saved
o Rejected
o Request updated
o Cancelled
o Withdrawn
 Action
o Raise modification
o Violation
o Share with competent department
 Clicking on “View Logs” users will be displayed with the logs of the
agreements. (Refer UC_8.17)
 On click of raise modification, manager will be able to raise the
modification request from operator.
Manager will be able to raise the modification against the saved

agreement and on click of raise modification, a pop-up will appear
where user can add the comment, upload document (if any) and
submit. Thereafter, the request will be sent to service provider admin.
 On click of violation, an agreement will be deemed as violated and

triggered to the violation system.
 Share agreement copy- The wholesale manager will be able to

share a saved agreement copy with the competent department.
(A saved copy will contain all the associated pdfs and agreement
form). In order to achieve it, the manager should be able to enter
the email ID, select department and click on submit.
Progress status:-
to the CITC.
 Amendment- When any type of amend request raised by the CITC
could be amend on data or amend on agreement.
 Saved- When IA agreement is approved/saved by the CITC.
 Rejected- When IA agreement is rejected by the CITC and send
back due to issues.
 Cancelled- When CITC is not getting the response within certain
time stamp then CITC can close the agreement.

 Once agreement approved by the wholesale manager it will be
deemed as saved.
 Manager can toggle between saved and all agreements where in
saved listing only saved/approved agreement will be shown and in
all cancelled/withdrawn and rejected agreement will be shown.
 Once a CITC users (examiner and wholesale manager) agree
(approves/rejects/cancelled) the particular agreement it will
notify all the associated users.
them to understand.
 Manager should be able to share a saved agreement copy with
the competent department and for that manger needs to enter
the email ID, select department and submit.
 While sharing agreement should contain pdf and form together
and department will receive both the items. (pdf and agreement
form)
View Logs Button
Violation Button
Share with competent department
Enter email ID Text button, Mandatory (allow
alphanumeric char with limit of 20-
25 )
Select department From dropdown list, mandatory
(single selection)
Submit Button
Raise modification
Raise modification request Button
Comments Free Text field, (Mandatory) with
word limit of 400-500 char.
Submit Button
Wireframes:
8.17 Logs
Requirement Definition Manager should be able to view all the logs against the agreement.

agreement.
Workflow Logs.
 Process:
On click of logs a pop-up will appear where work log, and Saved
workflow Logs button will be shown.
from assignment of new agreement request, sent to an
amendment request and final approval. (internal and external)
o Operator/CITC
o Previous status
o Current status
o Email
o comment
o Date and time
page.
specific changes.
 Saved Workflow Logs will display both side communication
(CITC and operator user) on agreement.

the CITC.
o CITC user details
o Image
o CITC user
o Previous status
o Current status
o Comment
o Email ID
time.
o All
o Change logs
o Image
o CITC user
o Previous status
o Current status
o Date and time
o Comment
o Email ID
time.
o Request ID
o Fields
o Current agreement
o Date & time
Work logs Button
All Button
Change logs Button
8.18 My Profile
Requirement Manager will be able to maintain his/ her profile from here.
Definition

agreement.
 Super admin name
 Email ID
 Phone Number
 Profile Photo
Wholesale manager will be able to edit the email, mobile number and
upload profile photo from this section.

 Change password
o New password
o Confirm password
o Submit>>
Fields and NA
than 15 digits)
raw image and .PNG)
8.19 Advance search
Actors Wholesale manager user
Requirement Definition Wholesale manager user should have the option where they can
enter different parameters to get the exact match.
agreement.
 Advance search
o Request ID
o Name of agreement
o Date of agreement
o Type of license
o Type of agreement
o Type of service
o Currency
o Fees
o Search >>
o Reset>>
Process:
given parameters.

UC_8.15)

under review agreements only. (all the ongoing agreements on the
platform)


outcome.
natural or reset.
please try again”
information:
o Request ID
o Name of agreement
o Date of agreement
o Type of license
o Type of agreement
o Type of service
o Currency list
 Fees values
 Fees currency
o Date range from (format DD/MM/YYYY)
o Date range to (format DD/MM/YYYY)
character limit
DD/MM/YYYY )

DD/MM/YYYY)

option)
option)
option)
option)
-SAR
-USD
Search Button
Reset Button
Requirement Definition Wholesale manager user should be able to view searched results on
this page.
agreement.

displayed.
 List view
o Request ID
o Name of agreement
o Date of agreement
o Type of agreement
o Status
o Action
 View details
Description:
status.
again”

again”
View details Button

8.21 Inbox
Requirement Definition Manager should be able to view inbox where they can view
remainders and notifications.
agreement.
2. Users should be clicked on inbox tile/section from home page.
Post - Condition Manager should be able to view inbox section where they can
reminders and notifications.
where users can view below separate sections:
 Inbox
 Reminders
 Notifications

section.
 These reminder & notifications will sent related to below
mentioned events.
 Description
 Date and time

 Any new agreement from service provider admin
 Approval at examiner level of the assigned agreement
 Status updates for an agreement
 On saved agreement by examiner
 On rejection by examiner
 On cancelled by examiner
 On amendment request sent by examiner (on agreement or data
request)
 On amendment response from service provider
 When user receives the response from the department user
 On request update in existing agreement from service provider

 All reminders for an application during approval process (based
on timeline / SLA) will be sent to the respective users through
the inbox feature.
 Manager will be able to receive all the reminders related to
ongoing agreements assigned to examiner user.
operator users.
Inbox (reminder and Tabs

notifications)
8.22 Reports
Requirement Definition Wholesale manager should be able to view all the different reports from
this section.
agreement.
2. Users should be clicked reports home page.
Post - Condition Manger should be able to view different kinds of reports such as KPI.
This use case will allow users to view different kinds of KPI reports on
the below parameters:-
 Number of approval provided by the examiner
 Number of rejection provided by the examiner
 Average time to approve/reject the agreement from examiner
 Most number of amendment on agreement raise by the
examiner
 Most number of amendment on data/fields raise by the
examiner

should allow alphanumeric with 800 to
900 characters.
Send Button
8.23 Timeline configurable
Requirement Definition Wholesale manager should be able to view and configure the
timeline.
Pre - Condition 1. Manager should be successfully logged-in on the interconnection
agreement.
2. Manager should be clicked on timeline configurable.
Post - Condition Wholesale manager should be able to manage the timeline for
different events.
Business Rules / Logic Wholesale manager should be able to view the default time for
various events and can change the timeline for the same.
Examiner user
 Examiner user will receive the agreement request from

wholesale manager.
 Estimated time to review is 10 business days
 Following notification & email events will be triggered
o Reminder email at the beginning of the day (5)
o Email when the duration expires/ends
Wholesale and Interconnection Services Manager

 The user will be able to review and save the agreement.
o Email when the duration expires/ends
 Service provider
 Amending the agreement (in case of requesting an amendment
to the agreement after studying)
 When the deadline ends, the request will be transferred to the
Authority.
 Amending the data/entries (in case of requesting an amendment
to the request after studying)
Authority.
Department user
 Reply to the inquiry
 Reminder email at the beginning of the day (3)
 Reminder email at the beginning of the day (4)
 When the deadline expires, a daily email is sent to the director of
the department and the concerned employee.
Request by the authority (CITC)

 Service provider will receive the commercial agreements
required by the authority.
 Estimated duration will be 10 working days to submit.
Authority
Request path for amendment of existing agreements (request by the

Authority)
 Service provider will receiving the request and amendment of the

agreement.
 Estimated duration will be 30 working days to submit.
Authority
Wholesale manager will be able to manage the above mentioned timeline

for various events however default timeline would be same as above.

 Manager will be able to manage (Add/Edit/delete) the timeline
for above events.
Edit timeline Text field
Save Button
8.24 Manage License type
Requirement Definition Wholesale manager should be able to view and manage License
types.
Pre - Condition 1. Manager should be successfully logged-in on the interconnection
agreement.
2. Manager should be clicked on manage license type.
Post - Condition Wholesale manager should be able to manage the license types on
the platform.
Business Rules / Logic Wholesale manager should be able to view the default created
license types on the platform and can also manage it from this
section.
 View license type

o Provide Facilities-Based Fixed Telecommunication
Services
o Facilities-Based Unified Telecommunication Services
License
o Provide telecommunication facilities leasing service (CSP)
o License Mobile Virtual Network Operator (MVNO)
services
o Provide wholesale infrastructure services
o Provide Internet of Things Virtual Network Operator (IoT-
VNO) services
WSIM will be able to manage the license types (Add/edit/delete)

 Create new license type
o Name of the service provider license type
o Add service name (associated to that license)
o Add>>

 Manager will be able to manage (Add/Edit/delete) license
type.
 WSIM will be able to add multiple services for specific license
type so that operators can choose the option related to it.
Add Button
Delete Button
Edit Button
9 Department user
Actors Visitor user
interconnection agreement system.
Pre - Condition 1. The user account should be created by the wholesale manager.
Department users will be created by the wholesale manager, and
login credentials will be shared over registered email.
 Email ID
 Mobile number
 Dummy password
 URL to access


 New password
 Submit>>

UC_9.2)

 Email (TBD)


mandatory
mandatory
picture)
Login Button

Change password

mandatory
9.2 Login page
Actors Visitor
Requirement Definition This use case is used to define the Login process for the Visitor
users
Pre - Condition 1. The user should already have an account with the platform to
log in.
1. Mobile number
2. OTP
3. Enter captcha
4. Submit>>
5. Forgot password

registered user. If no match is found, users can either try again
with their credentials or they can use forgot password flow.



Login Button
Actors Visitor user
user.

Password” button.
Once they will click on forgot password button, they will be asked
to enter their registered email ID and click submit. The system will
look for a match in the database and if a match is found, they will
be displayed a message that a reset password link has been
successfully shared on your registered email id, please use the link
to generate a new password.
When a user clicks on the link from their email, they will be asked
to enter a password and confirm the password in 2 different fields.
All validations will be the same as used while registration. Once
they set their new password, redirect them to the login page
directly.
with us first.

Interconnection agreement database the website shall notify
the user with the text, “Record not found.”
Submit Button
9.4 Home page
Actors Department user

Requirement Definition Users will be re-directed to the home page of the web application and
view available elements based on the user role.
Pre - Condition 1. User should be logged-in on the interconnection agreement and
clicked on Interconnection agreement.
Post - Condition User will be able to view available elements based on the user role.

 Home page
o Header
 Logo and name
o Tiles
 New inquires
 Previous inquires
 My profile
o My account
click)
o Footer
 FAQs
 Privacy policy
 Description-
 On the home page, users will be able to view above mentioned
details.
 New inquires- Users will be able to receive new inquires raised by
the wholesale manager. (refer to UC_9.5)
 Previous inquires- Users will be able to view all inquiries that they
have received on the platform. (Refer to UC_9.7)
 My profile- User will be able to view their profile where basic
information will be displayed. (Refer to UC_9.9)
Fields and Validation  On click of zoom in/out icon, users will be zoom in twice 125% and
and 50%.
page.
9.5 New inquires (List view)
Requirement Definition Users will be able to view the all newly inquires received from
wholesale interconnect manager.
agreement.
2. Users should be clicked on new inquires.
Post - Condition Users should be able to view the list of newly inquires received from
WIM.
This use case will start when user clicks on new inquires, hence they
will be able to view the listing of newly inquires received from WIM
and following details will be displayed.
o Request ID
o Operator name
o Name of agreement
o Request type
 New request
o Action

outcome.
Process:
 On click of new inquires on the home page, users will be re-
directed to the listing page where all the newly received
inquiries will be shown.

Validation
View detail Button
9.6 Inquiry detail page
Requirement Definition Users will be able to view the details of an inquiry.

agreement.
2. Users should be clicked view detail in new inquiry.
Post - Condition Users should be able to view the details of the newly received
inquiries.
Whenever user clicks on view detail in new inquiry listing, they will
be re-directed to this page where they can view the details in below
format.
 Details
 Request ID
 Request type
o New request
 Annual renewal
 Other
 Other
 Type of service
 Other
 Currency
 Other
 Fees Value
 Fees Currency
 Notes (if any)
 Action
o Add comment
o Submit>>
Description:
 Users will be able to view the details of new inquires and based
on the provided information they can revert back to the WIM.
 They will be able to revert just by adding the comment and
submit.

 They will be able to add the comment and submit to the WIM.

Submit Button
9.7 Previous inquires (List view)
Requirement Definition Users will be able to view the all previous inquires on which they
have worked.
agreement.
2. Users should be clicked on previous inquires.
Post - Condition Users should be able to view the list of previous inquires on which
they have worked.
This use case will start when user clicks on previous inquires, hence
they will be able to view the listing of previous inquires on which
they have worked till now.
o Request ID
o Operator name
o Name of agreement
o Request type
 New request
o Action

outcome.
Process:
 On click of previous inquires on the home page, users will be re-
directed to the listing page where all the previous received
inquiries will be shown.

Validation
View detail Button
9.8 Inquiry detail page
Requirement Definition Users will be able to view the details of an inquiry.

agreement.
2. Users should be clicked view detail in previous inquiry.
Post - Condition Users should be able to view the details of the previously received
inquiries.
Whenever user clicks on view detail in previously received inquiries
listing, they will be re-directed to this page where they can view the
details in below format.
 Details
 Request ID
 Request type
o New request
 Annual renewal
 Other
 Other
 Type of service
 Other
 Currency
 Other
 Fees Value
 Fees Currency
 Notes (if any)
 Action
o View added comment
Description:
 Users will be able to view the details of previous inquires.
 They will be able to view the provided comments. Also, if any
comment added by the WIM.

 They will be able to add the comment and submit to the WIM.
9.9 My Profile

Definition

agreement.
 Department user name
 Email ID
 Phone Number
 Profile Photo
Users will be able to edit the mobile number from this section.

 Change password
o New password
o Confirm password
o Submit>>
Fields and NA
than 15 digits)
raw image and .PNG)
10 Operating Environment:
The proposed system’s web application will be compatible with the following browsers
Browser Version Operating System

Internet Explorer IE 11 Windows
Mozilla Firefox Firefox 55 and above Windows & Linux
Google Chrome Google Chrome 50 and above Windows & Linux
Safari 10+ Mac OS
11 Assumption & Dependencies:

 Proposed web application (Examiner, service provider admin, and service provider user)
is aimed to be responsive in order to provide the user an optimized view of the web
application making it easy to read and navigate on all types of devices like mobile, iPad,
tablet, and desktop. It will fit on the below mentioned resolutions –
o 320x567 – iPhones and Android phones
o 568X767 - iPhones and Android phones
o 768X980 – iPads and Android Tablets
o Above 980 for Desktop
 Static Content in required languages and logo will be provided by client.

 Client will have to bear cost of all the third party APIs required for the development of
the proposed system. Any credentials required for 3 rd party integration will be shared by
the client. Integration will be done by Neosoft.
 Violation system third-party will be provided by the client.
 All the 3rd Party APIs that would be integrated with the proposed system will be finalized
before the start of the development. (Development time will be calculated based on the
number of 3rd Party APIs and complexity of the same)
 We will design and develop the above mentioned system.
 Any additional modules or workflow will result in additional time & cost.
 Theme based designed will be applied for the back-end portal.
 Admin will be able to view all type of agreements uploaded on the platform till now.
 Any changes in above scope will lead to additional time and costs.
 Web Application will be developed in English and Arabic language.
 We will use readymade themes for admin panel.
 K2 workflow needs to be created and yet to be finalized.
12 External Interfaces:
 Not yet defined. Client’s project manager and NeoSOFT’s Project Manager will work
together on it and find best 3rd party solution befitting the proposed system.
 Based on the research and type of system selected by the client to be integrated with
the proposed system, implementation time will vary.
13 Technical Requirement:
 Web application: TBD
 Database: MySql (TBD)
 Design Tools : Adobe Photoshop, Corel Draw, HTML5, CSS
14 Hardware Requirement:
NA.

03 NS Ia SRS V1.0

Uploaded by

Document Information

Original Description:

Original Title

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

03 NS Ia SRS V1.0

Uploaded by

Copyright:

Available Formats

Software Requirement Specification

Project: Interconnection Agreement

Document Control Sheet

Current Version 1.0

Project Code NS_InterconnectionAgreement_04102021

Project Name Development of Interconnection agreement

Document Type SRS Document

Frequency of Document Review Next Revision of Standards Documents

Document Creation Date 08/11/2021

Version Date Name Comments

1.0 08/11/2021 Nakul SRS Document.

User types Target platform End user capacity

Web based Portal As per user assigned role

Wholesale Manager Web based Portal Unlimited

Service provider Web based Portal Unlimited

Web based Portal As per user assigned role

 Service provider admin: https://o1ulnt.axshare.com

Actors Visitor user

Whenever user clicks on interconnection agreement in the existing

5 Service provider Admin (Operator)

Actors Visitor user

The received credentials would be following:

Moreover, users will be asked to change the password where below

 Enter old password

Now users will be able to login on the proposed system. (refer to

Third-party services  SMS (TBD)

OTP Text field (should accept numeric with

Old password Text field (Should match with dummy

5.2 Login page

Actors Service provider admin

For general login through Mobile – Users can enter their

On click of submit button, the system will look a match in their

Password expiry- user password will be auto expiry after 90 days

Third-party services  SMS (third-party service TBD)

Fields and Validation Validation:

Mobile number Text field, (Mandatory, and allow

Forgot password? Button

Enter captcha Text field (should be same as shown

5.3 Forgot password?

Actors Service provider admin

Business Rules / Logic

Fields and Validation Validation:

Enter registered email ID Text field

5.4 Home Page

Actors Service provider Admin

Whenever user successfully logged-in on the platform they will be

 Landing page/Home page

 On the home page, users will be able to view above details.

5.5 Agreement requests (List view)

Actors Service provider admin

 On click of view details, users will be re-directed to the detail

Users will be able to filter out the agreement by selecting/entering

Fields and Validation:

View detail Button

Actors Service provider admin

Fields and Validation Validation:

5.7 Agreement upload requests (to SP user)

Actors Service provider admin

 Agreement upload requests (To SP user)

Select service provider Dropdown, (mandatory) single selection

5.8 Agreement upload

Actors Service provider admin