Scribd
Upload
117 views6 pages

Software Requirements Specification For Online Courier Tracking System

The document outlines requirements for a FedEx courier tracking mobile application. It allows customers to track packages by entering a tracking ID or barcode number. The app will provide real-time status updates via the app, SMS, or email. It aims to reduce misdelivered packages and allow users to view nearby location details. The app must be deployed on Google Play, perform within 2 minutes of loading, and be accessible through authenticated administrators on encrypted backend servers. Repairs must be addressed within 1 hour. The app requires standard Android hardware and software including Android OS, Java web server, Oracle database, and JDBC connectivity.

Uploaded by

Gaurav Jain
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
117 views6 pages

Software Requirements Specification For Online Courier Tracking System

The document outlines requirements for a FedEx courier tracking mobile application. It allows customers to track packages by entering a tracking ID or barcode number. The app will provide real-time status updates via the app, SMS, or email. It aims to reduce misdelivered packages and allow users to view nearby location details. The app must be deployed on Google Play, perform within 2 minutes of loading, and be accessible through authenticated administrators on encrypted backend servers. Repairs must be addressed within 1 hour. The app requires standard Android hardware and software including Android OS, Java web server, Oracle database, and JDBC connectivity.

Uploaded by

Gaurav Jain
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 6

Software Requirements Specification for FedEx Courier Tracking System

1. Introduction

1.1 Purpose:

The purpose of this SRS document is to provide a detailed overview of


our software product, its parameters and goals. This document describes
the project's target audience, hardware and software requirements. It
defines how our client, team see the product and its functionality.
Nonetheless, it helps any designer and developer to assist in software
delivery lifecycle processes.

1.2 Scope:

The System will help the customers to retrieve the current status of their
consignments. FedEx mobile application will be a installation
requirement to track the shipment.

1.3 References:

 Google
2. Overall Description

2.1 Problem Definition:

FedEx courier tracking application is a mobile application that helps


customers to track the progress of their packages online. It allows
customers to download the app and enter their Tracking id. The status of
their package is displayed to the customer. The application is also
planned to provide the status via sms or email in further releases. The
tracking system internally allows branches to share information
regarding the status of consignments among themselves. To summarize,
the online courier tracking system offers following advantages:

 It offers real-time package statuses to its customers


 It reduces the risk of wrongly routed delivery
 A way to provide customers the location of all the nearby centers
 Mechanism for customers to check the estimated pricing of
package they wish to deliver to their chosen location
3. Specific Requirements

3.1 Functional Requirements:

Package module:
This module shall correspond to the tracking of packages.

Locations module:
The system shall allow user to check all the nearby locations of the
FedEx delivery centers

Login module:
The system shall allow the customer to log in into his profile.

Choice of tracker module:


This module shall allow user to enter the choice of tracker i.e. whether they
wish to track using tracking id or barcode.

Pricing module:
The system shall allow user to enter the order information and check the
estimated pricing for their package.
3.2 Non Functional Requirements:

Performance Requirements

 The product shall be based on mobile and will be deployed on


Google play platform for all users.
 The product shall take initial load time depending on internet
connection strength which also depends on the media from
which the product is run.
 The performance shall depend upon hardware components of
the client/customer.

Security:
 The system’s back-end servers shall only be accessible to
authenticated administrators.
 The system’s back-end databases shall be encrypted

Maintainability:

Repair time shall be within 1 hour.

Supportability:
 There are no memory requirements
 The product must be stored in such a way that allows the
client easy access to it.
 Response time for loading the product should take no longer
than 2 minutes.
System Specifications:

Hardware Requirements

 Standard Hardware requirements for Android OS

Software Requirements

 Android OS
 Web/Application Server: Java Web Server2.0
 Database Server: Oracle
 Database Connectivity: JDBC
 Other Tools & Technologies: Android Studi

You might also like