Essay: The IT Mart auction system

Abstract:
The IT MART (online auctioning) system is a flexible solution for supporting lot- based online auctions. It explains the construction of an auction website. This system has been designed to be highly-scalable and capable of supporting large numbers of bidders in an active auction. The IT MART system lets you easily browse lots and place bids using a secure server. All cost of mailing lots will be paid by the buyer. The objective is to develop user-friendly auctioning site where any kind of product can be auctioned and provide value added services to the bidders and the sellers. The products will be authenticated and the site provides a safe environment for online users.
CHAPTER 1
*INTRODUCTION:
An Auction is Latin work which means augment. Auction is a bid, a process of selling; buying and services offered take place. There are several different types of auctions and certain rules exist for each auction. There are variations for an auction which may include minimum price limit, maximum price limit and time limitations etc. Depending upon the auction method bidder can participate remotely or in person. Remote auction include participating through telephone, mail, and internet. Shopping online has widely grown online auction system is increasing rapidly.
The online auction system is a model where we participate in a bid for products and service. This auction is made easier by using online software which can regulate processes involved. There are several different auction methods or types and one of the most popular methods is English be highly-scalable and capable of supporting large numbers of bidders in an active auction.
The online auction system is a model where we participate in a bid for products and
service. This auction is made easier by using online software which can regulate process involved. There are several different auction methods or types and one of the most popular methods is English auction system. This system has been designed to be highly-scalable and capable of supporting large numbers of bidders in an active auction. Online Auctioning System has several other names such as e-Auctions, electronic auction etc. The requirement for online auction or online bidding can be more accurately specified by the client.
Online Bidding has become more wide spread in all sorts of industrial usage. It not only includes the product or goods to be sold, it also has services which can be provided. Due to their low cost this expansion made the system to grow. Online bidding has become a standard method for procurement process. Bidders can be maintained in a single database according to the preference, and they can be monitored. User’s data can be maintained in a confidential way for validity and integrity of contractual documentation. Neat reporting reduces paperwork, postage, photocopying and time 2 beneficial.
It should be healthy and will be a good practice when it is made more transparent as a matter of fact. Multiple bidders can be communicated with a great ease. This system allows multiple bids by single users .Online bidding is based upon lowest or the highest price which is initiated but not the best value for the product. Although there is a chance to fix the criteria against the fact expected to have desired value by the seller.
1.1 OVERVIEW
The Objective is to develop a user-friendly auctioning site where any kind of product
can be auctioned and provide value-added services to the bidders and the sellers. The
products will be authenticated and the site provides a safe environment for online users:
‘ Secure registration of all users including a personal profile Administrators would
authorize the product to auction, set auction dates and Minimum auction amount for
that product.
‘ Prior to each bid, the user’s bank or credit account must be authenticated for available
balance required for the bid.
‘ Complete Search/Site Map of the entire site for easy access.
‘ Discussion forums for users to interact with other users to know about the product’s
value and originality.
‘ Online Legal Documentation to avoid disputes. Guidance to the users about the same
must be available.
‘ Rare articles may be withheld by owner on the advice of the administrator to be
thrown open in special auctions held by the site so as to increase the bid-values.
.
1.2 DESCRIPTION FORMODULES
The following sections include the descriptions for modules.
1.2.1 Admin Module
This module provides the complete information related to products for sale and the
buyers can bid for the products and can own them. All this has to be provided and maintained
by the admin because the complete auction process is to be kept under control till the product
sale gets confirmed.
1.2.2 Seller Module
Sellers want a place where seller can sale their products at a higher price and get
maximum benefit out of that. This is the place where seller can display all his products and
sell them.
1.2.3 Buyer Module
The people always want different things to purchase but in the local market they can
have local products only. But in this application buyer can buy any product from any part of
the world at a very best competitive price and own the product.
1.2.4 Visitor Module
Visitor is nothing but all the people who visits this application online. They can
know the information of all the products, which are for sale under this application.
1.2.5 Security and Authentication
The security and authentication is as follows:
‘ Login as buyer or seller or administrator.
‘ Change password.
‘ Forgot Password.
‘ Registration for buyer / seller.
1.2.6 Reports
In this module, different actors can generate the different types of reports according to
their access.
CHAPTER 2
RESEARCH & TECHNOLOGY
The online auctioning system is a flexible solution for supporting lot- based online
auctions. The system has been designed to be highly-scalable and capable of supporting large
numbers of bidders in an active auction. To help business with finance’s and purchases in
online auctioning system.
2.1 RESEARCH
Research includes what existing system is and the purpose of the system.
2.1.1 Existing System
From a recent study make by scientists at Carnegie Mellon University, found many
fraud schemes from the historical auction data using data mining techniques and other
accomplice [3,12]One of the most currently fraud schemes is that the bidders are masking
false identity or accounts in order to increase the sale price [12,13].
Currently there are two approaches mostly being implemented such as policy-based
and reputation-based trust management [2], which also lag certain security issues.
There was a recently proposed system by which was areputation based model for sensor networks. This system works well in maintain the
reputation for the nodes and also in evaluating trustworthiness [7]. But the main drawback is
that there is no effective and particular method to prevent the users from giving false identity
and hence the system fails in providing a secured environment.
2.1.2 Proposed System
The development of this new system contains the following activities, which try to
develop the web-application entire process keeping in the view of database integration
approach:
‘ This system will generate team progress and also provides secure registration and
profile management of the users.
5
‘ Administrators would authorize the product to auction, set auction dates & minimum
auction amount for that product.
‘ Prior to each bid, the user’s bank or credit account must be authenticated for available
balance required for the bid.
‘ Users can select their interested fields for bidding and periodic Mail alerts must be
sent in case an article in that field goes on auction.
‘ Complete Search/Site Map of the entire site for easy access.
2.1.3 Requirements
The Objective is to develop a user-friendly auctioning site where any kind of product
can be auctioned and provide value-added services to the bidders and the sellers. The
products will be authenticated and the site provides a safe environment for online users:
‘ Secure registration of all users including a personal profile.
‘ Prior to each bid, the user’s bank or credit account must be authenticated for.
‘ Available balance required for the bid.
‘ Complete Search/Site Map of the entire site for easy access.
2.2 TECHNOLOGYDESCRIPTION
The proposal has to be described in a detailed form to get an overview and an
understanding of the functionalities of the technical approach. This provides the technical
description of the characteristics of a proposal.
2.2.1 HTML
HTML, an initialize of Hypertext Markup Language, is the predominant markup
language for web pages. It provides a means to describe the structure of text-based
information in a document ‘ by denoting certain text as headings, paragraphs, lists, and so
on ‘ and to supplement that text with interactive forms, embedded images, and other
objects.
2.2.1.1 HYPER TEXTMARKUPLANGUAGE
Hypertext Markup Language (HTML), the languages of the World Wide Web
(WWW), allows users to produces Web pages that include text, graphics and pointer to other
Web pages (Hyperlinks).
6
HTML can be used to display any type of document on the host computer, which can
be geographically at a different location. It is a versatile language and can be used on any
platform or desktop.
HTML provides tags (special codes) to make the document look attractive. HTML
tags are not case-sensitive. Using graphics, fonts, different sizes, color, etc., can enhance the
presentation of the document. Anything that is not a tag is part of the document itself.
2.2.1.2ATTRIBUTES
The attributes of an element are name-value pairs, separated by “=”, and written
within the start label of an element, after the element’s name. The value should be enclosed in
single or double quotes, although values consisting of certain characters can be left unquoted
in HTML (but not XHTML).Leaving attribute values unquoted is considered unsafe.
Most elements take any of several common attributes: id, class, style and title. Most also take
language-related attributes: language and dir.
2.2.1.3ADVANTAGES
The advantages include:
‘ A HTML document is small and hence easy to send over the net.
CHAPTER 3
METHOD
The Action Form class provided by the Struts framework is abstract. You need to
create subclasses of it to capture your application specific form data. Within your subclass,
you should define a property for each field that you wish to capture from the HTML form.
The Action Form is populated from request parameters, not request attributes. If you
are forwarding from one action to another, you can’t add a request attribute and expect that
the Action Form will be populated from it. Request parameters and request attributes are two
separate resources.
3.1 The Action Form reset() Method
The re set() method has been a bane for much of the Struts user community at one
time or another. Exactly when the re set() method is called and what should be done within it
is almost always misinterpreted. This doesn’t mean that one implementation is more correct
than another, but there are misconceptions that many new Struts developers pick up and then
have a hard time shaking regarding the reset().
It’s called before the Action Form has been populated from the request. The method
was added to the Action Form class originally to help facilitate resetting boolean properties
back to their defaults. To understand why they need to be reset, it’s helpful to know how the
browser and the HTML form submit operation processes checkboxes. When an HTML form
contains checkboxes, only the values for the checkboxes that are checked are sent in the
request. Those that are not checked are not included as a request parameter. Therefore, the
reset() method was added to allow applications to reset the boolean properties in the
Action Form back to false, since false wasn’t included in the request and the boolean values
would possibly be stuck in the ‘true’ state. The reset() method in the base Action Form
contains no default behavior, since no properties are defined in this abstract class.
Applications that extend the Action Form class are allowed to override this method and reset
the Action Form properties to whatever state they wish. This may include setting boolean
properties to true or false, setting String values to null or some initialized value, or even
instantiating instances of other objects that the Action Form holds on to. For an Action Form
that has been configured with request scope, the framework will essentially create a new
instance for each new request. Since a new instance is created, there’s not much need to
reset() the values back to any default state. Action Forms that are configured with session
scope are different however. This is the time that the reset() method comes in handy.
3.2 DATAFLOW
A graphical tool used to describe and analyze the moment of data through a system
manual or automated including the process, stores of data, and delays in the system. Data
Flow Diagrams are the central tool and the basis from which other components are
developed. The transformation of data from input to output, through processes, may be
described logically and independently of the physical components associated with the
system. The DFD is also know as a data flow graph or a bubble chart.
DFDs are the model of the proposed system. They clearly should show the
requirements on which the new system should be built. Later during design activity this is
taken as the basis for drawing the system’s structure charts.
1. Data Flow Diagram
Process: People, procedures, or devices that use or produce data
1st level of search:-
1st level of Token Generate:
1ST Level of Recruite:
3.3 UNIFIEDMODELING
LANGUAGE (UML) DIAGRAMS
The Unified Modeling Language allows the software engineer to express an analysis
model using the modeling notation that is governed by a set of syntactic semantic and
pragmatic rules. A UML system is represented using five different views that describe the
system from distinctly different perspective. Each view is defined by a set of diagram, which
is as follows.
3.3.1 User Model View
This view represents the system from the users perspective. The analysis
representation describes a usage scenario from the end-users perspective.
3.3.2 Structural Model View
In this model the data and functionality are arrived from inside the system. This
model view models the static structures.
3.3.3 Behavioral Model View
It represents the dynamic of behavioral as parts of the system, depicting the
interactions of collection between various structural elements described in the user model and
structural model view.
3.3.4 Implementation Model View
In this the structural and behavioral as parts of the system are represented as they are
to be built.
3.3.5 Environmental Model View
In this the structural and behavioral aspects of the environment in which the system is
to be implemented are represented.
UML is specifically constructed through two different domains they are:
‘ UML Analysis modeling, this focuses on the user model and structural model views
of the system.
‘ UML design modeling, which focuses on the behavioral modeling, implementation
modeling and environmental model views.
Use case Diagrams represent the functionality of the system from a user’s point of
view. Use cases are used during requirements elicitation and analysis to represent the
functionality of the system. Use cases focus on the behavior of the system from external
point of view
Actors are external entities that interact with the system. Examples of actors include
users like administrator, buyer, seller’etc., or another system like central database.
System here refers to the Online Auctioning system and the actors that are using the
system are Admin and Customer
Admin can view all the customers, view the bid items, view today and end day
auction items and view the profiles of the customers Customer registers, and upon successful login can buy or sell the items, can view his
profile, can view the new auction items today and end day
Figure shows an Admin sequence diagram.
After providing login details for admin login the details will be validated and after
2.Structured Design:-
Context Level:-
3. System Use case Diagram:
3. System analysis and Design
Object Oriented Design
3.1 Use Case Diagram:-
1. System Use Case:-
2. Admin Use Case:-
‘
3. Customer Use Case:-
4.Logical design diagram:
E-RDiagram:
E-R Diagram:-
5. Activity Diagram:-
1. system:-
2. Admin Activity Diagram:-
3. Customer Activity Diagra m:-
4.IT Vender Activity Diagram:-
6. Sequence Diagram:-
CHAPTER 4
TESTING
4.1 SOFTWARE TESTING
Software Testing is the process used to help identify the correctness, completeness,
security, and quality of developed computer software. Testing is a process of technical
investigation, performed on behalf of stakeholders, that is intended to reveal quality-related
information about the product with respect to the context in which it is intended to operate.
This includes, but is not limited to, the process of executing a program or application with the
intent of finding errors. Quality is not an absolute; it is value to some person. With that in
mind, testing can never completely establish the correctness of arbitrary computer software;
testing furnishes a criticism or comparison that compares the state and behavior of the
product against a specification. An important point is that software testing should be
distinguished from the separate discipline of Software Quality Assurance (SQA), which
encompasses all business process areas, not just testing.
There are many approaches to software testing, but effective testing of complex
products is essentially a process of investigation, not merely a matter of creating and
following routine procedure. One definition of testing is “the process of questioning a
product in order to evaluate it”, where the “questions” are operations the tester attempts to
execute with the product, and the product answers with its behavior in reaction to the probing
of the tester [5]. Although most of the intellectual processes of testing are nearly identical to
that of review or inspection, the word testing is connoted to mean the dynamic analysis of the
product’putting the product through its paces. Some of the common quality attributes
include capability, reliability, efficiency, portability, maintainability, compatibility and
usability. A good test is sometimes described as one which reveals an error; however, more
recent thinking suggests that a good test is one which reveals information of interest to
someone who matters within the project community.
In general, software engineers distinguish software faults from software failures. In
case of a failure, the software does not do what the user expects. A fault is a programming
53
error that may or may not actually manifest as a failure. A fault can also be described as an
error in the correctness of the semantic of a computer program. A fault will become a failure
if the exact computation conditions are met, one of them being that the faulty portion of
computer software executes on the CPU. A fault can also turn into a failure when the
software is ported to a different hardware platform or a different compiler, or when the
software gets extended. Software testing is the technical investigation of the product under
test to provide stakeholders with quality related information.
Software testing may be viewed as a sub-field of Software Quality Assurance but
typically exists independently (and there may be no SQA areas in some companies). In SQA,
software process specialists and auditors take a broader view on software and its
development. They examine and change the software engineering process itself to reduce the
amount of faults that end up in the code or deliver faster.
Regardless of the methods used or level of formality involved the desired result of
testing is a level of confidence in the software so that the organization is confident that the
software has an acceptable defect rate. What constitutes an acceptable defect rate depends on