Skip to content
Permalink
master
Switch branches/tags

Name already in use

A tag already exists with the provided branch name. Many Git commands accept both tag and branch names, so creating this branch may cause unexpected behavior. Are you sure you want to create this branch?

projects/03 Bookshop.md

Go to file
 
 
Cannot retrieve contributors at this time
Book Shop Testing Stage 1 Part 1 Part 2 Part 3 Stage 2 Stage 3 Extras Sensors Media Data
109 lines (69 sloc) 4.61 KB
Raw Blame
Open in GitHub Desktop

Book Shop

Build a website for an online company selling books.

Testing

The system should include the data for at least 10 real books and include the correct details for each. The customer details should also be valid.

You are required to create the following accounts to allow the system to be tested. All accounts should have the password p455w0rd:

  1. customer1
  2. customer2
  3. admin (only required for stage 3 functionality).

Stage 1

The core functionality consists of three screens.

Part 1

A home page that should be visible without logging in. This should display all the books that are for sale. For each book the following should be shown:

  1. The name of the book
  2. The name of the author
  3. A thumbnail image
  4. A price

Part 2

Clicking on either the thumbnail or name should load a product details page that shows:

  1. The name of the book
  2. A full resolution image
  3. The price
  4. A detailed, multi-line, formatted description taken from the endleaf.
  5. The EAN (barcode) number.

If the customer is logged in they should also see a link or button to add the item to their shopping cart.

Part 3

If the customer is logged in they should see a link or button taking them to their shopping cart.

This should list all the items added to the cart plus a total and a checkout link or button.

There should be a remove link or button next to each item which should remove the item from the cart and recalculate the total.

Stage 2

The intermediate tasks require you to make changes to the functionality:

  1. The product details page should allow the customer to refine their choice by choosing from hardback/paperback and new/used.
    1. The options available will vary with availability.
    2. As they switch between these options the price should automatically change.
    3. When the customised item is added to the cart this should list the options selected.
  2. There should be a Make Payment link or button in the shopping cart which takes the customer to a (fake) payment screen. This should include:
    1. Overall weight.
    2. Shipping cost (based on weight).
    3. Overall cost including base, vat and total.
  3. Once the order is complete (the fake payment has been approved), the customer should receive a nicely formatted email with their order details.

Stage 3

  1. There should be one account flagged up as admin. They log in using the same login page but will see additional functionality:
    1. On the home screen there will be a link or button to add new books, this will take them to a screen where they can add the product information (see the basic task for the fields).
    2. Next to each of the existing products there should be a link or button to allow the admin to edit the product details.
    3. For each product, the admin should be able to add and edit options including price for each of the four option combinations.
  2. The product details page should display multiple images of the product:
    1. The admin user needs to be able to upload more than one image for each product (no maximum limit).
    2. the user should see thumbnails of all the images.
    3. Clicking on an image should display it full-size.
    4. There should only be one large image displayed at one time on the page.

Extras

In some assignment briefs you are given marks for the appropriate use of media and using sensors built into the user's device.

Sensors

In some assignment briefs you are given marks for the appropriate use of sensors and sensor data. You should be implementing:

  1. When a custotomer places an order the system should automatically determine which country they are ordering from and use this to calculate the delivery cost.
  2. When the customer checks out the order, the address field(s) should be prefilled based on their current location but they should be able to correct this.
  3. The user should be able to use their device camera (if available) to scan a barcode which either adds the book to the cart or flags it up as invalid.

Media

In the requirements listed above you need to provide the user with the ability to upload photos. For the extra media marks you will need to expand this by:

  1. Providing the user with the choice of uploading photos, video clips or audio clips.
  2. Giving users the option to directly capture images, audio and video clips using the built-in camera and/or microphone if available.

Data

There are lots of online RESTful APIs you can make use of when developing this system. You should consider:

  1. The Google Books API
  2. LocationIQ