0% found this document useful (0 votes)
106 views6 pages

Courier Manegment System

This document describes the functional requirements for an online shopping system. It includes sections on the main and login page, product category display, product search and selection, viewing cart items, order details, and order confirmation. The functional requirements specify the purpose, inputs, processes, and outputs for each system module. The document also provides a cost estimate and project schedule for developing the online shopping system.

Uploaded by

krawariya
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
0% found this document useful (0 votes)
106 views6 pages

Courier Manegment System

This document describes the functional requirements for an online shopping system. It includes sections on the main and login page, product category display, product search and selection, viewing cart items, order details, and order confirmation. The functional requirements specify the purpose, inputs, processes, and outputs for each system module. The document also provides a cost estimate and project schedule for developing the online shopping system.

Uploaded by

krawariya
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

(SRS)
Abstract
This document fully and formally describes the requirements of the proposed
said project system. It sets out the functional and non-functional
requirements and includes a description of the user interface and
documentation and training requirements.

Introduction

Internet is attracting all type people day by day. The users are increased to
20 million in India alone. As it gets popularity there are many sites offering
products online. People have the choice to buy the product online. But all the
business segment people cant able to sell the product online because the
technology problem. Here we made an attempt to provide generalized
program to suit all the people to sell their products.

Proposed System

This general Online shopping site program will help many people who want to
sell their product online. This is general product. Each business people can
customize this program according to their requirement. So it help the many
people to sell their product online with their own site.

Hardware Requirements
Software Requirements

Functional Specification

The Functional Specification is created after the Software Requirements


Document. It provides more detail on selected items originally described in
the Software Requirements Document. Some software development
organizations combine these two documents into a single document.
The Functional Specification describes the features of the software product. It
describes the product's behavior as seen by an external observer, and
contains the technical information and data needed for the design. The
Functional Specification defines what the functionality will be, but not how
that functionality will be implemented.
The software engineer uses the Functional Specification document to create a
detailed design document that explains in detail how the software will be
designed and developed. The detailed design work may further decompose

and translate the functional requirements into pseudocode, and from there
into a computer module or program.
The functional specification translates the Software Requirements Document
into a technical description that:

Ensures that the product feature requirements are correctly


understood before moving into the next step, the software design
process.
Clearly and unambiguously provides all the information necessary to
design the software.

Developing Functional Specification Contents


The Functional Specification contents are determined by the project
manager, the software developer, and typical end-users.
The end-users are important members of this team, because they will help
ensure the software will meet the business and engineering needs of those
who will use the software. The project's user group is a good source for
information and review. For guidance on drafting a functional specification,
please see the links in the Background Material and Examples section below.

Functional Specification Scope


The Functional Specification includes specific information about each
functional requirement of the software. The Functional Specification should
describe, for each functional requirement:

Purpose - What the function is intended to accomplish.


Input - What inputs will be accepted, in what format the inputs arrive,
sources for the inputs, and other input characteristics.
Process -The steps to be performed, algorithms, formulas, or
techniques to be used. Software implementation details are not
included, however.
Output - Desired outcomes such as the output form (e.g. report
layout), the destination of the output, output volume and timing, error
handling procedures, and units of measure.

Usability items need to be included in the Functional Specification. These are


features that ensure user friendliness of the software. Examples include clear
error messages, input range checking as soon as entries are made, and order
of choices and screens corresponding to user preferences.

FUNCTIONAL DESCRIPTION:
The

problem

under

study

is

being

divided

into

several

modules/functions discussed below to understand the approach to the


solution in the broader way:
Main and Login Page : The main page, neatly designed page, here
login option is provided to login. Also new signup option is provided to
for new user to signup.
Product Category Display page : This screen display all the main
categories from this point user can select any category and they can
proceed to select the products in this category.
Product Selection Screen : This search screen. Option must be
provide to select the product based on name. select product based on
the category and based on the company. Etc.,
Product search result screen : This screen shows all the products
under the search criteria. If there are no products under this search
criteria then system will give the message that there are no products
found under this category. Also option is provided to select the
products.
View Cart Screen : View cart screen shows all the selected items,
here quantity as to be entered. And also option is provided to deselect
the products.
Order Details Screen : This screen shows the final products in the
view cart. This gives product list, quantity, Total Amount etc., So user
will get the clear information that how much is the total amount of this
selection.
Order Confirmation Screen : This is the final screen in buying
process. Here customer as confirm the order.

Detailed description of
components

Main and Login Page : The main page, neatly designed page, here
login option is provided to login. Also new signup option is provided to
for new user to signup.
Product Category Display page : This screen display all the main
categories from this point user can select any category and they can
proceed to select the products in this category.
Product Selection Screen : This search screen. Option must be
provide to select the product based on name. select product based on
the category and based on the company. Etc.,
Product search result screen : This screen shows all the products
under the search criteria. If there are no products under this search
criteria then system will give the message that there are no products
found under this category. Also option is provided to select the
products.
View Cart Screen : View cart screen shows all the selected items,
here quantity as to be entered. And also option is provided to deselect
the products.
Order Details Screen : This screen shows the final products in the
view cart. This gives product list, quantity, Total Amount etc., So user
will get the clear information that how much is the total amount of this
selection.
Order Confirmation Screen : This is the final screen in buying
process. Here customer as confirm the order.

PROJECT SCHEDULING
Cost Estimation :
The category of this system is Organic.
For this a=3.2 & b=1.05 are constant
The size of the system is 2.5 KDL(Thousand of delivered line of code)
Initial cost estimate Ei = a * (size)b
= 3.2 * ( 2.5 ) 1.05
= 8.375

EAF is Effort Adjustment Factor.


Reliability is high
--- > 1.15
Database size is normal
--- > 1.00
Complexity is very low
--- > 0.70
Programmer experience is very low --- > 1.29
Programmer capacity is normal
--- > 1.00
Language experience is low
--- > 1.07
Analyst capacity is normal
--- > 1.00
EAF = 1.15 * 1 * 0.70 * 1.29 * 1.0 * 1.07 * 1.00
EAF = 1.11
Final cost E = Ei * EAF
= 8.375 * 1.11
E = 9.30 PM
Duration:
Dmonth = a * ( EPM )b
Where a & b are constant
Here

a = 2.5 & b = 0.38


D = 2.5 * (9.30) 0.38
= 5.8339
Total Duration D = 5.8 Month
Staff = Total E / Total Duration
= 9.30 / 5.8
= 1.6( approximately 2)
Here we calculate the cost by following way. Here we assume the
programmer salary as 5000 Rs.
Here for Organic type of software the month is calculated by using
following formula:
M = 2.5 * E 0.38

Where E = Total cost


Phase
System Design
Detailed Design
Coding & Unit
Testing
Integration

Cost
0.16 * 9.30*5000
= 7440
0.258*9.30*5000
= 11997
0.4166*9.30*5000
= 19372
0.165*9.30*5000
= 7673

Phase

Month

System
Design

0.19*5.83 =
1.10
=1M

Programming 0.623*5.83 =
3.63
= 4M
Integration
0.18*5.83 =
1.04
=1M

MILESTONE

Cost

Milestone Graph
40000
35000
30000
25000
20000
15000
10000
5000
0

34485
26812

7440
5

1
1

2
Month

6
3
cost
month

You might also like