ABSTRACT

Since the internet has become a popular place to buy and sell goods, online
auctioning services have made their way into most homes. Online auction system
is web based application, in which the seller can sell the goods by sitting in his
own house ,so the main advantage of this application is that there is no more
system compatibility requirement problem. The main advantage of the online
auction system is that the user can have the better choices for their investment
and also it is time saving , and through this system user can invest in their own
selected firm.

5
 Software Requirements Specification
(Online Auction System)

1. Problem Statement: To collect software requirements and create software requirement

specification.

SOFTWARE REQUIREMENTS: Ms Word.

1. Introduction
1.1 Purpose Basic Description of Problem
The main purpose for this project is people invest their money to get maximum profit and
know ledge about our online trading system. Here all type of user can go and analyses the
data of different field and get maximum profit for future investment.

1.2 Scope

This web application system will be a online auction system which consists of the seller,
buyer of consumer products. The admin web application will allow the online auction
administrator to sell and buy the products through the desired person(administrator). In
this the seller will post the product with the help of images and description of the product.
The buyer have to select the product and bid accordingly.and the bidding will have a specific
time limit which will be set by a seller of the product The buyer with the highest bid, the
product will be sold to the bidder.

1.3 Definitions, Acronyms, and

Abbreviations OAS – Online Action System

GUI - Graphical User Interface

BARAT - Bus Advance Reservation from anywhere-to-anywhere Travel

1.4 References

1. IEEE Std 830-1998: IEEE Recommended Practice for Software

Requirements Specification

2. J. Peters, and W. Pedrycz, Software Engineering – An Engineering Approach. New

York, NY: Wiley, 2000.
3. D. P. Gilliam, T. L. Wolfe, J. S. Sherif, and M. Bishop, “Software Security Checklist for
the Software Life Cycle,” in Proc.
WETICE’03, 2003, pp. 243-248.
4. A. D. Rubin, “Security Considerations for Remote Electronic Voting,”

CACM, vol. 45, pp. 39-44, Dec. 2002.

1.5 Overview
This specification includes a brief product perspective and a summary of the functions
the software will provide. User characteristics are discussed, and any general
constraints or assumptions and dependencies are listed.
6
Requirement statements are categorized as functional requirements, performance
requirements, non-functional requirements, or design constraints. The rest of the
document contains the overall description of the system, requirements, data model and
behavioral description of the system and project planning.

2 General Description

2.1 Product Perspective

The online auction system is an independent system. This system involves two users i.e
buyer and seller. The Database connection is provided online to make faster and easy
acess to data retrieval.

2.2 Product Functions

Customer must have a valid User Id and password to login to the system. If there is a
new user he has to register for this auction process. If a wrong password is given three
times in succession, that account will be locked and the customer will not be able to
use it. When an invalid password is entered a warning is given to the user that his
account is going to get locked. User can search the product he want and also in the
particular price he wants i.e- maximum and minimum price. User can view his monthly
as well as annual auctions. He can also view future auctions. Administrator can take a
back up of the database for every auction that is happening, periodically. Al users are
authenticated to avail the services FAQ section is also included for end users benefit.

2.3 User Characteristics

There are three different types of users for the OAS system:
Type 1 The Administrator, who have complete authority on the ecosystem.
The Adim can start the auction, can handle who can participate in an auction, and
many.
Type 2 Seller who will sell the product with the fixed price on the auction or on the
System. The seller will write the description about the product.
Type 3 Buyer who will buy the product on the online when auction.
Based on the above categorizations, in order to meet user’s needs the following precautions
should be taken:

 the interface should be designed with the computer novice in mind.

 data entry masks should recognize and correct improperly entered data.

 for deleting or revising a record the system should ask the users for confirmation.

 report generation should occur in a timely fashion.

 diverse computer education levels should be considered.

 online help is important.

 the design should not assume users will perform their jobs as expected.

 error messages should be used.

 system design should follow the manual process as closely as possible.

 the interface should be easy to understand.

7
  users should be consulted throughout design.
2.4 General Constraints

The following constraints will limit the developer’s options for designing thesystem:

 the budget for this project is 870 Lakhs rupees.

 implementation is required within 10 weeks.

3 Specific Requirements
3.1 Functional Requirements
 Register: If the user doesn't have an account then he will be allowed to register himself with
his personal details (email, name etc)

 Login: Prompts the user to enter his login credentials so that he can access the further
functionalities provided.

 Sell products: To sell the products for the auction.

 Chatting: To make conversation with the admin or other bidding mates.

 Bidding: To get participate for the bidding.

 Report: To generate report for after the auction.

3.2 . Non Functional requirements

 Security: The security requirements are concerned with security and privacy issues. All
the users information should be kept private (hidden)

 Maintainability: The maintainability requirements one censored with the maintainence

issues of the system,

 Scalability: The scalability requirements are concerned with the scalable issues of
problem.