This assignment provides your group with a DFD and a set of requirements.
It is your job to be part of the programming team that implements this system for Top Bikes. You team would need to read the requirements thoroughly and then manage the various roles in order to make sure that the project is delivered
on time.
It is each individuals responsibility to know and understand the code that is created.
Due date: 31st Oct 2014 at 11:59pm
Details of the System
Figure 1: The Simplified To-Be Auction DFD
1. Implement the new online Auction sub-system that is based on the Auction To Be System DFD above. ONLY the Auction Sub-system is to be implemented. The system that you are required to implement must:
1(a) Display an initial welcome screen to the customer that gives her the option to proceed into the auction system.
(b) Require the customer to login to the system with their unique username and password. Each customer's Username, Password, CustomerID and other relevant properties are to be stored in a private XML database. You may assume that all customers exist in the database. You are NOT required to provide customer registration functions.
Validation of the customer's Username and Password are to be use a Customer XML database and return the unique CustomerID if Username and Password are found.
Customers should not be able to proceed past this page until they have successfully logged in. When the customer has successfully logged in, their unique CustomerID must be stored in a Session variable for use in later modules.
(c) Allow the user to search for an item by the Manufacturer's name ONLY. You may assume that there are no duplicates. Manufacturer names in the system. To allow additional manufacturers to be easily added, their names are to be dynamically loaded into a webform control from an XML file containing manufacturer names and unique manufacturer identification numbers.
(d) Display a list of items that are manufactured by that manufacturer (and are in stock) in a format that allows the user to select the required items from those available.
(e) When the user selects the required item, the details of the items including its picture and its price are to be displayed with a field for the user to enter a bid (minimum $5,000), and a button to place the bid. All input fields must be validated to prevent invalid entries.
(f) If the user clicks the bid button, the bid is recorded and the total cost, including commission is updated and displayed. FOR THIS ASSIGNMENT,
THE SYSTEM IS ONLY REQUIRED TO HANDLE A SINGLE ITEM IN EACH
BID.
(g) The details of the bid must then be displayed to the user with a con- firmation button and an option to go back and change the bid. If the confirmation button is pressed, the user must be taken to the bid finalisation screen. NOTE: Credit card details do not need to be entered as this information will be held offline for security reasons.
(h) A bid confirmation document containing all the details of the bid must then be displayed on a new page. The page should be laid out in a format suitable for printing. The bid must also be AUTOMATICALLY emailed to [email protected]. NOTE: You are not required to test the email function but you MUST insert the required code.
(i) Staff and customers must also be able to view the custom modifications pricelists using a browser. A pricelist for at least one workshop is required but you may provide more if you wish.
(j) As a guide, the following sections of the to be system should be implemented as a minimum:
22. Validate Customer, Find Items, Display Item Information, Place Bid, Finalise Bid, Confirm Bid and Display Pricelist processes
3. The Items, Bids and Customers entities in the data model
4. Welcome, Search, Display item, Show items Details, Bid Confirmation, Bid Details and Workshop Pricelist Display screens.
Breakdown of Marks
• The sub-system specified in the requirements definition
• A short User's Manual that can be accessed from a browser. The manual should be no more than two A4 pages and must be written in (or converted to) XHTML and linked into the systems web pages at appropriate locations.
• A System Manual that includes:
- A brief description of the program structure including a structure chart
- A separate specification sheet for each of the User Login, Find items and Show items Details modules;
∗ A test plan and test results for each module
∗ Description of any known bugs
∗ A list of all program file names, data file names and the directories in which the files are required to be placed for the system to operate
correctly
∗ Details of the required XmlDataSource names and the XML files to which they should be linked.