Software Requirement Specification

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 abbreviations……3 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

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

3

GUI

Graphical User Interface

DBA

Database Administrator

N/A

Not Applicable

References 1.4 1. IEEE “Recommended Practice Specifications” IEEE STD 830-1998

for

Software

Requirement

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

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. 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 .access of internet Product Functions 2.2 :The system will perform the following functions

4

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

Tracking

Login/Logout

Register

Administrator

Update Customer

Delete Customer

Update Luggage Status

Suggestion

Head

Add Admin

Delete Admin

Update Admin

Login/Logout Guest Book

Login Logout

Calculate Price

Pick Ups

5

'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

Customer

Head

Post Suggestions

Manages Customers Manages Database

6

Online Logistics System

Specific Requirements .3

Admin

Non-Functional 3.1 .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

OLS01 Add Admin

Requirement

Restriction/Risk

The Head of the company must be able to add .new administrators Administrators are necessary to manage the .customers and their luggage N/A

Data Format

Text, numbers, date

End Messages

.Successfully registered administrators

Identifier Title

OLS02 Update Admin

Requirement

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

Rationale

Rationale

7

Restriction/Risk Data Format

Failure to edit information may lead to .misunderstandings Text, numbers, date

End Messages

.Successfully updated administrator's information

Identifier Title

OLS03 Deactivate Administrator

Requirement Rationale

The head of the company must be able to .deactivate the administrator .Administrator fired or retired

Restriction/Risk

N/A

Data Format

Text and Numbers

End Messages

Successfully deactivated administrators

Login Management 3.2.1.1 Identifier Title

OLS04 Username

Requirement

Data Format

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

End Messages

Nil

Identifier Title

OLS05 Password

Requirement

The administrator must enter a password of .minimum 8 characters long To save the system from unauthorized access

Rationale Restriction/Risk

Rationale Restriction/Risk Data Format

Failure to supply incorrect password will not allow .the user to access the system Text and Numbers

End Messages

Nil

Customer Management 3.2.2 Login Management 3.2.2.1

8

Identifier Title

OLS06 Username

Requirement

The username must be the email ID

Rationale

.The user must be able to access the system

Restriction/Risk Data Format

Failure to supply incorrect username will not allow .the user to access the system Text and Characters

End Messages

Nil

Identifier Title

OLS07 Password

Requirement

The customer must enter a password of minimum .8 characters long To save the system from unauthorized access

Rationale Restriction/Risk Data Format

Failure to supply incorrect password will not allow .the user to access the system Text and Numbers

End Messages

Nil

Identifier Title

OLS08 Change Password

Requirement

Data Format

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

End Messages

Message Successfully Changed

Rationale Restriction/Risk

Registration 3.2.2.2 Identifier Title

OLS09 First Name

Requirement Rationale

The customer must enter his/her name to get registered To create record of the customer

Restriction/Risk

Mandatory

Data Format

Text Only

End Messages

Nil

9

Identifier Title

OLS10 Last Name

Requirement Rationale

The customer must enter his/her name to get registered To create record of the customer

Restriction/Risk

Mandatory

Data Format

Text Only

End Messages

Nil

Identifier Title

OLS11 Email ID

Requirement Rationale

The customer must submit his/her Email ID to get registered To create record of the customer

Restriction/Risk

Mandatory

Data Format

Text and characters

End Messages

Nil

Identifier Title

OLS12 Country

Requirement Rationale

The customer must submit the name of his/her country to get registered To create record of the customer

Restriction/Risk

Mandatory

Data Format

Text only

End Messages

Nil

Identifier Title

OLS13 City

Requirement Rationale

The customer must submit the name of his/her city to get registered To create record of the customer

Restriction/Risk

Mandatory

Data Format

Text only

End Messages

Nil

Identifier

OLS14

10

Title

Address

Requirement Rationale

The customer must submit his/her Address to get registered To create record of the customer

Restriction/Risk

Mandatory

Data Format

Text and characters

End Messages

Nil

Identifier Title

OLS15 Mobile Number

Requirement Rationale

The customer must submit his/her mobile number to get registered To create record of the customer

Restriction/Risk

Mandatory

Data Format

Numbers and characters

End Messages

Nil

Identifier Title

OLS16 Password

Requirement Rationale

The customer must enter a password of minimum .8 characters long To save the system from unauthorized access

Restriction/Risk

Mandatory

Data Format

Text and Numbers

End Messages

Nil

Identifier Title

OLS17 Confirm Password

Requirement

The customer must re-enter his/her password

Rationale

To verify the password

Restriction/Risk

Mandatory

Data Format

Text and Numbers

End Messages

Nil

Price Calculator 3.2.2.3 Identifier

OLS18

11

Title

Send From

Requirement Rationale

The customer must enter the name of the city where he lives To locate the customer

Restriction/Risk

Mandatory

Data Format

Text

End Messages

Nil

Identifier Title

OLS19 Send To

Requirement Rationale

The customer must enter the name of the city of the receiver To locate the receiver

Restriction/Risk

Mandatory

Data Format

Text

End Messages

Nil

Identifier Title

OLS20 Service Type

Requirement Rationale

The customer must select the type of the service .he/she wants to avail To calculate price

Restriction/Risk

Mandatory

Data Format

Text

End Messages

Nil

Identifier Title

OLS21 Weight

Requirement

The customer must enter the weight of the parcel

Rationale

To calculate price

Restriction/Risk

Mandatory

Data Format

Numbers

End Messages

Nil

Find nearest location 3.2.2.4 Identifier

OLS22

12

Title

Select City

Requirement Rationale

The customer must select one city from the drop .down menu To find nearest location

Restriction/Risk

N/A

Data Format

Text

End Messages

Show Result

Guest Book 3.2.2.5 Identifier Title

OLS23 Name

Requirement

Restriction/Risk

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

Data Format

Text Only

End Messages

Nil

Identifier Title

OLS24 Email ID

Requirement

Restriction/Risk

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

Data Format

Text and characters

End Messages

Nil

Identifier Title

OLS25 Comment

Requirement

Restriction/Risk

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

Data Format

Text

End Messages

Nil

Rationale

Rationale

Rationale

13

Suggestion, Complaints or Feedback 3.2.2.6 Identifier Title

OLS26 First Name

Requirement Rationale

The user must enter his/her name to give Suggestion, Complaints or Feedback To create record of the user

Restriction/Risk

Mandatory

Data Format

Text Only

End Messages

Nil

Identifier Title

OLS27 Last Name

Requirement Rationale

The user must enter his/her name to give Suggestion, Complaints or Feedback To create record of the user

Restriction/Risk

Mandatory

Data Format

Text Only

End Messages

Nil

Identifier Title

OLS28 Email ID

Requirement Rationale

The user must submit his/her Email ID to give Suggestion, Complaints or Feedback To create record of the user

Restriction/Risk

Mandatory

Data Format

Text and characters

End Messages

Nil

Identifier Title

OLS29 Country

Requirement Rationale

The user must submit the name of his/her country to give Suggestion, Complaints or Feedback To create record of the user

Restriction/Risk

Mandatory

Data Format

Text only

14

End Messages

Nil

Identifier Title

OLS30 City

Requirement Rationale

The user must submit the name of his/her city to give Suggestion, Complaints or Feedback To create record of the user

Restriction/Risk

Mandatory

Data Format

Text only

End Messages

Nil

Identifier Title

OLS31 Phone Number

Requirement Rationale

The user must submit his/her mobile number for providing Suggestion, Complaints or Feedback To create record of the user

Restriction/Risk

Mandatory

Data Format

Numbers and characters

End Messages

Nil

Identifier Title

OLS32 Select Subject

Requirement Rationale

The user must select the type of the comment he/she wants to make for Suggestion, Complaints .or Feedback To keep record

Restriction/Risk

Mandatory

Data Format

Text

End Messages

Nil

Identifier Title

OLS33 Comment

Requirement

Restriction/Risk

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

Data Format

Text

End Messages

Nil

Rationale

15

Pickups 3.2.2.7 Identifier Title

OLS34 Name

Requirement

The user must write his/her name

Rationale Restriction/Risk

To create record of the users who gave order for pickup Mandatory

Data Format

Text

End Messages

Nil

Identifier Title

OLS35 Company Name

Requirement

The user must write the name of his/her company

Rationale Restriction/Risk

To create record of the users who gave order for pickup Mandatory

Data Format

Text

End Messages

Nil

Identifier Title

OLS36 Pickup Address

Requirement Rationale

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

Restriction/Risk

Mandatory

Data Format

Text and Numbers

End Messages

Nil

Identifier Title

OLS37 City

Requirement

The user must provide the name of the city

Rationale Restriction/Risk

To check whether pickup can be arranged in the desired city or not Mandatory

Data Format

Text

End Messages

Nil

16

Identifier Title

OLS38 Contact Number

Requirement

Restriction/Risk

The user must provide the contact number for the pickup To create record of the users who gave order for pickup Mandatory

Data Format

'-' Numbers and character

End Messages

Nil

Identifier Title

OLS39 Pickup Date

Requirement Rationale

The user must provide the date at which pickup must be arranged To arrange pickup at the desired day

Restriction/Risk

Mandatory

Data Format

'-'Numbers and character

End Messages

Nil

Identifier Title

OLS40 Pickup Time

Requirement Rationale

The user must the time at which pickup must be arranged To arrange pickup on the correct time

Restriction/Risk

Mandatory

Data Format

':' Numbers and character

End Messages

Nil

Identifier Title

OLS41 Weight

Requirement

The user must provide the weight of the package

Rationale

To create record of the users package

Restriction/Risk

Mandatory

Data Format

Text and numbers

End Messages

Nil

Identifier Title

OLS42 Special Instructions

Rationale

17

Requirement Rationale

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

Restriction/Risk

Optional

Data Format

Text

End Messages

Nil

Tracking 3.2.2.3 Identifier Title

OLS43 Tracking Number

Requirement Rationale

The customer must enter the tracking number of the luggage To check the status of their parcels

Restriction/Risk

N/A

Data Format

Text and Numbers

End Messages

Nil

18