Online Auction System (Osa)

Online Voting System For Corporate Sectors
1. COLLEGE PROFILE
1.1Brief overview / Highlight
Introduction:
Our motto is “all round quality education”. The student become a valuable service
provider by sharing his/her knowledge in the society and gains a place at the highest
peak in his/her respective area though technical professional skill.
Udhna Academy Education Trust was established in 1964 with the objective of
catering to the education needs of the citizens of udhna area and south Gujarat. The
Trust has completed 52 years of brilliance since inception in 1964. It has spread the
light of education in the region providing education ranging from pre-primary to
Higher Secondary and Higher Secondary and graduation.
Its pioneers started this institution with a very noble aim and far reaching vision. As a
result, today,udhna academy Education Trust governs the following institutions,
where about 6000 students seek high quality education.
SMT. DIWALIBEN HARJIBHAI GODALIYA COLLEGE OF C.A &

I.T.(B.C.A.) –JUNE 2008
S.P.B COLLEGE OF BUSINESS ADMINISTRATION (B.B.A) -JUNE 2005
UDHNA CITIZEN COMMERCE COLLEGE (B.COM) –JUNE 2002
R.N. NAIK H.S. SCHOOL (SCIENCE) –JUNE 201
R.N. NAIK H.S. SCHOOL (COM & ARTS) –JUNE 2001
UDHNA ACADEMY SHISHUVIHAR-2 –JUNE 2002
SMT. MADHUKANT KANTABEN J. MEHTA PRIMARY SCHOOL –JUNE
1998
SURAT NATIONAL PRIMARY SCHOOL –JUNE 1968
R.N. NAIK HIGH SCHOOL –JUNE 1964
SDHG COLLAGE OF COMPUTER APPLICATION AND IT Page 1 of 96

Vision:
“To be an eminent and vibrant institute for education, our credo will always be
excellence through innovations, empathy, ethics and teamwork and to cater to the ever
changing needs of community at large.”
Mission:
“To impart quality education, nurture aspirations and facilitate continuous learning
and contribute to the society by developing outstanding individuals who would take
up leadership challenges in several of economy.”

1.2Organization structure /chart

Salient Features
 Qualified and Experienced faculty members
 Book Bank Facility
 Well-equipped Text and References Library
 Strong Industry- Institute Interaction through seminars, Guest

Lectures,Projects,Visits.
 Faculty Feedback System to strengthen Teaching-Learning Process
 Indoor and outdoor Co-Curricular & Extra –curricular Activities
 Social Welfare Initiatives in Plantation of trees, Blood Donation Camp, NSS Camp
and relief during Natural Calamities
 NSS Sports as Character Building Activities
 Tie-up with Health centre for free medical service to all students and staff
 Well equipped computers laboratories with Broadband Internet Connection
 Canteen Facility for Students and staff
 Scholarship to toppers in academics, extra-curricular activities and sports
 Anti-ragging Cell
 Women’s Cell
 Placement Cell
 Smart Class
 Seminars conducted by doctors

Institute structure / chart
Udhna Academy Education Trust
Member of the Trust
Dr.Mehul P. Desai
(I/C Principal)
B.COM B.B.A B.C.A
Dr.Mehul P. Desai Dr. Daisy Thekanlal Dr. Manish kaysth
Teaching Teaching Teaching

staff staff staff

2. CURRENT / EXISTING SYSTEM STUDY
The existing "Open Voting System" is managed manually. Prior to each auction, the day of
auction, the venue and the posts on auction are announced those news media. Those who
wish to take part in the auction have to arrive at the venue on that day on time.
This conventional method most of the time prevent aspiring Candidates from participating in
the auction process. Another headache of the old system is to track each voting process and
to make it oral settlement. The Process is very conflicting and time consuming.
2.1 Major Component / Flow

In each and every system there is a particular system component through the system is
running till now. All system is common component like maintain user details and give
information of company.
The existing or in other words the current system is completely manual on this way. The
admin is done by the all system usage. As system has different kind of registers to maintained
different kinds of process. All the process is maintained in the user register.

2.2 Minimum Hardware / Software Configuration
Hardware Details:-
Developer:-
Process : intel core i3 processor or above
RAM : 4 GB RAM
HDD : 1 TB Disk
User:-
Process : Intel corei3 processor
RAM : 256MB or more RAM
HDD : 20 GB Hard Disk
Software Details:-
Developer:-
Web server :
 Apache/2.2.17 (Win64) PHP/5.3.5

 MYSQL client version: MYSQLND 5.0.7-dev - 091210 - $Revision: 304625 $

 PHP extension: MYSQL
 Tools : Version information: 3.3.9
User side:-
Web browser :
Google chrome 72.0.3626.119
Operating system :Windows XP, Windows 2003, Windows 7, Windows 8.1,

Windows 10 and other windows platforms and Ubantu or any
compatible OS Browser
2.3 Drawbacks / Limitations
Now a day each and every system has certain drawbacks that are improper working.
Following are some drawbacks of manual system that are observed and forced us to design
new system.
Limited business Area

Our traditional way business is limited area because geographical limitation always their
company cannot take requirement for other country client.

High Amount of Paper Work:

Each and every user Information are recorded on the paper so there would be high amount of
stationary is required to maintain all the register each and every year and though the all
transaction after few year it would be difficult to get record of the particular customer’s and
on opposite side it would require much register to maintain all these and would create many
problems.
In our current system, all the process is carried out by human and there are many physical
forms for registration of the customers so naturally. It requires more time and in that sense, it
will require more time to complete works.
Security is not maintained

In our current system all the work that is done is carried out on the register and so there are
not any security criteria to guard our data and any person can open data and any person can
open register and make change and make affect our reports. In this it is quite open to
everybody.
Time Consuming
In our current system, all the process are carried out by human and there are many physical
forms for registration of the customers so naturally it requires more time and in that sense, it
will require more time to complete

3. PROPOSE PROJECT PROFILE
3.1Introduction
A world that loves to participate in real-time activities would certainly appreciate the idea of
an Online Voting System For Corporate Sectors that opens 24/7. Unlike the traditional voting
system, this modern system brings together voters and vote from across the different sectors
of the corporates to a single location. Since the description of the voters are listed for few
days, voters can think and study before vote. Since, there is no geographical or time
restrictions, the number of votes received will be more. The cost for conducting a voting
online is less when compared to physical voting and the time consuming is also low. This
way both parties the owner and the voter are benefited.
The global reach of online voting system allows both to the owner/admin and voters to
overcome physical constraints and make the vote for the respective posts from anywhere over
the internet. The use of Online Voting System for Corporate Sectors makes use of the
decision making assistance tool that results in voter’s certainty towards their choice of the
vote. The decision making assistance tool consists of three parts that is the voter information
, his/her valuable votes and his voting activities / process.
The voter information signals seek to fully describe the vote through the use of textual and
visuals, this strives to ensure the voter’s vote certainty. The admin give detailed vote ratings
of all aspects of the voters and giving facilities through the view category facility.
Voter’s description, consists the information regarding the voter’s current position, his/her
contact, his/her capabilities that why he/she is a deserving candidate.

3.2Objective / Goal / Aim
Objective
The purpose of this project is to build an “on-line voting system”, a place for voter and admin
to come together and take decision based on the capabilities of the contenders or the
respective candidate. In fact, the system consists in a web-portal where registered users can
propose new vote, place votes in order to select the post on portal, Registration of users is
preceded by a “pre-registration”: to check whether users insert their real e-mail address.
Voting procedure have a name, a description, an end period: users cannot place vote when
the voting interval (start - end period) ends.
Moreover, administrators have the possibility to accept or refuse voters proposed by users, to
view information about users and after judging on the capabilities of the user the
administrator can decide whether the user is a deserving candidate for the voting or not. The
system is realized with a 3-tier architecture: a relational database that store the information
regarding users, votes and winning table; an application server that cares about the business
logic of the system and the presentation layer that consists in the web browser where users
can interact with the system.
With such architecture, the database is never directly accessed: for example administrators
can change the data stored in the database without connecting directly to it but using their
own browser.
3.3Scope
Admin
Admin can login in website. He/she can also manage all the things in the system like users,
viewing vote, winners, and so on.
The user can be divided into 2 categories i.e. Seller and Buyer.
Candidate

User will first register as a candidate and then can login.

Candidate can post his/her details for the post. And also can manage vote as per choice that
appears on the website. He/she can approve the vote and also cancel the vote.
Voter
User will first register as a voter and then can login.
Voter can view all the details for the posts with proper filtering like category wise, city wise,
etc. than he/she can vote on the product which he/she want than will check for approve the
vote. If vote will be approve than voter will receive the approval letter.
3.4 Type of Project
This system is fully Web based application, for the online voting to the respective and
deserving candidate .
An online project that holds online voting of various posts on a website that serves the
efficient, effective and convenient way of voting precisely .
The system is designed to allow the voters to vote up their vote for deserving candidate and
register it from ‘n’ numbers of voters.
3.5 Technology / Environments E.G. Tools
Front end and back end are generalized terms that refer to the initial and the end stages to
handle a system. The front end is responsible for collecting input in various forms from the
user and processing it to conform to a specification the back end can use. The front end is an
interface between the user and the back end.The main reason of forming a combination this to
ends is, to provide different functionality of both getting and providing data or information to
the users with help of medium
Hardware

RAM 4 GB RAM
Processor CORE i3 5th Generation
HDD 1 TB GB
Software
Front End PHP,HTML,MYSQL,CI
Back End MYSQL
Operating system Windows XP, Windows 2003, Windows 7,
Windows 8.1, Windows 10 and Ubuntu or
any compatible OS Browser
Browser All web browsers supported.
3.6 Applicability of the System
This website is Application for all organization and voters who interests in online voting for
the respective posts.
The system is designed to allow users to set make their votes for voting and voters to register
and vote for various respective posts that are available for voting.

4. SOFTWARE ANALYSIS
4.1Preliminary Investigation
Preliminary investigation is the actual study of the system. It involves an accurate study of
what all aspects your software would cover. In our case as we were developing commerce
site, it covered answers to question like:
What is the basic functionality of commerce site website?
How automated do you want the application to be?
What kind of functionalities is to be developed to make system easy to use on both owner and
admin side?
How can we build attractive site so that more and more users can use this web site?

4.2Problem Identification
The problem with public voting is that participation of the general public is very limited. The
aim of the project is to socialize the voting so that people from far and wide and even across
the continent can participate in it.
The voting site is developed with a vision to wipe out the inherent problems of "Conventional
voting House".
The silent features of the site are as follows:
1. Paperless voting System

2. Accessible to everyone, at any time, no matter where they are in any department of
industry.
3. Reliable user validation and checking.
4. Easy online settlement
4.3Feasibility Study / Risk Analysis

This activity is designed to help to do initial operational, technical, schedule and economic
feasibility evaluation of the project and practice the three approaches to cost benefit analysis
knowledge of cost benefit analysis is critical for a successful system analysis and also for
anyone who must decide whether or not to approve a project.
It is the measure of how beneficial or practical the development of information system will be
to an organization.
4.3.1 Technical Feasibility

This project dose require that much of higher & advanced technology. It requires database
interaction and it requires to be accessed via web or internet. This can be easily done. It must
be developed within the four validation, verification. Thus it seems that the project is
technically feasible to be.
4.3.2 Economic Feasibility

Economical feasibility has great importance as it can outweigh other feasibilities because
costs affect organization decisions. The concept of Economic Feasibility deals with the fact
that a system that can be developed and will be used on installation must be profitable for the
Organization. The cost to conduct a full system investigation, the cost of hardware and
software, the benefits in the form of reduced expenditure are all discussed during the
economic feasibility.
Economical feasibility test we maintained the balance between the Operational and
Economical feasibilities, as the two were the conflicting. For example the solution that
provides the best operational impact for the end-users may also be the most expensive and,
therefore, the least economically feasible.
4.3.3 Operational Feasibility
Operation feasibility is a measure of how people feel about the system. Operational
Feasibility criteria measure the urgency of the problem or the acceptability of a solution.
Operational Feasibility is dependent upon determining human resources for the project. It
refers to projecting whether the system will operate and be used once it is installed.
Behaviourally also the proposed system is feasible. A particular application may be

technically and but may fail to produce the forecasted benefits, because the company is not
able to get it to work. For the system, it is not necessary that the user must be a computer

expert, but any computer operator given a little bit of knowledge and training can easily
operate.
Our Project is operationally feasible since there is no need for special training of staff
member and whatever little instructing on this system is required can be done so quite easily
and quickly as it is essentially This project is being developed keeping in mind the
general people who one have very little knowledge of computer operation, but can
easily access their required database and other related information. The redundancies can
be decreased to a large extent as the system will be fully automated.
4.3.4 Management Feasibility
The general manager will be the one to plan and will be in charge of the overall supervision
of the farm. He will be the one to screen the candidates to be recruited and hired.
The technical operations manager will oversee the efficiency and effectiveness of the
farmhands. He will also be responsible for the general care of the pigs, maintaining the herd
health and environment of the pigs.
4.3.5 Time Feasibility
Time feasibility describes the time cost for converting the existing system to new system.
As an aspect of time feasibility our system takes 4 month for completion. This system is
develop under the time period of just four month so we can say that this system is time
feasible.
4.4Requirement Analysis

During the requirement analysis gather the all the software. As per the requirement planning
about software how it work? What flow of it? After that mane ONLINE VOTING SYSTEM
FOR CORPORATE SECTORS that contain the all requirement of software.
It is the most important part of software development because software developed based on
that phase.
4.4.1 Fact Finding Techniques
To study any system the analyst needs to do collect facts and all relevant information. the
facts when expressed in quantitative form are termed as data. The success of any project is
depended upon the accuracy of available data. Accurate information can be collected with
help of certain methods/ techniques.
These specific methods for finding information of the system are termed as fact finding
techniques. Interview, Questionnaire, Record View and Observations are the different fact
finding techniques used by the analyst. The analyst may use more than one technique for
investigation.
Interview
This method is used to collect the information from groups or individuals. Analyst selects the
people who are related with the system for the interview. In this method the analyst sits face
to face with the people and records their responses. The interviewer must plan in advance the
type of questions he/ she is going to ask and should be ready to answer any type of question.
He should also choose a suitable place and time which will be comfortable for the
respondent.
The information collected is quite accurate and reliable as the interviewer can clear and cross
check the doubts there itself. This method also helps gap the areas of misunderstandings and
help to discuss about the future problems. Structured and unstructured are the two sub

categories of Interview. Structured interview is more formal interview where fixed questions
are asked and specific information is collected whereas unstructured interview is more or less
like a casual conversation where in-depth areas topics are covered and other information
apart from the topic may also be obtained.
Questionnaire
It is the technique used to extract information from number of people. This method can be
adopted and used only by a skilful analyst. The Questionnaire consists of series of questions
framed together in logical manner.
The questions are simple, clear and to the point. This method is very useful for attaining
information from people who are concerned with the usage of the system and who are living
in different countries. The questionnaire can be mailed or send to people by post. This is the
cheapest source of fact finding.
Observation
Unlike the other fact finding techniques, in this method the analyst himself visits the
organization and observes and understand the flow of documents, working of the existing
system, the users of the system etc.
For this method to be adopted it takes an analyst to perform this job as he knows which points
should be noticed and highlighted. In analyst may observe the unwanted things as well and
simply cause delay in the development of the new system.
Record View
The information related to the system is published in the sources like newspapers, magazines,

journals, documents etc. This record review helps the analyst to get valuable information
about the system and the organization.
4.4.2 Time Line Chart
The time line chart describes the time scheduling for project completion.
This time line chart show project tasks in weekly schedule.
Task Month1 Month2 Month3
1) Requirement analysis
Collected requirement from our guide
Analyze gathered information
Determine scope of the system
Milestone: requirement Analysis complete
2) Planning and risk analysis

Analyze data for possible risks

Identify technical risks
Determine different modules
Milestone: Planning completed
3) Designing
Design basic interface of the site
Design database tables
Design web form for modules
Milestone: designing completed
4) Coding and integrating modules
Implement logic for different modules
Implement database connectivity
Integrate different modules
Implement Report
Milestone: coding completed
5) Testing
Validate input control and check accuracy of
Milestone:
Reports testing completed
6) Documentation
Milestone: documentation completed
4.4.3 Model with Justification
Spiral Model
The spiral software methodology is one of the other methodologies that we analysed but we
found out that using such a methodology would probably not result in the system being
delivered within the set deadlines. The spiral model implements risk driven approach rather
than code driven approach it makes use of both the top down and the bottom-up approaches
(Nilson, 2008). The spiral model combines the idea of iterative development with the
systematic, controlled aspects of the waterfall model. Spiral model is a combination of
iterative development process model and the linear development model that is the waterfall

model which provides high priority on risk analysis. It allows for incremental releases of the
product, or incremental refinement through each iteration around the spiral (Barry, 1988).
The Spiral model basically tries to combine the features of the waterfall and the prototyping
model.
Following is a diagrammatic representation of spiral model listing the activities in each

phase:
The spiral model consists of four phases. A software project repeatedly passes through these
phases in iterations called Spirals.
Identification
This phase starts with gathering the business requirements in the baseline spiral. In the
subsequent spirals as the product matures, identification of system requirements, subsystem
requirements and unit requirements are all done in this phase. This also includes
understanding the system requirements by continuous communication between the customer

and the system analyst. At the end of the spiral the product is deployed in the identified
market.
Design
Design phase starts with the conceptual design in the baseline spiral and involves
architectural design, logical design of modules, physical product design and final design in
the subsequent spirals.
Construct or Build
Construct phase refers to production of the actual software product at every spiral. In the
baseline spiral when the product is just thought of and the design is being developed a POC
(Proof of Concept) is developed in this phase to get customer feedback.
Then in the subsequent spirals with higher clarity on requirements and design details a
working model of the software called build is produced with a version number. These builds
are sent to customer for feedback.
Evaluation and Risk Analysis:
Risk Analysis includes identifying, estimating, and monitoring technical feasibility and
management risks, such as schedule slippage and cost overrun. After testing the build, at the
end of first iteration, the customer evaluates the software and provides feedback.
Based on the customer evaluation, software development process enters into the next iteration
and subsequently follows the linear approach to implement the feedback suggested by the

customer. The process of iterations along the spiral continues throughout the life of the
software.
Spiral Model Application
Spiral Model is very popular software used in the software industry as it is in synch with the
natural development process of any product that is learning with maturity and also involves
minimum risk for the customer as well as the development firms. Following are the typical
uses of Spiral model:
 When costs there are a budget constraint and risk evaluation is important.
 For medium to high-risk projects.
 Long-term project commitment because of potential changes to economic priorities as
the requirements change with time.
 Customer is not sure of their requirements which are usually the case.
 Requirements are complex and need evaluation to get clarity.
 New product line which should be released in phases to get enough customer
feedback.
 Significant changes are expected in the product during the development cycle.
Advantages and disadvantages of Spiral Model
The advantage of spiral lifecycle model is that it allows for elements of the product to be
added in when they become available or known. This assures that there is no conflict with
previous requirements and design.
This method is consistent with approaches that have multiple software builds and releases
and allows for making an orderly transition to a maintenance activity. Another positive aspect
is that the spiral model forces early user involvement in the system development effort.

On the other side, it takes very strict management to complete such products and there is a
risk of running the spiral in indefinite loop. So the discipline of change and the extent of
taking change requests is very important to develop and deploy the product successfully.
4.4.4 UML
UML (Unified Modelling Language)

The UML is an international industry standard graphical notation for describing software
analysis and designs (Williams, 2004). UML is a unification and standardization of earlier
modeling notations of Book, Rum Baugh, Jacobson, Mellor and Wirf-Brock, among others.
UML is an object oriented approach which allows for an easy way to translate it to object
oriented code. The Unified Modeling Language (UML) is a language for specifying,
visualizing, constructing, and documenting the artifacts of software systems, as well as for
business modeling and other non-software systems (Mitchell, 2003). UML uses simple
graphical notations that non-programmers can also understand its model. UML makes use of
sequence diagrams, use case diagrams and state chart diagrams.UML diagrams are used to
show system requirements and the general system design. UML is very important in the use
of RAD as it facilitates the development of the project.
Symbols Used In UML Diagram
Initial activity (starting point / 1 activity of flow)
Activity description

Decision
Output Signal
Final Activity
Use case Diagram

Diagram display the relationship among actor and use cases. The two main components of a
use case diagram are use cases and actors.
Actor
Use case
A use case is an external view of the system that represents some action the user might
perform in order to complete a task.


Manage state
Manage city
Manage
position
Manage
registration
Login
View table
Admin
View
Winning table
Figure 1. Use Case Diagram for Admin

Login
Singup
Update Details
Add Product
Seller Bid Product
Feedback
View Bid
Status
Contact /
Inquiry
Approval
Letter
Figure 2. Use Case Diagram for Seller

Registration
Login
View Product
Bid Product
Update Details
Bidder
Feedback
View Bid
Status
Contact /
Inquiry
Approval
Letter
Figure 3. Use Case Diagram for Bidder

Signup
View Product
User Contact /
Inquiry
Figure 4. Use Case Diagram for End User
View Product
Bid Product
View Bid
Status
Login Update Details
Bidder Download
Approval
Letter
Contact /
Inquiry
Logout
Figure 5. Use Case Diagram for After Login Bidder

View Product
Bid Product
View Bid
Status
Login Update Details
Bidder
Feedback
Approval
Letter
Contact /
Inquiry
Logout
Figure 6. Use Case Diagram Bidder
Add
View
Login Subcategory Delete
Admin
Update
Status
Figure 7. Use Case Diagram for Subcategory

Add
View
Login Category Delete
Admin
Update
Status
Figure 8. Use Case Diagram for Category
Add
View
Login City Delete
Admin
Update
Status
Figure 9. Use Case Diagram for City

Add
View
Login Area Delete
Admin
Update
Status
Figure 10. Use Case Diagram for Area
View
Login Product
Status
Admin
Figure 11. Use Case Diagram for Product

View
Login User
Status
Admin
Figure 12. Use Case Diagram for Login User
Login Feedback View
Admin
Figure 13. Use Case Diagram for Feedback

Login Manage Bidding View
Admin
Figure 14. Use Case Diagram for Manage Bidding

Admin
Login
Wrong Email &
Password Failed
Enter Email &

Password
«Success move
Profile »
Dashbord
Manage
Manage Manage Manage Manage
Manage Manage Product
Category Winner Approval Wishlit
Subcategory Manage Area
City Manage Manage
Manage
Contact Subcategory
Feedback Manage
User
Whether Admin wants

to Manage or Logout
Logout
Figure 15. Activity Diagram for Admin

Buyer
Registration
Wrong Email & Login

Password Failed
Enter Email &

Password
«Success move
Profile »
Dashbord
View Product
Recomandation
Search Product Detail View Scheme
Compares Product
View Product
Whether Bidder Want to

Continue Editing Profile
or Logout
Logout
Figure 16. Activity Diagram for Bidder

Seller
Registration
Wrong Email & Login

Password Failed
Enter Email &

Password
«Success move
Profile »
Dashbord
View / Edit
View / Edit Product Profile Add Product
complain
Whether Seller Want to

Continue Editing Profile
or Logout
Logout
Figure 17. Activity Diagram for Seller

Approval Latter
approve__id: int
area_master city_master
Bid_id: int
Area__id: int City__id: int Approve_letter: Varchar
City_id: int City_name: City_date: datetime
Area_name: Varchar varchar bid_master
Area_date: datetime City_date: Bid__id: int
Area_status: enum datetime Product_id: int
winner_master
Add() Add() User_id: int
Update Update Bid_price: float Winner_id: int
Delete() Delete() User_name: varchar Bid_id: int
View() View() Bid_date: datetime Winner_date: datetime
Winner_status: enum
View()
View()
category_master
feedback_master User
Category_id: int
FB__id: int User__id: int Category_name: varchar
User_id: int City_id: int
FB_Des: Varchar Add()
User_name: varchar
Area_date: datetime Update()
User_img: varchar
Area_status: enum product_master Delete()
User_type: enum
View()
Add() user_date: datetime Product_id:int
Update user_status: enum Sub__id: int
Delete() Category_id: int
View() Add() User_id:int
Update() Product_name: int
View() Product_img: varchar
Product_des: varchar
Min_bid_price:float
Product_date:datetime
contact_master Product_status:enum subcategory_master
wishlist
Bid__id: int Add() Sub__id: int
Wish__id: int
Product_id: int Update() Category_id: int
User_id: int
User_id: int Delete() Sub_name: varchar
Product_id: int
Bid_price: float View()
Wish_date: datetime Add()
User_name: varchar Bid()
Wish_Status: enum Update()
Bid_date: datetime
Delete()
Add()
View()
View() Delete()
View()
Figure 18. Class Diagram

Figure 19. Relationship Diagram

Sequence Diagram
A sequence diagram in unified modeling language (UML) is a kind of interaction diagram

that show how processes operate with one another and in what order. It is a construct of
massage sequence chart. A sequence diagram shows objects interactions arranged in time
sequence. It depicts the object and classes involved in the scenario and the sequence of
massage exchanged between the objects needed to carry out the functionality of scenario.
Sequence diagrams typically are associated with use case realizations in the logical view of
the system under development.
Sequence diagrams are sometime called event diagram, event scenarios, and timing diagram.

Admin System Database
Login Authentication
successfully Login And Login Fails Acknowledgement
Manage User User details
View User Details Update User Details
Manage product Request Manage product

View Product Information Successfully Response for manage product
Manage Category Request for manage category
View Category Information Response for manage category
Send Update To Seller & Bidder Request for send update
Send Update Successfully Response for send update
Manage Bidding
Request for manage bidding
View Bidding Information
Response for manage bidding
Request for logout
logout succussfully
Sequence Diagram for Admin

Bidder System Database
registration Registration details
successfully Registration Response for registration
successfully Login And Login Fails Acknowledgement
Search product Product details

View Product Search product Details
View Product Details Request for View Product Details
View Product Details Response for View Product Details
Bid for the Product Request for Bid for Product
Bid For the Product Successfully Response for Bid for Product
modify Bid amount Request for modify Bid amount
modify Bid amount successfully Response for modify Bid amount
Request for logout
logout succussfully
Sequence Diagram for Bidder

Seller System Database
registration Registration details
successfully Registration Response for registration
Successfully Login And Login fails Acknowledgement
Upload product Product details

Upload Product Successfully Response for upload product
Set Time & Price of Product Request for Set Time & Price of Product
Set Time & Price of Product Successfully Response for Set Time & Price of Product
View Bid Information Request for View Bid Information
View Bid Information Successfully Response for View Bid Information
Request for logout
logout succussfully
Sequence diagram for seller

4.4.6 Process / Control Specification
Login Process
Email & Password 1 Login
User
It Receive Email & Password From admin stored in

table user. If invalid then generate exception error.
Adding City Process
City Details Add new City

2
City
It Receive information from Admin and store in table city_master. If

invalid then generate exception error.

Adding Area Process
Area Details Add New Area

3
Area
It Receive information from Admin and store in table

area_master. If invalid then generate exception error.
User Registration Process
User Details Registration

4
User
It Receive information from Admin and store in table User. If

invalid then generate exception error.

Bid Process
Bid Details Add New Bid

5
Bid
It Receive information from Admin and store in table bid_master.

If invalid then generate exception error.
Product Process
Product Details Add New Product

6
Product

Product_master. If invalid then generate exception error.

Category Process
Category Details Add New Category

7
Category

Category_master. If invalid then generate exception error.
Subcategory Process
Subcategory Details Add New Subcategory

8
Subcategory

Subcategory_master. If invalid then generate exception error.

Feedback Process
Feedback Details Add New Feedback

9
Feedback

Feedback_master. If invalid then generate exception error.
Winner Process
Winner Details Add New Winner

10
Winner

Winner_master. If invalid then generate exception error.

4.4.7 Data Dictionary
A data dictionary is a catalogue, a repository of the element system as the name suggest, the
elements centre on data and they are structured to meet user requirement and organization
needs. Thus, data dictionary gives the details and description of data flows, process and stores
used in data flow diagram.
 Importance of Data Dictionary :-

 To manage the details in large system.
 To communicate a common meaning for all elements.
 To document the features of the system.
 To facilitate analysis of the details in order to evaluate characteristics
and determine where system change should be made.
 To locate errors and omissions in the system.

1) Data Dictionary for category_master
Category
Name
Alias None
When to used and 1. To store information for category
how to used type
2. To store category detail.
Supplementary information Data element:-
Table of Category detail
Content Description
Category_idit is used to unique id for all category.
Category_nameit is the name of particular category.
2) Data Dictionary for Area_master
Name Area
Alias None
When to used and 1. To store information for Area
how to used 2. To store Area detail.
Table of Area detail
Content Description
Area_idit is used to unique id for all Area.
Area_nameit is the name of particular Area.
City_idit is used to unique id for all City.

3) Data Dictionary for city_master
Name City
Alias None
When to used and 1. To store information for city
how to used 2. To store city detail.

Table of city detail
Content Description
City_idit is used to unique id for all city.
City_nameit is the name of particular city.
4) Data Dictionary for User
Name User
Alias None
When to used and 3. To store information for User
how to used 4. To store user detail.
Table of User detail
Content Description
City_idit is used to unique id for all city.
User_idit is used to unique id for all User.
User_nameit is the name of particular User.
User_imgBy using it admin can assign image to particular User.

5) Data Dictionary for Subcategory_master
Name Subcategory
Alias None
When to used and 5. To store information for
how to used Subcategory
6. To store Subcategory detail.
Table of Subcategory detail
Content Description
Sub_idit is used to unique id for all Subcategory.
Category_idit is used to unique id for all Category.
Sub_nameit is the name of particular Subcategory.
6) Data Dictionary for Bid_master
Name Bid
Alias None
When to used and 7. To store information for Bid
how to used 8. To store Bid detail.
Table of Bid detail
Content Description
Bid_idit is used to unique id for all Bid.
Product_idit is used to unique id for all Product.
User_idit is used to unique id for all user.

7) Data Dictionary for Product_master

Name Product
Alias None
When to used and 9. To store information for Product
how to used 10. To store Product detail.
Table of Product detail
Content Description
Product_idit is used to unique id for all Product.
Category_idit is used to unique id for all Category.
Subcategory_idit is used to unique id for all Subcategory.
Product_nameit is the name of particular Product.
Product_imgBy using it admin can assign image to particular Product.
8) Data Dictionary for Feedback_master

Name Feedback
Alias None
When to used and 11. To store information for Feedback
how to used 12. To store feedback detail.
Table of feedback detail
Content Description
FB_idit is used to unique id for all Feedback.

9) Data Dictionary for Approval_letter

Name Approval
Alias None
When to used and 13. To store information for approval
how to used 14. To store approval detail.

Table of approval detail
Content Description
Approval_idit is used to unique id for all Approval.
10) Data Dictionary for Winner_Master

Name Winner
Alias None
When to used and 15. To store information for Winner

how to used 16. To store Winner detail.

Table of Winner detail
Content Description
Winner_idit is used to unique id for all Winner.


5. SOFTWARE DESIGN
The overall objective in the development of database has been to treat data as an
organizational resource and as an integrated whole. DBMS allow data to be protected and
organized separately from other resources. Database is an integrated collection of data. The
most significant from of data as seen by the programmers is data as stored on the direct
access storage device. This is the difference between logical and physical data.
Database files are the key source of information into the system. It is the process of designing
database files, which are the key source of information to the system. The files should be
properly designed and planned for collection, accumulation, editing and retrieving the
required information.
The organization of data in database aims to achieve three major objectives:-
 Data integration.
 Data integrity.
 Data independence.

5.1 Project Design Process Hierarchy
online
Auction
System
Registration Login Feedback
A B C

Login Send Query Fill The From
View Website Provide Access

Details To User

Accept Store
Feedback Feedback

5.2 Database Design
Table Name: Approval Letter
Sr Filed Name Data Data Constraint Description

No Type Size
1 Approval_id int 11 Primary key It is contains approve identity.
2 Bid_id int 11 Foreign key It is contains bid identity.
3 Approval_Letter varchar 200 It is contains for approval
letter.
4 Approval_Date datetime It is contains for approval date.
5 Approval_Status enum It is contains for approval
status.
Table Name: area_master

No Type Size
1 Area_id int 11 Primary key It is contains area identity.
2 Area_Name varchar 25 It is contains for the area
name.
3 City_id int 11 Foreign key It is contains for approval
letter.
4 Area_Entry_Date datetime It is contains for area date.
5 Area_Status enum It is contains for area status.

Table Name: bid_master
Sr No Filed Name Data Type Data Size Constraint Description
1 Bid_id int 11 Primary key It is contains Bid identity.
2 User_id int 11 Foreign key It is contains user identity.
3 Product_id int 11 Foreign key It is contains product identity.
4 Bid_Date datetime It is contains for bid date.
5 Bid_Price int 11 It is contains for bid price.
6 Bid_Status enum It is contains for bid status.
Table Name: category_master

No Type Size
1 Category_id int 11 Primary key It is contains category identity.

2 Category_Name varchar 25 It is contains for the category
name.
3 Category_Entry_Date datetime It is contains for category date.
4 Category_status enum It is contains for categorystatus.

Table Name: city_master
Sr No Filed Name Data Data Constraint Description

Type Size
1 City_id int 11 Primary It is contains city identity.
key
2 City_Name varchar 11 It is contains for the city
name.
3 City_Entry_Date datetime It is contains for city date.
4 City_Status enum It is contains for city status.
Table Name: feedback_master

No Type Size
1 FB_id int 11 Primary key It is contains feedback identity.
2 User_id int 25 Foreign key It is contains user identity.
3 FB_Descriptio varchar 11 It is contains for feedback description.

n
4 FB_Date datetime It is contains for feedback date.
5 FB_Status enum It is contains for feedback status.

Table Name: subcategory_master
Sr Filed Name Data Type Data Constraint Description

No Size
1 Sub_id int 11 Primary It is contains subcategory identity.

key
2 Sub_Name varchar 25 It is contains for the sub name.
3 Category_id int 11 Foreign key It is contains category identity.
4 Sub_Entry_Dat datetime It is contains for subcategory date.

e
5 Sub_Status enum It is contains for subcategory status.

Table Name: product_master

No Type Size
1 Product_id int 11 Primary It is contains product identity.
key
2 Product_Name varchar 25 It is contains for the Product name.
3 Category_id int 11 Foreign It is contains category identity.

key
4 Subcategory_id int 11 Foreign It is contains subcategory identity.
key
5 Product_Brand_ varchar 25 It is contains for brand name.
name
6 User_id int 11 Foreign It is contains user identity.
key
7 Product_Image varchar It is contains for image.
8 Product_Descrip varchar It is contains for product
tion description.
9 Min_Bid_Price float It is contains for bid price.
10 Max_Time_Limi time It is contains for time limit.
t
11 Product_Entry_ datetime It is contains for date.
Date
12 Product_Status enum It is contains for status.

Table Name: winner_master
Sr Filed Name Data Type Data Constraint Description

No Size
1 Winner_id int 11 Primary It is contains approve
key identity.
2 Bid_id int 11 Foreign It is contains bid identity.
key
3 Winner_Entry_Date datetime It is contains for date.
4 Winner_Status enum It is contains for status.
Table Name: user
Sr No Filed Name Data Type Data Constraint Description

Size
1 User_id int 11 Primary key It is contains approve identity.
2 User_Name varchar 25 It is contains for user name.
3 User_email varchar 30 It is contains for email.
4 User_Password varchar 20 It is contains for password.
5 Gender varchar 10 It is contains for gender.
6 User_Image varchar 100 It is contains for image.
7 User_Contact_No bigint 15 It is contains for contact number.
8 User_DOB date It is contains for dob.
9 User_Address varchar 200 It is contains for address.
10 City_id int 11 Foreign key It is contains City identity.
11 User_Type enum It is contains for user typ.
12 User_Entry_Date datetime It is contains for date.
13 User_Status enum It is contains for status.

5.2.1 Justification of Normalization
Normalization is a technique of separating redundant fields and braking up a large table in to

smaller one. It is used to avoid insertion, deletion and updating anomalies. All the tables have
been normalized up to the third normal form.
Normalization is the decomposition of complex data structure into ‘flat’ files called
‘relations’. In short the rules for each of the three normal forms are as below:
First Normal Form:
The rules for the first normal form are as follows:

 Columns with similar content must be eliminated.
 A table must be created for each group of associated data.
 Each data record must be identifiable by means of a primary key.
Second Normal Form:
Here are the rules for the second normal form:
 Whenever the contents of columns repeat themselves, this means that the table
must be divided into several sub tables.
 These tables must be linked by foreign keys.
Third Normal Form:
The third normal form has a single rule, and here it is:

 Columns that are not directly related to the primary key must be eliminated
(that is, transplanted into a table of their own).
5.3Architectural Design
When you are making a Design of System, It is more necessary to develop the
architectural design of system which is useful for now Basic flow and the detailed.
The Architectural Design defines the relationships between The Design Pattern and the
constraint of the system. It derived from system specification, the analysis model like
DFD and interaction of subsystem defined in the model. When we are developing the
architectural Design we generally follows the architectural view with Data Design and
Design Flow.
 Architecture With Data Design :
 In this Design we describe all aspects to relate to external data and entities for the
software to be built. Here we consider the data connected recourses with our system
and connection with the database.
UML
Architectural
Process
design
Specification
Data Object

In Architectural Data Design, we Follows the Two Abstractions:
 High Level Abstraction(Data Abstraction) :
Data Abstraction is the collection of data that describes the data objects.
 Architecture with Data Flow :
In This Architectural Design consider the Data flows of the system. For Knowing the
flow of system we consider some faces of the analysis like Data Flow Diagram and
Process specification which gives the detail transaction and transform flow.
 Mapping With Architectural Design :
Software requirements can be mapped into various representation of data model. The
Architectural Design Consider the various mapping flow for developing a good and
attractive design of the system.
1) Transform Flow:
 In Transform Flow we consider the fundamental system or basic system model

as level-0 of Data Flow Diagram. In our system we get and pass the information related to
system at the basic level so, here we show the basic level transform flow.

2) Transaction Flow:
 Here we consider the detailed information of data flow during the requirement
analysis more detailed flow models would be created for the system such as control
and process specification, flow diagram and data dictionary.
To perform this Detailed Process we have to perform following steps.
o Review the fundamental system model
o Review and Refine Data Flow Diagram of system
o Determine whether DFD has Transform or Transaction flow DFD
o Detail considering of Incoming and Outgoing Flow boundaries
5.5 User Interface Design

Depending on the inputs and outputs of the system i.e. the interaction between the user
and the system we have designed the interface. We have made it simple and attractive
which makes it user friendly.
User interface design describe how the system communicated and how it reliable with the
user. This design is generally developed for the better understanding of the system and for
the satisfaction for the user.
The most important principle of use interface design is “know the user, know the task”.
There are mainly for basic process for user interface design:
1. User, task analysis
2. Interface design of that analysis
3. Interface implementation
4. Interface validation.

In our system, we follow all the above process to satisfy user and to build a good interface
design.
First we consider GUI in the form interaction, we put many graphics and easy interface
on the forms which is useful to build good interface.
For the interface design, we consider the use case diagram at the analysis face. This
diagram gives the form interaction and the flow.
5.6 Security Issues

1. What type of page should be included?
2. How to manage all pages?
3. How to manage reminder process?
4. How to manage login and logout process?
5. How to manage all pages linked with each other?
6. How to manage intercommunication with internet?
7. How to manage the bunch of data of a particular member so that it can have the
security purpose and keep the data private.
8. How to perform all member security level and perform an authentication and give
person account to each member for security purpose.

5.7 Quality / Reliability Measures

To produce high quality software is a goal to develop the software with all kinds of the
satisfaction with user, cost and assurance, and also with the developers.
If requirement is not consider or gathered properly then the lack of the adaption or
conformation to requirement is also lack of quality. So to build quality software first we
define and consider the meaningful and useful requirement.
To develop quality software we must compare our software with some known data. So for
that we measure our software in 3 different divisions.
1. Software operation
2. Software revision
3. Software transition
Software operation
In these we define the quality with correction, reliability, usability, efficiency, and integrity.
In our system there are many different modules and sub modules are exists and to manage
their quality we follows all above factors.
Correction: if any changes occurred in our modules then we easily correct them. So the
qualities of those modules become as usual and not decrease.
Integrity: if all modules are complete successfully then we integrate them and manage the
quality of all those modules.
Software revision
In those we concerned with those aspects related to modification of the program such as
maintainability, testability.
Software transition
It deals with qualitys like portability, interoperability and reusability.

Interoperability: is the effort required to couple the system with other system and the
relation of two modules.
Reusability: is the extent to which parts of software can be reused in othe related application.
Quality in different views

When any software is develop, developers consider two main views for software quality.
Quality with user satisfaction

If user satisfied with all requirements of the product and accept the system with no any
excuses then we can save that our software has good quality and ratability. To work on the
user satisfaction we consider the following aspect.
Quality with product cost

Costs of quality are conducted to provide a baseline for the current cost of the product and
identify opportunities for reducing the cost of the product.
To decease the cost of the product mainly constraint on the different modelling of the system.
In which we reduce unnecessary and division.
For example
In our system we used many modules (Admin information, user information), if when these
two modules are different then we maintain these individually, correct them individually, all
cost related to the quality and function for all modules are increased.
So we combine above two modules into a one single modules. Therefore all cost of the
modules is decreases and the quality of the cost is increases.

5.8 System Map
Admin
Manage City
Manage
Area Add
View
Delete
Manage Status
Category
Magage
Subcategory
Magage User
View
Status
Magage
Admin Login
Product
Magage
Contact
Magage
Winner
Magage Bid View
Magage
Feedback
Magage
Wishlist

User
Add Product
Bid Product
View
View Bid
Status
Seller /
Login View Winner
Bidder
Add Wishlist
Add
Delete
Add Contact
Add Add
Feedback View

6: SOFTWARE CODING
6.1: Tools & Techniques
 Software:-
 Front End : PHP 5, Apache, JavaScript, AJAX
 Back End : My-SQL Server 2010
 Operating System : Windows XP, Windows 7, Windows 8, Windows 10
 Web browser : Mozilla Firefox (36.0), Google chrome (40.0
 Other:-
 `Ajax Toolkit, JavaScript, Css, Jquery tab-control
 Tools Used :-
 Language Used: Php , JavaScript
 Language Editor: NuSphere PhpED
 Developer:-
 Apache Version : Apache /2.4.10
 Php version : 5.5.19

 MySQL version : 5.0.11

 Tools : php Myadmin (4.2.11)
6.2 Result Snapshot
Admin Side
Admin Login Page

Home
City

Manage City
Area

Manage Area
Category

Manage Category
Subcategory

Manage Subcategory
Manage User

Manage Bidding
Manage Product

Manage Feedback

7. SOFTWARE TESTING
7.1 Test Cases & Test Data Design
We use many types of testing to improve the quality of over system and develop an
acceptable system by client. For the client satisfaction we do validation, verification and
many more testing. But implement all these testing first we should know how to develop the
testing. Therefore, to improve the testing we use two important parts for testing.
1. Test Case
2. Test Data
1) Test Case:-
Testing case is one kind of a formal discussion of predefine documentation at the analysis
phase .It is not used as a practical testing. It is only a Theoretical discussion. In this we
discuss following:-
A Staring Stage:-
In which we discuss the requirements of customer and checks that all information which was
define at analysis phase is full fill or not. We discusses all basis requirements related to
Auctions is much with document or not.
Event and Module to Which Software must Response:-

Here we discuss that all events or modules which we developed, are accept the all inputs and
data which user wants to puts data which are useful for that module or not. In our system we
checks that the inputted data for registration, service booking, and test drive booking are
related to all those event or not.
 Expected output for Ending Stage:-

At this stage we do discuss the expected output of the all event and modules, we checks that
all output and results are matched with all requirement of the client or not. In our system we

discuss that search modules, view enquiry module, view Reports Module, View User
Module, etc. Produces the resultant output or not.
Things which are useful For Test Cases:-

 Analysis phase documentation is very useful when we preparing Test Case.
 Output Online Voting System For Corporate Sectors is Object Oriented so we used
Use Case.
 Diagram and activity model for preparing Test Case.
2) Test Data:-
The data is also part of developing the testing. Here we do not discuss any theoretical concept
or topic. Here we performed many differences testing as a practical form.
In test data we generally used some validation and verification on data and check all
These validation practically and match the constraints with documentation.
We use test data in our system for check the all constrain related to our system like:
Service booking data is not great then purchased data or test drive booking data and
Match all the constrain which defined in documentation.
A test case is a unit of testing activity. Test cases have three parts:
Goal- the aspect of the system being tested.
Input and System State- data provided to the system under stated conditions.
Expected Behaviour the output or action the system should take according to these
requirements.

7.2 Output Comparison
We performed different testing to compare the many requirement and constrain related to the
system. We compare many outputs and data with the predefine document and the user
satisfaction.
Generally testing is used to compare all the aspect related to input, output, validation etc. but
most important comparison is the output comparison for user satisfaction and for develop use
full website.
7.3 Testing Strategies
Black-Box Testing:
 Black-box testing, also called behavioural testing, focuses on the functional

requirements of the software. That is, black-box testing enables the software
engineer to derive sets of input condition that will fully exercise all functional
requirements for a program. Black-box testing is not an alternative to white-
box techniques. Rather, it is a complementary approach that is likely to
uncover a different class of errors than white-box methods.
Black-box testing attempts to find errors in the following categories:
 Incorrect or missing functions
 Interface errors
 Errors in data structures or external data base access
 Behaviour or performance errors
 Initialization and termination errors.

White-Box Testing:
 White box testing sometimes called glass-box testing is a test design method
that uses the control structure of the procedural design to derive test cases.
Using white-box testing methods, the software engineer can derive test cases
that...
 Guarantee that all independent paths within a module have been
exercised at least once.
 Exercise all logical decisions on their true and false sides.
 Execute all loops at their boundaries and within their operational

bounds.
 Exercise internal data structures to ensure their validity.
7.4 Unit Testing
Unit testing focuses verification effort on the smallest unit of software design – the software
component or module. Using the component-level design description as a guide, important
control paths are tested to uncover errors within the boundary of the module. The unit test
focuses on the internal processing logic and data structures within the boundaries of a
component. This type of testing can be conducted in parallel for multiple components.

7.5 Integration Testing
Integration testing is a systematic technique for constructing the software architecture while
at the same time conducting tests to uncover errors associated with interfacing. The objective
is to take unit tested components and build a program structure that has been dictated by
design.
 Top-down integration:
It is an incremental approach to construction of the software architecture.

Modules are integrated by moving downward through the control hierarchy,
beginning with the main control module.
 Bottom-up integration:
It begins construction and testing with atomic modules. Because components

are integrated from the bottom up, processing required for components
subordinate to a given level is always available and the need for stubs is
eliminated. System testing is actually a series of different tests whose primary
purpose is to fully exercise the computer-based system.
 Recovery Testing:
It is a system test that forces the software to fail in a variety of ways and
verifies that recovery is properly performed. If recovery is automatic,
initialization, check pointing mechanisms, data recovery, and restart are
evaluated for correctness. If recovery requires human intervention, the mean-
time-to-repair is evaluated to determine whether it is within acceptable limits.

 Security Testing:
Security testing verifies that protection mechanisms built into a system will, in
fact, protect it from improper penetration. During security testing, the tester
plays the role(s) of the individual who desires to penetrate the system. The role
of the system designer is to make penetration cost more than the value of the
information that will be obtained.
 Stress Testing:
Stress testing executes a system in a manner that demands resources in

abnormal quantity, frequency, or volume.
 Performance Testing:
Performance testing is designed to test the run-time performance of

software within the context of an integrated system. It occurs throughout all
steps in the testing process. Even at unit level, the performance of an
individual module may be assessed as tests are conducted. Performance tests
are often coupled with stress testing and usually require both hardware and
software instrumentation.
7.6 System Testing
This website can be run on any machine as well as Web Browser like Mozilla, Netscape
Navigator and Internet Explorer 6.0 onward.

In this testing I take the requirements Document of Company functionality, reliability and
maintainability.
7.7 Alpha Testing
Alpha and Beta Testing are the part of validation Testing. In this Testing we perform the test
according to the both user and developer’s way. This testing is very useful at the ending stage
of the system. And we concentrate on both the way with satisfaction.
Alpha & Beta testing is impossible for the developer without consider the user views and its
satisfaction. So in this testing we perform testing twice for user and developer.
Alpha Testing:
Alpha Testing is used in natural application and in common way which every developer
performed in system. This testing is conduct in present of developer and user not present at
the time of this testing. This technique is generally used to finding the errors.

8. SOFTWARE IMPLEMENTATION
8.1User Training
User training is designed to prepare the user for testing and converting the system. User
involvement and training take place parallel with programming for three reason
 The system group has time available to spend on training while the programs are
being written.
 Initiating a user training program use the system group a cleared image of the user
interest in the new system.
 A trained user participate more effectively in the system testing.
The training programmers should be planned and organized.

Training programmers should
 Identify the user and trainer’s needs.
 Design a comprehensive training program.
 Select the best method of instruction.
 Determine whether the system need the objectives.

8.2User Manual
A well designed user manual can reduce the overall cost of training and support.
User documentation for modem system is almost always electronic and is usually integrated
part of the system. User manual are important organizational assets.
Components of user manuals
 Title & version of software release
 Table of content
 Features of product
 Installation guide and system requirement
 Getting started
 Frequently asked question (FAQ)
 Sample scenario
 Glossary of the terms used in the manual.

9. LIMITATIONS / CONSTRAINTS
If you’re a commercial or residential property owner, you’ll know how protracted and
expensive it can be to sell through an estate agent.
Property auctions can be a quick-fire and adrenaline-fuelled route to buying a property, but
they’re also a useful avenue if you have property to sell, whether it’s residential or
commercial. However, the process does have its advantages and disadvantages for the seller.
Limitation
 Selling at auction can deter some buyers because of the competitive nature of the
bidding process – not everyone enjoys that scenario.
 Potential bidders must register to attend an auction and this may also put potential
purchasers off.
There is no guarantee that your property will reach its reserve price or sell at all. In
this eventuality you may have to relist it which will incur further costs. If you are
relying on the proceeds of an auction to buy another property immediately it may
make the process difficult or impossible.
 The price you receive may not fully satisfy your expectations. If it only just reaches
slightly over the reserve price you may be disappointed. However, by then it will be
too late.
 The costs of selling at auction may exceed those of using an estate agent, and you’ll
have to pay the auctioneer’s fees regardless of whether the property is sold or not.
 On the day of the auction, your solicitor must attend with you. You will need to pay
for their time and associated costs for their attendance.
If you have a commercial or residential property to sell, an auction may be a great way to do
so. However, it’s up to you to decide on whether that’s the best method for you as an
individual or a company.

10.FUTURE ENHANCEMENT / PATH-A-HEAD
Future Enhancement:
Our System is efficient but still we can add another new feature in future as need
arises means our system is flexible that if we needed in future we can increases or add that
requirements to our system and can extend the work to our system.
We also add the chatting facility between admin to user and user to user.
Mobile number verification through OPT.
Path a head:
Back up of Database.
Database Relationship.
Ads By Google Featured.
Forum Modules (For Answer and Question).
In the future we provide admission facility also.
In the future the students can also compare the fees of different colleges.

11.BIBLIOGRAPHY / APPENDIX….AND SO ON…
Website reference:
http://www.olx.in
http://www.quiker.com
http://www.tutorialspoint.com
http://www.w3school.com
http://www.dreembox.com
Prashant dixit is a fastest emerging entrepreneur.


Online Auction System (Osa)

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Online Auction System (Osa)

Загружено:

Авторское право:

Доступные форматы

Online Voting System For Corporate Sectors

1.1Brief overview / Highlight

SMT. DIWALIBEN HARJIBHAI GODALIYA COLLEGE OF C.A &

SDHG COLLAGE OF COMPUTER APPLICATION AND IT Page 1 of 96

SDHG COLLAGE OF COMPUTER APPLICATION AND IT Page 2 of 96

1.2Organization structure /chart

 Qualified and Experienced faculty members

 Book Bank Facility

 Well-equipped Text and References Library

 Strong Industry- Institute Interaction through seminars, Guest

 Faculty Feedback System to strengthen Teaching-Learning Process

 Indoor and outdoor Co-Curricular & Extra –curricular Activities

 NSS Sports as Character Building Activities

 Well equipped computers laboratories with Broadband Internet Connection

 Canteen Facility for Students and staff

 Scholarship to toppers in academics, extra-curricular activities and sports

 Seminars conducted by doctors

SDHG COLLAGE OF COMPUTER APPLICATION AND IT Page 3 of 96

Institute structure / chart

Udhna Academy Education Trust

Member of the Trust

B.COM B.B.A B.C.A

Dr.Mehul P. Desai Dr. Daisy Thekanlal Dr. Manish kaysth

Teaching Teaching Teaching

SDHG COLLAGE OF COMPUTER APPLICATION AND IT Page 4 of 96

2. CURRENT / EXISTING SYSTEM STUDY

2.1 Major Component / Flow

SDHG COLLAGE OF COMPUTER APPLICATION AND IT Page 5 of 96

2.2 Minimum Hardware / Software Configuration

Process : intel core i3 processor or above

Process : Intel corei3 processor

RAM : 256MB or more RAM

HDD : 20 GB Hard Disk

 Apache/2.2.17 (Win64) PHP/5.3.5

SDHG COLLAGE OF COMPUTER APPLICATION AND IT Page 6 of 96

 PHP extension: MYSQL

 Tools : Version information: 3.3.9

Google chrome 72.0.3626.119

Operating system :Windows XP, Windows 2003, Windows 7, Windows 8.1,

2.3 Drawbacks / Limitations

Limited business Area

SDHG COLLAGE OF COMPUTER APPLICATION AND IT Page 7 of 96

High Amount of Paper Work:

Security is not maintained

SDHG COLLAGE OF COMPUTER APPLICATION AND IT Page 8 of 96

3. PROPOSE PROJECT PROFILE

SDHG COLLAGE OF COMPUTER APPLICATION AND IT Page 9 of 96

3.2Objective / Goal / Aim

SDHG COLLAGE OF COMPUTER APPLICATION AND IT Page 10 of 96

User will first register as a candidate and then can login.

3.4 Type of Project

3.5 Technology / Environments E.G. Tools

SDHG COLLAGE OF COMPUTER APPLICATION AND IT Page 11 of 96

3.6 Applicability of the System

SDHG COLLAGE OF COMPUTER APPLICATION AND IT Page 12 of 96

SDHG COLLAGE OF COMPUTER APPLICATION AND IT Page 13 of 96

The silent features of the site are as follows:

1. Paperless voting System

4.3Feasibility Study / Risk Analysis

4.3.1 Technical Feasibility

SDHG COLLAGE OF COMPUTER APPLICATION AND IT Page 14 of 96

4.3.2 Economic Feasibility

4.3.3 Operational Feasibility