04-08-2012, 11:26 AM
Software Requirements Specification For Online Bidding
srs for online bidding.docx (Size: 285.66 KB / Downloads: 44)
Literature Survey:
Online auctions are one of the most successful forms of electronic commerce. The first is that online auctions provide a less costly way for buyers and sellers on local “thin “markets such as specialized collectibles to meet and conduct transactions. Online auctions have extensive listings and powerful search technologies that create liquid markets for specialized product categories. Due to the resulting reduction in transaction costs, some intermediaries like the antique dealer above have been forced to exit the market.
Many users of online auctions clearly enjoy contemplating the subtleties of strategic bidding, and sharing their insights with others. Online auction sites have active message boards that provide collectors with a sense of community and where one can learn the fine points of collecting.
The study of Internet auction sites, with the wide variety of auction formats and rules they offer, can also give us some valuable insights regarding auction design. On many Internet auction sites, sellers are allowed to fine tune their auctions by experimenting with minimum bids or secret reserve prices. Several sites also allow the sellers to make choices regarding which auction format to use.
In modern world with development of technology; auction mechanisms have become more complex and efficient. The first Web-based commercial auction sites were launched in 1995. Lucking-Reiley’s (2000) introduction to Internet auctions is significant because he investigated 142 Internet auction sites, and provided a comprehensive overview of the Internet auction industry, including its early history, business models, goods sold, auction formats and options, and concerns about fraud.
Herschlag and Zwick’s (2000) review of non -academic articles touches on many of the same themes. Online-auction studies have focused primarily on reputation issues and on auction-listing issues, such as the value of providing photographs/images of an auction item (Ottaway et al., 2003), setting an opening bid amount (Gilkeson and Reynolds, 2003) or setting the bid increment amount (Bapna et al., 2003). Chakravarti et al. (2002) outline key auction concepts and empirical findings; identify some areas for future research and highlight that Internet auctions can lead to new principles in marketing theory and practice. Andrews and Benzene 2007 also provide a definition of online auctions.
2.Introduction
2.1 Purpose
The purpose of this software requirement specification document is to describe the behaviour and functionalities of Online Bidding System. This system is designed to be an online auction and trading site with built-in real-time communication tools between potential bidders and the auction owner. The document is intended to serve as the guideline and intended goals for the implementation of the various functions of the program. The expected audience of this document is the faculty in charge of Internet Technologies & Applications lab for 6th semester Information Technology, NITK, Surathkal.
2.2 Scope
Online Bidding System is designed to run on both any modern platform with GUI. It is a web application where users can buy and sell items. Users can place auctions or bid on auctions of other users and also purchase items.It is assumed that the back end that will be used for implementation is MySQL and the front end that will be used is PHP. We also hope to provide a comfortable user experience.
2.3 Definitions, Acronyms and Abbreviations
There are no standard definitions, acronyms or abbreviations in this document.
2.4 References
http://wilma.vub.ac.be/~se2_0910/docs/sr...s-v0_2.pdf
http://www.cas.mcmaster.ca/~sartipi/cour...mplate.doc
http://www.ftc.gov/be/vogt.pdf
2.5 Overview
The rest of this SRS is organized as follows: Section 3 gives an overall description of the software. It gives what level of proficiency is expected of the user, some general constraints while making the software and some assumptions and dependencies that are assumed. Section 4 gives specific requirements which the software is expected to deliver. Functional requirements are given by various use cases. Section 5 gives some of the issues while implementing the final product. Section 6 includes the design documents.
3 General Description
3.1 Product Perspective
This is proposed to be an enhanced model of the present day existing auctioning portals. Many flaws in the present online bidding portals haven’t been able to exploit the full potential of e-commerce market. The Software Requirements Specifications intends to identify the flaws in the current existing system and propose an alternative or a solution to them.
3.2 Product Functions
• It consists of two modules
1. Customer module
2. Administrator module
• A customer should have a user account for carrying out transactions.
• Transactions include buying, selling and auctioning.
• Administrator provides the customer with an account following proper registration procedures to prevent malpractices in the transactions.
• Any visitor is allowed to browse through the product list, their prices and bidding procedures.
• Buying, selling and bidding procedures are kept transparent so that any user is able to go through the procedures.
3.3 User Characteristics
There are 4 kinds of users for the proposed system
Administrators: They create user accounts and give it to the required customers.
• They must provide rules for the transactions.
• They must maintain the website and update the same making necessary changes at times.
• They must take care of the security issues involved in the transactions.
• They must inform the users about their transaction status.
• They must receive feedbacks from their customers or any users about their system.
Buyers: They are the genuine customers of the website. They can see the listing, bid for various things, and also buy them through various payment options.
Sellers: These are the people involved in selling their products through the online bidding system. They consider this as a virtual market place. They need to be provided with proper advertisement place.
3 General Description
Casual Visitors: These people don’t come to the site on specific intensions of buying or selling. They just visit to see the listing and too see the products. They need not have a user account. They can be future potential customers. The sellers can lure them with advertisements on the site based on their budget.
3.4 General Constraints
• User Interface Constraints
The Online Bidding website will be accessed through a web browser by the user from his or her computer.
• The members must have their correct usernames and passwords to enter into the system.
• The main constraint here would be the checking the genuineness of the buyer, which is not always possible. There can be security risks involved.
• The design constraints are that the browser at each place may not follow similar screen resolutions, browsers etc. This can lead to the website not having the impact it is planned to have.
• Also storage space constraints may come if the listing becomes too large. Hence a strong server needs to be chosen to host the database.
• Must have an Internet browser.
• JavaScript must be enabled on the client browser.
• Real-life credit card validation and Banking system is not implemented.
3.5 Assumptions & Dependencies
• The details related to the product, customer and payment are provided manually.
• User should be accessing the site through a desktop or laptop.
• The site’s primary language of operation is English.
General Descriptions
3.6 Product Features
3.6.1 Listing:
This includes the listing feature of the website where request of a user to a particular subject is served. The pertinent web pages are loaded and the particular database is initialized. This is actually the listing of web pages to the users by time of selling, deadline, price, quality etc. Listing includes listing of
• Products to be sold.
• Products open for bidding till a particular date.
• Used products on for sale.
• Just casual listings of random things
• Payment options to buy or sell
3.6.2 Account creation:
This includes creating user accounts for sellers and buyers. This includes taking pertinent information from them and then initializing the database. The database needs to be properly updated on each transaction by the user and all the details of his/her account should figure in the account listing.
3.6.3 Selling:
Here the seller can list his/her things on his /her quoted price. Or else he can keep it for a bidding process where he is not sure of the price. The details of which will be kept in the user database. The process of selling can include some bargaining too, but the details are yet to be thought of. The payment and feedback details are kept transparent.
3.6.4 Buyer:
Here the buyer can buy things of quoted price. Or else he can buy it from a bidding process. The details of which will be kept in the user database.
3.6.5 Others:
Includes money transactions, but won’t be seen in detail in the document as the things are beyond the reach of the design team.