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/02 Domestic Repairs.md

Go to file
 
 
Cannot retrieve contributors at this time
Domestic Repairs Testing Feature 1 Feature 2 Feature 3 Feature 4 Extras Sensors Media Data
98 lines (62 sloc) 4.75 KB
Raw Blame
Open in GitHub Desktop

Domestic Repairs

You have been asked to develop a website for a company that specialises in the repair of domestic white goods such as washing machines and cookers.

Testing

The system should include the data for at least 10 real issues 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. technician1
  4. technician2

Feature 1

If a user is logged in they should see a New issue link or button on the home screen, which takes them to a screen to report a new issue. They should be prompted for the following information:

  1. The type of appliance (from a fixed list).
  2. A slider where they can select the age of the appliance in years (max age 10).
  3. The appliance manufacturer (from a fixed list).
  4. A short one line summary of the fault (max 100 characters).
  5. A multi-line description of the fault that supports the use of markdown syntax.
  6. A slider where they can state how much they will pay for the work (max £200).

The system should also store the following data without the user needing to enter it:

  1. The location of the user (longitude and latitude).
  2. The date and time the issue was logged.
  3. The username of the person logging the issue.
  4. The status which should be set to unassigned.
  5. The assigned technician field which should be left blank.

To demonstrate this feature and to prove that the form works correctly you will need to show that the data is being persisted correctly, either by running a database query or an API call depending on the platform and technology you are using.

Feature 2

If the user is logged in their home page should list a summary of athe jobs they have added to the system. Only the following information should be displayed:

  1. The type of appliance.
  2. The summary.
  3. The date the issue was added (but not the time).
  4. The status (at this stage it should be set as unassigned).

Feature 3

When a customer is logged in they should see a Work available button or link. This should take them to a screen that shows a summary of every unassigned job in the system ordered by distance from the current location. Each summary should display the following only:

  1. The approximate distance away (in Km).
  2. The Type of appliance.
  3. The summary.
  4. The amount the person is willing to pay.

Feature 4

Each of the summaries on the Work Available screen should have a Details button or link. This should take the user to a screen that displays the full details of the job. There should be three buttons:

  1. Clicking on the Accept button allocates the user to that job. The job status is now assigned and the user added as the assigned technician. The user is returned to the Work Available screen.
  2. Clicking on the Decline button returns the user to the Work Available screen but hides that job.
  3. Clicking on the Cancel button just returns the user to the Work Available Screen.

If the user has allocated themselves any jobs there should be a My jobs link or button on the home screen that displays summaries of the jobs the user has allocated themselves.

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 user adds a job to the system it should capture their location.
  2. When a user adds one or more photos to their job they should be given the option to take this with the built-in camera if available.
  3. When a technician views a list of jobs they should be able see the address of each and roughly how far away the job is from their current location.
  4. The list of qualified technicans should include their location and be placed in order with the nearest tradesman at the top of the list.
  5. The list of qualified technicans should be available as either a list or a map. Clicking on a map pin should show more information and take the user to the technican details page.

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. Axesso
  2. LocationIQ