Essays /

Bidding Website Essay

Essay preview



Contents
Introduction 3
1.1 Purpose 3
1.2 Scope 3
1.3 Definition and Abbreviation 3
1.4 Overview 3
Overall Description 3
2.1 Product Perspective 3
2.2 User Characteristics 4
2.3 Interfaces 4
2.3.1 User interfaces through forms 5
2.4 Product Functions 6
2.4.1 Guest 6
2.4.2 User 6
2.4.3 Administrator 6
2.5 Constraints 7
Specific Requirements 7
3.1 Requirements Control Plan 7
3.2 Functional Requirements 7
USE CASE DIAGRAM 20
4.1. Relationship 20
4.2 Architectural Diagram: 20
4.3 Architecture Detail 21
4.4 USER CONTROL PANEL 21
4.5 BIDDING STATE CHART 22
Database Requirements 22
5.1 Design Constraints 22
5.2 Software system attributes 22
TIME ESTIMATION 23

Introduction
1.1 Purpose
The purpose of this document is to present an overall description and listing of the functionality of the system behind an online auction website. This document is intended for users of the system including designers, testers, implementation unit and the employer. 1.2 Scope

Salesmen are the system behind an online auction website. An auction site is a web application where users can buy and sell objects. Users can place auctions or bid on auctions of other users. There are also some social features such as sending messages to users, add a seller to favorite sellers and a rating system for users. 1.3 Definition and Abbreviation

_ SRS: Software Requirements Specification
_ UML: Unified Modeling Language
_ XHTML: Extensible Hypertext Markup Language
_ HTML: Hypertext Markup Language
_ CSS: Cascading Style Sheets
_ HTTPS: Hypertext Transfer Protocol Secure
_ CAPTCHA: Completely Automated Public Turing test to tell Computers and Humans Apart 1.4 Overview
Section 2 describes the general factors that a_ect the product and its requirements. This section does not state specific requirements. Instead, it provides a background for those requirements, which are designed in detail in Section 3 of the SRS, and makes them easier to understand. Section 3 contains all of the software requirements, to a level of detail sufficient to enable designers to design the system to satisfy these requirements, and testers to test that the system satisfies these requirements. Overall Description

2.1 Product Perspective

The project will make use of a database and a web server that can be accessed with any web browser. There are 4 types of users on the system: guests, registered users, administrators and banned users. Before a user can make use of the full functionality of the site, the user has to register. The user will have to enter some personal information in a form in order to do this.

Both guests and users can browse the different auctions, but only registered users can bid on auctions or place their own auctions. Users can browse through auctions with categories or tags. Users can also search for a specific auction. When a user places an auction, he or she also has to specify payment methods, a minimum price, duration for the auction and other general information about the auction. A user can follow an auction. The followed auctions list is a list of auctions that interest the user but on which he or she may not have bid yet. Then when the user wants, he or she can bid on the auction. A user can view all the auctions he or she has bid on in the active auctions list. When a user has won an auction, he or she can pay for the item. This will be done through a transaction. The buyer can pay for the item by choosing one of the payment options the seller has specified. One of these methods is through PayPal. When the transaction is done, buyers and sellers can rate the transaction. Each user will have a rating then which is based on the ratings of their transactions. Users can also contact other users through personal messages. Other sellers can also be added to a favorite sellers list, so that a user can easily check if a seller they like has new auctions. Administrators have some extra functionality; they can manage the users and auctions. Administrators can also retract a bid of a user. 2.2 User Characteristics

The users of the system will be users with different levels of technical expertise. Any user with a basic understanding of the internet and auctions should be able to make use of all the available functionality of the system.

There are three different types of use...

Read more

Keywords

1 1.1 1.2 1.3 1.4 10 11 12 13 14 15 16 160 17 18 19 2 2.1 2.2 2.3 2.3.1 2.4 2.4.1 2.4.2 2.4.3 2.5 20 21 22 23 24 25 26 27 28 29 3 3.1 3.2 3.2.1 3.2.1.1 3.2.1.2 3.2.2 3.2.2.1 3.2.2.2 3.2.2.3 3.2.3 3.2.3.1 3.2.3.10 3.2.3.11 3.2.3.12 3.2.3.13 3.2.3.14 3.2.3.15 3.2.3.16 3.2.3.17 3.2.3.18 3.2.3.19 3.2.3.2 3.2.3.20 3.2.3.21 3.2.3.3 3.2.3.4 3.2.3.5 3.2.3.6 3.2.3.7 3.2.3.8 3.2.3.9 3.2.4 3.2.4.1 3.2.4.2 3.2.4.3 3.2.5 3.2.5.1 3.2.5.2 3.2.5.3 3.2.5.4 3.2.5.5 3.2.6 3.2.6.1 3.2.6.2 30 31 32 33 34 35 36 4 4.1 4.2 4.3 4.4 4.5 48 5 5.1 5.2 5.2.1 5.2.2 6 7 8 80 9 abbrevi abl access account activ actor ad add address administr advanc allow almost along alreadi also alway anoth anyon apart applic architectur aren assist attempt attract attribut auction autom automat avail background ban base basic behind bid bought brows browser budget buy buyer captcha cascad case categori certain chang characterist chart check choos clear client code comment communic compat complet comput concurr confirm connect consist constraint contact contain content control cooki correct correspond creat css data databas default definit delet deliveri describ descript design detail detect develop diagram differ discuss display divid document done durat e e-mail e.g easier easili ect eld employ empti enabl encrypt end end-us english enter error es estim except expertis extens extra factor favorit favourit featur field fill first fix follow form forward found frequent full function fundament general generat good group guest handl hardwar high home homepag hour html http https human hypertext i.e id identifi implement inbox includ incomplet incorrect inform instead intend interest interfac internet introduct item languag last let level like limit linux list lls log login made mail make man manag mandatori mani markup match maximum may member messag method minimum minor model modif modifi modul modular must name need new nice none note noti notif number object object-ori occur offer one onlin oper option order orient other overal overbid overview page paid panel password path pay payment paypal perform person perspect phone php place plan port power precondit prefer present price prioriti product project protocol provid public purpos put queri rate reason receiv recommend recov redirect referenc regist registr relationship reliabl remain remov replac request requir result retir retract run salesmen satisfi save scope scratch search section secur select sell seller send sensit sent server sheet ship short simpl simplifi singl site small social softwar sourc special specif specifi srs standard state store structur style subject submit suffici system tag taken tcp/ip technic tell term test tester thing though three time togeth top transact transfer tri ture type typo uml understand unifi uniqu unit updat use user usernam valid valu verif view visit visitor w3c want web websit week whenev within won work wrong xhtml yet