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/11 Local Community.md

Go to file
 
 
Cannot retrieve contributors at this time
Local Community Stage 1 Stage 2 Stage 3
42 lines (32 sloc) 2.3 KB
Raw Blame
Open in GitHub Desktop

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.

Stage 1

The core functionality consists of three screens:

  1. The home screen should display all the issues that have been flagged by the users, this should include:
    1. A brief title
    2. The location of the issue
    3. The status of the issue (new, verified, resolved)
  2. There should be a link or button on the home screen to allow a resident to add new issues, this should include:
    1. The brief title
    2. The location of the issue
    3. A detailed, multi-line, formatted description.
    4. An optional photo
  3. If a user selects one of the issues on the home screen they should be taken to am issues detail screen that should display:
    1. The issue details (see last point)
    2. An action link or button that allows a user to take charge of resolving the issue.
    3. The original poster should also see a resolved link or button so they can confirm the issue has been resolved.

Stage 2

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

  1. A verify button that allows a user to verify that this is a valid issue (the button should be hidden from the user who initially posted the issue)
  2. The local council would like to use this app to allow them to prioritise the work the repair teams are scheduled to do:
    1. There should be way for users to be identified as council workers to be able to log in and see a list of the jobs in order of distance from their current location.
    2. Any jobs fixed by this team should be flagged as resolved by the council.

Stage 3

  1. Some of the users will engage with the system. To encourage this you will be implementing gamification elements:
    1. Each time a user reports or verify an issue they get 10 points.
    2. Each time an issue is resolved as fixed by the original reporter, the reporter gets 20 points and the person who fixed the issue gets 50 points.
    3. The home page should display the top 10 users with the highest scorer at the top.
  2. Each time an issue is fixed, an email should be sent to the person who raised the issue, this should include:
    1. The issue name, description and photo.
    2. A link to the details page.
    3. A button to click to resolve the issue.