Professional Documents
Culture Documents
Document Approval
The following Software Requirements Specification has been accepted and approved by the following:
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.
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
1. INTRODUCTION
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
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.
DB Database
OS Operating System
SYSTEM
OVERVIEW
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:
Figure 3.1
General Deployment Diagram
This diagram desceibes the structural view of the system.Online Auction System
is a web based system.All the data of that system are stored in database and it
connect with database through a connector and the connector is MYSQL
Connector.All data of the users are stored in database and system can acess the
data of users from database
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 password.if he don’t have a valid
password and username he cannot get enters into the system
Fig 3.6
Sequence Diagram of User Information
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
4. DATA DESIGN
4.1 Data Description
Username String
Password String
Address String
Email Email
Phone String
Description String
ProfilePic Image
2. Product
ProductName String
ProductType String
ProductAddedBy String
ProductRating Float
Reviews:
Parameters Parameter Type
productID String
UserID String
Review String
IsReported Boolean
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
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.