ACCESSIBILITY VIOLATIONS CMPE 451 SPRING 2012 GROUP 5

ACCESSIBILITY VIOLATIONSCMPE 451 SPRING 2012GROUP 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 • 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.

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

Functinal Requirements

•System Point of view•User Point of view•Guest Point of view

System PoV• 1. The system shall have a user sign up/sign in interface • 1.1. The system shall support an anonymous guest login • 1.2. The system shall have mail address validation • 1.3. The system shall have 'forgotten password' section

• 2. The system shall provide violation types related to different disability types.(i.e. blindness, paralyzedness, deafness) • 2.1. For all types there shall be reference links.

• 3. The system shall provide a map of violations. • 3.1. Different types of violations shall appear in different icons. • 3.2. The status of posts shall appear in different colors. • 3.3. The system shall provide a map search. • 3.4. The system shall filter the violations according to types.

System PoV cont’d• 4. The system shall provide the search functionality for the

existing violation reports. • 4.1. The system shall provide location based search functionality

for the existing violation reports • 4.2. The system shall provide disability type based search

functionality for the existing violation reports • 4.3 The system shall provide friendly locations based search

functionality for the existing violation reports • 5. There shall be an administrator who checks entries for bad-

intended reports. • 5.1. The abusers should be blocked. • 5.2. They have the right to give authorization to

experienced/most liked users

System PoV cont’d• 6. The system shall provide weekly summary reports for

municipality and publicity. • 7. For blind users, the system shall provide a special interface. • 8. The system shall provide accessible directions for blind

people. • 8.1. Directions shall be given from the perspective of visually

impaired people. (As mentioned here) • 8.2. This shall be realised via context-aware system. (As

mentioned here) • 9. The system shall provide indoor violations in a building. • 9.1. Indoor location shall not be provided

User PoV• 1. The users shall submit a report of a violation. • 1. The users shall specify the violation's type. • 2. The users shall specify the violation's location. • 3. The users shall specify the violation's description. • 4 The user shall specify the status of the violation.(i.e. detected,

still same, in progress, fixed) • 4.1. The default status of the violation shall be 'detected'.

• 5. The users shall specify the violation's urgency. • 6. The users should specify the violation's media.

• 6.1. The user should be able to post videos/images of the violations.

• 2. The users shall submit disabled-friendly places • 2.1. The users shall specify the type. • 2.2. The users shall specify the location. • 2.3. The users shall specify the description.

User PoV cont’d• 3. The users shall comment on other reports. • 3.1. The users should be able to see and edit their comments. • 3.2. The system shall provide +1,-1 and a "Report This" button to comments.

• 3.2.1. The system should hide the comments with rate below -5. • 3.3. The system shall provide +1,-1 and a "Report This" button to the reports.

• 4. The users shall have their own personal pages. • 4.1. The users shall be able to see and edit their previous reports.

• 4.1.1. The users shall be able to update the status of the violations.

• 5. The users can send a change status request to administration for other violations not posted by theirselves.

• 6. Active users should get a right to change status of the other violations to reduce the work of administrator.

• 7. User shall search for a destination and get the right directions. • 7.1. Also for blind users, another detailed direction mechanism should be

designed.(Look at System Point of View)

Guest PoV

• 1. The guests shall see other violations. • 1. The guests shall not be able to write reports.

• 2. The guests shall comment on other reports. • 2.1. The guests should not be able to change their own

comments

Non-Functional Requirements

• Product Requirements• Efficiency R.• Usability & Accessibility R.• Security R.• Dependability R.• Scability R.

• External Requirements• Legislative R.• Ethical R.

Product Requirements

• 1. Efficiency Requirements • 1.Pages shall be loaded in max 5 sec. • 2.The system shall be recoverable in case of a system shutdown

within 24 hours.

• 2. Usability and Accessibility Requirements • 2.1. The system shall provide a user friendly, easy to use

interface. • 2.2. The system shall have a tutorial to guide people new to the

system.

• 3. Security Requirements • 3.1. The system shall keep personal data in a secure manner.

• 3.1.1. User passwords shall be hashed in the database

Product Requirements cont’d

• 4. Dependability Requirements • 4.1. The web site of the system shall be compatible with major

browsers(i.e. Firefox, Google Chrome) and Android smart phones. • 4.2. The web page shall conform the W3C standards and must

avoid usage of non-standard technologies.

• 5. Scalability Requirements • 5.1. The web page shall be designed to handle hundreds of

thousands of user records and corresponding data such as photos, documents and other media.

External Requirements

• 1. Legislative Requirements • 1. The web page content shall be fully compliant

with web site laws. • 2. Ethical Requirements • 2.1. Personal data shall never be given to third

party companies without user confirmation.

Project Planning

• OpenProj• Time Estimation• Milestones•Core / GUI Seperation in most of tasks

Gantt Charts

Thank you for your attention!

Any Questions??