Accessibility Violations

Group 6

Description

• Everyone naturally has right of accessibility to the places which all people can access. However, some people with disabilities cannot easily access whole places. To overcome this issue and make them use their natural right, we can report violations. By reporting violations we both can aware related authorities and make life of disabled people much more easier. Hence, the aim of this project is maintaining natural rights of people.

• Violation: An action that breaks or acts against something, especially a law, agreement, principle or something that should be treated with respect.

• User: Users are all people who will receive information from this application and contribute data to this application. There should be three types of users: Guest, Member and Admin. These user groups should have different permissions.

Similar Projects

• -Road Hero is an application focusing on the traffic violations. Anyone can report a dangerous driver just by saying the license plate number and the driver will be "flagged". In this application, users can track every flag on a map, search for a license plate and see its driver record. Submitting photos and sharing messages are also provided. It is very close to our project. It also uses voice-tagging which can be helpful in our project to assist the blind people.

• -Fix It Plano is dealing with watering violations via mobile application and website interface. The residents of the city can report watering violations, along with a photo of the violation. It is similar to Road Hero. The good thing is people can directly report the violations to the local government.

Requirements•Functional

- Behavior of system- Users point of view

•Nonfunctional

Functional Requirements Behavior of system

1. System shall provide sign-up and sign-in functionalities.

  1.1. There shall be control for mail verification.

  1.2. There shall be e-mail service for forgotten password.

2. System shall provide search property for reports.

  2.1. Search shall be done according to type and location.

3. System shall provide a map of violations and friendly locations

    3.1. Friendly locations should be shown on map as green pin.

    3.2. Violations should be shown on map as red pin.

    3.3. System shall provide search property for map.

   3.4. Map should be filtered according to disabilities.

Functional Requirements Behavior of system

4. There should be a “how it works” section which includes information about how to use the application.4.1. Help messages for users should appear based on the user’s request.

5. Every registered user should have a score.5.1. The score of user should be increased in every correct report.

5.2. The score of user should be decreased in every false report.

6. Wrong reports should be able to be reportable.6.1. Admin shall warn the users who reports wrong violation via e-mail.

6.2. After 5 wrong reports, admin should ban the user who reports wrong violation.

Functional Requirements Behavior of system

7. System should provide a notification system.7.1. User should be able to subscribe a violation. Notification system should inform users about changing status of violation in the list via e-mail.

  7.2. User should be able to subscribe a location. Notification system should inform users about a new report in this location via e-mail.

8. Admin shall periodically report permanent violations to related authorities.

Functional Requirements Users point of view

1. Users shall be able to report a violation. 1.1. There shall be a map where violation is tagged.

1.2. User shall be able to add a location for violation.

1.3. Users shall be able to add a description in detail to their report.

1.3.1. Users shall be able to add status which indicates the current situation of the violation like “in progress” or “completed”.

1.4. Users shall be able to upload images and videos.

1.5. Users should be able to provide voice recordings of the violations for blind people.

1.6. The date and the time of violations shall be reported also in terms of reliability. (For instance, a new report will be more reliable than an older one.)

1.7. Violation type shall be chosen. (i.e; blind, wheelchair, friendly location, etc)

Functional Requirements Users point of view

2. Users shall view a violation.2.1. Users shall be able to search a particular violation via entering any of type and location.

2.2. Users shall be able to see the violations in the order sorted by date or rate.

2.3. Users shall be able to see the summary of all violations.

2.4. Users should be able to see violations on map and filter according to their disability.

3. Users shall be able to comment on violations.

Functional Requirements Users point of view

4. Users should be able to rate violations up/down to increase/decrease the credibility of that report.

5. Users should edit a violation report.5.1. Users should be able to update state of violation (nothing, changed-in, progress-fixed) to make application up-to-date.

6. Guest users shall be able to view, comment on and rate up/down a violation report.

Non-Functional Requirements

1. Usability1.1. Our application shall be user friendly which means appropriate to ISO/TR 16982:2002 and ISO 9241 standards.

1.2. Web pages shall be simple and complexities shall be avoided.

1.3. The language of application shall be understandable and should not cause ambiguity and perfectly appropriate to the grammar of used language.

1.4. Interface of application shall be simple and easy to use.

Non-Functional Requirements

2. Security and reliability2.1. System shall be able to detect and deal with users who abuse the system.

3.2. Users private information shall be protected.

3. Availability3.1. The webpage shall support with internet explorer, google chrome, mozilla firefox.

3.2. The application shall support mobile interaction in android.

4. Fast access4.1. User shall be able to access violation reports in max 4-5 sec.

Project Plan