BUSINESS REQUIREMENT DOCUMENT

DEVELOPMENT AND IMPLEMENTATION OF

ONLINE SHIPMENT TRACKING APPLICATION
FOR WEB
IN OUTSYSTEMS PLATFORM (Phase “0)

FOR
JONES LOGISTICS

FROM
NETLINK

P a g e 1 | 28
 DOCUMENT DETAILS
COMPANY Jones Logistics

DOCUMENT TITLE Development And Implementation Of Online Shipment Tracking

Application in Web

DATE 24th March, 2022

REF Statement of Work – Document and

Requirement discussion at Jones Logistics, United States

CLASSIFICATION Highly Confidential

DOCUMENT TYPE Business Requirement Document

RECIPIENT DETAILS
DESIGNATION Jones Logistics

COMPANY Jones Logistics

ADDRESS Jones Logistics

DOCUMENT HISTORY
VERSIO
DATE AUTHOR COMMENTS
N
24/03/2022

24/03/2022

P a g e 2 | 28
 NETLINK SERVICES PRIVATE LIMITED CONTACT DETAILS

NAME NETLINK

TITLE TBD

COMPANY TBD

CONTACT NO. TBD

EMAIL TBD
ADDRESS

WEBSITE TBD

Notice

This document contains information, which is the intellectual property of Netlink

Services Private Limited. This document is confidence and its contents, cannot be
disclosed or copied without the prior written consent of Netlink Services Private
Limited.

Copyright

© Netlink Services Private Limited. All rights reserved.

Trademarks

Other product and corporate names may be trademarks of other companies, used only
for explanation and to the owners' benefit, without intent to infringe.

P a g e 3 | 28
Contents
1. Introduction.......................................................................................................5

1.1 Project Overview.............................................................................................5

1.2 About Outsystems............................................................................................5

1.3 Brief History....................................................................................................6

1.4 General Abbreviations......................................................................................6

1.5 Proposed Solutions...........................................................................................7

2. Flow Diagram.....................................................................................................8

3. Application Launch..............................................................................................9

3.1 Web Application Launch....................................................................................9

4. Track Your Transportation Page...........................................................................10

5. Results in Grid View...........................................................................................12

5. Order Details......................................................................................................14

6. View on Map.......................................................................................................15

7. Search Another Shipment.....................................................................................16

P a g e 4 | 28
 1. Introduction

1.1 Project Overview

Jones Logistics intends to revamp the shipment tracking and other features to their
current application.

The Applications developed should provide enhanced customer experience. Hence

Jones Logistics has approached Netlink to create a better customer experience for
tracking the shipments by users.

1.2 About Outsystems

Netlink and OutSystems exist to make your IT extremely more productive, by enabling
you to deliver value to the business faster than ever. OutSystems provide the only
open, high-productivity application platform (PaaS) that makes it easy to create,
deploy and manage enterprise mobile and web applications.

OutSystems Platform enables rapid delivery of beautiful applications for all devices
utilizing responsive web design. The Platform empowers IT to attack changing business
requirements by automating core DevOps best practices such as continuous integration
and delivery, thus dramatically reducing its total cost of ownership. It is available as a
public cloud, private cloud and on-premises solution.

Hundreds of companies in 24 countries across 22 industries use OutSystems Platform

to deliver, maintain, operate and continuously evolve custom, mission critical
applications.

1.3 Brief History

OutSystems founded in the year 2001 in Portugal, Europe. The Product Management
and R&D are head quartered in Portugal, along with Professional Services. Marketing is
head quartered in Atlanta, USA.

Up until 2012, OutSystems presence was confine to Europe and the States. In the later
years, OutSystems expanded to new regions with its own funds, launching direct and
indirect operations in Brazil, South Africa, Singapore, Japan, Australia and UAE

P a g e 5 | 28
 1.4 General Abbreviations
TBD To be discussed

UI/UX User Interface/User experience

N/A Not applicable

OS OutSystems

P a g e 6 | 28
 1.5 Proposed Solutions
Jones Logistics intends the customers should be able to search and track their
shipments using the tracking identification number, order number or the reference
numbers and view the details on the map as well. Below are the specified versions to
be used for the Web

No. Platform Channel Version Orientation

Responsive based on the screen

size. If the customer is using an
Chrome >35 older version, Need to show “Best
viewed in Latest version”. Will
confirm the feasibility
Responsive based on the screen
size. If the customer is using an
IE >9
older version, Need to show “Best
1 Web viewed in Latest version”.
Responsive based on the screen
size. If the customer is using an
Firefox >8
older version, Need to show “Best
viewed in Latest version”.
Responsive based on the screen
size. If the customer is using an
Safari >9
older version, Need to show “Best
viewed in Latest version”.

Mobile Device Browser Portrait and Landscape in Mobiles

Responsive based on the screen

Desktop Web
size
Web
IOS/Android
Application is Responsive based on the screen
2 Large Devices and
accessible in size
Web
the Devices

Phablet Device Browser Portrait and Landscape in Phablet

Tablet Device Browser Portrait and Landscape in Tablets

P a g e 7 | 28
2. Flow Diagram

P a g e 8 | 28
 3. Application Launch

3.1 Web Application Launch

Functional Requirements

Customer should be able to navigate to ‘Track Your Transportation’ through Jones Logistics
main website

 Customer can also access the application by entering the direct URL in the Web
browser.

 Both Logged-In and Non-Logged In Users can access this page.

 English will be default language for the web application

Validations

 NA for this module

Error Flows

 If the application experiences bad network, the application must throw an error
“Network lost! Please check your network settings.”

 Web Application should accept HTTPS request only. Any other protocol used should
redirect the user to the right protocol page.

 Web Application should handle 404 error pages. Error page needs to direct to ‘Page
Not Found’ designed page.

P a g e 9 | 28
Reference Screenshots

4. Track Your Transportation Page

Functional Requirements

 User will be able to see a Search Bar with Hint Message “Enter Your Tracking#,
Order#, Reference#” and a Track button.
 Partial Search is applicable and once the user provides the valid search input,
autosuggestions will be displayed if entered value matches with any “Reference#,
Order#, Tracking#”.
 User can enter the appropriate search criteria (Alphanumeric) and click Track
button, for single order result, it will be displayed on the “Order Details” page and
for multiple results, they will be displayed on “Track Your Transportation” page in
grid format.

Non-functional Requirements

 Application load time to be not more than 3 seconds

 Jones Logistics Logo and Static Message Screen under Search bar

Validation

P a g e 10 | 28
  Minimum 5 characters should be entered in order to do Partial Search and
Maximum 30 characters should be allowed in the search bar.

Error Flows

 If less than 5 characters are entered and Track button is clicked, then display
“Enter atleast 5 characters”
 If more than 30 characters are entered and Track button is clicked, then display
“Enter less than 30 characters”
 When the search field is empty and Track button is clicked, ‘Please Enter Search
Criteria’ is displayed.

Reference Screenshots

P a g e 11 | 28
 5. Results in Grid View
Functional Requirements

 The user must be able to see a grid view when there are multiple results for a
search done on Track Your Transportation page.
 The Grid must display the following columns:

o Order Number
o Tracking Number
o Reference No(s)
o Origin
o Destination
o Pick Up Date
o Delivery Date
o Status
 The order number in Order Number column must be a hyperlink which redirects to
the Order Details Page.
 If a Tracking number is not associated with an order, then the Tracking Number
column must be blank.
 In Origin and Destination column, the order’s Origin and Destination City and State
name must be displayed in format City, ST e.g., Minneapolis, MN.
 In Pick-up Date and Delivery Date column, the format of the date should be
MM/DD/YYYY
 If multiple Reference numbers are associated with an order, then in the search
result grid, under Reference Number column, a link as “View Reference No’s”
should be displayed on clicking of which a pop box should be displayed.
 Status of the Order is displayed in the Status column. The following statuses can be
displayed in the Status column: -

1. Available
2. Planned
3. Started
4. Completed

 Sorting functionality will be available on all the columns in the grid.

 Pagination functionality will be available on the screen.
 Functionality to view number of Rows in the grid should be available, e.g., 25. 50,
75. 100. Default number of rows in search result grid should be maximum 25.

Error Flows

 When user enters partial or complete “Reference Number, Tracking Number or Order
Number” and click on Track button and application doesn’t find any number same as

P a g e 12 | 28
 entered search criteria then application should display a verbiage on the screen as
“No Data Found”

Reference Screenshots

P a g e 13 | 28
5. Order Details
Functional Requirements

 When the user searches for an order by entering Tracking#, Order#, Reference# and
the result is a single order or when the user clicks on Order Number hyperlink on
Search Result Grid for multiple order results, the user is redirected to the Order
Details Screen and the following is displayed: -

1. Order Status
2. Progress Bar (Awaiting Pickup, In Transit, Delivered)
3. Order Details
4. View on Map

 The current status of the Order will be displayed on the progress bar along with the
Delivery or Expected Delivery Date.
 Order Details and View on Map will be displayed in accordion.
 When user clicks on order details then application should display the following fields

1. Order Number
2. Tracking Number
3. Reference Number
4. Pick Up Date
5. Delivery Date/ Expected Delivery Date

Reference Screenshot

P a g e 14 | 28
6. View on Map
Functional Requirements

 On the click of View on Map Accordion the user will be displayed a Map wherein the
current location of the Truck will be displayed.
 The last location of the Truck (Transportation Vehicle) will be displayed if Truck GPS
is lost due to network connectivity.
 User will be able to zoom in and out in the Map.

Reference Screenshot

7. Search Another Shipment

Functional Requirements

 The User will be able to search for another shipment on Order Details Page.
 The Search field must display a hint text “Search Another Shipment”.
 When partial or complete “Reference Number, Tracking Number or Order Number” is
entered in the search text box then application should display autosuggestions if the
entered number matches with any “Reference#, Tracking# or Order#”.
 Once either the Tracking number, Order number or Reference number is entered,
and ‘Track’ button is clicked, for a single order result, the result would be displayed

P a g e 15 | 28
 on the Order Details Page and for multiple orders, the user is redirected to Track
your Transportation page and the results are displayed in a grid format.

Validation

 Minimum 5 characters should be entered in order to do Partial Search and

Maximum 30 characters should be allowed in the search bar.

Error Flows

 If less than 5 characters are entered and Track button is clicked, then display
“Enter atleast 5 characters”
 If more than 30 characters are entered and Track button is clicked, then display
“Enter less than 30 characters”
 When the search field is empty and Track button is clicked, ‘Please Enter Search
Criteria’ is displayed.

Reference Screenshot

P a g e 16 | 28
8. User Management
8.1 User Creation
Functional Requirements

 System admin can create new users from the User Management Section

 When the System Admin clicks on Create User option from the left navigation
panel, the following sections would be displayed:
a) Username : Text Box
b) First Name : Text Box
c) Last Name: Text Box
d) Roles: Dropdown
i. The roles dropdown will have two options – System Admin and Customer
Admin
e) Company: Search Text Box
f) Page Access: Box
g) Buttons : Submit and Cancel
i. Once the details are provided system admin can “Submit” the details by
clicking on the “Submit” button or click “Cancel” to discard the changes.
ii. If the system admin clicks on “Submit”, the new user will be created and the
system admin will navigate to the “View users” page.

 When the role is selected as “System Admin”:

i. The “Company” textbox will be disabled
ii. The page access section must be auto-selected and disabled for edits.

 When the role is selected as “System Admin”:

iii. The “Company” textbox will be disabled
iv. The page access section must be auto-selected and disabled for edits.

Validation

 Following will be mandatory:

o User Name
o First Name
o Last Name
o Company
o Roles

Error Flows

 If the fields are left as blank and submit is clicked, the message must be displayed
as “Mandatory fields”.

P a g e 17 | 28
P a g e 18 | 28
8.2 View Users

Functional Requirements

 Once the users are created by System Admins, they can view all the users in the
“View Users” page.
 The page would display the users under the following columns:
o User Name
o First Name
o Last Name
o Company
o Roles

 The last column will include Actions that can be performed against the existing
users. These include –Edit and Delete. Others (TBD)

 The “Search” textbox will be displayed to provide the search input.

 The page will have search and reset buttons.

i. When the admin enters the search input and clicks on “Search button”, the details
would be displayed if matched.
ii. When the admin clicks on the “Reset” button, the search criteria would be cleared
and the text box would be blank.

 User Name would be a hyperlink. When the admins clicks on the username, they
will navigate to the user details page and can view the details.

 There would be three buttons- Update, Delete and Cancel.

Error Flows

 If the search inputs are not matched, the message would be displayed as “No
Records Found”.

P a g e 19 | 28
8.3 Edit Users

Functional Requirements

 On the view user’s page, the User Name field would be a hyperlink which when
clicked would navigate the users to the user details page.
 Also, under the actions menu column, there would be an option for directly
“Editing” the users.
 When the Edit option is clicked they system admins would be navigated to the user
details page in the “Edit mode”.
 The user details page would have the option to “Edit user”.
 When the Edit user is clicked from the user details section the fields will be
displayed in editable mode:
 First name
 Last Name
 Role
 Status
 Company
 When the Role is updated to “System Admin”, the below fields would be disabled:
a. Company
 When the Role is updated to “Customer Admin”, the below fields would be enabled:
a. Company
 When the Status is updated to “Active”, the following changes would be reflected
on the view users page:
 Users would be reflected under the Active status column
 When the Status is updated to “In Active”, the following changes would be reflected
on the view users page:
 Users would be reflected under the In Active status column
 No actions would be performed against these user except “Deletion”. All other
actions, if any, will not be displayed in the actions column.

Validation

 Following will be mandatory:

o User Name

P a g e 20 | 28
o First Name
o Last Name
o Company
o Roles

Error Flows

 If the fields are left as blank and submit is clicked, the message must be displayed
as “Mandatory fields”.

P a g e 21 | 28
8.4 Delete User
Functional Requirements

 Deletion can be performed from two areas

o View users page: Under the actions menu, the option would be displayed to
“Delete” the users
o User profile details page: Once the user navigates to the user profile page
by clicking on the edit icon or the user name hyperlink from the list of users,
they can view the “Delete” button on the profile details section.

 Once the user has been deleted, the following changes will be visible on the view
users page
a. The user and the details will not be displayed on the view user section
b. Total count of users to be reduced.

Validation
 The confirmation message would be displayed as “Are you sure you want to delete
the user?” with the “Yes” or “No” option. If the “Yes” is selected, the system will
continue to delete the user else it will discard the deletion.

P a g e 22 | 28
9. Role Management
9.1 View, Edit and Delete Role

Functional Requirements

• The user will be able to view all the roles in the system in a grid view in Manage
Roles page.

• The user will be able to search for a role via the search bar.

• The user will be able to select a Role Status via the Dropdown Button:

o All
o Active
o Inactive

• The user will be able to click on submit button and the results will be displayed in a
grid.

• The Grid will have the following columns:

o Role Name
o Role Description
o Role Status
o Created Date
o Updated Date
o Last Updated by

• The role name under Role Name column will be a hyperlink, which will redirect the
user to Add Role page when clicked.

• The user can then edit the appropriate role and click Submit button, which will be
reflected in the grid in Manage Roles page.

• Each row in grid will have a checkbox, the user can select single or multiple
checkboxes and Delete the role(s) using Delete button.

Error Flows

• If a user searches for a Role Name and no result is found then display “No Roles
Found”.

• If a user selects a value from the drop down and no result is found then display “No
Results Found”

P a g e 23 | 28
9.2 Add Role

Functional Requirements

• The User will be able to add a role via Manage Roles page.

• When Add Role is clicked the user will be redirected to Add Role page.

• The user will be displayed the following things:

o Role Name (Textbox)

o Role Description (Text area)
o Status (Toggle Button)
o Pages Name (Checkboxes)

• The checkboxes on Pages determine access to those pages, hence the user can
select the appropriate checkboxes while creating a role.

• When the data is filled and Submit is clicked, the role will be reflected in Manage
Roles page.

• If an active role is created then it will be displayed on Create User Page under Roles
dropdown.

Validations

• Role Name textbox is mandatory

Error Flows

• If Role Name is left blank and Submit is clicked then display “Please Enter Role
Name!”.

• If Role Name matches with any existing Role Names then display “Role Name already
exists!”

P a g e 24 | 28
10. Notifications
Functional Requirements

 The user will be able to see all the notification templates in Notification tab in grid
view
 The grid will have the following columns
o Template Name
o Template Description
o Created Date
o Updated Date
o Last Updated By
 Each row consisting of the template will have a checkbox, by selecting a checkbox or
multiple checkboxes the user can opt to edit or delete, single or multiple templates.
 The user can add a new template by clicking on “Add a Template button” on
Notifications page, the user will be redirected to Add a Template page.
 The user will see the following details:
o Template Name (Textbox)
o Template Description (TextArea)
o Save Button
 The User must fill the appropriate data and when Save is clicked the details will be
saved and will reflect on Notifications page.

Non-Functional Requirements

 The template would feature like a Mail Box.

Validations

 Template Name is a mandatory field.

Error Flows

 If Template Name is left blank and Save is clicked then display “Please Enter
Template Name!”.
 If Template Name matches with any existing Template Names then display
“Template Name already exists!”

P a g e 25 | 28
11. Reports
Functional Requirements

 From the left navigation panel, users can navigate to the “Reports” section.
 System Admins can view and download the reports.

10. Terms and Conditions

10.1 Setup
Functional Requirements
 This section is to setup the terms and conditions. System admin can view, edit
and update the terms and conditions document that the user has to agree and
accept during the registration process.

Validation
 Valid document formats are supported (eg: pdf’s and word files)

Error Flows
If the invalid documents are uploaded, the error message would be displayed as “File
Format not supported”.

11. Terms and Conditions

Functional Requirements

 The user should be able to Log in using Email ID and Password

 On Log in page the user will see the following:
o Email ID (Textbox)
o Password (Textbox)
o Forgot Password? (Hyperlink)
o Remember Me (Checkbox)
o Log in button
 The user must enter Email Id and password and click Login in order to login into the
system.

P a g e 26 | 28
  The user would be given 3 attempts for to log in. After 3 failures, the user will not be
allowed to log in for 1 hour.
 On selecting the Remember Me checkbox the user will be able to access the landing
page directly, the next time they access the website without having to log in again.
 If a user forgets their password, they can click on Forgot Password? Hyperlink which
will redirect the user to Forgot password page, via which they can get password
reset email on their Email.

Validations

 The Email ID format should be valid.

Error Flows

 If Email ID and Password are not valid, display “Enter Valid Credentials”
 If Email ID or Password are incorrect, display “Incorrect Credentials”
 If Email ID or Password are kept blank and Log In is clicked then display “Enter your
Credentials!”

12. Multi Factor Authentication

Functional Requirements

 In Multi Factor Authentication Page the user will be displayed the following:
o Enter Mobile Number (Textfield)
o Enter OTP (Textfield)
o Resend OTP (Hyperlink after 30 seconds)
o Confirm OTP button
 Once Log in is successful, the user will be asked to enter their Mobile Number and
the system will send an OTP on the user’s mobile and the user must enter the OTP
and click “Confirm OTP” button to access the landing page.
 The user will be able to generate another OTP by clicking on Resend OTP which
activates 30 seconds after the first OTP is sent.

Validations

 Each OTP will be valid for 10 minutes.

Error Flows

 If entered OTP is incorrect then “Incorrect OTP” would be displayed.

13. Registration
Functional Requirements

 The User should be able to Register themselves into the system.

 The Registration Page will display the following information:
o Email ID (Textbox)

P a g e 27 | 28
 o First Name (Textbox)
o Last Name (Textbox)
o Password (Textbox)
o Confirm Password (Textbox)
o Terms and Conditions (Checkbox and hyperlink)
o Register Button
 The User must enter valid details and select the checkbox and click on Register
button to get themselves Registered.
 User can click on Terms and Condition hyperlink and a pdf would be displayed.
 Password must be 8 characters (Alphanumeric) and must include 1 special character.
 Once the user is registered a confirmation email is sent to the user by the system.
 Once the user is registered, the user has to Login In and go through the Multi Factor
Authentication to access the system.

Validations

 The user must select the Terms and Conditions checkbox to Register themselves.
 Email ID format must be Valid.
 Email ID and Password are mandatory fields.

Error Flows

 If Email ID is not valid, display “Enter Valid Email ID”

 If password is not alphanumeric and 8 characters with 1 special character, display
“Invalid Password”

P a g e 28 | 28