Terrace Shop

Developer Problem

Client Problem

User Problem

Data Environment

User Interface

Requirements

St. Joseph's College Gregory Terrace

Constraints

Three User Types

No way to currently use Terrace Shop outside of the physical shop, reducing efficiency and effectiveness

Shop Attendants

Administrators

Customer

Anonymous

Logged In

Can browse products anonymously, look at prices, view sizes and product availability

Able to browse products and view prices, sizes and product availability

Able to lodge purchase orders for specific products, quantities and sizes

Purchases must be picked up and paid for at physical shop, but payment method and amount are entered and stored

Manage payments and physical distribution of sales

Manage, edit and finalise order information

Manage orders and compile complete list and database of all orders placed

Manage inventory, change stock levels and add/remove/edit product information

Generate sales reports, and access all relevant information needed for sales reports

Manage user information, such as customer and Attendant information. Can change usertype to Attendant or customer

Time Constraints: Up to 4 weeks

Accessibility

Style Guidelines

Logo and Images

Register, Login, Cart, Order pages

Shop managers are able to access order lists to ensure orders are fulfilled

Each usertype should be able to access their required functions easily, effectively and with accessibility functions if needed

Follows Usability Principles

Matches Style guidelines given by client (Gregory Terrace)

Login / Register Pages

Order Pages

Once logged in, parents can place orders and have their students pick up the order from the Terrace shop and pay.

Parents can create accounts and link student numbers to this account to allow for storage of student order data

Orders can be placed under account numbers and receipts are generated and can be turned into a order list to be given to the Terrace Shop. This can be used

Store Data

User data must be stored

Order Data

All personal data must be stored safely and securely, all data transactions must use encryption to ensure the user's data is safe.

Username, Email, Password, Student Number, Name, Phone Number, Payment Methods

Order data must be stored securely to ensure all users have their personal information safely stored

Order ID, User ID, Product ID, Quantity, Total price

Product information, Stock Levels, Restock Levels

Coding Environment

SQL using multiple tables to store user information, order information and product information.

Send confirmation emails using code for registration

Administrators must be able to add new events, change prior events, change student and official details, and manage data using SQL

Access and view current order information using pre-programmed algorithms that present an easily interpretable order