Project report(Smart Auction Access)

Smart Auction Access
Chapter 1
Introduction
1.1Problem summary:
 Auction is illegal in some countries. All countries not allow the people to make
auction.
 Seller have no right to sell their product by own decided price. All the pricing
decision taking by government agency.
 If there is manual auction system then you can’t directly put bid on that product.
There is always region limitation in Manual auction system.
1.2Aim and objectives ofthe project:
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.
 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.
1.3Problem specification:
The application of these online services removes the problem of distance between seller and
buyer. Its save the time of user here time saving problem is specified. Globally access this
site. Any register user any time sells and buy the products. Like that way this system
performs various problem solutions

1.4 Review of literature and Prior- art search:
Patent search report summary:
Table 1: patent search report
Web Search/Research
Publication
User Feedback Vendor/Market
Research
Patent Search
US2010035226 Computerized
Education
Chen upia Computerized
Education Device
Google patent
US 20130236877
Desktop computer Tiger T G, System and methods
for providing
Educational products
via cloud massive
Google patent
US 8060004 B2
Learning Jerzy Kallisiak Methods of Distance
Learning
Google patent
EP 0755608
Education Linda Grant Gregory
W Harper
Distance learning
System providing
individual television
participation
Google patent
US 7082418
informational AMellia Ellsworth Network based
personalized
education
Google patent
US 80498
Distance learning Fainholdolaeksii Method for creating
distance learning
Google patent
US 201214356845
Distributed
education
Huber robert System for
distributed education
Google patent
US 6024577
Review material Fujitsu limited System with
capability provide
review material
Google patent
EP 20040251496
Education system Kazuhorisumi Distance Education
System

1.5Plan of work
Table 2: plan of work
Duration of the Work Completed Work
July-August Finding the project definition and brief
learning about project.
August-September Doing literature survey to add functionality
in the project.
September-October Searching about patents of previous projects
which are related to our projects and also
made product development and ideation
canvas.
October-November Submitted PSAR report and verify the
documentation. Also made other observation
matrix canvas.
November-December Submitted Software Requirement
Specification report.
December-January Learn advanced JAVA and struts2
framework for developing project.
January-February Start with Admin module with designing and
completed with Admin module and
employee module.
February-March Adding extra features in user module and
completed visitor module. Submitted
progress report 1 and 2.
March-April Completed user module with all
functionalities. Also add the feature of online
payment for property, water tax and
submitted Business model canvas and its
report. Submitted progress report 3 and 4.
April-May Testing of the System and correcting
mistakes and finally documentation.

1.6Materials/Tools required
1.6.1 Hardware requirements
Main hardware is computer. Since the application must run over the internet, all the
hardware shall require to connect internet will be hardware interface for the system.
As for e.g. Modem, WAN – LAN, Ethernet Cross-Cable.
1.6.2 Software requirement
` Table 3: Software requirements
Following are some of the significant new features of Eclipse juno:
 Simplified Deployment
 Flexible & Simplified Data Access
 Web based Applications
 Stability
 Security
 More reuse because of inheritance
Components Development
Operating System Window 8
Language Advance Java using various
frameworks(Struts 2.0)
Front End Eclipse juno
Back End tool SQL server

Microsoft SQL Server 2008 Features:
The database component of Microsoft SQL Server 2008 is a Structured Query Language
(SQL)–based, scalable, relational database with integrated Extensible Markup Language
(XML) support for Internet applications. Following are some of the significant new features
of SqlServer 2008.
 Internet Integration
 Scalability and Availability
 Enterprise-Level Database Features
 Ease of installation, Deployment and Use.

Chapter 2:
Design: Analysis, design methodology and implementation strategy
In this chapter, we will see design methodology of our project and canvas exercise. Canvas
exercise includes various canvases which we have made and brief description of those
canvases.
2.1Design methodology:
In order to achieve the solution of the project we have divided work as follows:
 Study about the requirement of user.
 Analysis of the project with patent search.
 Decide the language in which we are going to implement.
 Study of the framework which make coding easy.
 Study of adding the functionality in the modules.
 Decision taking of testing and verifications.
 Study the document and implement it on canvas.
 Study of market and make the business model.
2.2 Canvas strategy:
2.2.1 Observation matrix canvas:
The objective is to adopt systematic approach based on design thinking and articulate
the insights derived from empathization process including observation, interaction etc during
ISY (Industrial Shodh Yatra) and finalise the problem/IDP/UDP definition and orient the task
as their final year project. In observation matrix we studied about some areas that are follows
and also put the image:
There are five sections in observation matrix that are:
 Observations
 Scouted challenges
 Top 5 problems on the basis of desirability, feasibility, viability.

 Final problem select 1 from top 5
 Photo grid
The image of observation matrix:
Fig.1 Observation matrix
1. Observations
Improper UI, People have not Many Choice, Service for limited area, Timing
Problem.
2. Challenges
Security, Reducing Work, Proper UI, Time Management, Globally access, People
have Many Choices.

3. Top 5 problems on the basis of Desirability, Feasibility and Viability
Time Management Problem, Security Problem, Database Management Problem,
Session Expiration Problem, Bid Management Problem.
4. Final Problem select 1 from Top 5
Bid Management
2.2.2Ideation canvas:
An ideation canvas is a rough whiteboard/sheet where ideas can be stretched into any limits
or dimensions. Its aim is to define the best possible problem and stretch out its possible
scope. The field is set and the overall agenda is to build the clones of the ideas and pivot them
throughout the canvas so as to discover new possibilities.
In this canvas there are seven section that are follows and also images as follow:
 People
 Activities
 Problem
 Situation/context/location
 Props/possible solution
 Input
 Revenues
1. People
Master Admin, Visitors, Users.
2. Activities
Registration, Login, Manage Profile, Product Upload, Manage Payment, Bid,
Feedback.
3. Problem
Physical distance, Lack of time.

4. Situation/Context/Location
Organization, Home, Globally Access.
5. Props/Possible Solutions
Easy Access, Time saving, Online Billing, Globally Access.
6. Inputs
Bid Information, Product Information, Payment and Order Information, User
Information, and Ratings.
7. Revenues
Advertisements, Bid Fees, Add-on
The image of ideation canvas:
Fig. 2 ideation canvas

2.2.3 Product Development Canvas:
This exercise is meant for giving strategic orientation to the project of each team so that it
achieves its true goal as defined by the previous canvas exercises. This exercise is more
about developing strategy for the proposed product/solution design.
 People
 Purpose
 Product experience
 Product functions
 Product features/ key components
 Components
 Customer revalidation
 Reject, Redesign and Retain
1. Purpose
Online Selling and Purchase, Easy to Access, Globally Access, More Realisable,
Time saving.
2. People
Master Admin, Visitors, Register Users.
3. Product Experience
Time Saving, Faster Response, Better Performance.
4. Product Functions
Flexible Environment, User Friendly GUI, Security, Durability.
5. Product Features
Blacklist, Fully Cutomizable,Notification,Support,Unlimited categories, Enable and
Disable Features.

6. Components
Software Specification (Windows OS), Front-end (J2EE, HTML, CSS, JavaScript,
JQuery), Back-end (MYSQL Server).
7. Customer Revalidation
Not applicable now.
8. Reject/Redesign/Retain
Not Applicable now
The image of product development canvas:
Fig 3 Product development canvas

Chapter 3
Implementation
We had done our whole project in eclipse and implementation using java platform
Below are snapshots of our whole project. :
3.1 Snapshots
3.1.1 User
Fig 4 Home

Fig 5 Login as user
Fig 6 Registration form

Fig 7 Validating fields in form
Fig 8 forget password

Fig 9 upload product
Fig 10 live product

Fig 11 close product
Fig 12 future product

Fig 13 payment
Fig 14 user profile

Admin Module:
Fig 15 Admin login page
Fig 16 all products

Fig 17 all Products with category
Fig 18 close Product

Fig 19 future product
Fig 20 live product

Fig 21 all users

3.2 Data Dictionary
Table 4: tbl_registration
Sr. No. Fields Data Type Constraints
1 Id Int Primary key
2 F_name Varchar(50) Not Null
3 L_name Varchar(50) Not Null
4 Address Varchar(100) Not Null
5 Email Varchar(20) Not Null
6 Password Varchar(20) Not Null
7 Mobile Int Not Null
8 Gender Varchar(50) Not Null
9 Country Varchar(50) Not null
10 State Varchar(50) Not null
11 City Varchar(50) Not null
Table 5: tbl_bid
1 Product_id Int Foreign key
2 User_Id Varchar(50) Not Null
3 Bid_price Varchar(50) Not Null

Table 6: tbl_product
1 Product_id Int Primary key
2 User_id Int Not Null
3 Product_name Varchar(50) Not Null
4 Product_company Varchar(50) Not Null
5 Starting Price Int Not Null
6 Category Varchar(50) Not Null
7 Description Varchar(50) Not Null
8 Username Varchar(50) Not Null
9 Filename Varchar(50) Not Null
10 Upload Date Date Not Null

3.3 Testing:
Software testing is the process of executing a program with intension of finding errors in the
code. It is a process of evolution of system or its parts by manual or automatic means to
verify that it is satisfying specified or requirements or not.
Generally, no system is perfect due to communication problems between user and developer,
time constraints, or conceptual mistakes by developer. To purpose of system testing is to
check and find out these errors or faults as early as possible so losses due to it can be saved.
Testing is the fundamental process of software success.
Testing is not a distinct phase in system development life cycle but should be applicable
throughout all phases i.e. design development and maintenance phase. Testing is used to
show incorrectness and considered to success when an error is detected.
Objectives of Software Testing:
The software testing is usually performed for the following objectives:
SOFTWARE QUALITY IMPROVEMENT: The computer and the software are mainly used
for complex and critical applications and a bug or fault in software causes severe losses. So a
great consideration is required for checking for quality of software
Verification and validation:
Verification means to test that we are building the product in right way .i.e. are we using the
correct procedure for the development of software so that it can meet the user requirements.
Validation means to check whether we are building the right product or not.
Software Reliability Estimation:
The objective is to discover the residual designing errors before delivery to the customer. The
failure data during process are taken down in order to estimate the software reliability.
Principles of Software Testing:
 It is impossible to test everything

 Testing time and resources should be limited i.e. avoid redundant testing.
 Use effective resources to test
 Test should be planned long before testing begins i.e. after requirement phase
 Test for invalid and unexpected input conditions as well as valid conditions
 Testing should begin in “in the small” and progress towards testing “in the large”
 For the most effective testing should be conducted by an independent party
 Keep software static (without change meanwhile) during test
 Document test cases and test results
 Examining what the software not doing which it expected to do and also checking
what it is doing that was not expected to do.
3.3.1 Testing Strategy:-
Different levels of testing are used in the test process; each level of testing aims to test
different aspects of the system.
 Unit Testing: In this testing, individual components are tested to ensure that they
operate correctly. It focuses on verification efforts.
 Integration Testing: It is a systematic technique for constructing the program
structure. In this testing, many tested modules are combined into the subsystems
which are then tested.
 System Testing: System testing is actually a series of different tests whose primary
purpose is to fully exercise computer based system. These tests fall outside scope of
software process and are not conducted solely by software engineers.
 Acceptance Testing: It is a kind of testing conducted to ensure that the software
works correctly in user’s working environment.
3.3.2 Test Cases:
The purpose of a test case is to describe how you intend to empirically verify that the
software being developed conforms to the specifications. In words, you need to be written
with enough clarity and detail that it could be given to an independent tester and have the
tests properly carried out.

Test Case Description
A test case contains all the information necessary to verify some particular functionality of
the software:
Purpose:
 Describe the features of the software to be tested, and the particular behaviour being
verified by this test. Requirement Traceability: A cross reference to the numbers of
the requirements (in the system specification) which are being verified in this test.
 Verifying conformance to applicable standards and guidelines and customers’
requirements.
 Validating expectations and customer needs
 Increasing control flow coverage
 Increasing logic flow coverage
 Increasing data flow coverage
 Simulating ‘real’ end user scenarios
 Exposing errors or defects
3.3.3 Testing Methods:
There are primarily two methods / techniques of software testing:
1. Black Box Testing is a software testing method in which the internal
structure/design/implementation of the item being tested is not known to the tester. These
tests can be functional or non-functional, though usually functional.
Test design techniques include:
 Equivalence partitioning
 Boundary Value Analysis
 Pair wise testing
2.White Box Testing is a software testing method in which the internal
structure/design/implementation of the item being tested is known to the tester.
Test design techniques include:
 Control flow testing
 Data flow testing
 Branch testing
The technique of testing without having any knowledge of the interior working of the
application is Black Box testing. The tester is oblivious to the system architecture and does

not have access to the source code. Typically, when performing a black box test, a tester will
interact with the system’s user interface by providing inputs and examining outputs without
knowing how and where the inputs are worked upon.
There is two test cases of login and registration is as following:
1] Test case For Log In:
Objective: - To check whether user name & Password valid or invalid.
Page: -login Screen
Test Data
Table: 16 Testcase for Login Page
Sr no. Steps Expected Data Status
1 Enter user name,
password and
press submit
button
Should navigate to
user homepage.
Pass
2 Enter User name
and press submit
button..
Should Display
message ‘please
enter the password’
Invalid
3 Enter password
and presssubmit
button
Should Display
message ‘please
entertheusername’
Invalid
4 Enter blank user
name and blank
password and
presssubmit
button.
Should display a
message ‘please
enter username’ and
‘please enter
password’
Invalid
5 Enter wrong
user
andPassword
Should display a
Message ‘Invalid
Username or
Password’
Invalid

2] Test case For Registration Form:
Objective: - To check whether enter detail right or wrong.
Page: -Home.
Test Data
Sr no. Steps Expected Data Status
1 Enter name,
username, E-mail,
Password and press
submit button.
Should navigate to
user homepage.
Pass
2 Enter User name and
press submit button.
Should Display
message ‘Please
enter all detail’
Invalid
3 Enter Password. in
and press Submit
button.
Should Display
message ‘Please
enter all detail’
Invalid
4 Enter E-mail in
wrong format.
Should display a
Message ‘please
enters the e-mail in
correct format.’
Invalid

Chapter 4:
Advantages
Time management:
In SAA system they do not need to go at auction location to get particular selling and do not
wait for bid. User can upload product online and get all the information about the other
products. Also see the update products. so it is time saving. They also can get approval for
procedure online and direct conversation with admin and user, too.
Less Costly:
In Smart auction Access, user can sell products anytime and anywhere. do not go to location.
So is very less costly.
User friendly:
This application is give user totally user friendly environment. Because in this user can direct
interact with admin and seller. Easily fill up the form and get approval and then by using sell
and buy the products.
Direct interaction with Faculty and admin:
In SAA, user can directly contact with the admin. Also put query of the any of products. They
also can give the feedback of the any products. So direct interaction is done in this
application.
Current update information of products:
In this application current update information will displayed by the admin to user and visitor,
too.
Reliable and Secure:
The system is reliable it gives fast and positive response. The system also gives privacy to
every user for their account and legal document.

4.2 Scope of future work:
Direct chat with user and Admin:
In short future in this application we will provide chat application between seller and buyer
so that user directly contact to higher authority.
Will provide better UI and More User Friendly
In Future we will provide more interactive system by giving better UI.

Project report(Smart Auction Access)

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Similar to Project report(Smart Auction Access)

Similar to Project report(Smart Auction Access) (20)

More from akki_hearts

More from akki_hearts (16)

Recently uploaded

Recently uploaded (20)

Project report(Smart Auction Access)