001_a project report on online auction

PREFACE

The present miraculous in the fields of technology and the resulting impact on almost all work of life can be attributed to the fast development of computer technology. The growth of technology particularly in the recent has been very fast.

In today's fast changing environment, computer can with proper programming process data towards logical conclusion classify and makes them readily available for the use. Computers are seen replacing human work. Use of computers can be seen in the offices, hospitals, railways and airline reservations, hotels, department stores etc.

Computers have not allowed the enhancement in computation speed but also have brought about considerable reduction in space with cost effectiveness. Computers have become so versatile, that they have become indispensable not only to engineers, scientists, business executive, managers administrators, but also to the common men. This era of information explosion is totally based upon computer technology, which is accepted world wide today practically each and everything is access by computer (Internet).

It used to be that computers made a difference only to lives of those used them. But with microprocessors being embedded in everything, from washing machine to toys and automobiles, they are going to impacting a lot more lives.

With the explosion of information technology and advert new electronic and computers devices users need to be acquainted with a lost of things relating to myriad branches of knowledge and skills and numerous aspect of social, economy political and technology system to achieve the goal of nations growth and development in the 21st century.

ABOUT THE PROJECT

THEORETICAL BACKGROUND

SYSTEM ANALYSIS AND DESIGN

METHODOLOGY ADOPTED,SYSTEM IMPLEMENTATION AND

DETAILS OF HARDWARE AND SOFTWARE

DETAILED LIFECYCLE OF THE PROJECT

1. DATA FLOW DIGRAM

2. INPUT AND OUTPUT DESIGN

3.METHODOLOGY USED FOR TESTING

CONCLUSION

BIBLIOGRAPHY

About The Project:-

Introduction:-

"U SmartBid" is an online SmartBid web site aimed at

taking the SmartBid to the finger tips of aspiring bidders

there by opening up the doors of the "OPEN SmartBid

House' to a wider cross section of Art Lovers and Antique

Collectors. This site also acts as an open forum where

buyers and sellers can come together and exchange their

products. The site makes sure that the sellers get a fair

deal and buyers get a genuine product.

Home Page - The site opens up door to aspiring web users

through the Home page. The Home page is designed in

such way that the layout is as user friendly as possible.

There is a navigational menu at the top of the page which

links to various inner pages. There is a category drop

down on the left side for easy manipulation. The center

area is for displaying latest products in the chorological

order.

Login/User Registration - Those who wish to take part in

bidding or sell products at the site have to register at the

site as seller or buyer. Only authenticated users can take

part in selling or in bidding. The system automatically

rejects un-authenticated users who try to bid or sell at the

site.

Register Products - This module is for presenting items for

bidding. Only those who have registered and

authenticated as sellers can place their articles for

bidding. The Module collects information like Product

Name, Product Details, Starting Bid amount, Incremental

value etc. The system automatically inputs the closing

date.

Bidding Module - The module is for bidding on any

selected item. The bidder has to authenticate before

participating in bidding. The system checks whether the

incremental amount entered by the bidder is equal or

more than the incremental minimum set during the

product registration time. The system places the record in

the bid history against the bidder account.

My SmartBid - This page is an interface for both buyer and

seller. Buyer can see the profile of the bidding history of

items which are still open on which he/she has already

bided. Similarly the seller can see the progress of bidding

on articles he/she has placed for bidding.

Feedback - The purpose of the page is to send messages/comments to the web administrator.

FAQ - This page is meant for first time users of the site.

The page provided answers to questions which are

common and frequently asked.

WebAdmin - This link opens to the administration module

which is open to web administrator only. Here site

administrator can add product categories and can edit

product information like closing date. Also there is an

option for administering the closed bids. This module is for

contacting the bidder and seller by email instructing them

to settle the transaction within a time frame.

PROBLEM DEFINITION

The problem with public SmartBid is that the participation of

the general public is very limited. The aim of the project is to

socialize the SmartBid so that people from far & wide and

even across the continent can participate in it. The "U

SmartBid" site is developed with a vision to wipe out the

inherent problems of "Conventional SmartBid House". The

salient features of the site are as follows:

1. Paperless SmartBid System

2. It's accessible to everyone, at any time no matter where

they are

3. Reliable user validation & checking.

4. Easy online settlement.

"U SmartBid" is designed in such a way that it is as user

friendly as possible. So any aspiring bidder or seller can visit

the site and engage in bidding with least effort.

2.1 EXISTING SYSTEM

The existing "OPEN SmartBid House" is managed manually.

Prior to each SmartBid, the day of SmartBid, the venue and

the items on SmartBid are announced through news media.

Those who wish to take part in the SmartBid have to arrive

at the venue on that day on time. This conventional method

most of the times prevent aspiring bidders from participating

in the bidding process. Another headache of the old system

is to track each bidding process and to make it culminate in

financial settlement. So the system has to keep records of

both buyers and sellers until the end of settlement. The

process is very cumbersome and time consuming.

2.2 PROPOSED SYSTEM

The slogan of the new site is AAA, 'Anyone, Anytime,

Anywhere'. That what it really is? The "U SmartBid" is online

SmartBid house so the seller or bidder doesn't need to go

anywhere, instead they can take part in the SmartBid just

sitting in the comfort of their living room, be it during the

day or night.

The proposed computerized "U SmartBid" site has made SmartBid process simple. The only5 pre-condition is that the user must register and authenticate before he/she can take part in the bidding process. The system uses HTTP forms authentication which creates a session cookie for any signed in user. Through out the span of the session the cookie remains valid until the user logs out.

An SmartBid house needs to have products to SmartBid, so

in the proposed system this is done using product

registration module. The module is open to user who is

registered sellers and they need to authenticate before they

register any product. The system controls the closing date

by adding 14 days to the submitting date there by restricting

the bidding process to go on indefinitely.

Another important module in the proposed project is the

"Bidding module ". Here one can see the details of any

particular product and also the bidding history. The user can

bid on that item by entering any amount greater than or

equal to the incremental bid amount. Here also system

checks to see whether the user has his credential verified

otherwise he/she will be directed to the login/registration

page.

The last but the least module is the "Web Administration"

module. The module is only open to the web administrator

due to security reasons. In this module the administrator can

add product categories; this is to avoid rampant creation of

categories. The 2nd thing is the option to edit any given

product. This will be necessary when some of the details of

the product need to be edited for one reason or other. The

3rd and last the closed bid manager where the administrator

notifies both the seller and buyer the need to complete the

transaction.

There is another module which runs more or less like

background process. The function of the module is to close

bid of those products whose closing date is less than the

current date. The process is automatic and hidden from the

web users.

THEORETICAL BACKGROUND

SYSTEM ANALYSIS AND DESIGN

ANALYSIS:

Requirement analysis is down in order to understand the problem the software system is to solve. The problem could be automating an existing manual process, developing a new automated system, or a combination of the two. For large systems that have many features, and that need to perform many different tasks, understating the requirements of the system is the major task. The emphasis in the requirements analysis is on identifying what is needed from the system, not how the system will achieve its goals. The developer has to develop the system to satisfy the client’s needs.

Once the problem is analyzed and the essentials understood, the requirement must be satisfied in the requirement specification document. For requirement specification in the form of a document, some specification language has to be selected. All the factors that may affect the design and the proper functioning of the system should be specified in the requirement document. Preliminary user manual

That describes the entire major user interfaces frequently forms a part bof the requirements documents.

DESIGN:

The purpose of the design phase is to plan a solution of the problem specified by the requirement document. This phase is the first step in moving fro the problem domain to the solution domain. Stating with what is needed; design takes us towards how to satisfy the needs. The designs affect the quality of software; it has major impact on the later phases, particularly testing and maintenances. The output of this phase is the design document.

This document is similar to a blue print or as plan fort the solution and is used later during

implementation, testing and maintenance. The design activity is often divided into two separate phases –system design And detailed design, which is some time also called top level design, aims to identify the modules should be in the system, the specifications of these modules, and how the they interact with each other to produce the desired results.

At the and of the system design all the major data structures, file formats, output formats and the major modules in the system and their specifications are decided.

Model-View-Controller Pattern

Model-View-Controller (MVC) is a classic design pattern often used by applications that need the ability to maintain multiple views of the same data. The MVC pattern hinges on a clean separation of objects into one of three categories — models for maintaining data, views for displaying all or a portion of the data, and controllers for handling events that affect the model or view(s).

Because of this separation, multiple views and controllers can interface with the same model. Even new types of views and controllers that never existed before can interface with a model without forcing a change in the model design.

How It Works

The MVC abstraction can be graphically represented as follows.

Events typically cause a controller to change a model, or view, or both. Whenever a controller changes a model’s data or properties, all dependent views are automatically updated. Similarly, whenever a controller changes a view, for example, by revealing areas that were previously hidden, the view gets data from the underlying model to refresh itself.

A Concrete Example

We explain the MVC pattern with the help of a simple spinner component which consists of a text field and two arrow buttons that can be used to increment or decrement a numeric value shown in the text field. We currently do not have an element type that can directly represent a spinner component, but it easy is to synthesize a spinner using existing element types.

The spinner’s data is held in a model that is shared with the text field. The text field provides a view of the spinner’s current value. Each button in the spinner is an event source

http://www.enode.com/x/markup/tutorial/spinner.html

that spawns an action event every time it is clicked. The buttons can be hooked up to trampolines that receive action events, and route them to an action listener that eventually handles that event. Recall that a trampoline is a predefined action listener that simply delegates action handling to another listener.

Depending on the source of the event, the ultimate action listener either increments or decrements the value held in the model — The action listener is an example of a controller.

The trampolines that initially receive the action events fired by the arrow buttons are also controllers — however, instead of modifying the spinner’s model directly, they delegate the task to a separate controller (action listener).

Multiple Controllers

The MVC pattern allows any number of controllers to modify the same model. While we have so far focused only on the two arrow buttons as likely source of events, there is, in fact, a third event source in this example — Whenever the text field has focus, hitting the enter key fires off an action event that may potentially be handled by a different action listener than the one handling action events from the buttons.

Some parts of a component may use different controllers than others

http://www.enode.com/x/markup/tutorial/action.html#trampoline

METHADOLOGY USED FOR TESTING

Testing is the process of detecting errors. Testing performs a very critical role for quality assurance and for ensuring the reliability of software. The results of testing are used later on during maintenance also.

LEVEL OF TESTING

In order to uncover the errors present in different phases we have the concept of levels of testing. The basic levels of testing are follows:-

System Testing

The philosophy behind testing is to find errors. Test cases are devised with this in mind. A strategy employed for system testing is code testing.

Code Testing

This strategy examines the logic of the program. To follow this method we developed some test data that resulted in executing every instruction in the program and module i.e. every path is tested. System is not designed as entire nor are they tested as single systems. To ensure that the coding is perfect two types of testing is performed or for that matter is performed on all system.

Types of Testing

Unit Testing

Link Testing

Unit Testing

Unit testing focuses verification effort on the smallest unit of software i.e. the module. Using the detailed design and the process specification testing is done to uncover errors within the boundary of the modules must be successful in the unit test before the start of the integration testing begins.

In this project each service can be thought of a module. Giving different set of inputs has tested each module. When developing the module as well as finishing the development so that each module works without any error. The inputs are validated when accepting from the user.

System Testing

Here the entire software system is tested. The reference document for this process is the requirement document, and the goal OS to see if software meets its requirements.

Here entire ‘ATM’ has been tested against requirements of project and it is checked whether all requirements of project have been satisfied or not.

Acceptance Testing

Acceptance Test is performed with realistic data of the client to demonstrate that the software is working satisfactorily. Testing here is focused on external behavior of the system: the internal logic of program is not emphasized.

In this project ‘Network Management of Database System’ I have collected some data and tested whether project is working correctly or not.

Test cases should be selected so that largest number of attribute of an equivalence class is exercised at once; the testing phase is an important part of software development. It is the process of finding errors and missing operations and also a complete verification to determine whether the objectives are met and the user requirements are satisfied.

White Box Testing

This is a unit testing method where a unit will be taken at a time and tested thoroughly at a statement level to find the maximum possible errors. I tested step wise every piece of code, taking care that every statement in the Code is executed at least once. The white box testing is also called Glass Box Testing.

I have generated a list of test cases, sample data. This is used to check all possible combinations of execution paths though the code at every module level.

Black Box Testing

This testing method considers a module as a single unit and checks the unit at interface and communication with other module rather getting into details at statement level. Here the module will be treated as a block box that will take some input and generate output. Output for a given set of input combination is forwarded to other modules.

METHADOLOGY ADOPTED, SYSTEM IMPLEMENTATION & DETAILS OF HARDWARE & SOFTWARE

System implementation:-

The implementation phase is less creative then system design. It is primarily concerned with user train, site preparation and file conversion. When the candidate system is linked to terminals or remote sites, the telecommunication network and tests of the network along with the system are also included under implementation.

During the final testing, user acceptance is tested followed by user training. Depending on the nature of the system, extensive user training may be required.

Details of hardware & software

Hardware:-

Processor Pentium IV 3.0 GHz

Ram 512 MB

Hdd-80 GB Capacity With 256 MB Free Space

LAN Card Software:-

Front-end Tools:-

Windows Xp

JSP/SERVLET

NETBEANS

Back-end Tools:-

MYSQL SERVER

LOW LEVEL0 DFD

Bidders

Use Case Diagram

ER- Diagram

Snapshot

Coding MyBid.java

package controllers;

import java.io.*;

import javax.servlet.*;

import javax.servlet.http.*;

import helpers.*;

import models.Customer;

public class MyBids extends HttpServlet {

String view = "/views/mybids.jsp";

public void action(HttpServletRequest request, HttpServletResponse response)

throws ServletException, IOException {

try {

Customer customer = (Customer) request.getSession(true).getAttribute("customer");

if (request.getMethod().equals("GET")) {

} else {

}//POST

request.setAttribute("bids", DatabaseHelper.BidForCustomer(customer.getId()));

Utils.TransferControlToView(view, request, response, this);

} catch (Exception ex) {

ex.printStackTrace(response.getWriter());

}

}

public void doGet(HttpServletRequest request, HttpServletResponse response)


action(request, response);

}

public void doPost(HttpServletRequest request, HttpServletResponse response)


action(request, response);

}

}

MyBid.java

/*

* To change this template, choose Tools | Templates

* and open the template in the editor.

*/

package models;

import helpers.DatabaseHelper;

import java.io.Serializable;

import java.math.BigDecimal;

import java.util.Date;

import javax.persistence.Basic;

import javax.persistence.Column;

import javax.persistence.Entity;

import javax.persistence.GeneratedValue;

import javax.persistence.GenerationType;

import javax.persistence.Id;

import javax.persistence.NamedQueries;

import javax.persistence.NamedQuery;

import javax.persistence.Table;

import javax.persistence.Temporal;

import javax.persistence.TemporalType;

/**

*

* @author Vinay

*/

@Entity

@Table(name = "bid")

@NamedQueries({

@NamedQuery(name = "Bid.findAll", query = "SELECT b FROM Bid b"),

@NamedQuery(name = "Bid.findById", query = "SELECT b FROM Bid b WHERE b.id = :id"),

@NamedQuery(name = "Bid.findByItemid", query = "SELECT b FROM Bid b WHERE b.itemid = :itemid"),

@NamedQuery(name = "Bid.findByCustomerid", query = "SELECT b FROM Bid b WHERE b.customerid = :customerid"),

@NamedQuery(name = "Bid.findByTs", query = "SELECT b FROM Bid b WHERE b.ts = :ts"),

@NamedQuery(name = "Bid.findByBidamount", query = "SELECT b FROM Bid b WHERE b.bidamount = :bidamount"),

@NamedQuery(name = "Bid.findByDirectamount", query = "SELECT b FROM Bid b WHERE b.directamount = :directamount"),

@NamedQuery(name = "Bid.findByIsapproved", query = "SELECT b FROM Bid b WHERE b.isapproved = :isapproved")})

public class Bid extends helpers.BaseModel implements Serializable, helpers.BasicEntity {

private static final long serialVersionUID = 1L;

@Id

@GeneratedValue(strategy = GenerationType.IDENTITY)

@Basic(optional = false)

@Column(name = "id")

private Integer id;

@Column(name = "itemid")

private Integer itemid;

@Column(name = "customerid")

private Integer customerid;

@Basic(optional = false)

@Column(name = "ts")

@Temporal(TemporalType.TIMESTAMP)

private Date ts;

@Column(name = "bidamount")

private BigDecimal bidamount;

@Column(name = "directamount")

private BigDecimal directamount;

@Column(name = "isapproved")

private Integer isapproved;

public Bid() {

}

public Customer getCustomer() throws Exception {

return DatabaseHelper.SingleCustomer(this.customerid);

}

public Item getItem() throws Exception {

return DatabaseHelper.SingleItem(this.itemid);

}

public Bid(Integer id) {

this.id = id;

}

public Bid(Integer id, Date ts) {

this.id = id;

this.ts = ts;

}

public Integer getId() {

return id;

}

public void setId(Integer id) {

this.id = id;

}

public Integer getItemid() {

return itemid;

}

public void setItemid(Integer itemid) {

this.itemid = itemid;

}

public Integer getCustomerid() {

return customerid;

}

public void setCustomerid(Integer customerid) {

this.customerid = customerid;

}

public Date getTs() {

return ts;

}

public void setTs(Date ts) {

this.ts = ts;

}

public BigDecimal getBidamount() {

return bidamount;

}

public void setBidamount(BigDecimal bidamount) {

this.bidamount = bidamount;

}

public BigDecimal getDirectamount() {

return directamount;

}

public void setDirectamount(BigDecimal directamount) {

this.directamount = directamount;

}

public Integer getIsapproved() {

return isapproved;

}

public void setIsapproved(Integer isapproved) {

this.isapproved = isapproved;

}

@Override

public int hashCode() {

int hash = 0;

hash += (id != null ? id.hashCode() : 0);

return hash;

}

@Override

public boolean equals(Object object) {

// TODO: Warning - this method won't work in the case the id fields are not set

if (!(object instanceof Bid)) {

return false;

}

Bid other = (Bid) object;

if ((this.id == null && other.id != null) || (this.id != null && !this.id.equals(other.id))) {

return false;

}

return true;

}

@Override

public String toString() {

return "models.Bid[id=" + id + "]";

}

}

//#################################################

Header.jsp

<%@taglib prefix="c" uri="http://java.sun.com/jsp/jstl/core" %>

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">

<html>

<head>

<title>Neo Bidz</title>

<link href="resources/themes/css/style.css" rel="Stylesheet" type="text/css" />

<link rel="StyleSheet" type="text/css" href="resources/styles/themes/redmond/jquery-ui-1.8.11.custom.css"/>

<link href="resources/whiteboard/whiteboard.css" rel="stylesheet" type="text/css" />

<script type="text/javascript" src="resources/scripts/jquery-1.4.4.min.js"></script>

<script type="text/javascript" src="resources/scripts/jquery.timer.js"></script>

<script type="text/javascript" src="resources/scripts/jquery-ui-1.8.10.custom.min.js"></script>

</head>

<body>

<div id="wrapper">

<div class="menuzone">

<div class="topMenu">

<ul>

<li class="first"><a class="current" href="HomePage">Home</a></li>

<li><a href="services.html">Services</a></li>

<li><a href="support.html">Support</a></li>

<li><a href="contact_us.html">Contact Us</a></li>

<li><a href="#">Privacy</a></li>

</ul>

</div>

<div class="clear"></div>

</div>


<div id="header">

<div id="logo">

<img src="resources/imgs/logo/neobidz.png" style="border: none"/>

</div>

<div id="menu2">

<ul>

<c:if test="${empty sessionScope['student']}">

<li><a href="Login">Login/Register</a></li>

</c:if>

<c:if test="${not empty sessionScope['student']}">

<li><a href="MyBids">My Bids</a></li>

<li><a href="LogOut">LogOut</a></li>

</c:if>

</ul>

</div>


</div>


<div id="banner">

<h1>DIGITAL R50</h1>

<div class="features">

<ul>

Footer.jsp


</div>


<div id="footer">

<ul>

Copyright (c) Neobidz.com. All rights reserved.

<a href="AdminLogin">Admin</a>

<c:if test="${not empty sessionScope.admin}">

<a href="AdminCateg">Categories</a>

<a href="AdminMfg">Manufacturer</a>

</c:if>

</ul>

</div>

</div>

</div></body>

</html>

Homepage.jsp


<jsp:include page="header.jsp"/>

<div>

<div style="width:180px;padding: 5px;float: left">

<ul class="itemcateg">

<li <c:if test="${id eq 0}" > class="selected" </c:if>>

<a href="HomePage?id=0">Recent</a>

</li>

<c:forEach items="${itemms}" var="itemm">

<li <c:if test="${id eq itemm.id}" > class="selected" </c:if>>

<a href="HomePage?id=${itemm.id}">${itemm.categ.name}=>${itemm.name}</a>

</li>

</c:forEach>

</ul>

</div>

<div style="padding: 5px;float: left">

<c:set var="count" value="0"/>

<c:forEach items="${items}" var="item">

<c:set var="count" value="${count+1}"/>

<div class="column1">

<h3>${item.model}</h3>

<img src="itemimgs/${item.id}.jpg" class="itemimg" alt="itemimg" width="100" height="119" />

<div class="columnText" style="padding-left:-20px;">${item.details}</div>

<div class="columnLink">

<a href="BidNow?id=${item.id}" style="color:#333;font-size:13px; ">Bid Now for any amount more than Re ${item.currentbid}!!!</a>

<br/>

<a href="DirectPurchase?id=${item.id}" style="color:#333;font-size:13px; ">Direct purchase for Re ${item.directprice}!!!</a>

</div>

</div>

<c:if test="${count eq 3}">

<c:set var="count" value="0"/>

</c:if>

</c:forEach>

</div>

</div>

<jsp:include page="footer.jsp"/>

Style.css

/* CSS Document */

body

{font-family:Arial, Helvetica, sans-serif;

font-size:11px;

background:#EEEFF3 url(../images/bodybg.jpg) repeat-x;

margin:0px;

padding:0px;

}

*{margin:0; padding:0}

#wrapper

{margin:0 auto;

width:904px;

}

.clear

{clear:both;

margin:0px;

padding:0px;

}

.menuzone

{

height:35px;

}

#logo

{

padding-top:15px;

margin-left:45px;

float:left;

}

.topMenu

{

margin:0px;

padding:10px 20px 0px 0px;

float:right;

}

.topMenu ul

{margin:0px;

padding:0px;

}

.topMenu li

{display:inline;

color:#FFFFFF; border-left:1px solid #fff; padding:0 5px 0 10px;

}

.topMenu li.first{border:none}

.topMenu li a

{color:#FFFFFF;

text-decoration:none;

font-weight:bold;


}

.topMenu li a:hover{text-decoration:underline}

.topMenu li a.current{text-decoration:underline}

#header

{width:904px;

height:76px;

background-image:url(../images/pic1.jpg);

}

#menu2

{height:45px;

float:right;

margin:0px;


}

#menu2 ul

{margin:0px;

padding:0px;

}

#menu2 li

{display:inline;

color:#FFFFFF;

list-style:none;

}

#menu2 li a

{color:#47608D;

margin:0px 20px 0px 0px; display:inline;

font-size:12px;


font-weight:bold;

}

#banner

{width:904px;

height:250px;

background:url(../images/mainbanner.jpg);

}

h1

{margin:0px;


font-size:21px;

color:#FFFFFF;

font-family:Arial, Helvetica, sans-serif;

}

h2

{margin:0px;


color:#333;

font-weight:200;

font:21px Gill Sans Condensed, Myriad Pro, Arial, Helvetica, sans-serif;

}

.features

{ width:408px;


}

.features ul

{margin:0px;

padding:0px;

}

.features li

{list-style-type:none;


font-size:12px;

color:#7DC6F1;

font-weight:bold;

}

.bannertxt {

color:#ffffff;

font-size:11px;

font-weight:100;

}

.readMore

{


margin:0px;

}

.readMore a

{

color:#7DC6F1;

font-size:12px;

margin:0px;

font-weight:bold;


}

.compatibility

{width:904px;

text-align:center;


margin:0px;

background-image:url(../images/pic2.jpg);

background-repeat:no-repeat;

font-weight:bold;

}

.compatibilitybox {

width:250px;

float:right;

}

.compatibilitytxt {

float:left;


margin-right:10px;

}

.compatibilityicon {

float:left;

margin-right:10px;

}

#columZone

{width:904px;

background:#EEEFF3 url(../images/piccontainerbg.jpg) left bottom no-repeat;


}

#container2

{width:650px;


float:left;

}

.column1 {

width:226px;

float:left;

background:url(../images/verticalline.jpg) right top no-repeat;


margin:0px 0px 0px 0px;

text-align:center;

}

.columnText

{ text-align:left;


}

.columnText1

{ text-align:left;


}

.columnLink

{ text-align:center;

width:226px;


font-weight:bold;

font-size:12px;

color:#E93B0C;

}

.order

{font-weight:bold;

font-size:12px;

color:#000;


}

.order a

{color:#000000;

}

.column2 {

width:226px;

float:left;



text-align:center;

}

h3

{text-align:center;

color:#000000;

font-size:12px;

font-weight:bold;

margin:0px;


}

.blueDot

{width:904px;

height:33px;

background-image: url(../images/bluebg.png);

}

.welCome

{width:650px; float:left;

background:#4564A7;

}

.welComeleft

{width:19px;

height:44px;

background-image:url(../images/blueleftbg.jpg);

float:left;

}

.welComeright

{width:19px;

height:44px;

background-image:url(../images/bluerightbg.jpg);

float:right;

}

.welCometextBox1

{width:650px;

background-color:#FFFFFF;

float:left;

}

.bottom_container{float:left; width:904px}

.welCometextBox2{float:left; width:192px; padding:0 0 0 38px}

.welCometextBox2 h4{float:left; width:170px; height:25px; font:18px/20px Gill Sans Condensed, Myriad Pro, Arial, Helvetica, sans-serif; color:#fff; background:url(../images/bluebg2.jpg) no-repeat 0 0; padding:68px 0 0 22px}

.welCometextBox2 .news{float:left; width:192px; background:url(../images/news_bg.gif) repeat-y 0 0}

.welCometextBox2 .news p{ float:left; width:154px; font:11px/13px Arial, Helvetica, sans-serif; color:#58595e; padding:5px 0 8px 20px}

.welCometextBox2 .news p span{color:#c45221; font:11px/13px Arial, Helvetica, sans-serif; font-weight:bold}

.welCometextBox2 .more{float:left; width:192px; height:58px; background:url(../images/more_bg.gif) no-repeat 0 0}

.welCometextBox2 .more a{float:left; font-weight:bold; color:#4564a7; font:11px/13px Arial, Helvetica, sans-serif; text-decoration:none; margin:13px 0 0 21px}

.welCometextBox2 .more a:hover{text-decoration:underline}

.welCometext

{

float:left;

text-align:justify;


color:#6C6B70;

border-bottom:solid #d6d7da 1px;


}

.welCometextBold

{color:#1E3C73;

font-weight:bold;

}

#footer{width:904px; float:left; border-top:2px solid #bfbfbf}

#footer ul{width:904px; float:left; text-align:center; list-style:none; padding:20px 0 50px 0 }

#footer li{width:auto; font:bold 11px/13px Arial, Helvetica, sans-serif; color:#4564a7; padding:0

10px 0 10px ; border-left: 1px solid #4564a7; display:inline}

#footer li.first{border:none}

#footer li a{color:#4564a7; text-decoration:none}

#footer li a:hover{color:#4564a7; text-decoration:underline}

#footer li a.current{text-decoration:underline}

/* inner pages css start */

h1.inner{font:24px tahoma, Arial; color:#4564a7; width:auto; font-weight:bold; margin:0px; padding:8px 0px 10px 0px; text-decoration:none}

h1.inner span{font:24px tahoma, Arial; color:#4564a7; font-weight:bold; margin:0px; padding:25px 0px 10px 0px; background:none}

.aboutus-img{float:right; border:4px solid #dcdcda;margin:0px 0px 10px 20px;}

h5{font:15px Myriad Pro, Arial, Helvetica, sans-serif; color:#555555; font-weight:100; padding:0px 0px 5px 0px; border-bottom:1px dotted #000; margin:0px 0px 10px 0px; background:none }

h6.inner{font:17px Myriad Pro, Arial, Helvetica, sans-serif; color:#555555; font-weight:100; padding:0px 0px 5px 0px; margin:0px 0px 0px 0px; background:none }

.aboutcolumnzone{padding:20px 0px 16px 0px;}

.aboutcolumn1{width:48%; float:left; margin:0px 0px 10px 0px;}

.aboutcolumn2{width:48%; float:right; margin:0px 0px 10px 0px;}

.abouticon{float:left; margin:0px 20px 0px 0px;}

.insidereadmore{padding:10px 0px 10px 0px;}

.insidereadmore a{color:#5D2D23; font-size:14px; text-decoration:none}

.insidereadmore a:hover{text-decoration:underline}

a.projects{color:#5D2D23; font-size:14px; text-decoration:underline}

a:hover.projects{text-decoration:none}

input.button{color:#ffffff; background:#414141;font:bold 11px Arial, Helvetica, sans-

serif; text-decoration:none; padding:10px 10px; margin:0px 5px 5px 0; border:1px solid #000;}

input.button:hover{cursor:pointer; color:#cccccc;}

.project-img{float:right; margin-left:20px;border: 6px solid #dcdcda;}

.whiteheading{font:30px Myriad Pro, Arial; color:#000; font-weight:100; padding:0px; margin:25px 0px 20px 0px;}

.ourprojectrow{margin-bottom:20px; border-bottom:1px dotted #000; padding-bottom:10px;}

.servicecolumnzone{padding:20px 0px 16px 0px;}

.servicecolumn1{width:48%; float:left; margin:0px 0px 10px 0px;}

.servicecolumn2{width:48%; float:right;margin:0px 0px 10px 0px;}

.blog-posted-row{padding:3px; background:#dcdcda}

.blog-posted-row a{color:#5D2D23; font-size:14px; text-decoration:underline; padding:0 0 0 8px}

.blog-posted-row a:hover{text-decoration:none}

/* inner pages css ends */

CONCLUSION

The project report entitled "ONLINE SMARTBID" has

come to its conclusion. The new system has been developed

with so much care that it is free of errors and at the same

time efficient and less time consuming. System is robust.

Also provision is provided for future developments in the

system.

References: -

Ian Somerville, “Software Engineering”, Sixth Edition,

Pearson Education Ltd, 2002.

Page Jones, “Fundamentals of Object Oriented design

in UML”, Addison Wesley Longman Pvt Ltd.

Elamsri and Navathe, “Fundamentals of Database

Systems”, Pearson Asia Edition 2000

001_a project report on online auction

Documents