A Web Auction Site

It requires developing of a prototype of a technological solution which utilizes servlets, database and EJB technologies for building multi-tier Web applications.
•The report is to describe the design of a simple auctioning system with a backend database and a Web front-end (mini-eBay), its prototype implementation and testing.
•The software development is for a simple auctioning Web site which features database backend and operates using standard browser only. It can be developed on a

different level of sophistication, depending on the personal preference of the students but must utilize synchronous server-side processing of customer registration

This is an individual coursework worth 25% of the total module mark. It requires developing of a prototype of a technological solution which utilizes servlets,

database and EJB technologies for building multi-tier Web applications. It finishes with a written report to be submitted by the deadline, software and demonstration

to be held during one of the last workshops of the term.

• The report is to describe the design of a simple auctioning system with a backend database and a Web front-end (mini-eBay), its prototype implementation and

testing.
• The software development is for a simple auctioning Web site which features database backend and operates using standard browser only. It can be developed on a

different level of sophistication, depending on the personal preference of the students but must utilize synchronous server-side processing of customer registration

and bidding (using Java servlets or JSP) and server-side persistent session for watching the auction (using session and messaging EJBs).
• The demonstration is to show the developed solution in operation. It will be organised in the Computer Labs and must be attended by each student in order to

gain the full mark.
Tasks

1. Design the software architecture of a Web auctioning site.
2. Design a database for storing information about users, items, auctions and bids.
3. Build a Web site for setting-up and maintenance of online auctions for selling items.
4. Develop a Web tier with servlets and/or JSPs.
5. Extend the server-side application with an EJB layer which allows watching and bidding in an online auction.

Deliverables

1. Written report in Word format, submitted online to the WebLearn by the deadline.
2. Web application submitted on a CD during the demonstration.
3. Demonstration presented using a desktop PC or laptop in the computer Lab during the workshop in Week 27.

Detailed Description

1. The written report does not have fixed structure, but can provide information on the following issues:
• Database design (using UML class diagram and SQL DDL script)
• Web site design (using UML State Transition diagram or page navigation map)
• Program description showing the flow of events during bidding (using UML sequence diagram)
• A full walkthrough of the working with the system (set of screen dumps)
• The software deployment (software products, libraries and application components, using UML deployment diagram and instructions)

2. The database for storing auctioning information

• It can be build using the native Java DB Derby, or a standard SQL DB such as MySQL/MSSQL or Oracle.
• It should contain at least 4 tables for storing the description of auction items, personal information about the bidders and operational information about the

past, ongoing and closed bids (i.e., USER, ITEM, AUCTION, BID).

3. The auction site should be built using HTML and Java/JSP. It may combine static and dynamic pages for the synchronous operations as necessary. The minimal

functionality of the site required includes cataloguing of an item, setting of a new auction and bidding for an item in an auction. Additional functionality can

include user registration with access control, watching an ongoing auction and statistic reporting.
• The static Web pages can be build using HTML/XHTML/DHTML and CSS. The Web site must contain pages for supporting the required operations as needed.
• The Web application must contain 4-6 servlets/JSPs to allow registering items (CatalogueItem), creating auctions (CreateAuction), searching for catalogued and

auctioned items (SearchItem, SearchAuction), watching auctions (WatchAuction), and bidding: (BidAuction). You may use either servlets or JSPs for Web server-side

development.
• The EJBs must support one or more of the following functionality: watching auctions, bidding and/or updating the highest bids. You may use session EJBs and

message EJBs for J2EE server-side development as needed.
4. The software should be delivered as a development archive containing both sources and compiled classes (in a single .zip file) and as deployable archives (in

Related

Post navigation

A Web Auction Site

It requires developing of a prototype of a technological solution which utilizes servlets, database and EJB technologies for building multi-tier Web applications.
•The report is to describe the design of a simple auctioning system with a backend database and a Web front-end (mini-eBay), its prototype implementation and testing.
•The software development is for a simple auctioning Web site which features database backend and operates using standard browser only. It can be developed on a

different level of sophistication, depending on the personal preference of the students but must utilize synchronous server-side processing of customer registration

This is an individual coursework worth 25% of the total module mark. It requires developing of a prototype of a technological solution which utilizes servlets,

database and EJB technologies for building multi-tier Web applications. It finishes with a written report to be submitted by the deadline, software and demonstration

to be held during one of the last workshops of the term.

• The report is to describe the design of a simple auctioning system with a backend database and a Web front-end (mini-eBay), its prototype implementation and

testing.
• The software development is for a simple auctioning Web site which features database backend and operates using standard browser only. It can be developed on a

different level of sophistication, depending on the personal preference of the students but must utilize synchronous server-side processing of customer registration

and bidding (using Java servlets or JSP) and server-side persistent session for watching the auction (using session and messaging EJBs).
• The demonstration is to show the developed solution in operation. It will be organised in the Computer Labs and must be attended by each student in order to

gain the full mark.
Tasks

1. Design the software architecture of a Web auctioning site.
2. Design a database for storing information about users, items, auctions and bids.
3. Build a Web site for setting-up and maintenance of online auctions for selling items.
4. Develop a Web tier with servlets and/or JSPs.
5. Extend the server-side application with an EJB layer which allows watching and bidding in an online auction.

Deliverables

1. Written report in Word format, submitted online to the WebLearn by the deadline.
2. Web application submitted on a CD during the demonstration.
3. Demonstration presented using a desktop PC or laptop in the computer Lab during the workshop in Week 27.

Detailed Description

1. The written report does not have fixed structure, but can provide information on the following issues:
• Database design (using UML class diagram and SQL DDL script)
• Web site design (using UML State Transition diagram or page navigation map)
• Program description showing the flow of events during bidding (using UML sequence diagram)
• A full walkthrough of the working with the system (set of screen dumps)
• The software deployment (software products, libraries and application components, using UML deployment diagram and instructions)

2. The database for storing auctioning information

• It can be build using the native Java DB Derby, or a standard SQL DB such as MySQL/MSSQL or Oracle.
• It should contain at least 4 tables for storing the description of auction items, personal information about the bidders and operational information about the

past, ongoing and closed bids (i.e., USER, ITEM, AUCTION, BID).

3. The auction site should be built using HTML and Java/JSP. It may combine static and dynamic pages for the synchronous operations as necessary. The minimal

functionality of the site required includes cataloguing of an item, setting of a new auction and bidding for an item in an auction. Additional functionality can

include user registration with access control, watching an ongoing auction and statistic reporting.
• The static Web pages can be build using HTML/XHTML/DHTML and CSS. The Web site must contain pages for supporting the required operations as needed.
• The Web application must contain 4-6 servlets/JSPs to allow registering items (CatalogueItem), creating auctions (CreateAuction), searching for catalogued and

auctioned items (SearchItem, SearchAuction), watching auctions (WatchAuction), and bidding: (BidAuction). You may use either servlets or JSPs for Web server-side

development.
• The EJBs must support one or more of the following functionality: watching auctions, bidding and/or updating the highest bids. You may use session EJBs and

message EJBs for J2EE server-side development as needed.
4. The software should be delivered as a development archive containing both sources and compiled classes (in a single .zip file) and as deployable archives (in