Download presentation
Presentation is loading. Please wait.
Published bySherman Bradford Modified over 8 years ago
1
HOPE Helping Our People Easily Phase I - Interim Team KRAFT
2
Vision We aim to develop a mobile, inexpensive, user-friendly application that mitigates communication barriers for the communication disabled while being aesthetically pleasing and discrete in public use.
3
Agenda Introduction Process & Team Organization Requirements Engineering Traceability Prototype To be done Our Strengths
4
Introduction The Problem Elderly people tend to have hearing, speech, vision, and memory disabilities o Communication difficulties o Lack of independence frustration and seclusion Who’s Affected? o People with hearing, speech, vision, and memory disabilities o Assistive persons o Family members o …
5
Introduction Traditional Aids o Costly, bulky, and difficult to use Our Solution o Focus on user needs o Simple interface and navigation o Balanced and unique set of features o Mobile application for Android
6
Stakeholders Users o Elderly o Assistive person Customer Kraft o Requirements Engineers o Project/Product Manager o Developers o QA & Testing
7
Our Process Software Development Process – Customized Spiral Model with two iterations – 1.x and 2.x – Interleaving, Iterative (Agile) and Incremental – Fluid Teams (RE, Arch + Implementation, Testing, QA & Documentation) IterationActivities Phase I Assign members to fluid teams Problem + Domain analysis Drafting WRS + Surveys + User Manual Creating Prototype Phase II Shuffling members of fluid teams Improved understanding + updating WRS Development Testing
8
Our Process Key Features: (Re)planning Role Play WBS – Work Breakdown Structure SVN SDM-Systematic Design and Management Issue(s) Identification Issue(s) Resolution Tradeoff Analysis
9
Our Process
10
Domain Requirement: Source exerpt – A1: As people get older, they tend to experience difficulties with hearing, speaking, vision and memory loss, and muscle weakness. – A3 : go beyond the current realm of AAC to identify all the physical and mental disorders – A6 : expands from the initial definition of AAC which is to deal with speech disorder, and take consideration the speech, hearing, memory and/or vision impairment up to varying degrees. – A8 : In the application domain, the communication typically consists of: An elderly with speech, hearing, vision and/or memory loss.
11
Domain Requirement: Source exerpt – A10: An assistive person is one that is either a disabled person or a non- disabled person with whom the user wants to communicate. – A12: In a typical scenario, people uses visual aids like pictures and icons and text and/or speech to communicate a message to the elderly having hearing loss and a weak memory – A21: The purpose of HOPE is to provide a platform for helping the elderly, the disabled – having unclear speech, hearing loss, weak vision and/or memory loss
12
Domain Requirement: Issue Issue : No clear definition of type of “disabilities” to tackle Options How to select disabilities to tackle – O1. base on project deadlines – O2. base on technical feasibility – O3. base on the similarity of disorders. – O4. base on the most frequent disabilities the elderly population suffers from. Vision Hearing Speech Muscular Memory
13
Domain Requirement DR1 The system will be used by people that suffer from communication disabilities who have been alphabetized. The disabilities that the system addresses are defined below: hearing disabilities speech disabilities memory disabilities vision disabilities
14
FR Source excerpt from A19: “Just like the elderly user, the system should be easily usable by the assistive person, e.g. by providing a good search interface through which that person need not know the entire system and can bring up any part by just visiting the search page. “ Issue 9: What defines a “good” search interface? Options O1. “Google-like” search O2. Search with auto-completion O3. Search by complete words O4. Search by incomplete words O5. Search stored sentences O6. Search using voice recognition based on Google API
15
FR Choice and Rationale O3 O5 O6
16
FR: I O FR 2: The system shall provide a search interface to allow users to retrieve: Favorite sentences Built-in common greetings Recently generated sentences Individual vocabulary items FR 2.1 The search feature shall be reachable from anywhere in the system. FR 2.2 The search input shall be converted from the recognized voice of the user. FR 2.3 Search results shall be returned in a scrollable list format containing an image and a text description of a sentence or vocabulary item for search result. FR 2.4 When the user clicks on a search result item, the system shall speak the item description out loud. I: a vocal input O: a list of search results showing image and description
17
NFR Source excerpt : “The system should be quickly understandable (the learning time should be very low) and very easy to use “ Issue I25: The system should be quickly understandable Description: What is meant by understandable ? Understandable is Ambiguous here. Options: O1. Text is easy to read O2. Low learning curve O3. Visual aids should have a minimal specified resolution (e.g., not blurry) O4. The user should be able to learn how to use the application in 2 weeks, using it 3 hours a day. Choice: O1, O2, O3.
18
Issue with the choices Issue I25.1: Text is easy to read. Description: What functional features shall realize “easy to read”. Options: O1. Choose contrasting colors O2. Choose a large icon size O3. Choose a large text size Choice: O1,O2,O3
19
Issue with the choices Issue I25.2: Low learning curve. Description: What functional features shall realize “Low learning curve”. Options: O1. One touch help shortcut O2. User manual written in non-technical language O3. Icons with descriptive text O4. Provide technical support O5. Interactive tutorial built-in the application Choice: O1,O2,O3
20
To be done Expand upon our issues and our rationale Finalize prototype concerns Prioritizing our requirements Update our domain model Verify our traceability matrix Complete product user manual
21
Why chose us? Dedicated to addressing user needs Focused on delivering the best product User-friendly Unique features Market Insight Consistently working with our clients Always considering new approaches Committed to the quality of our process
Similar presentations
© 2025 SlidePlayer.com. Inc.
All rights reserved.