1 / 15

ACCESSIBILITY VIOLATIONS

ACCESSIBILITY VIOLATIONS. CMPE 352 SPRING 2012 GROUP 5. ACCESSIBILITY VIOLATIONS. Our aim is to implement a violation tracking application with the following properties:. Reporting a violation (type, location, description, media) Report on disabled friendly locations

tekli
Download Presentation

ACCESSIBILITY VIOLATIONS

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. ACCESSIBILITY VIOLATIONS CMPE 352 SPRING 2012 GROUP 5

  2. ACCESSIBILITY VIOLATIONS

  3. Our aim is to implement a violation tracking application with the following properties: • Reporting a violation (type, location, description, media) • Report on disabled friendly locations • Update status of a violation (fixed, in progress, still same, ...) • Search for a particular violation or type of violations • Summary Reports on violations (summary of violations: types of violations and their status). Someone from the municipality could be interested in seeing the big picture of violations.

  4. Assist disabled with useful information so they can avoid troubled areas • Violation reports must support images, videos, and text • Comments (uses should be able to comment on violations) • Discourage cheating (users who abuse the system should be detected and dealt with) • User tagging • Allow volunteers to vocalize reports (for the blind) • Resource area: tips, hints, people and organizations related to the area. • Show violations on Map by showing all open violations, closed violations, by disability violations (those that impact the blind) etc.

  5. Functinal Requirements • System Point of view • User Point of view • Guest Point of view

  6. System PoV • The system shall have a user sign up/sign in interface • The system shall support an anonymous guest login • The system shall have mail address validation • The system shall have 'forgotten password' section • The system shall provide violation types related to different disability types.(i.e. blindness, paralyzedness, deafness) • For all types there shall be reference links. • The system shall provide a map of violations. • Different types of violations shall appear in different icons. • The status of posts shall appear in different colors. • The system shall provide a map search. • The system shall filter the violations according to types.

  7. System PoV cont’d • The system shall provide the search functionality for the existing violation reports. • There shall be an administrator who checks entries for bad-intended reports. • The abusers should be blocked. • The system shall provide weekly summary reports for municipality and publicity. • For blind users, the system shall have a special user interface. • Text-to-speech and volunteers shall be allowed.

  8. User PoV • The users shall submit a report of a violation. • The users shall specify the violation's type. • The users shall specify the violation's location. • The users shall specify the violation's description. • The user shall specify the status of the violation.(i.e. detected, still same, in progress, fixed) • The default status of the violation shall be 'detected'. • The users shall specify the violation's urgency. • The users should specify the violation's media. • The user should be able to post videos/images of the violations. • The users shall submit disabled-friendly places • The users shall specify the type. • The users shall specify the location. • The users shall specify the description.

  9. User PoV cont’d • The users shall comment on other reports. • The users should be able to see and edit their comments. • The system shall provide +1,-1 and a report button to comments. • The system should hide the comments with rate below -5. • The users shall have their own personal pages. • The users shall be able to see and edit their previous reports. • The users shall be able to update the status of the violations.

  10. Guest PoV • The guests shall see other violations. • The guests shall not be able to write reports. • The guests shall comment on other reports. • The guests should not be able to change their own comments.

  11. Non-Functional Requirements • Product Requirements • Efficiency R. • Usability & Accessibility R. • Security R. • Dependability R. • Scability R. • External Requirements • Legislative R. • Ethical R.

  12. Product Requirements • Efficiency Requirements • Pages shall be loaded in max 10 sec. • The system shall be quickly recoverable in case of a system shutdown. • Usability and Accessibility Requirements • The system shall provide a user friendly, easy to use interface. • The system shall have a tutorial to guide people new to the system. • Security Requirements • The system shall keep personal data in a secure manner.

  13. Product Requirements cont’d • Dependability Requirements • The web site of the system shall be compatible with major browsers and Android smart phones. • The web page shall conform the W3C standards and must avoid usage of non-standard technologies. • Scalability Requirements • The web page shall be designed to handle hundreds of thousands of user records and corresponding data such as photos, documents and other media.

  14. External Requirements • Legislative Requirements • The web page content shall be fully compliant with laws. • Ethical Requirements • Personal data shall never be given to third party companies without user confirmation.

  15. Thank you for your attention! Any Questions??

More Related