Meeting 27th March 07

Present:
James McDonald
Mark Jovic
Feng-Ming Liu
Rob Rowley

The purpose of this meeting was to collect everything that we have done so far together, and decide what additional methods need to be written. Also, we went through our existing methods to see if any additional functionality was needed. The outcomes of this are listed below:

• Firstly, the menu.jsp method lists all the methods that a user can access. This needs to have some additional functionality that accounts for whether a person viewing the page is either admin staff, a customer, or a non-customer. This functionality needs to be added to the session and the menu.jsp page needs to display different methods according to this session.

  So, a non-customer will be able to:

  • Browse the list of books using all the search book methods
  • Create a new customer account
  • Login as an existing customer

  A customer will be able to:

  • Browse the list of books using all the search book methods
  • Update their personal details
  • View a list of their past orders
  • Logout

  An administrator will be able to:

  • Browse the list of books using all the search book methods
  • Browse the list of customers using all the customer search methods
  • Update their personal details
  • Search for specific orders using search by Order ID
  • Logout

  There will be other methods available to each user type, but these will be accessed from the current page, rather than by the side menu.

• The method header.jsp will just contain the webpage title and will remain constant throughout.
• The method main.jsp will be the title welcome page and will contain no functionality.
• The NewUser.jsp page will be used to create a new customer. It contains some Javascript code to perform some validation checks, but no additional functionality will reside in this page.
• The search.jsp page covers all the search methods that will be used in this program. It requires no extra functionality.
• The book.jsp page returns one book and displays all the details on the page. This method will need additional functionality depending on the user. All users will need the ability to perform a new search. A customer will need the ability to buy the book. An administrator will be able to delete the book from the database, as well as being able to update the book's details.

  MJ to introduce the additional functionality that this method requires

• The bookResult.jsp will list a table of all the books returned from that search. It will need a function that allows each user to select an individual book and then list this book using the book.jsp page.

  FM to introduce the additional functionality that this method requires

• The customer.jsp page will list a customer's details only for an administrator. It will need additional functionality for updating or deleting that customer.

  JM to write this method.

• The NewBook.jsp method will create a new book and be only accessible by an administrator.

  RR to write this method.

• A logout.java method will be required to remove the current user from the session.

  MJ to write this method.

We also discussed which session parameters we will need. At the current time we will only be implementing a User attribute in the session. This will have the values:

• Null - for a non-customer
• Customer - a customer object (cust_id>1000) for the current customer
• Admin - a customer object (cust_id<=1000) for an admin member

N.B The way that we will distinguish between a customer and an administrator is by the customer id value. A value from 1 to 1000 represents an administrator and anything over 1000 represents a customer