The document provides a software requirement specification for an online shopping system. It describes the purpose as creating a web-based application for online shopping. It outlines the intended users, product perspective and functionality. The product allows customers to view item details, make purchases and returns. Administrators can add, update and manage inventory. Non-functional requirements include cost estimation, pricing, network bandwidth needs and flexibility for regulatory changes. UML diagrams including use case, class, sequence and collaboration diagrams are proposed to model the system design. Testing strategies like unit, integration and system testing are described.

1. ONLINE SHOPPING SYSTEM
Software Requirement specification
AIM:
To prepare a software requirement specification for online Shopping system.
TABLE OF CONTENTS
1 INTRODUCTION
1.1 DOCUMENT PURPOSE
1.2 PRODUCT SCOPE
1.3 INTENDED AUDIENCE AND DOCUMENT OVERVIEW
1.4 DEFINITIONS, ACRONYMS AND ABBREVIATIONS
1.5 DOCUMENT CONVENTIONS
2 OVERALL DESCRIPTION
2.1 PRODUCT PERSPECTIVE
2.2 PRODUCT FUNCTIONALITY
2.3 USERS AND CHARACTERISTICS
2.4 OPERATING ENVIRONMENT
3 SPECIFIC REQUIREMENTS
3.1 FUNCTIONAL REQUIREMENTS
3.2 NON FUNCTIONAL REQUIREMENTS
3.3 NETWORK BANWIDTH
3.4 FLEXIBILITY

2. 1. INTRODUCTION
1.1 Document Purpose and scope:
The main purpose of the system is to create a web based application for performing
shopping.and.The purpose scope is to present an efficient, reliable online shopping.
1.2 Intenended Audience and Document Organization
The intended users are the responsible for implementing the online shopping. This document
describes the online shopping system requirements in terms of systems requirements, execution
summary, and analysis and design diagram.
Organization Structure:
Online shopping System
System Plan System Coding Testing Delivery
Design
Review Test Plan
Specification Top-Level
Design
Test Case
Review
schedule User
Interface
Develop Plan
Detailed
Design
1.3 Definitions and Abbreviations
UML-unified modeling language.
SCI –software cost Estimation.

3. UML
UML is a language for specifying, constructing, visualizing and documenting the software
system and its components with a set of rules and semantics.
Use-case Diagrams
Use case diagram is a graph of actors, set of use cases enclosed by a system boundary,
communication (participation) association between the actors and the use cases and a
generalization among the use cases.
Actor
An actor represent a set of roles that user of a use case play when interacting with the use
cases. Actor identified here is administrator and staff.
Use case
A use case is a description of a set of sequence of actions that a system performs to yield
result of value to an actor.
Sequence Diagrams
Sequence diagrams are easy and intuitive way of describing the behavior of a system by
viewing interaction between the system and its environment. A sequence diagram shows an
interaction arranged in a time sequence.
Collaboration diagram
A collaboration diagram represents a collaboration, which is a set of objects related in a
particular context and interaction, which is a set of messages exchanged among the objects
within the collaboration to achieve a desired outcome.
Activity diagram
The activity diagram is used to describe the various activities taking place in an
application.
UML-unified modeling language.
SCI –software cost Estimation.
1.4 Document Conventions
In general this document follows the IEEE formatting requirements. Use Arial font size
11, or 12 throughout the document for text. Use italics for comments. Document text should be
single spaced and maintain the 1” margins found in this template.

4. 2. OVERALL DESCRIPTION
2.1 Product Perspective
The Online shopping system should provide the facility of online ‘Buying’ and
‘Cancellation’ of items. Online transaction should take place if the item is available and the
amount should be taken from the customer account by using their credit card number and if they
cancel the item means the amount should returned to the account.
2.2 Product Functionality
Access to the Online Shopping System for the administrator and customer is provided
with an individual login.
Username will be individual customer ID and each set their own password.
Administrator can only perform all kinds of operations.
Customer can just view their item details and can pay for their items. If any errors found,
they have to contact the admin directly and correct the error manually.
2.3 User Characteristics
Login
It is the login session for the Administrator, customer and Exit.
Product Details
It is used to view the product details from the database.
. Add New Products
It is used to add a product into the database and it includes searching a product details
and removing a product from database.
Updating The Quantity
It is used to update the product details from the database.
2.4 Operating environment
Software Requirements:
Front End: VISUAL BASIC 6.0
Back End: MS ACCESS
Hardware Requirements:
A PC with proper speed and memory
Tools:
Design Tool: Rational Rose suite

5. 3. SPECIFIC REQUIREMENTS
4.
3.1 FUNCTIONAL REQUIREMENTS:
This application is designed using VB as front end and MS-access as the back end. The
user interaction window is created using VB and the database for storing the details of the
items is created using MS-Access.
The inventory has two main options; they are the sales and the purchase of items. They
are used to buy goods into the inventory and sale of those send to the outlets.
The purchase has the simple option of adding new items to the inventory and in case that
item already exists then the record for that item is updated.
The selling option has the option to sell the available items. There are many items
available in the inventory all the details are listed in the window.
Once the items are sold then the data are to be updated in the database. When the number
of items available is less than what is required to the buyer then a message is to be
displayed by the user.
All the details of the items are stored in a database and it is accessed using data
connectivity.
3.2 NON FUNCTIONAL REQUIREMENTS
Non functional requirements includes
3.2.1Cost Estimation
An estimate is a prediction based upon probabilistic assessment. It is the responsibility of
the project manager to make accurate estimations of effort and cost. This is particularly true for
projects subject to competitive bidding where a bid too high compared with competitors would
result in loosing the contract or a bid too low could result in a loss to the organization. This does
not mean that internal projects are unimportant. From a project leaders estimate the management
often decide whether to proceed with the project. Industry has a need for accurate estimates of
effort and size at a very early stage in a project. However, when software cost estimates are done
early in the software development process the estimate can be based on wrong or incomplete
requirements. A software cost estimate process is the set of techniques and procedures that
organizations use to arrive at an estimate. An important aspect of software projects is to know
the cost, The major contributing factor is effort.

6. Why SCE is difficult and error prone?
Software cost estimation requires a significant amount of effort to perform it correctly.
SCE is often done hurriedly, without an appreciation for the effort required.
You need experience at developing estimates, especially for large projects.
Human bias i.e An Estimator is likely to consider how long a certain portion of the
system would take, and then to merely extrapolate this estimate to the rest of the system,
ignoring the non-linear aspects of software development.
The causes of poor and inaccurate estimation
 New software projects are nearly always different form the last.
 Software practitioners don't collect enough information about past
projects.
 Estimates are forced to match the resources available.
3.2.2 Cost Pricing
Our project is of high range and is highly efficient which can satisfy the payroll
calculation for almost all software companies. The chances of error occurrence is very
limited and so our costs around 10, 00,000(app).
A team of members is required for completing the task.
It takes a time span of 3 weeks to shape the project.
There are no specific environmental constraints.
3.3 Network bandwidth
You can have the best online application, unless you have proper bandwidth, the system
will not work well. Depending on how many people access the system at the same time and on
functions the program offers, it can become a burden to the existing network, slowing down
processes to a halt.
3.4 Flexibility
Flexibility is an important nonfunctional requirement of online shopping. As laws and
regulations change, the system must be updated as well.

7. ONLINE SHOPPING SYSTEM
Design Document
AIM:
To prepare a design documentation for online shopping system.
CLASS DIAGRAM:
Class diagram is represent the collection of objects. Employee details contain the
employee name, employee age, employee address. It involved verify().
USE CASE DIAGRAM:
Use case diagram used to interact the system and user. System involved in
employee and salary details. Employee involved in the allowance and allowance depend on the
system.
SEQUENCE DIAGRAM:
The employee select details from management then to decision. The salary given
based on designed to management providing salary the salary is received by the employee to the
management provide allowance.
ACTIVITY DIAGRAM:
Employee to details to get income the select two parts salary and allowance.
Salary to monthly and yearly allowance loan and insurance to get the report to completed.
COLLABORATION DIAGRAM:
Employee details to selected salary details.The allowance prepared to the details
about the conditions.
STATECHART DIAGRAM:
The statechart diagram to using employee to management designation and the
decision to the management all allowance.
TESTING
The verification and validation of software is a continuing process through each stage of
the software process. Verification and validation is the generic term for checking process. Which
ensure that the software meets its requirements?
Testing plays very critical role in determining the reliability and determining the
efficiency of software and hence it is very important stage in software development. Software
testing is done at different levels. They are unit testing, system testing which comprises of
integration testing.

8. UNIT TESTING
Unit testing comprises of test performed prior to integration of the different units into a
larger system. The software literature defines a unit along the lines of the smallest collection of
code, which can be tested. Typically this would be a source file. Unit testing is one of the levels
of testing which make the big picture of testing a system.
SYSTEM TESTING
System testing does not test the software but rather the integration of each module in the
system. System testing also verifies that the file sizes are adequate and that indexes have been
built properly. During system testing users enters data observes the results. System testing has
users verify. That the system performs as they expect it to.
INTEGRATION TESTING
After each program passes its own text its linkage to the other program is scrutinized with
a program. Integration testing ensures that the programs together as intended.
Testing is done with live data provided by the client to ensure that the software works
sufficiently. Testing focuses on the external behavior of the system. The system was tested by
giving inputs from actual data and the results were found to be satisfactory.
DEBUGGING
Debugging occurs as consequences of successful testing. The debugging process begins
with the execution of test case. Results are accessed and a lack of correspondence between
expected and actual performance is encountered debugging process attempts to match symptom
with cause, there by reading to error correction.
The debugging process will always have one of the two error correction.
 The cause will be found and corrected.
 The cause will not be found.
In this case, the person performing debugging may suspect a cause, design a test case to
help validate the suspicion and work toward error correction in an interactive fashion.

9. 3.3 UML Diagram:
3.3.1 Use case Diagram
customer items displayed purchase
login add item
admin
3.2.2Class Diagram

10. 3.2.3. Sequence Diagram
administrator customer add item view item purchase
adding the item
viewing the item to purchase
purchasing
updating the items to customer
purchasing again
3.2.4. Collaboration Diagram
administrat
1: add the item
or
add item
customer
5: purchasing again
2: viewing the item to purchase
3: purchasing
view item purchase
4: updating the items to customer