3.

SOFTWARE REQUIREMENTS SPECIFICATION

3.1. Introduction

3.1.1. Purpose

This document describes the SRS for an cargo shipping management system. The
document is intended for both user and admin (booking, maintaining details etc..). The reader is
assumed to have basic Knowledge of Transporting details. It describes What the system will
do.

3.1.2. Document Conventions

 The font used in this document is in Times New Roman.

 The title of the main section of the document are written in bold font and font size of 18.

 The subsections are also in bold font but they are written in font size only 14.

 The details of the main sections and subsections don’t apply any font face and are written
in font size of 12.

3.1.3. Intended Audience and Reading Suggestions

This document is intended for the users, admin and developers. The SRS document also
contains some information about the product like scope, system features, assumptions and
dependencies and other useful information. We suggest the reader read the document very well to
understand including the goal of the system, the advantages and how the system will work.
3.1.4. Product Scope

The software enables the users to book the shipment. This software offers benefits such as
Insurance provider in terms of material loss/damage and Time delay. It allow the admin to fix the
Insurance Rules when required. The document applies to VB.Net. This software facilities user to
book a shipment without going to a company. This Software takes Login and password as Input.
The system based on relational database SQL server.

 Booking shipment
 View Delivery report
 Generating Mail
 Cancelation of booking.
The software is excepted to complete within the duration of 6 months3.2. Overall
Description

3.2 Overall Description

3.2.1. Product Perspective

Cargo shipping management consists of various components. This software allows user to
access features without the help of admin and access the delivery report features. Hardware
components are machinery management, power management, Alarm management, Thurster
control, Navigation.

3.2.2. Product Functions

The functions should be organized in such a way that they are understandable by
the user. Provide a functions that the software will perform.

 Booking

 Insurance claim

 Price Finder

 Changing details.
3.2.3. User Classes and Characteristics
Physical actors:
The user is one to book a shipment and access a feature and the admin is one to
maintain records, changing details and send mail to the users.

System actors:
Database : The database handles all the records.

3.2.4. Operational Environment

The Software used for the development of this project is:

Operating System : Windows

Environment : Visual Studio .net 2008

Net Framework : Version 3.5

Language : VB.net

Front end : DOT NET

Back end : MS-SQL Server

The Hardware used for the development of this project is:

Processor : 3.6 MHZ

RAM : Minimum 1GB

Hard disk : 40GB – 100GB

3.2.5. Design and Implementation Constraints

 Material name should be valid no banned products and there is some

constraints in terms of weightage in initialization of booking.

 Constraints in terms of give password 3 times if enter the wrong password

Password is locked after the 3 attempts.
3.2.6. Assumptions and Dependencies

All the data enter will be correct and up to date. This software is developed using VB.Net
as front end, SQL server as the back end .Only authorized person will be allowed inside the
system. The maintanence of the database will assigned to admin only.

3.2.7. External Interface Requirements

3.2.7.1. User Interfaces

The user interface shall follow basic window style and functionality conventions. These
interface has four tabs at the top of the screen which allows user and admin to switch different
parts of a system. The first tab have all the necessary fields for an booking. Once the submit button
is pressed shipment is booked for transporting a materials. The second tab includes features user
access when required. The third tab used by admin if any damage occur for the ship .The fourth
tab have logout button.

3.2.7.2. Software Interfaces

The software requires a properly configured version of Microsoft windows 2008 to run
the application. The computer must have VB.Net Framework. MY SQL properly installed and
configured.

3.2.7.3. Communications Interfaces

All the data transfer between user shall use the networking protocol. This ensures
unauthorized access is prohibited. This system supports Google chrome and Mozilla firefox web
browers.

3.3. System Features

3.3.1. System Feature

 Booking

3.3.1.1. Description and Priority

The Feature Booking describes the booking of shipment. Booking is Mandatory one
for shipment.
3.3.1.2. Stimulus/Response Sequences
User gives the sender and receiver details and system accepts the details and
booking a shipment.

3.3.1.3. Functional Requirements

Functional requirements focus on “booking” will invite a user to booking a
shipment.

 New user need to register the shipment before booking

 After , In booking process the user need to enter the sender and
receiver details.
 Finally user click the submit button.

3.3.2. System Feature

 Price Finder and Bill Payment

3.3.2.1. Description and Priority

The term price Finder is used to find the price for the shipment based on the distance,
weightage and no of containers used for the shipment. And Then user will pay the Service Cost

3.3.2.2. Stimulus/Response
 User gives the distance (origin to destination) and system
calculates the price based on distance.
 User gives weight of a material and system calculates the price
based on weightage.

3.3.2.3. Functional Requirements

 User either give material weight/distance to find the price.

 User Pay the service cost and bill is generate in PDF format.
3.3.3. System Feature 3
 Insurance Provider

User can claim a insurance in three types.

 Material loss/damage

 Time Delay

 Benefits

3.3.3.1 Description and Priority

The feature Insurance Provider is used to claim insurance if any loss or damage has
occurred for the Customer’s goods. Shipping management can also provide some discount to the
Customer who having a long term relationship with the Shipping management.

3.3.3.2 Stimulus/Response Sequence

User gives a material name for any problem is mandatory and system accepts a
material name and other inputs to claim a insurance.

3.3.3.3. Functional Requirements

 User gives a delay days, booking date, deliver date ,weightage to claim
insurance.
 User access a benefits to give a material weightage and period of relationship
with a company warehouse.
3.3.4. System Feature 4
 Delivery Report

3.3.4.1 Description and priority

Delivery Report is used to check whether the customers material’s

are delivered or not. If the customer wants to know their delivery details, they can

report through this system. Their report will send to the shipping management.

Then the shipping management will the send the delivery details through the mail.

3.3.4.2. Stimulus/Response Sequences

User gives a User id , ship no as input and system will produce a report based on
user inputs.

3.3.4.3. Functional Requirements

Functional requirements focus on “Delivery report”.
 User gives organization unit, ship no, User id, Sending date, E-mail.
3.4 Other Nonfunctional Requirements

3.4.1 Performance Requirements

 User satisfaction : The system is such that it stands up to user expectations.

 User Friendliness : The system is easy to learn and understand. A native user
can also use the system effectively without any difficulties.

 Memory utilization : The system response time must be less than 10 seconds.

3.4.2 Safety Requirements

All the data in system must be backup every 24 hours and copies will be stored in
another server at different locations.

3.4.3 Security Requirements

 User accessibility is censured in all ways .User are advised to change the password within
the limited period. User should not tell the password to anyone. Maximum 3 attempts to
enter the password if forgot.
 Authorized Users only can update the details.

3.4.4 Software Quality Attributes

Reliability
The system can be used by multiple users concurrently .Any user can access a system at

a time.

Availability
The system is available for a 24 hours a day.

Maintainability
The system shall provide a capability to back up the data.

Portability
The user can log in to the system at any time.

Robustness
The system will not wholly affect by a single application failure.
3.4.5 Business Rules

 User can cancel the booking within the period.

 User not permit to change a details after booking.

 User need to change a password within 2 years if not password is locked.