You are on page 1of 18

Software Requirement Specification For Online Logistics System

:Submitted To Sir Touseef Tahir

,COMSATS Institute of Information Technology

Lahore

Table of Contents

.1 ......................3. Introduction Purpose.3 1.1 Scope.3 1.2 Definitions, acronyms, and abbreviations3 1.3 1.4 4 References Overview.4 1.5 Overall description.4 .2 Product Perspective..4 2.1 Product Functions..4 2.2 User Characteristics...5 2.3 Constraints..6 2.4 Use Cases.6 2.5 Specific requirements...7 .3 Non-Functional..7 3.1 Functional..7 3.2

:Introduction
Purpose 1.1 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 nonfunctional requirements of OLS. The intended audience for this SRS is .all the stakeholders involved in this process Scope 1.2 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. User 2. 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 for .their deliveries Administrator is responsible for creating, editing, updating and .deleting an account Definitions, Acronym and Abbreviations 1.3 OLS Online Logistics System

GUI DBA N/A

Graphical User Interface Database Administrator Not Applicable

References 1.4 1. IEEE Recommended Practice Specifications IEEE STD 830-1998 Overview 1.5 :This document has 4 sections Introduction .1 Overall description .2 Specific requirements .3 .Supporting information .4 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 for Software Requirement

Overall Description .2
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. Product Perspective 2.1 OLS is not going to become the part of a legacy system. Its 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 .access of internet Product Functions 2.2 :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:
OLS

Customer

Administrator

Head

Tracking

Update Customer

Add Admin

Login/Logout

Delete Customer

Delete Admin

Register

Update Luggage Status

Suggestion Login/Logout Guest Book

Update Admin

Login Logout

Calculate Price

Pick Ups

'Figure 'a 2.3 User Characteristics The 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: 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

Oversees Admins Tracks luggage

Registers

Arrange Pickups

Head

Customer

Post Suggestions

Manages Customers Manages Database

Specific Requirements .3
Non-Functional 3.1

Online Logistics System

Admin

.The product will be easily accessible to the general public .1 The reliability of the software will be more than 80 % and it will run .2 .for 2 months without any faults .The system will be portable for windows operating system only .3 The customer must be able to access their account 24 hours a day, 7 .4 .days a week The system should be able to respond within minimum 0.5 and .5 .maximum 2 seconds of user interaction .The system will ensure that the privacy of its user is maintained .6 The system will fulfill all ethical requirements i.e., it will be .7 .acceptable to its user and general public .The system will not allow unauthorized access to its data .8 The system will be able to enlarge in case of more than 25000 .9 .customers The system will operate under laws and regulations set by the .10 .country's legislation Functional Requirements 3.2 Administrator Management 3.2.1
Identifier Title Requirement Rationale Restriction/Risk Data Format End Messages Identifier Title Requirement Rationale OLS01 Add Admin The Head of the company must be able to add .new administrators Administrators are necessary to manage the .customers and their luggage N/A Text, numbers, date .Successfully registered administrators OLS02 Update Admin The head of the company must be able to edit the .information of the administrators To update the OLS with respective to .administrators new information

Restriction/Risk Data Format End Messages Identifier Title Requirement Rationale Restriction/Risk Data Format End Messages Login Management 3.2.1.1 Identifier Title Requirement Rationale Restriction/Risk Data Format End Messages Identifier Title Requirement Rationale Restriction/Risk Data Format End Messages

Failure to edit information may lead to .misunderstandings Text, numbers, date .Successfully updated administrator's information OLS03 Deactivate Administrator The head of the company must be able to .deactivate the administrator .Administrator fired or retired N/A Text and Numbers Successfully deactivated administrators

OLS04 Username The username must be the special ID given to the .Administrator All the activities of the respective administrator .must be tracked Failure to supply incorrect username will not allow .the user to access the system Text Nil OLS05 Password The administrator must enter a password of .minimum 8 characters long To save the system from unauthorized access Failure to supply incorrect password will not allow .the user to access the system Text and Numbers Nil

Customer Management 3.2.2


Login Management 3.2.2.1

Identifier Title Requirement Rationale Restriction/Risk Data Format End Messages Identifier Title Requirement Rationale Restriction/Risk Data Format End Messages Identifier Title Requirement Rationale Restriction/Risk Data Format End Messages Registration 3.2.2.2 Identifier Title Requirement Rationale Restriction/Risk Data Format End Messages

OLS06 Username The username must be the email ID .The user must be able to access the system Failure to supply incorrect username will not allow .the user to access the system Text and Characters Nil OLS07 Password The customer must enter a password of minimum .8 characters long To save the system from unauthorized access Failure to supply incorrect password will not allow .the user to access the system Text and Numbers Nil OLS08 Change Password The customer must be able to change his/her password Password must be changed after some period of .time Failure to supply incorrect password will not allow .the user to access the system Text and Numbers Message Successfully Changed

OLS09 First Name The customer must enter his/her name to get registered To create record of the customer Mandatory Text Only Nil

Identifier Title Requirement Rationale Restriction/Risk Data Format End Messages Identifier Title Requirement Rationale Restriction/Risk Data Format End Messages Identifier Title Requirement Rationale Restriction/Risk Data Format End Messages Identifier Title Requirement Rationale Restriction/Risk Data Format End Messages Identifier

OLS10 Last Name The customer must enter his/her name to get registered To create record of the customer Mandatory Text Only Nil OLS11 Email ID The customer must submit his/her Email ID to get registered To create record of the customer Mandatory Text and characters Nil OLS12 Country The customer must submit the name of his/her country to get registered To create record of the customer Mandatory Text only Nil OLS13 City The customer must submit the name of his/her city to get registered To create record of the customer Mandatory Text only Nil OLS14

10

Title Requirement Rationale Restriction/Risk Data Format End Messages Identifier Title Requirement Rationale Restriction/Risk Data Format End Messages Identifier Title Requirement Rationale Restriction/Risk Data Format End Messages Identifier Title Requirement Rationale Restriction/Risk Data Format End Messages Price Calculator 3.2.2.3 Identifier

Address The customer must submit his/her Address to get registered To create record of the customer Mandatory Text and characters Nil OLS15 Mobile Number The customer must submit his/her mobile number to get registered To create record of the customer Mandatory Numbers and characters Nil OLS16 Password The customer must enter a password of minimum .8 characters long To save the system from unauthorized access Mandatory Text and Numbers Nil OLS17 Confirm Password The customer must re-enter his/her password To verify the password Mandatory Text and Numbers Nil

OLS18

11

Title Requirement Rationale Restriction/Risk Data Format End Messages Identifier Title Requirement Rationale Restriction/Risk Data Format End Messages Identifier Title Requirement Rationale Restriction/Risk Data Format End Messages Identifier Title Requirement Rationale Restriction/Risk Data Format End Messages Find nearest location 3.2.2.4 Identifier

Send From The customer must enter the name of the city where he lives To locate the customer Mandatory Text Nil OLS19 Send To The customer must enter the name of the city of the receiver To locate the receiver Mandatory Text Nil OLS20 Service Type The customer must select the type of the service .he/she wants to avail To calculate price Mandatory Text Nil OLS21 Weight The customer must enter the weight of the parcel To calculate price Mandatory Numbers Nil

OLS22

12

Title Requirement Rationale Restriction/Risk Data Format End Messages Guest Book 3.2.2.5 Identifier Title Requirement Rationale Restriction/Risk Data Format End Messages Identifier Title Requirement Rationale Restriction/Risk Data Format End Messages Identifier Title Requirement Rationale Restriction/Risk Data Format End Messages

Select City The customer must select one city from the drop .down menu To find nearest location N/A Text Show Result

OLS23 Name The guest must enter his/her name to write in the guest book To create record of the users who appeared in the guest book Mandatory Text Only Nil OLS24 Email ID The guest must submit his/her Email ID to write in the guest book To create record of the users who appeared in the guest book Mandatory Text and characters Nil OLS25 Comment The guest must write something in the comment box in order to get it published in the guest book To create record of the users who appeared in the guest book Mandatory Text Nil

13

Suggestion, Complaints or Feedback 3.2.2.6 Identifier Title Requirement Rationale Restriction/Risk Data Format End Messages Identifier Title Requirement Rationale Restriction/Risk Data Format End Messages Identifier Title Requirement Rationale Restriction/Risk Data Format End Messages Identifier Title Requirement Rationale Restriction/Risk Data Format OLS26 First Name The user must enter his/her name to give Suggestion, Complaints or Feedback To create record of the user Mandatory Text Only Nil OLS27 Last Name The user must enter his/her name to give Suggestion, Complaints or Feedback To create record of the user Mandatory Text Only Nil OLS28 Email ID The user must submit his/her Email ID to give Suggestion, Complaints or Feedback To create record of the user Mandatory Text and characters Nil OLS29 Country The user must submit the name of his/her country to give Suggestion, Complaints or Feedback To create record of the user Mandatory Text only

14

End Messages Identifier Title Requirement Rationale Restriction/Risk Data Format End Messages Identifier Title Requirement Rationale Restriction/Risk Data Format End Messages Identifier Title Requirement Rationale Restriction/Risk Data Format End Messages Identifier Title Requirement Rationale Restriction/Risk Data Format End Messages

Nil OLS30 City The user must submit the name of his/her city to give Suggestion, Complaints or Feedback To create record of the user Mandatory Text only Nil OLS31 Phone Number The user must submit his/her mobile number for providing Suggestion, Complaints or Feedback To create record of the user Mandatory Numbers and characters Nil OLS32 Select Subject The user must select the type of the comment he/she wants to make for Suggestion, Complaints .or Feedback To keep record Mandatory Text Nil OLS33 Comment The user must write Suggestion, Complaints or Feedback in the text box To create record of the users who gave .Suggestion, Complaints or Feedback Mandatory Text Nil

15

Pickups 3.2.2.7 Identifier Title Requirement Rationale Restriction/Risk Data Format End Messages Identifier Title Requirement Rationale Restriction/Risk Data Format End Messages Identifier Title Requirement Rationale Restriction/Risk Data Format End Messages Identifier Title Requirement Rationale Restriction/Risk Data Format End Messages OLS34 Name The user must write his/her name To create record of the users who gave order for pickup Mandatory Text Nil OLS35 Company Name The user must write the name of his/her company To create record of the users who gave order for pickup Mandatory Text Nil OLS36 Pickup Address The user must provide the address of the place .from where the package is to be collected To collect the package from the given location Mandatory Text and Numbers Nil OLS37 City The user must provide the name of the city To check whether pickup can be arranged in the desired city or not Mandatory Text Nil

16

Identifier Title Requirement Rationale Restriction/Risk Data Format End Messages Identifier Title Requirement Rationale Restriction/Risk Data Format End Messages Identifier Title Requirement Rationale Restriction/Risk Data Format End Messages Identifier Title Requirement Rationale Restriction/Risk Data Format End Messages Identifier Title

OLS38 Contact Number The user must provide the contact number for the pickup To create record of the users who gave order for pickup Mandatory '-' Numbers and character Nil OLS39 Pickup Date The user must provide the date at which pickup must be arranged To arrange pickup at the desired day Mandatory '-'Numbers and character Nil OLS40 Pickup Time The user must the time at which pickup must be arranged To arrange pickup on the correct time Mandatory ':' Numbers and character Nil OLS41 Weight The user must provide the weight of the package To create record of the users package Mandatory Text and numbers Nil OLS42 Special Instructions

17

Requirement Rationale Restriction/Risk Data Format End Messages Tracking 3.2.2.3 Identifier Title Requirement Rationale Restriction/Risk Data Format End Messages

The user must provide instruction regarding the handling of the package To ensure that package is delivered safely Optional Text Nil

OLS43 Tracking Number The customer must enter the tracking number of the luggage To check the status of their parcels N/A Text and Numbers Nil

18

You might also like