Skip to content
Permalink
2b3e77454f
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/11 Local Community.md

Go to file
 
 
Cannot retrieve contributors at this time
Local Community Testing Feature 1 Feature 2 Feature 3 Feature 4 Extras Sensors Media Data
95 lines (60 sloc) 4.33 KB
Raw Blame

Local Community

A local council wants to build a community hub to allow local residents to both raise issues and proactively help to solve them.

Testing

The system should include the data for at least 10 valid issues.

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

  1. user1
  2. user2
  3. council

Feature 1

Trying to access the homepage should redirect to the login page if the user is not logged in. The homepage should include an Add issue link or button that sends them to a screen with a form requesting the details of the issue they are reporting. It should request the following information:

  1. A short issue name.
  2. A description of the location.
  3. A detailed, multi-line description that support the use of markdown formatting.
  4. An optional photo uploaded from their computer.

In addition to the information added by the user, the following should be captured automatically and stored in the database:

  1. The username of the person reporting the issue.
  2. The current date and time.
  3. The current status (set to new)

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

The home screen should display all the issues that have been flagged by all the users, this should include:

  1. The issue name.
  2. The location description.
  3. The date the issue was raised (but not the time).

Feature 3

If a logged-in user selects one of the issues on the home screen they should be taken to an Issue screen that should display:

  1. The issue name.
  2. The description of the location.
  3. The multi-line description with markdown formatting replaced with html.
  4. The photo (if supplied).
  5. The status of the issue.
  6. The username of the person raising the issue.
  7. The date the issue was raised (but not the time).

Feature 4

This feature requires you to make changes to the functionality to monitor the status of the issues:

  1. When an issue is created you should automatically capture the current location and store this in the database as longitude and latitude.
  2. The homescreen should capture the device current location and display the approximate distance to each if the issues in metres.
  3. if a user views someone else's issue they should see a button labelled Flag as fixed. This should set the issue status to addressed.
  4. If a user views one of the issues they raised and it was flagged as addressed they should see a button labelled Fix confirmed. Clicking this sets the status to fixed.
  5. The homescreen should only display new issues.
  6. The homescreen should have a button called My issues. This takes the user to a screen where only their own issues are listed. The list should contains all their issues whether fixed or not and the status should be displayed against each.

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 an issue is added, instead of the location being added manually this should be based on the user's current location.
  2. When the user is prompted to upload a photo they should be given the option of using the device camera (if available).
  3. The home screen should display a map showing the locations of all the unresolved issues:
    1. Clicking on a pin should show a summary bubble showing the brief title and the person who flagged it.
    2. Clicking on this should send the viewer to the issues detail screen.

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