Software Requirement Specification For Online Logistics System Submitted To : Sir Touseef Tahir
Oct 22, 2014
Software Requirement SpecificationFor
Online Logistics System
Submitted To:
Sir Touseef Tahir
COMSATS Institute of Information Technology, Lahore
Table of Contents
.………………………………………………3 ......................1. Introduction
1.1 Purpose………………………………………………………….3
1.2 Scope…………………………………………………………….3
1.3 Definitions, acronyms, and abbreviations……3
……………………………………………………4 1.4 References
1.5 Overview……………………………………………………….4
2 .Overall description…………………………………………………….…4
2.1 Product
Perspective……………………………………..4
2.2 Product Functions…………………………………….….4
2.3 User Characteristics.……………………………….….5
2.4 Constraints…………………………………………………..6
2.5 Use Cases…………………………………………………….6
2
3 .Specific requirements…………………………………………..…….7
3.1 Non-
Functional……………………………………………..7
3.2 Functional……………………………………………………..7
Introduction:
1.1 Purpose
The purpose of this SRS document is to provide a detailed description of our software product Online Logistics System (OLS).
The main purpose of this product is to help the logistics companies to enhance their courier services by providing online services to their customers. This document describes the functional as well as non-
functional requirements of OLS. The intended audience for this SRS isall the stakeholders involved in this process.
1.2 Scope
This software product is designed to assist the logistics companies for providing online services to their customers. It will enable the
customers to track their packages by providing the reference number online fro their PC's.
The goal with this project is to create a smart, contemporary looking corporate website that will be easy to navigate and organize quite a
lot of content to make its access quick and spontaneous .The system comprises of two main characters;
1. User2. Administrator
USER will get login with respective password and Id. This website allows logistics customers to track the status of their orders online by
a reference number. It also facilitates them to schedule a pickup fortheir deliveries.
Administrator is responsible for creating, editing, updating and
3
deleting an account.
1.3 Definitions, Acronym and Abbreviations
Online Logistics SystemOLS
Graphical User InterfaceGUI
Database AdministratorDBA
Not ApplicableN/A
1.4 References
1. IEEE “Recommended Practice for Software Requirement Specifications” IEEE STD 830-1998
1.5 Overview
This document has 4 sections:1 .Introduction
2 .Overall description3 .Specific requirements
4 .Supporting information.
The overall description of the system includes product perspective, system interface, user inter face, product functions and constraints.
The specific requirements describe the functional and quality requirements of OLS and finally, the last section, supporting
information, presents the index and appendixes.
2 .Overall Description
In this section of the document over all description is now going to be given for the better understanding of the requirements. Online logistics System is helpful because it eliminates and improves the inefficiencies and difficulties such as lack of documentation, management issues, confusion, communication or data loss.
2.1 Product Perspective
OLS is not going to become the part of a legacy system. It’s a standalone project that will fulfill all the needs of its customers. It will
be very helpful for the customers of the logistic company to track their luggage by sitting any where in the world if they have the
4
access of internet.
2.2 Product Functions
The system will perform the following functions:
1. Administrator must be able to add, edit, and remove customer from the system.
2. Administrative user must be able to modify the roles of each customer as to set the access level of the customer.
3. Administrator must be able to maintain all the records of the customer.
4. Enable the customer to easily track its luggage.5. Enable the customer to know any online information about its
luggage.6. Enable the customers to register themselves directly through
the website. The figure 'a' depicts the products Functions:
5
Figure 'a'2.3 User CharacteristicsThe users of this system are the Head of the Company (admin), The DBA and the customers of the logistics system. The head of the company is the owner of the company and the DBA performs all database operations. The customers in the system are the general public and can come from different background with sometimes having very little knowledge of computer.
2.4 Constraints
The following constraints are to be imposed on OLS:
Add Admin
Delete Admin
Update Admin
LoginLogout
HeadCustomer
Login/Logout
Guest Book
Suggestion
Register
Tracking
OLS
Administrator
Update Luggage Status
Delete Customer
Update Customer
Calculate Price
Pick Ups
Login/Logout
6
1. System will not allow unauthorized access.2. Username must be the Email ID of the User.3. Password must be of minimum 8 characters.4. System must be accessible from anywhere through internet.5. The privacy of the customers must be protected against unauthorized use.6. Every customer must be given a unique identification number.7. The first name and last name field must consist of letters only of maximum 30 characters long.
2.5 Use Case
The following use case depicts the overall functionality of OLS.
3 .Specific Requirements
3.1 Non-Functional
1 .The product will be easily accessible to the general public.2 .The reliability of the software will be more than 80 % and it will run
for 2 months without any faults.3 .The system will be portable for windows operating system only.
4 .The customer must be able to access their account 24 hours a day, 7 days a week.
7
Tracks luggage
Oversees Admins
Customer
Head
Admin
Registers
Arrange Pickups
Post Suggestions
Manages Customers
Manages Database
Online Logistics System
5 .The system should be able to respond within minimum 0.5 and maximum 2 seconds of user interaction.
6 .The system will ensure that the privacy of its user is maintained.7 .The system will fulfill all ethical requirements i.e., it will be
acceptable to its user and general public.8 .The system will not allow unauthorized access to its data.
9 .The system will be able to enlarge in case of more than 25000 customers.
10 .The system will operate under laws and regulations set by the country's legislation.
3.2 Functional Requirements
3.2.1 Administrator Management
OLS01IdentifierAdd AdminTitle
The Head of the company must be able to add new administrators.
Requirement
Administrators are necessary to manage the customers and their luggage.
Rationale
N/ARestriction/Risk
Text, numbers, dateData Format
Successfully registered administrators.End Messages
OLS02IdentifierUpdate AdminTitle
The head of the company must be able to edit the information of the administrators.
Requirement
To update the OLS with respective to administrators new information.
Rationale
Failure to edit information may lead to misunderstandings.
Restriction/Risk
Text, numbers, dateData Format
Successfully updated administrator's information.End Messages
OLS03IdentifierDeactivate AdministratorTitle
The head of the company must be able to deactivate the administrator.
Requirement
Administrator fired or retired.Rationale
N/ARestriction/Risk
Text and NumbersData Format
8
Successfully deactivated administratorsEnd Messages
3.2.1.1 Login Management
OLS04IdentifierUsernameTitle
The username must be the special ID given to the Administrator.
Requirement
All the activities of the respective administrator must be tracked.
Rationale
Failure to supply incorrect username will not allow the user to access the system.
Restriction/Risk
TextData Format
NilEnd Messages
OLS05IdentifierPasswordTitle
The administrator must enter a password of minimum 8 characters long.
Requirement
To save the system from unauthorized accessRationale
Failure to supply incorrect password will not allow the user to access the system.
Restriction/Risk
Text and NumbersData Format
NilEnd Messages
3.2.2 Customer Management
3.2.2.1 Login Management
OLS06IdentifierUsernameTitle
The username must be the email ID Requirement
The user must be able to access the system.Rationale
Failure to supply incorrect username will not allow the user to access the system.
Restriction/Risk
Text and CharactersData Format
NilEnd Messages
OLS07IdentifierPasswordTitle
The customer must enter a password of minimum 8 characters long.
Requirement
To save the system from unauthorized accessRationale
9
Failure to supply incorrect password will not allow the user to access the system.
Restriction/Risk
Text and NumbersData Format
NilEnd Messages
OLS08IdentifierChange PasswordTitle
The customer must be able to change his/her password
Requirement
Password must be changed after some period of time.
Rationale
Failure to supply incorrect password will not allow the user to access the system.
Restriction/Risk
Text and NumbersData Format
Message Successfully ChangedEnd Messages
3.2.2.2 Registration
OLS09IdentifierFirst NameTitle
The customer must enter his/her name to get registered
Requirement
To create record of the customerRationale
MandatoryRestriction/Risk
Text OnlyData Format
NilEnd Messages
OLS10IdentifierLast NameTitle
The customer must enter his/her name to get registered
Requirement
To create record of the customerRationale
MandatoryRestriction/Risk
Text OnlyData Format
NilEnd Messages
OLS11IdentifierEmail IDTitle
The customer must submit his/her Email ID to get registered
Requirement
To create record of the customerRationale
10
MandatoryRestriction/Risk
Text and charactersData Format
NilEnd Messages
OLS12IdentifierCountryTitle
The customer must submit the name of his/her country to get registered
Requirement
To create record of the customerRationale
MandatoryRestriction/Risk
Text onlyData Format
NilEnd Messages
OLS13IdentifierCityTitle
The customer must submit the name of his/her city to get registered
Requirement
To create record of the customerRationale
MandatoryRestriction/Risk
Text onlyData Format
NilEnd Messages
OLS14IdentifierAddressTitle
The customer must submit his/her Address to get registered
Requirement
To create record of the customerRationale
MandatoryRestriction/Risk
Text and charactersData Format
NilEnd Messages
OLS15IdentifierMobile NumberTitle
The customer must submit his/her mobile number to get registered
Requirement
To create record of the customerRationale
MandatoryRestriction/Risk
11
Numbers and charactersData Format
NilEnd Messages
OLS16IdentifierPasswordTitle
The customer must enter a password of minimum 8 characters long.
Requirement
To save the system from unauthorized accessRationale
MandatoryRestriction/Risk
Text and NumbersData Format
NilEnd Messages
OLS17IdentifierConfirm PasswordTitle
The customer must re-enter his/her passwordRequirement
To verify the passwordRationale
MandatoryRestriction/Risk
Text and NumbersData Format
NilEnd Messages
3.2.2.3 Price Calculator
OLS18IdentifierSend FromTitle
The customer must enter the name of the city where he lives
Requirement
To locate the customerRationale
MandatoryRestriction/Risk
TextData Format
NilEnd Messages
OLS19IdentifierSend ToTitle
The customer must enter the name of the city of the receiver
Requirement
To locate the receiverRationale
MandatoryRestriction/Risk
12
TextData Format
NilEnd Messages
OLS20IdentifierService TypeTitle
The customer must select the type of the service he/she wants to avail.
Requirement
To calculate priceRationale
MandatoryRestriction/Risk
TextData Format
NilEnd Messages
OLS21IdentifierWeightTitle
The customer must enter the weight of the parcelRequirement
To calculate priceRationale
MandatoryRestriction/Risk
NumbersData Format
NilEnd Messages
3.2.2.4 Find nearest location
OLS22IdentifierSelect CityTitle
The customer must select one city from the drop down menu.
Requirement
To find nearest locationRationale
N/ARestriction/Risk
TextData Format
Show ResultEnd Messages
3.2.2.5 Guest Book
OLS23IdentifierNameTitle
The guest must enter his/her name to write in the guest book
Requirement
To create record of the users who appeared in the guest book
Rationale
13
MandatoryRestriction/Risk
Text OnlyData Format
NilEnd Messages
OLS24IdentifierEmail IDTitle
The guest must submit his/her Email ID to write in the guest book
Requirement
To create record of the users who appeared in the guest book
Rationale
MandatoryRestriction/Risk
Text and charactersData Format
NilEnd Messages
OLS25IdentifierCommentTitle
The guest must write something in the comment box in order to get it published in the guest book
Requirement
To create record of the users who appeared in the guest book
Rationale
MandatoryRestriction/Risk
TextData Format
NilEnd Messages
3.2.2.6 Suggestion, Complaints or Feedback
OLS26IdentifierFirst NameTitle
The user must enter his/her name to give Suggestion, Complaints or Feedback
Requirement
To create record of the userRationale
MandatoryRestriction/Risk
Text OnlyData Format
NilEnd Messages
OLS27IdentifierLast NameTitle
The user must enter his/her name to give Suggestion, Complaints or Feedback
Requirement
14
To create record of the userRationale
MandatoryRestriction/Risk
Text OnlyData Format
NilEnd Messages
OLS28IdentifierEmail IDTitle
The user must submit his/her Email ID to give Suggestion, Complaints or Feedback
Requirement
To create record of the userRationale
MandatoryRestriction/Risk
Text and charactersData Format
NilEnd Messages
OLS29IdentifierCountryTitle
The user must submit the name of his/her country to give Suggestion, Complaints or Feedback
Requirement
To create record of the userRationale
MandatoryRestriction/Risk
Text onlyData Format
NilEnd Messages
OLS30IdentifierCityTitle
The user must submit the name of his/her city to give Suggestion, Complaints or Feedback
Requirement
To create record of the userRationale
MandatoryRestriction/Risk
Text onlyData Format
NilEnd Messages
OLS31IdentifierPhone NumberTitle
The user must submit his/her mobile number for providing Suggestion, Complaints or Feedback
Requirement
To create record of the userRationale
MandatoryRestriction/Risk
15
Numbers and charactersData Format
NilEnd Messages
OLS32IdentifierSelect SubjectTitle
The user must select the type of the comment he/she wants to make for Suggestion, Complaints
or Feedback.
Requirement
To keep recordRationale
MandatoryRestriction/Risk
TextData Format
NilEnd Messages
OLS33IdentifierCommentTitle
The user must write Suggestion, Complaints or Feedback in the text box
Requirement
To create record of the users who gave Suggestion, Complaints or Feedback.
Rationale
MandatoryRestriction/Risk
TextData Format
NilEnd Messages
3.2.2.7 Pickups
OLS34IdentifierNameTitle
The user must write his/her name Requirement
To create record of the users who gave order for pickup
Rationale
MandatoryRestriction/Risk
TextData Format
NilEnd Messages
OLS35IdentifierCompany NameTitle
The user must write the name of his/her companyRequirement
To create record of the users who gave order for pickup
Rationale
MandatoryRestriction/Risk
TextData Format
16
NilEnd Messages
OLS36IdentifierPickup AddressTitle
The user must provide the address of the place from where the package is to be collected.
Requirement
To collect the package from the given location Rationale
MandatoryRestriction/Risk
Text and NumbersData Format
NilEnd Messages
OLS37IdentifierCityTitle
The user must provide the name of the cityRequirement
To check whether pickup can be arranged in the desired city or not
Rationale
MandatoryRestriction/Risk
TextData Format
NilEnd Messages
OLS38IdentifierContact NumberTitle
The user must provide the contact number for the pickup
Requirement
To create record of the users who gave order for pickup
Rationale
MandatoryRestriction/Risk
Numbers and character'-' Data Format
NilEnd Messages
OLS39IdentifierPickup DateTitle
The user must provide the date at which pickup must be arranged
Requirement
To arrange pickup at the desired day Rationale
MandatoryRestriction/Risk
Numbers and character'-'Data Format
NilEnd Messages
17
OLS40IdentifierPickup TimeTitle
The user must the time at which pickup must be arranged
Requirement
To arrange pickup on the correct time Rationale
MandatoryRestriction/Risk
Numbers and character':' Data Format
NilEnd Messages
OLS41IdentifierWeightTitle
The user must provide the weight of the packageRequirement
To create record of the users package Rationale
MandatoryRestriction/Risk
Text and numbersData Format
NilEnd Messages
OLS42IdentifierSpecial InstructionsTitle
The user must provide instruction regarding the handling of the package
Requirement
To ensure that package is delivered safely Rationale
OptionalRestriction/Risk
TextData Format
NilEnd Messages
3.2.2.3 Tracking
OLS43IdentifierTracking NumberTitle
The customer must enter the tracking number of the luggage
Requirement
To check the status of their parcelsRationale
N/ARestriction/Risk
Text and NumbersData Format
NilEnd Messages
18
19