Вы находитесь на странице: 1из 24

TITLE OF THE PROJECT

Online E-WASTE Auction System


(OAS)
Introduction

An online e-waste auction project is a system that holds online auctions for E-waste products on a website
and serves sellers and bidders accordingly (Electronic and IT Assets). The system is designed to allow
users to set up their products for auctions and to register and bid for various products available for
bidding. The system also consists of products sorted by categories and by price. User’s feedback is also
provided to Admin.

This project, An Online e-waste Auction System has two parts- customer interface and admin interface.
Customer Panel permits a customer to upload a product for sale and bid on a particular product to buy.
This system presents an online display of category wised products they want to sell or bid. There is an
admin panel by which an admin can control the whole bidding system.

Admin can approve products by the categories and also can control the registered customers. There is
fixed delivery policy. After finishing the bidding process there is a notify system to notify the sellers and
bidders. This is a fully dynamic system which can be easily operated by the users

It provides the users for sign up to this application and search for products, manages their accounts. Each
customer will have their own account showing their username they have logged in. On the other hand
users can also see all product pages without having an access with their account. Signed up users will
have to log in first then they can upload products on the site from their account and also can bid for other
products which are not owned by them. Users can edit their profile and see their uploaded products and
bided products. Administration panel can approve products, update products, delete products, delete user,
update and delete all ongoing bids and can also see all the products, categories, users and bids.

All particular bids have limited time to finish. After finishing the bids admin can notify the sellers and
also the bidders. This is a well secured system and can be easily operated. This is fully dynamic. There is
nothing static here. The main aim of this web application is to make a good online system that provides a
great alternative of bidding policy for general people that saves both time and money.

Online E-waste Auction or the E-auction system project consists of the following features:
User Login: User can register online and then access the system on authentication.
Sort Products: User can sort products by category and price range.

Auction products: User can set up products for auction by providing details and minimum bid.
Delete Products: User can delete his own products.

Admin Login: Admin can login to system and view products as well as feedback and even delete other
user’s products.

Auction time: User can set auction time on posting product for selling; the winner is declared after time
elapse.

Email notification: Auction winner gets seller details; auction seller gets winner details on email.
Advantages:
 Excludes noisy crowds like conventional system where users have to sit and bid.
 Excludes general frustration that usually happens while bidding in conventional system.
 No schedule constraint that means bidder can bid anytime and from anywhere.
 The bidding can be made on a global level.

Disadvantages:
 No human interaction.
 If there are poor quality photographs then it's of no use.
Applications:
 The system can be applied to warehouses where the items are put up for auctions.
 Any person can use it to put up their product for auction.

The user can view the item in quantity.


SOFTWARE REQUIREMENT SPECIFICATION

Software Requirements Specification (SRS) is a document that completely describes what the proposed
software should do without describing how the software will do it. The basic goal of requirement phase is
to produce the SRS, which describes the complete external behavior of the proposed software. A basic
purpose of software requirements specification is to bridge the communication gap between the software
developer and the client. SRS is the medium through which the client and user needs are accurately
specified; indeed SRS forms the basis of Software Development. Another important purpose of
developing an SRS is helping the clients understand their own needs.

The main phases of Software Requirements Specification are: -

Problem Definition:

When we are concerning the manual process of a company, the major problem is the waste of time. A
customer has to waste his/her valuable time when he needs to buy an item as all the events such as
searching, purchasing are done by members of the staff .In briefly, the manual process is very slow. But
automation will reduce the time taken in the whole process.
In a company we should deal with a large store. Then person (storekeeper) has to maintain it with
documents which are recorded by him. Therefore, there may be defective reports. Also company has to
appointed more persons to complete the maintenance of the stationery. Then the company has to have an
additional cost.

FUNCTIONAL REQUIREMENTS

Functional requirements specify which outputs should be produced from the given inputs. They describe
the relationship between the input and output of the system. For each functional requirement, a detailed
description of all the data inputs and their source, the units of measure, and the range of valid inputs must
be specified. All the operations to be performed on the input data to obtain the output should be specified.
This includes specifying the validation checks on the input and output data.
PURPOSE OF THIS DOCUMENT

The purpose of this document is to convey the requirements of the project (as specified by the client) to
the programmers to ensure that the programmers understand and fulfill the requirements to the expectation
of the client Secondly, this document is used to ensure that the development team understands the
requirements specified by the client. This document will act as the contract for all future development; all
development spawns from and adheres to the details in the requirements. The SRS also outlines the
performance requirements that may be set and required by the client/user.

This document provides a description of the purpose, functionality and interface of the software designed
by the developer with input of the project. In this Software Requirement specification, constraints and
other design issues are addressed.

Overview of Document

The remainder of this document describes the intended users that would be expected to interact with the
system frequently, and a simple profile of each user type is provided as a sample. This document now will
go into more detail on the expected users their interface and interaction with the product and more on the
technical approach and considerations to be implemented.

General Description

User Persons and Characteristics:

The primary users of this product are the Institute employees, director perspective candidates. Most of
them already have some experience in using computer components (mouse and keyboard), and are willing
to learn and explore under the supervision of their superiors. The employees have adequate knowledge so
that they can be trained easily to operate the system.
Overview of Functional Requirements

Our product will be stand alone and will have an interface, which can be accessed on more than one-
computer at the same time, such as computers connected with LAN. Our main goal is to present facts on a
comprehensive level, and make it easier as well.

Hardware Interface Requirements:


Our product will require at least a PowerPC Macintosh or a Pentium class PC with 64 MB of RAM (64+
recommended), and color display.

Other Software Components: Operating System: WindowME/NT/2000

Template for describing functional requirements

Purpose A description of the functional requirement and its


motivations(s)

Inputs which inputs; in what form/format will inputs


arrive; from what sources input will be derived;
legal domains of each input element

Processing Describes the outcome rather than the


implementation; include any validity checks on the
data, exact timing of each operation (if needed),
how to handle unexpected or abnormal situations

Outputs the form, shape, destination, and volume of the


output; output timing; range of parameters in the
output; unit measure of the output; process by
which the output is stored or destroyed; process for
handling error messages produced as output.
Tools/Platform

Hardware Tools To Be Used: -

Processor :- Intel Pentium IV 2.4 GHz.


Mother Board :- 845E Intel chipset.
RAM :- 512 MB. DDR II.
Monitor :- LG Color 15” (Studio works 452v)
Keyboard :- TVS Gold 104-105 keys.
Mouse :- 3 Buttons Logitech.
Hard Disk :- 160 GB. Seagate.
Ports :- USB.

Software Tools To Be Used: -

Platform :- Windows.
Operating System :- Windows XP SP2.
Front-End-Tool :- JSP with JavaScript.
Back-End-Tool :- Oracle 10G.
DATA FLOW DIAGRAMS

Zero Level Data Flow Diagram

The Online
Existing Existing
User Auction User
Make query Response
System
FIRST LEVEL DFD FOR ITEMS ENQUIRY

Customer
Customer Searching
Items
1 ITEM

Accessing Item
Invalid Item Info
Info
Search
Process Accessing Item Info

Valid Item for Display

Item Info Display


Process
FIRST LEVEL DFD FOR CUSTOMER ENQUIRY

EMPLOYEE

Customer Code For 1 Customer


Searching

Accessing Customer
Info
Invalid Search Process
Customer

Valid Customer for


Display

Customer Info Display Process Accessing Customer


Info
FIRST LEVEL DFD FOR CHANGE PASSWORD

USER

User Enter Their Id And 1 User_Id


Password For Changing
Password
Accessing User
Info

User_Id And
Invalid Password
Password Validity Process

Valid User For New


Password

Password Updating Password


New Password Updating
Information
Process
E -R DIAGRAM FOR OAS
Phone
C_Code E_Code E_Name No.
C_Name Salary
Subject
E_mail Staff Qualification
Company
Designation
City T_Address
Department
Date of joining
Phone
No. Branch
P_ Address
Address
Description
E_mail
User_Id.
ISBN B_Name
User
OAS
Sample Pwd
I_code.
C_Date
Itemid
Qty.
Qty Company
Have Price

Custid B_id Bill


Time

Itemname
Tot_amount
Date_of_bill
Itemid
Item_Master
Made_of_Payment

Incrementcost

Initialcost
Cdate

Noofdays Type Itemdesc


Use Case Diagram

User
Registration

User Login

Search Item

Browse
Itemss
Web Customer

Purchase
Items

View Items
Modules And Their Process Logic

Module: - 1. User.

Description: - This module manages the list of users, which may use this software. This module adds,
remove and change the password of different users.

Module: - 2. Item Search.

Description: - This module displays the all information about the Item according to the selection criteria
of the customer. This module gives the facility of selecting different types of query about the particular
Item.

Module: - 3. Staff Enquiry.

Description: - This module displays the all information about staff according to the selection criteria of
the manager. This module gives the facility of selecting different types of query about the particular staff
member

Module: - 4. Customer Enquiry.

Description: - This module displays the all information about customer, who buys the item on credit. This
module gives the facility of displaying previous balance, current credit amount and list of items.

Module:- 5. Staff Master.

Description: - This module handles the all possible operations which may be apply on the
database of staff such as Insert, Delete and Modify etc.
Module: - 6. Item Management.

Description: - This module handles the purchasing of the Item for Company on request of Customer, staff
members. This module also maintains the record of the Product display for the Marketing in the Particular
area.

Module: - 7. Sample Master.

Description: - This module handles the all information about the sample which gives free to the
Customer for use and after that they use this product regularly. And by this
Company came to know that what the Customer want and its need to improve.
DATA STRUCTURE OF EACH MODULE

Table Name: - Admin Login

Field Name Data Type Constraints


User_Id. Varchar(100). Not Null.
Pwd. Varchar(100). Not Null.
Primary Key: -User_Id.

Table Name: - Item Master

Field Name Data Type Constraints


Custid Int Null
Itemid Int Null
Itemname Varchar(25) Null
Intitalcost Float Null
Incrementcost Float Null
Itemdesc Varchar(50) Null
Noofdays Varchar(25) Null
Type Varchar(25) Null
Cdate Datetime Null
Primary Key: -Custid.

Table Name: - Buyer

Field Name Data Type Constraints


Itemid Int Null
Itemname Varchar(20) Null
Custid Int Null
Buyerdate Datetime Null
Amount Float Null
Type Varchar(25) Null
Primary Key: -Itemid.
Table Name:- Sample_Master

Field Name Data Type Constraints


Itemid Varchar(20). Not Null.
I_Describe Varchar(50). Null
I_Catagory Varchar(10). Not Null.
I_Price Number(10,2). Not Null.
Qty Number(5). Not Null.
Company Varchar(100) Not null
Sample_type Varchar(10) Not null
Primary Keys:- Itemid.

Table Name:- Item_Stock_Transaction

Field Name Data Type Constraints


Itemid Varchar(20). Not Null.
I_Describe Varchar(50). Null
I_Catagory Varchar(10). Not Null.
I_Qty Number(5). Null.
FormDate Date/Time Not Null.
Company Varchar(100) Not null
Primary Keys:- Itemid

Table Name:- Staff_Details

Field Name Data Type Constraints


S_Code Varchar2(20) Not Null.
Name Varchar(8). Not Null.
F_Name Varchar(18). Not Null
Date_of_Birth Date/Time Not Null
Nationality Varchar(8). Not Null.
Post Varchar(8). Not Null.
Sex Varchar(5) Not Null.
Marital Status Varchar(8). Not Null.
Address Varchar(100). Not Null.
City Varchar(100). Not Null.
Pin Varchar(6). Not Null.
State Varchar(100). Not Null.
Qualifications Varchar(100). Not Null.
Experience Varchar(100). Not Null.
Salary Number(10). Not Null.
Primary Keys:- S_Code
Table Name:- Bill

Field Name Data Type Constraints


B_id. Number(15). Not Null.
Itemid. Varchar2(26). Null.
Qty. Number(5). Null.
Price Number(5). Null.
Tot_Amount. Number(6,2) Null.
Date_of_Bill Datetime Not Null.
Time. Varchar(10) Null.
Mode_of_Pay Varchar(10) Not Null.
Primary Keys:- B_id.

Table:- Company Master

Field Name Data Type Constraints


C_Code. Varchar(6). Not Null.
C_Name Varchar(20). Null
Branch Add Varchar(20). Not Null.
Phone Varchar(15). Null.
Email id Varchar(40). Not Null.
Primary Keys:- C_Code
SECURITY MEASURES TAKEN

The dictionary definition of security encompasses a set of measures taken to guard against theft, attack,

crime and sabotage. Here, security measures include control and monitoring physical access to the

software.

Authentication is one of the physical security measure taken to deny access to unauthorized users and to

allow legitimate users. Since unauthorized access or destruction of data can violet individual’s privacy.

Corruption or theft of business data can result in significant and potential catastrophic loss or mills.

So, in the software under this project, the most common authentication mechanism namely “Password” is

applied to prevent from any authorized access.

In the software, when logging in, it request to the user for a secret and user specific password. The

software matches the user-supplied password. If it matches with software inherent coded password, then

the main menu of the software is available to the user to access otherwise it denies and asks to enter right

password. Similarly, an authentication known as Access Groups is applied to protect the table created in

oracle environment from unauthorized access.


Conclusion
Summary
Online Auction System is a new experience and has greatly impacted the lives of consumers in its short
time of existence. It is expected to grow constantly in years to come with advancements in technology.
Online Auction System has made consumers more effective and efficient in their behavior and has driven
businesses to a new level, forcing many to make the necessary adjustments and changes to reach the new
market of knowledgeable consumers.

The results of this survey underscore the need for businesses to take the online market seriously. The
survey conducted revealed a positive attitude and behavior toward online Auction System even by those
consumers who still like traditional stores. These consumers are mostly in low and high age groups. Those
consumer groups have time to spend in traditional stores and malls and value the offline Auction System
experience for social reasons, such as meeting with friends. These consumers appear to be more
knowledgeable by gathering information online and then purchase it from traditional stores. Rapid growth
of e-auction has resulted in a e-transformation in the global retail infrastructure. Internet has emerged as a
cost effective means of doing business.

Despite being faced with numerous bottlenecks, Thanks to rising internet and higher incomes and more
savvy population. Secured online payments, better to Electronic Stores, return policies and exciting
discounts could help the Perceptions of Auction System Benefits. Considering the demographic profiles of
online users; gender, age and education have significant association to web Auction System in the current
Indian scenario. Online users are aware of the serviceable and pleasure-seeking benefits of online Auction
System, they are reluctant to actually utilize internet for Auction System purpose. The overall results
prove that the respondents have perceived online Auction System in a positive manner. This clearly
justifies the project growth of online Auction System in the country. However, the frequency of online
Auction System is relatively less in the country.

Online Auction System organizations can use the relevant variables and factors, identified from the study,
to formulate their strategies and plans in the country. The organizations can prioritize the consumer
implicit and explicit requirements in Online Auction System environment. The results can also be used by
various organizations to identify their target customer segments. The results of the study can be utilized
by practitioners in 45% relooking or revamping their strategies for Online Auction System. Online
websites should pay more attention to the female segments as results prove that females shop more in
online Auction System as compared to men.

So companies should devise the policies and strategies to attract more number of people in this segment in
future also. With the advances in technology, more business opportunities will be discovered by
companies. Electronic commerce will become an important part of the business in companies. Better
understandings of consumer online Auction System behavior will help companies in getting more online
consumers and increasing their e- business revenues. At the same time, as realized the benefits from e-
auction, consumers are more willing to make purchases online. With the popularity of Internet, the
number of Internet users will continue to grow and more Internet users will become online consumers,
even regular online buyers.

However, the evolvement of e-auction will bring new problems. The changes in business operation,
business environment, and economic condition etc. will affect consumer online Auction System behavior.
Therefore, continuous efforts have to be devoted to studying consumer online Auction System 230
behavior in a dynamic way. With the knowledge of consumer online Auction System behavior, it is
believed that e-auction will continue to grow and it will become not only an important business revenues
channel, but also a part of people’s daily life.

Future Work:

The future plan of this project is to improved design; implementation and documentation in such a way
that anyone can use this project for better perform. I will develop the site more dynamically and the
database work as well. There are some limitations in my project. In future I will add the following module
for better improvement of the project.

 Mobile application of the existing sites.

 More security in the system.

 More user friendly system.


REFERENCES
It is very important that we acknowledge the work of others that we have used

or adapted in our work, or that provides the essential background or context to our project.

The use of references is the standard way to do this. Please follow the references for books,

journals, and online materials given here these are very helpful for us.

BOOK REFERENCES
1. ISO/IEC: 18019: Guidelines for the Design and Preparation of User Documentation for

Application Software.

2. All semesters of MCA IGNOU study material.

WEBSITE REFERENCES
1 http://www.w3schools.com/jsp/default.asp

2 http://www.jsp/get-started

3 NPTEL Video Lectures on Software Engineering By Prof. N.L. Sarda, Prof. Umesh

Bellur and Prof. Rushikesh K Joshi, IIT Bombay

http://nptel.iitm.ac.in/video.jsp?courseId=1076