Case Study/Background Info Part 2

Initial analysis reveals that System Actors in SGD Online Tour Booking System include:

Online Customer

Company Staff

Initial analysis also reveals the following use case scenarios

Customer scenarios:

Search items/products and place orders

A customer visits the SGD web site; he/she can then search for an item based on several criteria (e.g. category, price etc.). If suitable result(s) found, the customer could select an item and be provided with details of the item including category, price, availability, descriptions, photos etc.

If the item is available for order, the total cost of the item is supplied to the customer, and the customer confirms the order for which an order reference number is provided. However, if there are insufficient items available for the order the customer is asked to make another search.

Staff scenarios:

Add items

SGD staff adds details of a new items. Items details include name, description, price, quantity, item id etc.

Remove items

SGD staff can remove an item i.e. make it unavailable for order.

Description of problem to be solved

Capture all business requirements using UML and ER diagrams. Design a logical front end interface which would connect to a relational database through online application.

Deliverables

Your front-end implementation should follow standards specified by World Wide Web Consortium (W3C) and design diagrams (Use case, ER and storyboard diagrams). Please make sure your documentation includes screenshots from your website. (LO 2a).

Any dynamic content in application should be pulled out from a database in real time using optimal queries. Your application is expected to implement select, insert, update as well as any read-only operations. (LO 2b, 2c).

Make sure you include evidence of server side programming and back-end database manipulation. (PHP, MySQL)