ONLINE AUCTION SYSTEM (OAS)

SOFTWARE DESIGN DESCRIPTION DOCUMENT

VERSION:
Revision History
Date Description Author Comments

Document Approval
The following Software Requirements Specification has been accepted and approved by the following:

Signature Printed Name Title Date

SDD Document 1.0 Page 2 of 3 10/12/19

f
PREFACE
This document contains the system design information for Online Auction System
(OAS) project. The document is prepared according to the “IEEE Standard for Information
Technology – Systems Design – Software Design Descriptions – IEEE STD 1016 – 1998”.

This Software Design Documentation provides a complete description of all the system design
and views of Online Auction System (OAS) Project.
The first section of this document includes purpose, scope, overview, reference material and
definitions and abbreviations of the project.
The second chapter of this document includes an overview of the functionality of the application.
It describes the informal design generally.
The third chapter of this document will give the user a detailed description of each function of
the system.
The fourth chapter of this document contains data design and data description of the project.
The fifth chapter of this document contains a general overview of what the user interface will
look like.
The sixth and last chapter of this document includes of requirements matrix of the project.

SDD Document 1.0 Page 3 of 3 10/12/19

f
 Table of Contents

Contents
1. INTRODUCTION ..................................................................................................................................... 7
1.1 Purpose ......................................................................................................................................... 8
1.2 Scope ............................................................................................................................................. 8
1.3 Overview ............................................................................................................................................. 9
1.4 Reference Material ............................................................................................................................. 9
1.5 Definitions and Acronyms ................................................................................................................... 9
2. SYSTEM OVERVIEW ............................................................................................................................. 10
2.1 Technologies Used ............................................................................................................................ 11
2.2 Application Overview ........................................................................................................................ 11
2.3 Design Language ............................................................................................................................... 11
3. SYSTEM ARCHITECTURE .......................................................................................................................... 11
3.1 Architectural Design .......................................................................................................................... 11
3.2 Decomposition Description............................................................................................................... 13
3.2.1 Login and Logout Component sequence Diagrams ....................................................................... 13
Sequnce diagram of LOGIN HANDLER ................................................................................................... 13
3.2.2 Sequnce diagram of Logout Handler ........................................................................................ 14
3.2.3 Sequnce diagram of Register handler ............................................................................................ 15
3.2.4 Sequnce diagram of update handler .............................................................................................. 16
Information Components........................................................................................................................ 17
3.2.2 Class Diagrams ............................................................................................................................... 19
Admin class diagram ............................................................................................................................... 19
Admin Class ............................................................................................................................................. 19
3.2.3 Class diagram of Auction System ................................................................................................... 20
4. DATA DESIGN .......................................................................................................................................... 23
4.1 Data Description ............................................................................................................................... 23
4.1.1 Data Objects ................................................................................................................................... 23
4.2 Data Dictionary ................................................................................................................................. 24
5. COMPONENT DESIGN ............................................................................................................................. 27

SDD Document 1.0 Page 4 of 3 10/12/19 f

 5.1 Overview of User Interface ............................................................................................................... 28
6. HUMAN INTERFACE DESIGN ................................................................................................................... 28
6.1 Overview of User Interface ............................................................................................................... 30
6.2 Screen Images ................................................................................................................................... 30
6.3 Screen Objects and Actions .............................................................................................................. 30
6.3.1 Login Screen ................................................................................................................................... 30
6.3.3 Profile, Login and Registration Interface ........................................................................................... 36

SDD Document 1.0 Page 5 of 3 10/12/19 f

SDD Document 1.0 Page 6 of 3 10/12/19
f
Chap No.1
INTRODUCTION

1. INTRODUCTION

SDD Document 1.0 Page 7 of 3 10/12/19

f
 The Online Auction System (OAS) is a model where all the
people participate in a bid for products. By using the online software the auctioning
become easier. It decreases the complexities of manual system. In manual system lots of
human resources and paper work is involved but by using OAS the system is subjected to
[Link] has several other names such as e-Auction (Electronic auction) and
virtual Auction etc. OAS is a web based system. The main benefit of OAS is that user can
buy his own selected product. OAS many people are participating in bidding for a
product on a specific time and date that are mention on website. Times limits are also
defined for bidding. Bidding starts from a minimum prize which is fixed by admin and
the participant who gives the highest bid of that product wins the bidding after that
process he pays the amount of this product to admin via bank account and admin sent the
product to this person.

1.1 Purpose
The purpose of this project is to build an “Online Auction System”, a place for buyers
and sellers to come together and trade almost any product. This document is to provide
detailed description of online auction System. It improves the complexities of manual
system. The participants can understand it with ease and in a fast way. It is very helpful
to save the time of many persons. This document describes the conceptual design of the
Online Auction System (OAS) according to the document guidelines presented in the
IEEE 1016-1998 Recommended Practice for Software Design Descriptions (SDD).This
document shows that how the system will be proposed to satisfy the software requirement
identified by Software Requirements Specification. It is a translation of requirements into
a document of the software structure, software components, interfaces and data necessary
for the implementation phase. The SDD becomes detailed information for the
implementation activity of the software. In a complete SDD, each requirement must be
traceable to one or more design entities.

1.2 Scope
This project OAS will be a web based project. This system will help to define the
following functionalities of OAS:
 Manage the information of the users of this system.
 Managing the product information that is available for Bid.
 Create a Bid and add time constraints on it.
 Only authorized person can access the system.
 Backup of database

SDD Document 1.0 Page 8 of 3 10/12/19

f
 This system provides the facility to buying things by highest bidding there are different
things which are present on this website for bidding. A user can enter through the valid id
and password after login the system there are many things for bidding but he choose his
desire one and buy it by highest bidding among different peoples .The system is design to
provide the quick facilities, easy to use interface that will help and maintaining the whole
system.

1.3 Overview
This document will help the readers to understand the solution to the project
presented before. The document satisfies how the design meets the requirements
specified in the Software Requirements Specifications through design viewpoint.
By using information from IEEE 1016-1998, this document will provide a direct
approach to the development of this project.

1.4 Reference Material

IEEE, IEEE Std 1016-1998 Recommended Practice for Software
Design Descriptions, 1998-09-23, The Institute of Electrical and Electronics Engineers,
Inc., (IEEE )
IEEE, IEEE 1016 Software Design Document (SDD) Template for CENG491

1.5 Definitions and Acronyms

OAS Online Auction System

SDD Software Design Description Document

DB Database

OS Operating System

PHP Programming language

Sublime Text Editor

SDD Document 1.0 Page 9 of 3 10/12/19

f
 Chap No.2

SYSTEM
OVERVIEW

SDD Document 1.0 Page 10 of 3 10/12/19

f
System Overview
2.1 Technologies Used
PHP Language is used to code this system by using
sublime text editor. Database will be used in this System. My SQL server is used to store
the data.

2.2 Application Overview

The purpose of online auction system is to carry out the
activities of auction system is an efficient way. It will take the operations of auction to an
upper level by providing admin a faster access to data and allowing deleting, updating,
modification of data. This system provides an easy way to people to buy the products by
highest bidding. Our system is computerized and overcome the problems of manual
system. Detailed information is required to perform any kind of activity in the whole
system. For example first of all user need to verify himself by entering his username and
password than he perform different functionalities and give bid for any product. Admin
can insert, delete and maintain product. Admin also has the ability to remove any person
from bidding.

2.3 Design Language

Unified Modeling Language (UML) is used for graphical
representations of viewpoints in Online Auction System Project in [Link]
[Link] Design and [Link] Design parts.

3. SYSTEM ARCHITECTURE
3.1 Architectural Design
The Figure 1 shows the general deployment diagram of Online
Auction System. The Online Auction System will be developed as a web based
application and it will:

 Provide common services for online Auction System.

SDD Document 1.0 Page 11 of 3 10/12/19

f
  Communicate with the remote server to retrieve or update users
information.
 To interact user with system

A library MYSQL connector is used to connect online Database to Online Auction

System . It the most recent library used to build a connection. It acts like a bridge
between Online Auction System and Database.

Figure 3.1
General Deployment Diagram
This diagram desceibes the structural view of the [Link] Auction System
is a web based [Link] the data of that system are stored in database and it
connect with database through a connector and the connector is MYSQL
[Link] data of the users are stored in database and system can acess the
data of users from database

SDD Document 1.0 Page 12 of 3 10/12/19

f
3.2 Decomposition Description

3.2.1 Login and Logout Component sequence Diagrams

Sequnce diagram of LOGIN HANDLER

This diagram shows the login activity of the user if connection data service is available then user
user can enter into the system by entering a valid username and [Link] he don’t have a valid
password and username he cannot get enters into the system

SDD Document 1.0 Page 13 of 3 10/12/19

f
3.2.2 Sequnce diagram of Logout Handler

This diagram shows the logout activity of users

SDD Document 1.0 Page 14 of 3 10/12/19

f
3.2.3 Sequnce diagram of Register handler

SDD Document 1.0 Page 15 of 3 10/12/19

f
3.2.4 Sequnce diagram of update handler

SDD Document 1.0 Page 16 of 3 10/12/19

f
Information Components

Fig 3.6
Sequence Diagram of User Information

SDD Document 1.0 Page 17 of 3 10/12/19

f
 Complete Sequence Diagram Of Online Auction System

SDD Document 1.0 Page 18 of 3 10/12/19

f
3.2.2 Class Diagrams
Admin class diagram

Fig 3.8 Class Diagram of Admin

Admin Class
We will use Admin class to control the activities of admin in application.
+getUserName() : Indicates whether admin gets username of user
+getUserPassword(): Indicates whether admin user Password to control the activities of User
+AdminLogin(): Indicates the Login panel of Admin into application
+removeUser(): Indicates the that Admin remove reported user by other users
+createBid():Indicate that user can create a bid.
+addproduct(): Indicates that admin can give reviews that admin can add a product for a bid
+updateproduct(): Indicates that Admin update product
+removeReviews(): Indicates that Admin can remove a product which can be sold.

User Class

SDD Document 1.0 Page 19 of 3 10/12/19

f
 We will use user class to control the activities of user in application.
+addproduct() : Indicates whether user add a product
+post product(): Indicates whether user post for a product
+viewproduct():Indicate that user can also view product
+deleteproduct(): Indicates the that user can delete a product
+bidproduct():Indicate that buyer can go for bid of product
+viewproduct(): Indicates that user can view a product
+givefeedback(): Indicates that user can give a feedback.

3.2.3 Class diagram of Auction System

SDD Document 1.0 Page 20 of 3 10/12/19

f
 The class User contains several parameters that are information about a normal user that
browses the system (username, password, name, surname…); the parameter administrator
is a flag that indicates whether the user is an administrator or not. This class performs the
operations of a normal user (search for an item, get the items on auction, post a new
auction, send messages to other users) and those of a system administrator (create a new
category, delete a category, delete an item, delete an user). The class Message has a text,
a topic and the user_id of the sender and of the receiver. The class Item contains several
information about the item on auction (the name of the item, its photo, a textual
description of it..) and about the category it belongs to. A category has a name and,
eventually, a super-category it belongs to: a category can belong to another category (e.g.
category sport car belongs to category car). Class Motor and Music are subclasses of
Item. Car and Motorcycle are subclasses of Motor: they inherit the properties of class
Item and they have their specific attributes (model, km, matriculation date). CD, MC and
Instrument also inherit properties form Item and have their own specific attributes (genre,
condition). Class SoldItem represent an already sold auction item, its attributes are the
name of the item, the final price, the date in which it was sold and its buyer and seller.

SDD Document 1.0 Page 21 of 3 10/12/19

f
SDD Document 1.0 Page 22 of 3 10/12/19
f
Chap No 4
DATA DESIGN

4. DATA DESIGN
4.1 Data Description

4.1.1 Data Objects

These Are The Objects Of User Side.
User:
UserID:Identity number given from the database for each User. This attribute is unique for
any User.

Name: Name of the User

Email:Email Address of User
Password: Password of userid
Contact: Any contact info of user

SDD Document 1.0 Page 23 of 3 10/12/19 f

 Address:Mailing Address of user
Description: Description about User
Profile Pic: Picture of user
THES ARE THE OBJECTS OF PRODUCT THAT ARE AVAILABLE FOR BID
PRODUCT:
ProductID: Unique key of product that identifies Product
ProductName:Name of the Product
ProductType: Type of product.
ProductaddedBy: Name of user who added this product
Reviews: Reviews about product from many other users.
Images: Images of product added by admin.

4.2 Data Dictionary

Alphabetically list the system entities or major data along with their types and
descriptions.
[Link]
Parameter Parameter Type
UserID User

Username String

Password String

Address String

Email Email

Phone String

Description String

ProfilePic Image

2. Product

SDD Document 1.0 Page 24 of 3 10/12/19 f

 Parameter Parameter Type
productID String

ProductName String

ProductType String

ProductAddedBy String

ProductRating Float

Reviews:
Parameters Parameter Type

productID String

UserID String

Review String

IsReported Boolean

STATE TRANSITION DIAGRAM

SDD Document 1.0 Page 25 of 3 10/12/19

f
SDD Document 1.0 Page 26 of 3 10/12/19
f
Chap No.5
COMPONENT
DESIGN

SDD Document 1.0 Page 27 of 3 10/12/19

f
5. COMPONENT DESIGN
5.1 Overview of User Interface
` The user will login and directed to timeline page where
he can view recently added product that are available for bidding. If user is not registered
there will be a button to sign up into application. There will be a menu where he/she can
view his profile, add products, get recommendation to visit for a new product according
to interest.

5.2 Admin functionality

 Delete Product
 Add product
 Update product

SDD Document 1.0 Page 28 of 3 10/12/19

f
Chap No.6
HUMAN
INTERFACE
DESIGN

SDD Document 1.0 Page 29 of 3 10/12/19

f
6. HUMAN INTERFACE DESIGN
6.1 Overview of User Interface
Describe the functionality of the system from the
user’s perspective. Explain how the user will be able to use your system to complete all
the expected features and the feedback information that will be displayed for the user.

6.2 Screen Images

Display screenshots showing the interface from the user’s
perspective. These can be handdrawnor you can use an automated drawing tool. Just
make them as accurate as possible.
( Graph paper works well.)

6.3 Screen Objects and Actions

This section briefly describes the interfaces and
interface components of Intelligent Tourists Guide

6.3.1 Login Screen

Login interface for registered users to get into application.

SDD Document 1.0 Page 30 of 3 10/12/19 f

 From this page we can entering into our main system by using username and password. if
he use a authentic roll number and password he enters into the system and if he does not
enters a valid password and username he cannot able to enters into it.
6.3.2Sign Up Page

INTERFACE OF USER LOGIN

If the user has not valid id and password than he can make his account from this signup
page and enters some information into it. After making a account on this he can able to
login into the system from login page

SDD Document 1.0 Page 31 of 3 10/12/19

f
SDD Document 1.0 Page 32 of 3 10/12/19
f
The buyer can select a desired category from number of products.

SDD Document 1.0 Page 33 of 3 10/12/19

f
SDD Document 1.0 Page 34 of 3 10/12/19
f
SDD Document 1.0 Page 35 of 3 10/12/19
f
 6.3.3 Profile, Login and Registration Interface

SDD Document 1.0 Page 36 of 3 10/12/19

f
Chapter 7

Requirements matrix
Provide a cross reference that traces components and data structures to the requirements in your
SRS document. Use a tabular format to show which system components satisfy each of the
functional requirements from the SRS. Refer to the functional requirements by the
numbers/codes that you gave them in the SDD.

Components:
Change
Requirements Login Delete Add update REPORTS
password
from SRS
(use cases):
Uc1 X X X X
UC2 X
UC3 X

SDD Document 1.0 Page 37 of 3 10/12/19f

Chapter 8 appendices

8.1Appendix A-background research on:

8.2 Appendix B-data dictionary

8.3 Appendix C-data flow diagram

8.4 Conclusion
This system is user friendly since it has been developed in wamp server a successful GUI.
The project online auction Management System is for computerizing working.
The software takes care of all the requirements of an a traveling and is capable to provide
easy and effective storage of information related to users. Our system is computerized
and overcome the problems of manual system. Detailed information is required to
perform any kind of activity in the whole system first of all user need to verify himself by
entering his username and password than he perform different functionalities and give bid
for any product. Admin can insert, delete and maintain product. Admin also has the
ability to remove any person from bidding.

SDD Document 1.0 Page 38 of 3 10/12/19

f