Net Auction java based project report
#1

[attachment=13114]
[attachment=13117]
[attachment=13118]
[attachment=13119]
[attachment=13120]
[attachment=13121]
[attachment=13122]



Abstract

Title of the project: Net Auction
Introduction:
Here we'll talk about the three different types of auctions you can come across. But before we go into that, here is a brief introduction to auctions.
Auction:
An auction is a sale in which a seller presents his product on a public platform/ forum. The selling price in an auction is determined by the bids made by interested buyers. The price they bid is based on their own valuation of, and need for, the product. The product is sold to the highest bidder. A potential buyer participates by bidding on an item that a seller has listed. The person who has offered the highest bid at close of auction wins the right to purchase the item at that price.
Bid:
A bid is the amount of money proffered for an item that has been put on sale in an auction. The bidder competes with other potential buyers, keeping in mind that the buyer with the highest bid is obliged to complete the purchase with the seller. In other words, your bid tells other buyers, "I want to buy this item at this price."
Win:
You win an auction by placing the winning (read highest) bid and obtaining the item on auction. The person with the highest bid is the winner of the auction. Now that you're familiar with how an auction generally works.
This application has been divided into four modules
1. Buyer Module
2. seller Module
3. Admin Module
4. Reports Module


1. Buyer Module:

Bidding can be carried out automatically by enabling the automatic bidding feature. Automatic Bid features bids on a particular item for you up to the maximum amount that you have specified. This amount is the maximum amount that you, the buyer, are willing to pay for an item. It is kept confidential. To activate the Automatic Bid, just enter your maximum bid amount in the "Enter Automatic Bid amount" box and click on the "Bid Now" button.
2. Seller Module:
Automatic Bid is an optional facility. If you activate Automatic Bid, you need not be online to bid for and win an item you desire. The system will bid for you if necessary by the specified bid increment amount to the limit of your Automatic Bid. Please note that the Automatic Bid system will only bid for you when you have been outbid or to meet the reserve price at the end of the auction. You will receive an email notification every time the Automatic Bid bids for you. To bid on a multiple items is considered to be a special auction where a seller has more than one quantity of the item he or she wants to sell/bid. The seller selects the starting bid amount and indicates how many of these items are available for the auction. An auction is a multiple auction or not can be known by checking the quantity box of the item. If there is number of quantities displayed is more than 1, then it is a MQA (Multiple Quantity Auction).
3. Admin Module:
Admin module will control both buyer and seller modules and also they will maintain all reports regarding today’s expiry auctions and next day’s expiry auctions etc.
Reports Module:
By using this module user will get different types of reports like buyer and seller information and no. of. Transactions.






Software requirements:


Operating System : Windows
Technology : Core java, Adv Java (JDBC, Servlets, JSP)
Web Technologies : Html, JavaScript, CSS
IDE : My Eclipse
Web Server : Tomcat
Database : Oracle
Software’s : J2SDK1.5, Tomcat 5.5, Oracle 9i

Hardware requirements:

Hardware : Pentium based systems with a minimum of P5
RAM : 256MB (minimum).



STUDY OF THE SYSTEM
To provide flexibility to the users, the interfaces have been developed that are accessible through a browser. The GUI’S at the top level have been categorized as
1. Administrative user interface
2. The operational or generic user interface

The ‘administrative user interface’ concentrates on the consistent information that is practically, part of the organizational activities and which needs proper authentication for the data collection. These interfaces help the administrators with all the transactional states like Data insertion, Data deletion and Date updation along with the extensive data search capabilities.

The ‘operational or generic user interface’ helps the end users of the system in transactions through the existing data and required services. The operational user interface also helps the ordinary users in managing their own information in a customized manner as per the included flexibilities
2.2 INPUT & OUTPOUT REPRESENTETION

Input design is a part of overall system design. The main objective during the input design is as given below:
• To produce a cost-effective method of input.
• To achieve the highest possible level of accuracy.
• To ensure that the input is acceptable and understood by the user.

INPUT STAGES:
The main input stages can be listed as below:
• Data recording
• Data transcription
• Data conversion
• Data verification
• Data control
• Data transmission
• Data validation
• Data correction

INPUT TYPES:
It is necessary to determine the various types of inputs. Inputs can be categorized as follows:
• External inputs, which are prime inputs for the system.
• Internal inputs, which are user communications with the system.
• Operational, which are computer department’s communications to the system?
• Interactive, which are inputs entered during a dialogue.

INPUT MEDIA:
At this stage choice has to be made about the input media. To conclude about the input media consideration has to be given to;
• Type of input
• Flexibility of format
• Speed
• Accuracy
• Verification methods
• Rejection rates
• Ease of correction
• Storage and handling requirements
• Security
• Easy to use
• Portability
Keeping in view the above description of the input types and input media, it can be said that most of the inputs are of the form of internal and interactive. As Input data is to be the directly keyed in by the user, the keyboard can be considered to be the most suitable input device.

OUTPUT DESIGN:

In general are:
• External Outputs whose destination is outside the organization.
• Internal Outputs whose destination is with in organization and they are the User’s main interface with the computer. Outputs from computer systems are required primarily to communicate the results of processing to users. They are also used to provide a permanent copy of the results for later consultation. The various types of outputs
• Operational outputs whose use is purely with in the computer department.
• Interface outputs, which involve the user in communicating directly with the system.


OUTPUT DEFINITION
The outputs should be defined in terms of the following points:
 Type of the output
 Content of the output
 Format of the output
 Location of the output
 Frequency of the output
 Volume of the output
 Sequence of the output

It is not always desirable to print or display data as it is held on a computer. It should be decided as which form of the output is the most suitable.

For Example
• Will decimal points need to be inserted
• Should leading zeros be suppressed.

OUTPUT MEDIA:
In the next stage it is to be decided that which medium is the most appropriate for the output. The main considerations when deciding about the output media are:

• The suitability for the device to the particular application.
• The need for a hard copy.
• The response time required.
• The location of the users
• The software and hardware available.

Keeping in view the above description the project is to have outputs mainly coming under the category of internal outputs. The main outputs desired according to the requirement specification are:

The outputs were needed to be generated as a hard copy and as well as queries to be viewed on the screen. Keeping in view these outputs, the format for the output is taken from the outputs, which are currently being obtained after manual processing. The standard printer is to be used as output media for hard copies.


SDLC (Umbrella Model):







SDLC is nothing but Software Development Life Cycle. It is a standard which is used by software industry to develop good software.

Stages in SDLC:

• Requirement Gathering
• Analysis
• Designing
• Coding
• Testing
• Maintenance
Requirements Gathering stage:

The requirements gathering process takes as its input the goals identified in the high-level requirements section of the project plan. Each goal will be refined into a set of one or more requirements. These requirements define the major functions of the intended application, define
operational data areas and reference data areas, and define the initial data entities. Major functions include critical processes to be managed, as well as mission critical inputs, outputs and reports. A user class hierarchy is developed and associated with these major functions, data areas, and data entities. Each of these definitions is termed a Requirement. Requirements are identified by unique requirement identifiers and, at minimum, contain a requirement title and
textual description.


These requirements are fully described in the primary deliverables for this stage: the Requirements Document and the Requirements Traceability Matrix (RTM). The requirements document contains complete descriptions of each requirement, including diagrams and references to external documents as necessary. Note that detailed listings of database tables and fields are not included in the requirements document.
The title of each requirement is also placed into the first version of the RTM, along with the title of each goal from the project plan. The purpose of the RTM is to show that the product components developed during each stage of the software development lifecycle are formally connected to the components developed in prior stages.

In the requirements stage, the RTM consists of a list of high-level requirements, or goals, by title, with a listing of associated requirements for each goal, listed by requirement title. In this hierarchical listing, the RTM shows that each requirement developed during this stage is formally linked to a specific product goal. In this format, each requirement can be traced to a specific product goal, hence the term requirements traceability.
The outputs of the requirements definition stage include the requirements document, the RTM, and an updated project plan.
• Feasibility study is all about identification of problems in a project.
• No. of staff required to handle a project is represented as Team Formation, in this case only modules are individual tasks will be assigned to employees who are working for that project.
• Project Specifications are all about representing of various possible inputs submitting to the server and corresponding outputs along with reports maintained by administrator
Analysis Stage:


The planning stage establishes a bird's eye view of the intended software product, and uses this to establish the basic project structure, evaluate feasibility and risks associated with the project, and describe appropriate management and technical approaches.


The most critical section of the project plan is a listing of high-level product requirements, also referred to as goals. All of the software product requirements to be developed during the requirements definition stage flow from one or more of these goals. The minimum information for each goal consists of a title and textual description, although additional information and references to external documents may be included. The outputs of the project planning stage are the configuration management plan, the quality assurance plan, and the project plan and schedule, with a detailed listing of scheduled activities for the upcoming Requirements stage, and high level estimates of effort for the out stages.


Designing Stage:


The design stage takes as its initial input the requirements identified in the approved requirements document. For each requirement, a set of one or more design elements will be produced as a result of interviews, workshops, and/or prototype efforts. Design elements describe the desired software features in detail, and generally include functional hierarchy diagrams, screen layout diagrams, tables of business rules, business process diagrams, pseudo code, and a complete entity-relationship diagram with a full data dictionary. These design elements are intended to describe the software in sufficient detail that skilled programmers may develop the software with minimal additional input.


When the design document is finalized and accepted, the RTM is updated to show that each design element is formally associated with a specific requirement. The outputs of the design stage are the design document, an updated RTM, and an updated project plan.

Development (Coding) Stage:


The development stage takes as its primary input the design elements described in the approved design document. For each design element, a set of one or more software artifacts will be produced. Software artifacts include but are not limited to menus, dialogs, data management forms, data reporting formats, and specialized procedures and functions. Appropriate test cases will be developed for each set of functionally related software artifacts, and an online help system will be developed to guide users in their interactions with the software.


The RTM will be updated to show that each developed artifact is linked to a specific design element, and that each developed artifact has one or more corresponding test case items. At this point, the RTM is in its final configuration. The outputs of the development stage include a fully functional set of software that satisfies the requirements and design elements previously documented, an online help system that describes the operation of the software, an implementation map that identifies the primary code entry points for all major system functions, a test plan that describes the test cases to be used to validate the correctness and completeness of the software, an updated RTM, and an updated project plan.

Integration & Test Stage:

During the integration and test stage, the software artifacts, online help, and test data are migrated from the development environment to a separate test environment. At this point, all test cases are run to verify the correctness and completeness of the software. Successful execution of the test suite confirms a robust and complete migration capability. During this stage, reference data is finalized for production use and production users are identified and linked to their appropriate roles. The final reference data (or links to reference data source files) and production user list are compiled into the Production Initiation Plan.


The outputs of the integration and test stage include an integrated set of software, an online help system, an implementation map, a production initiation plan that describes reference data and production users, an acceptance plan which contains the final suite of test cases, and an updated project plan.

• Installation & Acceptance Test:

During the installation and acceptance stage, the software artifacts, online help, and initial production data are loaded onto the production server. At this point, all test cases are run to verify the correctness and completeness of the software. Successful execution of the test suite is a prerequisite to acceptance of the software by the customer.
After customer personnel have verified that the initial production data load is correct and the test suite has been executed with satisfactory results, the customer formally accepts the delivery of the software.

The primary outputs of the installation and acceptance stage include a production application, a completed acceptance test suite, and a memorandum of customer acceptance of the software. Finally, the PDR enters the last of the actual labor data into the project schedule and locks the project as a permanent project record. At this point the PDR "locks" the project by archiving all software items, the implementation map, the source code, and the documentation for future reference.

Maintenance:


Outer rectangle represents maintenance of a project, Maintenance team will start with requirement study, understanding of documentation later employees will be assigned work and they will under go training on that particular assigned category.
For this life cycle there is no end, it will be continued so on like an umbrella (no ending point to umbrella sticks).
2.4 SYSTEM ARCHITECTURE
Architecture flow:
Below architecture diagram represents mainly flow of requests from users to database through servers. In this scenario overall system is designed in three tires separately using three layers called presentation layer, business logic layer and data page link layer. This project was developed using 3-tire architecture.

Reply
#2
the project source code of Net Auction java based project available on the page seminarprojects.kreviewitem.php?id=140
Reply
#3
to get information about the topic "netauction java code" full report ppt and related topic refer the page link bellow

http://studentbank.in/report-net-auction

http://studentbank.in/report-net-auction...ect-report

http://studentbank.in/report-secure-net-...ull-report
Reply

Important Note..!

If you are not satisfied with above reply ,..Please

ASK HERE

So that we will collect data for you and will made reply to the request....OR try below "QUICK REPLY" box to add a reply to this page
Popular Searches: ppt on online net auction system, e auction project on asp net, auction system project report in asp net, e auction shopping project in net, car auction asp project, rto number auction project in asp net, project report for auction,

[-]
Quick Reply
Message
Type your reply to this message here.

Image Verification
Please enter the text contained within the image into the text box below it. This process is used to prevent automated spam bots.
Image Verification
(case insensitive)

Possibly Related Threads...
Thread Author Replies Views Last Post
  projects in core java project topics 6 16,073 16-01-2018, 11:15 AM
Last Post: dhanabhagya
  Steganography implemented in Java science projects buddy 14 12,139 24-05-2016, 10:15 AM
Last Post: dhanabhagya
  college website project full report project report tiger 28 67,020 29-11-2015, 02:37 PM
Last Post: Guest
  STUDENT INFORMATION SYSTEM IN JAVA project topics 14 10,532 19-08-2015, 11:28 PM
Last Post: Guest
  mini projects in java project topics 7 18,775 01-05-2015, 04:18 PM
Last Post: seminar report asees
  Online Library Management System Project report science projects buddy 15 46,059 24-02-2015, 01:53 PM
Last Post: Guest
  Handwriting recognition project report seminar addict 3 4,114 24-06-2013, 11:24 AM
Last Post: computer topic
  web based supply chain management full report project report tiger 11 9,925 02-02-2013, 04:28 PM
Last Post: seminar details
  IEEE Project Idea based on Network Simulation VickyBujju 5 4,526 04-12-2012, 01:31 PM
Last Post: seminar details
  Net- Banking mechanical engineering crazy 4 5,588 02-12-2012, 03:33 PM
Last Post: Guest

Forum Jump: