CS7075 Enterprise Software Component Development Coursework: A Web Auction Site Summary This is an individual coursework worth 75% of the total module mark. It requires developing of a prototype of a technological solution which utilizes Java Enterprise technologies and tools. It finishes with a written report to be submitted by the deadline, software and demonstration • 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 an auctioning Web site which features database backend and operates using standard browser only. It can be developed according to the personal choice of enterprise technology but must utilize at least synchronous server-side processing of item registration, auctioning, searching and bidding (using servlets, applets, JSPs and/or JSFs for the front-end, and either EJBs or Web services for the middleware). Optionally, the application can have user registration, logging, access control using the security services supported by the server and additional asynchronous server-side functionality (reporting, notification, etc.) required by the client. • 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. 5. Extend the server-side application with a business tier which allows registration, watching and bidding 6. Optionally, implement user registration, logging and access control Deliverables 1. Written report in Word format, submitted online to the WebLearn by the deadline. 2. Web application submitted to WebLearn by the deadline. 3. Demonstration presented using a desktop PC or laptop in the computer Lab as specified. Requirements 1. The written report must provide information on the following issues: • Software Architecture (using UML deployment diagram) • Database design (using UML class diagram and SQL DDL script) • Web site design (using UML State Transition diagram or page navigation map) • Program description (major scenarios description, UML sequence diagrams, etc) • A full walkthrough of the working with the system (set of screen dumps) • Deployment instructions (UML component diagram, specification of the software products, libraries and off-the-shelf components needed, deployment and configuration instructions) 2. The database for storing auctioning information • It can be build using the native Java DB Derby, or a general purpose SQL DB such as MySQL or Oracle. • It should contain at least 4 tables for storing the description of auction items, personal information about the bidders, operational information about the auctions and historical information about the bids (i.e., USER, ITEM, AUCTION, BID). 3. The auction site should combine static and dynamic pages for the synchronous operations performed during cataloguing, auctioning and bidding. • The Web site may contain static for supporting the required operations as needed. The static Web pages can be build using HTML/XHTML/DHTML and CSS plus JavaScript where useful. • The Web application must contain 5-8 dynamic pages to allow registering items (CatalogueItem), creating auctions (CreateAuction), searching for catalogued or auctioned items (SearchItem, SearchAuction) and placing bids (PlaceBid). You may use servlets, applets, JSPs and/or JSFs as necessary. • The non-Web tier must support the Web-tier with backend and frontend session management, database connectivity and business data manipulation. You may use session EJBs, message EJBs and/or Web Services to implement this functionality as needed. • Optionally, the application can be extend with additional functionality for remote operation over IIOP (i.e,.requesting and receiving reports, or event notification). For this you may wish to use desktop client applications, EJBs and/or Web Services to implement the extended functionality 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 containing all libraries and class files (in one or more .war, .jar and/or .ear files as needed) Marking Scheme • Static Web Pages 10% • Web Site Database 5% • Dynamic Web Pages 15% • Middleware 30% • Web Application Design & Development 15% • Web Application Testing and Deployment 10% • Web Site Walkthrough Presentation 5% • Software Quality and Documentation 10% Total 100% Notes: 1. The demonstration is not marked but without it the mark for the software will be set to 0% and the marks will be max 40% (guaranteed fail) 2. The use of Java EE is critical to pass the assignment since without it the mark will be max 50% (typical fail) 3. The use of EJB/WS technologies is not critical to pass but without it the mark will be max 70% (without guaranteed distinction) 4. The report is not critical but without it the mark will be max 60% (guaranteed with no distinction)