Helping Old People Easy Software Requirements …chung/CS4351/...Helping Old People Easy Software...

Helping Old People Easy

Software Requirements Analysis

Gary Mirsky ([email protected])Tucker Smith ([email protected])

Osama Alsaleh ([email protected])Tom Langford ([email protected])Ben Wright ([email protected])

Cliff Halasz ([email protected])Arlen Aghakians ([email protected])

Project Homepage:http://home-greyhatent.homelinux.org/redmine/projects/req-eng

Project Zip File:http://utdallas.edu/∼tss063000/req eng/project.zip

November 30, 2010

Version 1.22

1

Contents

1 Revision History 3

2 INTRODUCTION 42.1 Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42.2 Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42.3 Mission Statement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42.4 Process of Requirement Development . . . . . . . . . . . . . . . . . . . . . . . . . . 42.5 Requirement Analysis Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52.6 Superiority of this Product . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

3 OVERALL DESCRIPTION 63.1 Product Perspective . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63.2 Product Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63.3 User Classes and Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63.4 Operating Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73.5 Design and Implementation Constraints . . . . . . . . . . . . . . . . . . . . . . . . 73.6 User Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73.7 Assumptions and Dependencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73.8 Acceptable Change . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

4 NONFUNCTIONAL REQUIREMENTS 84.1 Memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84.2 Medical . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94.3 Softgoal Interdependency Graphs . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

5 PENDING REQUIREMENTS 135.1 Memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145.2 Medical . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

6 COMPLETE REQUIREMENTS 176.1 Medical . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186.2 Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

7 REQUIREMENT BACKLOG 257.1 Vision . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267.2 Speech and Hearing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 287.3 Memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 317.4 Medical . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 327.5 Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 337.6 Family/User Web Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 387.7 Easy-To-Use Phone Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

8 PROBLEMS 46

9 GOALS 49

10 TRACEABILITY 51

11 REQUIREMENTS ANALYSIS 5811.1 Vision . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5911.2 Speech and Hearing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6311.3 Memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6711.4 Medical . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

2

11.5 Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9211.6 Family/User Web Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10211.7 Easy-To-Use Phone Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110

3

1 Revision History

Ver Date Author Comment1.22 2010-11-30 tss063000 Fixed another, unrelated typo1.21 2010-11-30 tss063000 Fixed typo1.20 2010-11-30 tss063000 Added SIGs1.19 2010-11-11 tss063000 Added Arlens nifty logo. Fixed the acceptable change incident.1.18 2010-11-11 tss063000 Reorganized to show what is done, and what is left to be done1.17 2010-11-11 tss063000 Added traceability graphs1.16 2010-11-11 tss063000 Added traceability graphs - attempt 11.15 2010-10-21 tss063000 First generation from new requirement system.1.14 2010-10-05 tss063000 Added watermark.1.13 2010-10-05 tss063000 Added a missing split in medical.1.12 2010-10-04 tss063000 Changed title.1.11 2010-10-04 tss063000 Expanded scheduler. Added some of arlen’s requirements to hear-

ing/speech.1.10 2010-09-30 tss063000 Filled in some Speech Requirements and some Memory Require-

ments.1.9 2010-09-30 tss063000 Added Osama’s Requirements to Vision. Added some NFR’s to

Vision.1.8 2010-09-30 tss063000 Added Cliff’s requirements to Web Service. Split some require-

ments in that section.1.7 2010-09-30 tss063000 Added some NFR’s to Medical. Imported Gary’s Requirements

for Location. Filled out Location some more.1.6 2010-09-30 tss063000 Medical Aide section tentatively done for phase I presentation.1.5 2010-09-29 tss063000 Finished splitting requirements in the medical section.1.4 2010-09-29 tss063000 Started splitting requirements.1.3 2010-09-29 tss063000 Caused automatic system to rebuild document1.2 2010-09-29 tss063000 Chose alternatives and updated requirements for Medical Aide

Feature.1.1 2010-09-29 tss063000 Initial Commit. Filled out parts of the Medical Aide Section.

4

2 INTRODUCTION

2.1 Purpose

This document is automatically generated from an SQL database of requirement data. It representsthe current understanding and continued evolution of our requirements. It is essentially a snapshotof our current development status. Additionally, this document describes our development processand methodology.

2.2 Format

This document is composed of 5 major sections. Besides this introduction, there is the Require-ments Specification, the Problem section, the Goal section, and the Requirements Analysis. TheRequirements Specification lays out the current understanding of the problems and requirementsinvolved with this project. The Problem and Goal sections lay out the specific problems and goalspresent in the domain. The Requirements Analysis lays out a log of every evolution of everyrequirement.

2.3 Mission Statement

To help as many old people as effectively as possible and as soon as possible, prioritized by need.

2.4 Process of Requirement Development

The first stage of our requirement gathering process is to identify problems in the domain. Wethen formulate a goal to remove that problem. With a goal and a problem, we formulate an initial‘soft-requirement’ that embodies an approach to solving the problem in accordance with the goal.This initial requirement is intended to be vague and bloated. From this initial requirement, wesystematically identify issues, formulate alternatives, identify the trade-offs associated with thosealternatives, and integrate the best alternatives back into the original requirement. This continuesuntil the requirement becomes arbitrarily bloated, and is then split into smaller requirements.These are then each iteratively improved and further split until we arrive at individual requirementsthat can be tested by a single test case, and are believed to be totally correct.

One aspect of our process involves prioritization of requirements. In accordance with ourmission statement, requirements that help people the most are given precedence. Each requirementis given a priority number ranging from 0 to 10, with 0 being a worthless requirement, and 10being a requirement that absolutely must be completed before any other. Requirement prioritiesmay change during the evolution of a requirement as more information is gained. Because of thisprioritization, many low priority requirements are not iterated beyond the first couple improvementiterations as other, more important, requirements take precedence. These ‘stub’ requirements will,of course, be returned to when the higher priority requirements reach maturity.

Another aspect of our process is the division of requirements into categorical ‘features’ whichare each designed for a specific subset of users. At this point in time, we are focusing almostentirely on the features of Memory and Medical, as we have prioritized the requirements withinthem as greatest.

5

2.5 Requirement Analysis Structure

The requirements analysis is a log of every requirement through every iteration of its lifetime. Itfollow a formal structure representing an acyclic directed graph. This structure can be definedwith the following ad hoc notation:

Feature → Requirement∗

Requirement → Requirement+|Issue|εIssue → Alternative+

Issue → RequirementAlternative → Requirement|ε

Let x→ y be read as “an x must have a y as a child”.Let x∗ be read as “any number of x’s”, and x+ be read as “at least one x”.Let x|y be read as “either x or y, but not both”.Let x→ ε mean that x can have no children.

Thus the first rule may be read as “Every feature may have any number of Requirements aschildren”. The second is “A requirement either links to sub-requirements, an issue, or nothing.But no combination thereof.” The third is “An issue must link to at least one alternative.” Thefourth, “An issue must have a new requirement as a child.” And the last, “Alternatives are eitherlinked to a requirement or nothing.”

2.6 Superiority of this Product

We believe that this product is superior to its competitors due to the fact that it has both breadthand depth. From the beginning, we attempted to include every feasible requirement that we couldidentify, but we then prioritized, and sought depth in our requirements. This gave us the highestprobability of identifing the most important areas to focus on.

Additionally, we have put far more work into our development infrastructure than other team.We have developed a web-based entry system that allows us to enter requirements into our centralrequirement database from anywhere. This system not only enforces the requirement structuredescribed in the previous section, but automatically generates documents such as this one, totallypreventing document inconsistencies. This serves to not only improve our overall productivity, butalso the quality of our finished product.

6

3 OVERALL DESCRIPTION

3.1 Product Perspective

The product described here is a series of several integral components that shall form a singleapplication. Each component will correspond to a single feature. The first phases of the projectwill focus on the components with highest priority.

3.2 Product Features

The Helping Old People Easywill aid the user in the domains of vision, speech, memory, location,and hearing. It shall also provide a web interface for the user or the user’s family/caretakers toconfigure the application with minimal difficulty.

3.3 User Classes and Characteristics

There are two major user classes that will interact with this application: the elderly, and thosewho care for the elderly. Of the elderly, there are four subcategories: the visually impaired, thespeech impaired, the memory impaired, and the infirm.

The visually impaired may have difficulty identifying their environment by themselves. Thecauses of the impairment can range from simple physical damage to the eyes to neurological damage.Our ability to help these users is limited, and many other applications already exist to providemany types of aid that we simply cannot do through the user’s phone. Additionally, many of thetechnologies necessary to help these users on any meaningful level do not exist yet, or are in theirinfancy. As such, we consider these users, and the features associated with them to be of the lowestrelative priority in comparison to our other potential users.

The speech impaired have difficulty communicating with others. The causes can range fromlaryngitis to neurological damage. We have a medium to high potential to help these users,although other products do already exist which can aid them in communicating. We considerthem a medium priority.

The memory impaired, unsurprisingly, have difficulty remembering things, places, and people.The causes of this impairment can range from simple forgetfulness, to dementia, to passing fuguestates. We have a very high potential to help these users. Few other products can be so close to theuser at all times, and be able to provide assistance when the user becomes forgetful. Additionally,the technology involved is well within our grasp. We consider these users and the features associatedwith them to be of a very high priority.

The infirm have medical issues that must be monitored and reported to medical professionals,require medication, and may result in situations where the user is incapacitated or at serious riskof death. Depending on the individual, we have either a high potential to help these users or verylittle potential. There can be significant overlap between this group and all other groups. Many ofthe medical issues that require monitoring are beyond the scope of this project, since they wouldrequire medical monitoring devices that are beyond the capabilities of any phone. However, ourapplication still resides an important niche for these users, since few other products are so oftenclose to the user, and can provide near instant communication to emergency services. As such, weconsider these users and the features that aid them to be of a high relative priority.

An important thing to note is that the elderly do not typically buy phones, nor do they generallyinstall applications on them. These responsibilities typically fall to the people who are close tothe elderly (i.e. their children, grandchildren, caretakers, etc..). These people generally buy thephones for the purpose of checking up on the elderly and ensuring they are in good health whenthey cannot physically visit the person themselves. As such, our application must appeal to thisgroup of users, or it will never make it to the elderly in the first place. If these users do not find ourapplication valuable in the task of caring for their loved ones, they will not give it to the elderly.Thus, these users are our highest priority.

7

3.4 Operating Environment

The application will run on Windows Phone 7, and is intended for touch-screen smart phones.

3.5 Design and Implementation Constraints

The application must run on the resource constraints of a typical Windows Phone 7 capable smartphone.

3.6 User Documentation

Users of the HOPE application will be provided documentation in an electronic format. Fromthe application users may access the on-board help of the systems major functions. Additionalhelp including in depth topics can be accessed via HTTP through the on-board help. If using thesystems Family Web Interface a full help library will be available on the website.

3.7 Assumptions and Dependencies

The HOPE application is intended to be used on a Windows 7 based Smart phone. The windowsSmart phone must have Internet Access for application functionality, updates, and configuration.In addition, a functioning always on GPS needs to be installed in the phone. To take advantage ofnotifications, an available SMS, or email service may be required. Support for Smartphones usingthe Apple or Android operating system is not in the scope of this project.

3.8 Acceptable Change

We estimate that we can accept at most 10 percent change in requirements for our current require-ments. Any more and we cannot guarantee all attempted requirements will be completed.

8

4 NONFUNCTIONAL REQUIREMENTS

4.1 Memory

Requirement NFR-3.1Name: Scheduler Security

The application shall keep the user’s schedule secure.

Requirement NFR-3.1.1Name: Scheduler Confidentiality

Only the user and people that the user allows shall be able to view the user’s schedule.

Requirement NFR-3.1.2Name: Scheduler Integrity

Only the user and people that the user allows shall be able to edit the user’s schedule.

Requirement NFR-3.1.3Name: Scheduler Availability

The user’s schedule shall always be available when the user trys to access it.

Requirement NFR-3.2Name: Scheduler Usability

The user shall have a simple interface that is intuitive to use.

9

4.2 Medical

Requirement NFR-4.1Name: Secure Medical Data

The user’s medical data shall be secure.

Requirement NFR-4.1.1Name: Secure Medicine Data

The user’s medicine data shall be secure.

Requirement NFR-4.1.1.1Name: Confidential Medicine Data

Only the user, and people the user allows, shall be able to view or access any of theuser’s medicine data.

Requirement NFR-4.1.2Name: Secure Medical History Data

The user’s medical history data shall be secure.

Requirement NFR-4.1.2.1Name: Confidential Medical History Data

Only the user, and people the user allows, shall be able to view or access any of theuser’s medical history data.

Requirement NFR-4.2Name: Medical Data Doctor Availability

Doctors or emergency medical professionals shall be able to access the user’s medicaldata.

Requirement NFR-4.2.1Name: Medicine Data Doctor Availability

Doctors or emergency medical professionals shall be able to access the user’s medicinedata.

Requirement NFR-4.2.2Name: Medical History Data Doctor Availability

Doctors or emergency medical professionals shall be able to access the user’s medicalhistory data.

Requirement NFR-4.3Name: Medical Data Doctor Usability

10

The user shall be able to easily access his medical data.

Requirement NFR-4.3.1Name: Medicine Data Doctor Usability

The user shall be able to easily access his medicine/prescription data.

Requirement NFR-4.3.2Name: Medical History Data Doctor Usability

The user shall be able to easily access his medical history data.

11

4.3 Softgoal Interdependency Graphs

12

5 PENDING REQUIREMENTS

This section details all requirements that will be completed in this iteration, but have not yet beencompleted.

14

5.1 Memory

Requirement R-3.1.v3.1Name: Calendar EntryDate Created : 2010-10-20 23:35:52Last Modified: 2010-11-11 06:42:50Priority : 8Problem : P-8Goal : G-7

The application shall allow the user to enter event dates and times by a calendarinterface.

Requirement R-3.1.v3.2Name: Manual EntryDate Created : 2010-10-20 23:36:02Last Modified: 2010-11-11 06:42:50Priority : 8Problem : P-8Goal : G-7

The application shall allow the user to enter event dates and times manually, by typingthem in.

Requirement R-3.1.v3.3Name: Event RecurrenceDate Created : 2010-10-20 23:36:04Last Modified: 2010-11-11 06:42:50Priority : 8Problem : P-8Goal : G-7

The application shall allow the user to specify the recurrence of an event as hourly,daily, weekly, monthly, or yearly.

Requirement R-3.1.v3.4Name: Alert on EventDate Created : 2010-10-20 23:36:06Last Modified: 2010-11-11 06:42:50Priority : 8Problem : P-8Goal : G-7

The application shall alert the user when an event’s time and date occur.

Requirement R-3.1.v3.5Name: Alert - VibrationDate Created : 2010-10-20 23:36:08Last Modified: 2010-11-11 06:42:50Priority : 8Problem : P-8Goal : G-7

15

The application shall be configurable to alert the user by vibrating the phone.

Requirement R-3.1.v3.6Name: Alert - RingtoneDate Created : 2010-10-20 23:36:09Last Modified: 2010-11-11 06:42:50Priority : 8Problem : P-8Goal : G-7

The application shall be configurable to alert the user by playing a ringtone.

Requirement R-3.1.v3.7Name: Alert - Visual DisplayDate Created : 2010-10-21 00:37:55Last Modified: 2010-11-11 06:42:50Priority : 8Problem : P-8Goal : G-7

The application shall be configurable to alert the user by displaying the event on thescreen.

16

5.2 Medical

Requirement R-4.3.v1.1Name: List of MedicationsDate Created : 2010-10-21 08:04:29Last Modified: 2010-11-11 06:42:50Priority : 9Problem : P-12Goal : G-9

The application shall keep a list of the user’s medications, and their dosage schedule.

Requirement R-4.3.v1.2Name: Confirmation of AlertDate Created : 2010-10-21 08:04:30Last Modified: 2010-11-11 06:42:50Priority : 9Problem : P-12Goal : G-9

When the application alerts the user that he should take his medicine, it shall requireconfirmation that the user received the alert.

Requirement R-4.3.v1.3Name: Confirmation Failed AlertsDate Created : 2010-10-21 08:04:31Last Modified: 2010-11-11 06:42:50Priority : 9Problem : P-12Goal : G-9

If the user does not confirm, the application shall send an alert to the user’s caregiver.

Requirement R-4.3.v1.4Name: Configuration: Medication InfoDate Created : 2010-10-21 08:04:31Last Modified: 2010-11-11 06:42:50Priority : 9Problem : P-12Goal : G-9

The alert shall be configurable to either send medication data, or not send medicationdata to the caregiver.

17

6 COMPLETE REQUIREMENTS

This section lists all requirements that are complete as of November 30, 2010.

18

6.1 Medical

Requirement R-4.1.v1.1Name: List of medicationsDate Created : 2010-10-21 07:00:17Last Modified: 2010-11-11 06:42:50Priority : 9Problem : P-10Goal : G-9

The application shall keep a list of the user’s medications, and when they should betaken.

Requirement R-4.1.v1.2Name: Display MessageDate Created : 2010-10-21 07:00:18Last Modified: 2010-11-11 06:42:50Priority : 9Problem : P-10Goal : G-9

When it is time for the user to take a medication, the application shall display a messagethat indicates a single medication is due, and the name of the medication.

Requirement R-4.1.v1.3Name: Auditory MessageDate Created : 2010-10-21 07:00:19Last Modified: 2010-11-11 06:42:50Priority : 7Problem : P-10Goal : G-9

When it is time for the user to take a medication, the application shall play a ringtone,and play a prerecorded voice that vocally indicates that a medication is due.

Requirement R-4.1.v1.4Name: Dismissing an AlertDate Created : 2010-10-21 07:00:19Last Modified: 2010-11-11 06:42:50Priority : 9Problem : P-10Goal : G-9

When an alert occurs, the user shall have a button which shall dismiss the alert.

Requirement R-4.1.v1.5Name: Display Next MedicationDate Created : 2010-10-21 07:00:20Last Modified: 2010-11-11 06:42:50Priority : 9Problem : P-10Goal : G-9

19

If there is more than one medication due, the next medication shall be displayed whenthe user dismisses this alert.

Requirement R-4.2.v2.1Name: List of prescriptionsDate Created : 2010-10-21 07:27:44Last Modified: 2010-11-11 06:42:50Priority : 7Problem : P-11Goal : G-10

The application shall keep a list of the user’s prescriptions, and when they are to berefilled.

Requirement R-4.2.v2.2Name: Prescription AlertsDate Created : 2010-10-21 07:27:45Last Modified: 2010-11-11 06:42:50Priority : 7Problem : P-11Goal : G-10

When a prescription is due to be refilled, the application should trigger an alert.

Requirement R-4.2.v2.3Name: Configuration: Who to alertDate Created : 2010-10-21 07:27:46Last Modified: 2010-11-11 06:42:50Priority : 7Problem : P-11Goal : G-10

The application shall be configurable to either alert the user or alert a contact.

Requirement R-4.2.v2.4Name: Configuration: Text MessageDate Created : 2010-10-21 07:27:47Last Modified: 2010-11-11 06:42:50Priority : 7Problem : P-11Goal : G-10

If configured to alert a contact, the application shall be further configurable to alertthe contact by text message

Requirement R-4.2.v2.5Name: Configuration: Email MessageDate Created : 2010-10-21 07:27:48Last Modified: 2010-11-11 06:42:50Priority : 7Problem : P-11Goal : G-10

20

If configured to alert a contact, the application shall be further configurable to alertthe contact by email message

Requirement R-4.2.v2.6Name: Configuration: Phone CallDate Created : 2010-10-21 07:27:48Last Modified: 2010-11-11 06:42:50Priority : 5Problem : P-11Goal : G-10

If configured to alert a contact, the application shall be further configurable to alertthe contact by an automated phone call

Requirement R-4.2.v2.7Name: Sending of medication dataDate Created : 2010-10-21 07:27:49Last Modified: 2010-11-11 06:42:50Priority : 7Problem : P-11Goal : G-10

Regardless of the alert method, the application should not send the name or type ofmedication to a contact

Requirement R-4.4.v2.1Name: Current Medication in SystemDate Created : 2010-10-21 08:22:14Last Modified: 2010-11-11 06:42:50Priority : 7Problem : P-13Goal : G-11

Given the user’s medication schedule and whether he has confirmed taking them, theapplication shall calculate what medicines should now be in the user’s body

Requirement R-4.4.v2.2Name: Medication ListingDate Created : 2010-10-21 08:22:15Last Modified: 2010-11-11 06:42:50Priority : 7Problem : P-13Goal : G-11

The application shall be capable of listing all medications that the user is taking, andwhich medications that the user probably has in their system.

Requirement R-4.4.v2.3Name: Security QuestionDate Created : 2010-10-21 08:22:15Last Modified: 2010-11-11 06:42:50Priority : 3Problem : P-13Goal : G-11

21

The application shall only list medical data if the user first correctly answers a securityquestion.

Requirement R-4.4.v2.4Name: Security Question ConstraintsDate Created : 2010-10-21 08:22:16Last Modified: 2010-11-11 06:42:50Priority : 7Problem : P-13Goal : G-11

The application shall only accept security questions that can be answered with infor-mation that the user would normally have on them.

Requirement R-4.5.v2.1Name: Entering Medical HistoryDate Created : 2010-10-21 08:31:11Last Modified: 2010-11-11 06:42:50Priority : 7Problem : P-14Goal : G-11

The user shall be able to list his medical history into the application.

Requirement R-4.5.v2.2Name: Listing Medical HistoryDate Created : 2010-10-21 08:31:12Last Modified: 2010-11-11 06:42:50Priority : 7Problem : P-14Goal : G-11

The application shall be capable of listing the user’s medical history on the screen.




22


Requirement R-4.6.v3.1Name: List DoctorsDate Created : 2010-10-21 08:51:42Last Modified: 2010-11-11 06:42:50Priority : 7Problem : P-15Goal : G-12

The application shall provide an interface to list the user’s doctors

Requirement R-4.6.v3.2Name: One per pageDate Created : 2010-10-21 08:51:43Last Modified: 2010-11-11 06:42:50Priority : 7Problem : P-15Goal : G-12

The application shall display one doctor per page

Requirement R-4.6.v3.3Name: Information DisplayedDate Created : 2010-10-21 08:51:44Last Modified: 2010-11-11 06:42:50Priority : 7Problem : P-15Goal : G-12

Each page shall display the doctor’s picture, phone number, address, and specializationif they are configured.

Requirement R-4.6.v3.4Name: Information Not DisplayedDate Created : 2010-10-21 08:51:45Last Modified: 2010-11-11 06:42:50Priority : 6Problem : P-15Goal : G-12

Each page shall not display the doctor’s picture, phone number, address, and special-ization if they are not configured.

Requirement R-4.6.v3.5Name: Call DoctorDate Created : 2010-10-21 08:51:45Last Modified: 2010-11-11 06:42:50Priority : 7Problem : P-15Goal : G-12

23

Each page shall have a button that shall call the doctor.

Requirement R-4.6.v3.6Name: Page NavigationDate Created : 2010-10-21 08:51:46Last Modified: 2010-11-11 06:42:50Priority : 7Problem : P-15Goal : G-12

The user shall be able to navigate back and forth between pages.

24

6.2 Location

Requirement R-5.1.v1Name: Display the user’s location as an icon on a mapDate Created : 2010-10-21 09:08:26Last Modified: 2010-11-11 06:42:50Priority : 6Problem : P-17Goal : G-14

The device will be able to get the phone’s location based on GPS or cell phone signal,and display it as an icon on a map.

Alternatives used: A-1Justification: Changing to a different application is disorienting to an elderly user.

25

7 REQUIREMENT BACKLOG

This section lists all requirements that will not be attempted in this iteration.

26

7.1 Vision

Requirement R-1.1Name: Money Visual AideDate Created : 2010-10-20 07:20:01Last Modified: 2010-11-11 06:42:50Priority : 1Problem : P-1Goal : G-1

The application will have the capacity to identify US paper currency using the camera.The application will speak the denomination of the bill aloud.

Requirement R-1.3Name: Color AideDate Created : 2010-10-20 09:20:45Last Modified: 2010-11-11 06:42:50Priority : 2Problem : P-3Goal : G-3

The application will identify colors via the camera, and say the name of the color aloud.

Requirement R-1.4.v1Name: Only Face DetectionDate Created : 2010-10-20 09:38:51Last Modified: 2010-11-11 06:42:50Priority : 1Problem : P-4Goal : G-4

The application will allow the user to take a picture of a person, and if that personmatches a contact, it will say the name of the contact aloud.

Alternatives used: A-2Justification: This seems to be the only feasible thing we can do.

Nonfunctional Requirement R-1.5Name: Color Accuracy, Precision, and RangeDate Created : 2010-10-20 09:40:46Last Modified: 2010-11-11 06:42:50Priority : 3Problem : P-3Goal : G-3

The color aide will have sufficiently accurate and precise estimations of color, and itwill have a wide range of colors that it reports.

Nonfunctional Requirement R-1.6Name: Facial Recognition AccuracyDate Created : 2010-10-20 09:43:50Last Modified: 2010-11-11 06:42:50Priority : 3Problem : P-4Goal : G-4

27

The facial recognition system will not mis-classify people.

Nonfunctional Requirement R-1.7Name: Currency Recognition AccuracyDate Created : 2010-10-20 09:45:19Last Modified: 2010-11-11 06:42:50Priority : 3Problem : P-1Goal : G-1

The currency recognizer will not report the wrong denomination of bill

Nonfunctional Requirement R-1.8Name: Currency Recognition SpeedDate Created : 2010-10-20 09:46:23Last Modified: 2010-11-11 06:42:50Priority : 3Problem : P-1Goal : G-1

The currency recognizer will recognize currency at a reasonable rate

28

7.2 Speech and Hearing

Requirement R-2.1.v1Name: User enters all text firstDate Created : 2010-10-20 16:57:50Last Modified: 2010-11-11 06:42:50Priority : 4Problem : P-5Goal : G-5

The application will provide the user with a text box, and the user may enter all thetext that he wants the application to speak. When the user indicates that he is done,the application will speak the text.

Alternatives used: A-2Justification: It is more important that the user is understood clearly

Requirement R-2.2.v1Name: Send the Nurse a Text MessageDate Created : 2010-10-20 17:43:53Last Modified: 2010-11-11 06:42:50Priority : 3Problem : P-6Goal : G-5

The application will play a tone, and send a text message to the nurse, to get herattention when the user demands.

Alternatives used: A-1Justification: If the user is very demanding, he may end up getting frustrated and pressing the

button as many times as possible. If the application constantly alerted a contact every time thishappened, the contact would quickly start ignoring the user’s alerts.

Requirement R-2.3Name: Order Food or WaterDate Created : 2010-10-20 18:07:47Last Modified: 2010-11-11 06:42:50Priority : 4Problem : P-6Goal : G-5

The application will allow the user to inform their nurse or caregiver that they are arehungry, thirsty, or need to use the restroom.

Requirement R-2.4Name: MegaphoneDate Created : 2010-10-20 18:11:19Last Modified: 2010-11-11 06:42:50Priority : 3Problem : P-5Goal : G-5

The application will amplify the user’s voice through the built-in loudspeaker.

29

Requirement R-2.5Name: Sound CatcherDate Created : 2010-10-20 19:04:30Last Modified: 2010-11-11 06:42:50Priority : 3Problem : P-7Goal : G-6

The application will amplify and filter the sound in the user’s environment, and playit through the phone’s speaker.

Requirement R-2.6Name: Speech RecognitionDate Created : 2010-10-20 22:21:33Last Modified: 2010-11-11 06:42:50Priority : 3Problem : P-7Goal : G-6

The application will translate the speech of others into text for the user to read.

Nonfunctional Requirement R-2.7Name: Type of ToneDate Created : 2010-10-20 22:22:42Last Modified: 2010-11-11 06:42:50Priority : 4Problem : P-6Goal : G-5

The tone played will be easily recognizable and heard

Nonfunctional Requirement R-2.8Name: Speech Synthesis UnderstandabilityDate Created : 2010-10-20 22:26:13Last Modified: 2010-11-11 06:42:50Priority : 4Problem : P-5Goal : G-5

The Text-to-Speech system will be easy to understand

Nonfunctional Requirement R-2.9Name: Megaphone VolumeDate Created : 2010-10-20 22:39:53Last Modified: 2010-11-11 06:42:50Priority : 4Problem : P-5Goal : G-5

The megaphone will have a high enough volume that others can hear it easily

30

Nonfunctional Requirement R-2.10Name: Quality of Speech RecognitionDate Created : 2010-10-20 22:42:16Last Modified: 2010-11-11 06:42:50Priority : 4Problem : P-7Goal : G-6

The application will recognize speech correctly at least 90 percent of the time.

31

7.3 Memory

Requirement R-3.2Name: Memo RecorderDate Created : 2010-10-21 00:38:55Last Modified: 2010-11-11 06:42:50Priority : 5Problem : P-9Goal : G-8

The application will allow the user to speak a reminder into the phone, and have itplayed back at any time.

Nonfunctional Requirement R-3.4Name: Memo FidelityDate Created : 2010-10-21 00:44:21Last Modified: 2010-11-11 06:42:50Priority : 5Problem : P-9Goal : G-8

Recorded memos must be easy to hear and understand.

32

7.4 Medical

Requirement R-4.7Name: Pulse MonitorDate Created : 2010-10-21 08:54:27Last Modified: 2010-11-11 06:42:50Priority : 4Problem : P-16Goal : G-13

The application shall be capable of monitoring the user’s pulse when they require.

33

7.5 Location




Requirement R-5.2.v1.1Name: AlertDate Created : 2010-10-21 09:12:19Last Modified: 2010-11-11 06:42:50Priority : 6Problem : P-17Goal : G-14

When the user leaves a designated geographical area, an alert will be sent to an emer-gency contact.

Requirement R-5.2.v1.2Name: Alert LocationDate Created : 2010-10-21 09:12:20Last Modified: 2010-11-11 06:42:50Priority : 6Problem : P-17Goal : G-14

The alert will contain the phone’s current location.

Requirement R-5.2.v1.3Name: Text MessageDate Created : 2010-10-21 09:12:21Last Modified: 2010-11-11 06:42:50Priority : 6Problem : P-17Goal : G-14

The alert will be configurable as a text message.

Requirement R-5.2.v1.4Name: Email MessageDate Created : 2010-10-21 09:12:22Last Modified: 2010-11-11 06:42:50Priority : 6Problem : P-17Goal : G-14

34

The alert will be configurable as an email message.

Requirement R-5.2.v1.5Name: Phone CallDate Created : 2010-10-21 09:12:23Last Modified: 2010-11-11 06:42:50Priority : 6Problem : P-17Goal : G-14

The alert will be configurable as an automated phone call.

Requirement R-5.2.v1.6Name: PersistenceDate Created : 2010-10-21 09:12:23Last Modified: 2010-11-11 06:42:50Priority : 6Problem : P-17Goal : G-14

The application will continue to alert the emergency contact until the contact respondsthat it should stop.



Requirement R-5.3.v1.2Name: LocationDate Created : 2010-10-21 09:19:10Last Modified: 2010-11-11 06:42:50Priority : 5Problem : P-17Goal : G-14



35








Requirement R-5.4.v0.1Name: Offer to helpDate Created : 2010-10-21 09:22:41Last Modified: 2010-11-11 06:42:50Priority : 6Problem : P-17Goal : G-14

When the user leaves a designated geographical area, the system will offer to help.

Requirement R-5.4.v0.2Name: Ask for helpDate Created : 2010-10-21 09:22:42Last Modified: 2010-11-11 06:42:50Priority : 6Problem : P-17Goal : G-14

36

When the user indicates to the application that he is lost, the system will offer to help.

Requirement R-5.4.v0.3Name: Offer typeDate Created : 2010-10-21 09:22:42Last Modified: 2010-11-11 06:42:50Priority : 6Problem : P-17Goal : G-14

The system’s offer to help will be both verbal and visual


The system will continue to guide the user, step by step, until he is back in a designatedarea

Requirement R-5.5.v0.1Name: NoticingDate Created : 2010-10-21 09:25:29Last Modified: 2010-11-11 06:42:50Priority : 6Problem : P-17Goal : G-14

The application will notice when the user has moved around an area at car speeds, buthas not stopped for any lengthy period of time, and yet has not left the area for sometime.


If the application determines that the user is lost, it will send an alert to the user’semergency contact that the user may be lost.

Requirement R-5.5.v0.3Name: Send LocationDate Created : 2010-10-21 09:25:30Last Modified: 2010-11-11 06:42:50Priority : 6Problem : P-17Goal : G-14

37

If the emergency contact responds to the alert, the application will send the user’slocation to the contact

Requirement R-5.6.v1.1Name: Noticing UseDate Created : 2010-10-21 09:32:07Last Modified: 2010-11-11 06:42:50Priority : 6Problem : P-18Goal : G-15

The application will notice when the phone has not moves, nor been interacted withfor a user-configurable length of time.


If the application determines that the phone has been lost, it will send an alert to adesignated contact. The alert will contain the phone’s location.

Nonfunctional Requirement R-5.7Name: Map ReadabilityDate Created : 2010-10-21 09:33:01Last Modified: 2010-11-11 06:42:50Priority : 6Problem : P-17Goal : G-14

The map application will be easy to read, and easy to understand for someone who isold.

Nonfunctional Requirement R-5.8Name: Map AccuracyDate Created : 2010-10-21 09:33:40Last Modified: 2010-11-11 06:42:50Priority : 6Problem : P-17Goal : G-14

The map application will be accurate as to the user’s location.

Nonfunctional Requirement R-5.9Name: Map PrecisionDate Created : 2010-10-21 09:34:15Last Modified: 2010-11-11 06:42:50Priority : 6Problem : P-17Goal : G-14

The map application will be precise as to the user’s location.

38

7.6 Family/User Web Services

Requirement R-6.1Name: Web service allowing remote configuration of app settings.Date Created : 2010-10-21 09:35:17Last Modified: 2010-11-11 06:42:50Priority : 7Problem : P-19Goal : G-16

After logging in to the web service and authenticating, the user may remotely selectanything from the phone configuration, and modify it

Requirement R-6.2Name: Web Service Contact ConfigurationDate Created : 2010-10-21 09:35:22Last Modified: 2010-11-11 06:42:50Priority : 6Problem : P-19Goal : G-16

The service will allow the user to read any contact information, and may add or changeany names, addresses, phone numbers, or pictures

Requirement R-6.3.v1.1Name: Display areasDate Created : 2010-10-21 09:41:12Last Modified: 2010-11-11 06:42:50Priority : 6Problem : P-19Goal : G-16

The service will display all restricted and designated areas

Requirement R-6.3.v1.2Name: Edit areasDate Created : 2010-10-21 09:41:13Last Modified: 2010-11-11 06:42:50Priority : 6Problem : P-19Goal : G-16

The service will allow the user to edit any restricted or designated area

Requirement R-6.3.v1.3Name: GUIDate Created : 2010-10-21 09:41:13Last Modified: 2010-11-11 06:42:50Priority : 6Problem : P-19Goal : G-16

39

The service will display areas on a map, which has controls to zoom and pan

Requirement R-6.3.v1.4Name: DrawingDate Created : 2010-10-21 09:41:14Last Modified: 2010-11-11 06:42:50Priority : 6Problem : P-19Goal : G-16

The service will edit and add areas by having the user draw on a map

Requirement R-6.4.v0.1Name: Leave areaDate Created : 2010-10-21 09:44:12Last Modified: 2010-11-11 06:42:50Priority : 6Problem : P-19Goal : G-16

The service will allow the user to view and configure whether the application sendsalerts when the user leaves a designated area

Requirement R-6.4.v0.2Name: Enter AreaDate Created : 2010-10-21 09:44:13Last Modified: 2010-11-11 06:42:50Priority : 6Problem : P-19Goal : G-16

The service will allow the user to view and configure whether the application sendsalerts when the user enters a restricted area

Requirement R-6.4.v0.3Name: Location ContactDate Created : 2010-10-21 09:44:14Last Modified: 2010-11-11 06:42:50Priority : 6Problem : P-19Goal : G-16

The service will allow the user to view and configure the designated contact for locationalerts

Requirement R-6.4.v0.4Name: Location Alert TypeDate Created : 2010-10-21 09:44:16Last Modified: 2010-11-11 06:42:50Priority : 5Problem : P-19Goal : G-16

40

The service will allow the user to view and configure what type of alert is to be usedfor location alerts

Requirement R-6.4.v0.5Name: Alert on LostDate Created : 2010-10-21 09:44:17Last Modified: 2010-11-11 06:42:50Priority : 6Problem : P-19Goal : G-16

The service will allow the user to view and configure whether the application sendsalerts when the user appears lost

Requirement R-6.4.v0.6Name: Alert on Lost PhoneDate Created : 2010-10-21 09:44:18Last Modified: 2010-11-11 06:42:50Priority : 6Problem : P-19Goal : G-16

The service will allow the user to view and configure whether the application sendsalerts when it thinks that the phone is lost

Requirement R-6.4.v0.7Name: Lost Time ConfigDate Created : 2010-10-21 09:44:19Last Modified: 2010-11-11 06:42:50Priority : 6Problem : P-19Goal : G-16

The service will allow the user to view and configure the length of time by which theapplication gauges that the phone is lost

Requirement R-6.4.v0.8Name: Medication AlertsDate Created : 2010-10-21 09:44:19Last Modified: 2010-11-11 06:42:50Priority : 6Problem : P-19Goal : G-16

The service will allow the user to view and configure whether the application sendsalerts when the user’s medication is due

Requirement R-6.4.v0.9Name: Medication Confirm AlertsDate Created : 2010-10-21 09:44:21Last Modified: 2010-11-11 06:42:50Priority : 6Problem : P-19Goal : G-16

41

The service will allow the user to view and configure whether the application sendsalerts to a contact when the user does not confirm that they took their medication.

Requirement R-6.4.v0.10Name: Missed Medication ContactDate Created : 2010-10-21 09:44:21Last Modified: 2010-11-11 06:42:50Priority : 6Problem : P-19Goal : G-16

The service will allow the user to view and configure the designated contact for missedmedication.


The service will allow the user to view and configure whether the application sendsalerts when the user’s prescription is due to be refilled

Requirement R-6.4.v0.12Name: Prescription Alert ContactDate Created : 2010-10-21 09:44:23Last Modified: 2010-11-11 06:42:50Priority : 6Problem : P-19Goal : G-16

The service will allow the user to view and configure whether the application sendsalerts to a designated contact when a prescription needs refilled.

Requirement R-6.4.v0.13Name: Prescription ContactDate Created : 2010-10-21 09:44:24Last Modified: 2010-11-11 06:42:50Priority : 6Problem : P-19Goal : G-16

The service will allow the user to view and configure whether the designated contactfor prescription refills.

Requirement R-6.5Name: Web Service Medical HistoryDate Created : 2010-10-21 09:50:18Last Modified: 2010-11-11 06:42:50Priority : 7Problem : P-19Goal : G-16

42

The service will allow the user to view their medical history and modify it

Requirement R-6.6.v0.1Name: Which MedicationsDate Created : 2010-10-21 09:51:53Last Modified: 2010-11-11 06:42:50Priority : 7Problem : P-19Goal : G-16

The service will allow the user to view and configure which medications they are taking.

Requirement R-6.6.v0.2Name: DosageDate Created : 2010-10-21 09:51:54Last Modified: 2010-11-11 06:42:50Priority : 7Problem : P-19Goal : G-16

The service will allow the user to view and configure the dosage of a medication.

Requirement R-6.6.v0.3Name: ScheduleDate Created : 2010-10-21 09:51:54Last Modified: 2010-11-11 06:42:50Priority : 7Problem : P-19Goal : G-16

The service will allow the user to view and configure the schedule of a medication.

Requirement R-6.7.v0.1Name: Which PrescriptionsDate Created : 2010-10-21 09:53:42Last Modified: 2010-11-11 06:42:50Priority : 7Problem : P-19Goal : G-16

The service will allow the user to view and configure which prescriptions they currentlyhave.

Requirement R-6.7.v0.2Name: End DateDate Created : 2010-10-21 09:53:42Last Modified: 2010-11-11 06:42:50Priority : 7Problem : P-19Goal : G-16

43

The service will allow the user to view and configure the end date of the prescription.

Requirement R-6.7.v0.3Name: Refill DateDate Created : 2010-10-21 09:53:43Last Modified: 2010-11-11 06:42:50Priority : 7Problem : P-19Goal : G-16

The service will allow the user to view and configure the date that the prescriptionnext needs to be refilled.

Requirement R-6.8Name: Web Service Calendar ConfigurationDate Created : 2010-10-21 09:54:48Last Modified: 2010-11-11 06:42:50Priority : 7Problem : P-19Goal : G-16

The service will allow the user to view their calendar events and reminders, modifythem, and add new ones

Requirement R-6.9Name: Web service to access device information.Date Created : 2010-10-21 09:55:24Last Modified: 2010-11-11 06:42:50Priority : 6Problem : P-19Goal : G-16

A user may remotely login to the web service and access all last known phone configu-ration settings and data, including location, last used, medical information and historyof medications taken.

Nonfunctional Requirement R-6.10Name: Security of Web ServiceDate Created : 2010-10-21 09:55:50Last Modified: 2010-11-11 06:42:50Priority : 8Problem : P-19Goal : G-16

The web service should only allow access to individuals that the user designates

Nonfunctional Requirement R-6.11Name: Intuitive Web ServiceDate Created : 2010-10-21 09:56:29Last Modified: 2010-11-11 06:42:50Priority : 7Problem : P-19Goal : G-16

The web service should be easy to use

44

7.7 Easy-To-Use Phone Interface

Requirement R-7.1Name: Touch pad dialerDate Created : 2010-10-21 09:57:13Last Modified: 2010-11-11 06:42:50Priority : 7Problem : P-20Goal : G-17

The application shall provide a touch pad dialer that allows the user to dial numbersdirectly, as well as buttons to start and end their call.

Requirement R-7.2Name: Contact StorageDate Created : 2010-10-21 09:57:14Last Modified: 2010-11-11 06:42:50Priority : 8Problem : P-20Goal : G-17

The application shall provide a small storage area for a limited number of contacts,as well as a few different ways of sorting the contacts. Using the Family/User WebServices portal, the contacts can be added and reconfigured as necessary. There is alsoa section for In Case of Emergency (ICE) if needed by the user or if the phone is foundby a third party.

Requirement R-7.3Name: Recent CallsDate Created : 2010-10-21 09:57:15Last Modified: 2010-11-11 06:42:50Priority : 7Problem : P-20Goal : G-17

The application shall provide a storage area for the calls placed, received, and missedby the user. The Calls Dialed list allows the user to see who they have called and allowsthem to call that person again, if desired. Calls that are un-answered are placed onthe Calls Missed list. When a call from a doctor or care-giver goes un-answered, thephone will make a noticeable alert every minute until they are acknowledged.

Requirement R-7.4Name: MessagingDate Created : 2010-10-21 09:57:15Last Modified: 2010-11-11 06:42:50Priority : 7Problem : P-20Goal : G-17

The application shall provide a messaging service for both text and voice messages.Important calls from doctors or care-givers are given special priority and play an alertuntil cleared by the user.

45

Requirement R-7.5Name: Volume AdjustmentDate Created : 2010-10-21 09:57:16Last Modified: 2010-11-11 06:42:50Priority : 7Problem : P-20Goal : G-17

The application shall provide a volume control that the user can use to change thevolume of the phone’s speaker

Nonfunctional Requirement R-7.6Name: Dialer Button SizeDate Created : 2010-10-21 10:01:21Last Modified: 2010-11-11 06:42:50Priority : 7Problem : P-20Goal : G-17

The size of the dialer’s buttons shall be large enough, and have big enough numbers,that they are easy to read and press for an elderly person

Nonfunctional Requirement R-7.7Name: Loudness of Message AlertsDate Created : 2010-10-21 10:01:24Last Modified: 2010-11-11 06:42:50Priority : 7Problem : P-20Goal : G-17

Message alerts shall be loud enough that an old person can easily hear them.

46

8 PROBLEMS

This section details all problems that have been identified in the problem domain.Problem P-1

Name: Vision Impaired People and MoneyPriority: 1

Elderly people who have developed vision problems may be find it difficult to identifythe denomination of currency. This leaves them in a position to be taken advantage of.

Problem P-2Name: Vision Impaired People and NavigationPriority: 1

The elderly may have vision problems that makes it impossible for them to guidethemselves around town safely

Problem P-3Name: Vision Impaired People and ColorPriority: 2

The elderly may have difficulty discerning different colors because of vision problems.This makes it difficult for them to find something of a specific color, or to wear matchingcolored clothes.

Problem P-4Name: Vision Impaired People and Objects Around ThemPriority: 1

The elderly may have difficulty identifying objects or people around them because ofvision problems.

Problem P-5Name: The Speech Impaired and CommunicationPriority: 4

The elderly sometimes have difficulty speaking or making sufficiently audible words.This makes it difficult to communicate with others.

Problem P-6Name: The Speech Impaired and Getting HelpPriority: 6

The speech-impaired may have difficulty getting the attention of a nurse or caregiverwhen they need it, due to inability to call out vocally.

Problem P-7Name: The Hearing Impaired and CommunicationPriority: 4

The elderly sometimes have difficulty hearing. This makes it difficult for them tocommunicate.

Problem P-8Name: The Memory Impaired and EventsPriority: 8

47

The elderly have difficulty remembering events.

Problem P-9Name: The Memory Impaired and RemindersPriority: 5

The elderly have difficulty remembering small things. They may try to write thesereminders down, but they may have difficulty reading their own handwriting due toshaky hands or bad vision.

Problem P-10Name: The Elderly and Taking MedicationPriority: 10

The elderly often have many different types of medication that they must take on adaily basis, but often have difficulty remembering to take their medication or whichmedications to take.

Problem P-11Name: The Elderly and PrescriptionsPriority: 7

The elderly often have trouble remembering to refill prescriptions, or asking their care-givers to pick up their prescriptions. This leads to them running out of medicationbefore their prescription is refilled.

Problem P-12Name: The Elderly, Medication, and CaregiversPriority: 9

When an elderly person forgets their medication, their caregivers have no way of know-ing that the elderly person did not take their medication, and will not be able to correctthe situation.

Problem P-13Name: The Elderly and Remembering Medication InformationPriority: 7

The elderly often have difficulty remembering which medications they are currentlytaking. If required to list all of their medications (for instance, for a medical form),they may not be able to.

Problem P-14Name: The Elderly and Remembering Medical HistoryPriority: 7

The elderly often have difficulty remembering their medical history, which can be aproblem if they, for instance, need to list any medical conditions that they have to anemergency room doctor.

Problem P-15Name: The Elderly and Their DoctorsPriority: 7

The elderly, and particularly the ill, often have see multiple specialists for their ailments.Keeping track of their numbers, who they are, and what they specialize is difficult forelderly.

48

Problem P-16Name: The Elderly and Heart ProblemsPriority: 7

Some elderly with heart problems must keep track of their heart rate, and countingtheir pulse may be difficult.

Problem P-17Name: The Elderly and Getting LostPriority: 7

The elderly often become lost, and don’t know where they are. This creates a situationwhere the elderly user can become extremely disorientated. Patients with any degreeof dementia can benefit from being able to determine where they are. This will alsoallow a caregiver the ability to track the location of an individual.

Problem P-18Name: The Elderly and Losing their PhonePriority: 8

The elderly may sometimes lose their phone. The elderly’s caregivers and loved onesthen cannot contact them.

Problem P-19Name: Configuring the ApplicationPriority: 8

The elderly may not understand the phone interface for changing settings or addingdata, or may not desire to manipulate the phone to enter all the data manually. Phonestypically have small screens and keyboards that are difficult to use for extended con-figuration

Problem P-20Name: The Elderly and Phone InterfacesPriority: 8

The elderly sometimes have difficulty understanding and reading phone interfaces. Theuser should not have to intentionally leave our application to do simple tasks.

49

9 GOALS

This section details all goals that have been created to address the problems detailed in the previoussectionGoal G-1

Name: Help the Vision Impaired with Money

Prevent the vision impaired from being taken advantage of during financial transactionsbecause of their disability.

Goal G-2Name: Help the Vision Impaired to Navigate

Provide a way for the vision impaired to safely navigate autonomously.

Goal G-3Name: Help the Vision Impaired with Colors

Provide for the vision impaired to be able to detect colors, so that lack of color visionno longer negatively impacts their lives.

Goal G-4Name: Help the Vision Impaired Identify Objects

Allow the vision impaired to be able to identify objects that they are unable to identifywith their own sight.

Goal G-5Name: Help the Speech Impaired Communicate

Allow the speech impaired to communicate effectively with others despite their disabil-ity.

Goal G-6Name: Help the Hearing Impaired Communicate

Allow the hearing impaired to communicate with others effectively despite their dis-ability.

Goal G-7Name: Help the Memory Impaired to Remember Events

Prevent the memory impaired from forgetting when events occur, and from missingthem when they do.

Goal G-8Name: Help the Memory Impaired with Small Facts

Prevent the memory impaired from forgetting small, but important facts.

Goal G-9Name: Help the Elderly to take their Medication

Prevent the elderly from forgetting their medication, or making mistakes with medicinedosage.

Goal G-10Name: Help the Elderly with their Prescriptions

50

Ensure that the elderly never run out of their medication because they did not get theirprescription refilled.

Goal G-11Name: Help the Elderly with their Medical Data

Allow the elderly to always be able to access their private medical information.

Goal G-12Name: Help the Elderly with Contacting their Doctors

Make it easier for the elderly to remember information about their doctors, and easierto get in touch with them.

Goal G-13Name: Help the Elderly keep track of their Heart Health

Allow the elderly to easily monitor and log their heart conditions.

Goal G-14Name: Help the Elderly who get Lost

Prevent the elderly from getting lost in the first place, and if they do get lost, get themhome safely.

Goal G-15Name: Help the Elderly keep track of their Phone

Prevent the elderly from losing their phone, and help them find it when they do.

Goal G-16Name: Help the user Configure the Application

Make it easy for the user to configure the application effectively and correctly.

Goal G-17Name: Provide an easy to use interface

Provide an interface that the elderly can use effectively and with minimal frustration.

51

10 TRACEABILITY

This section specifies the traceability of every requirement that we are currently attempting in thisiteration. The following key explains the meaning of the shapes used:

10.0.1 R-3.1 - User Schedules

52

10.0.2 R-3.3 - Intuitive Schedule

10.0.3 R-4.1 - Alerts About Medicine

53

10.0.4 R-4.2 - Alerts when a prescription needs refilled

54

10.0.5 R-4.3 - Alerts when the user does not take medication.

55

10.0.6 R-4.4 - Listing of user’s current medications

56

10.0.7 R-4.5 - Listing of user’s medical history

57

10.0.8 R-4.6 - Fast Interface to Doctors

58

11 REQUIREMENTS ANALYSIS

This section provides all requirement, issue, and alternative data.

59

11.1 Vision

Requirement R-1.1Name: Money Visual AideDate Created : 2010-10-20 07:20:01Last Modified: 2010-11-11 06:42:50Priority : 1Problem : P-1Goal : G-1

The application will have the capacity to identify US paper currency using the camera.The application will speak the denomination of the bill aloud.

Requirement R-1.2Name: GPS Guidance for the Vision-ImpairedDate Created : 2010-10-20 07:42:37Last Modified: 2010-11-11 06:42:50Priority : 1Problem : P-2Goal : G-2

The application will guide the user to a location by guiding them along sidewalks andother safe walkways. The application will give the user instructions every 3 seconds tokeep the user informed.

Issue I-1.2.v0Name: Technically Infeasible

The GPS precision necessary to keep a person on a sidewalk does not exist. The bestprecision available is typically around 3 meters. Also the necessary map data to decidewhat areas are safe for foot-traffic does not exist either

Alternative A-1.2.v0.1

Name: Only far from roads

Description: Only guide the user in areas that are far away from roads.

Positives : Ensures the system does not lead the user into traffic.

Negatives : Not really useful.


Name: Drop

Description: Drop the requirement

Positives : Requires no implementation

Negatives : The user will have no guide; the problem is left unsolved

60

Requirement R-1.2.v1Name: Requirement DroppedDate Created : 2010-10-20 09:18:00Last Modified: 2010-11-11 06:42:50Priority : 0Problem : P-2Goal : G-2

This requirement will not be pursued.

Alternatives used: A-2Justification: Because of technical limitations, there is simply no way we can even begin to

solve the user’s problem with GPS.

Requirement R-1.3Name: Color AideDate Created : 2010-10-20 09:20:45Last Modified: 2010-11-11 06:42:50Priority : 2Problem : P-3Goal : G-3

The application will identify colors via the camera, and say the name of the color aloud.

Requirement R-1.4Name: What’s around me?Date Created : 2010-10-20 09:26:44Last Modified: 2010-11-11 06:42:50Priority : 1Problem : P-4Goal : G-4

The application will allow the user to take a picture of an object with the camera, andwill then say the name of the object in the picture.

Issue I-1.4.v0Name: Technically Infeasible

The technology required to identify any object simply does not exist.


Name: Fewer Objects

Description: Only recognize a small subset of objects.

Positives : More feasible than recognizing any object.

Negatives : Still requires substantial work to recognize an object under ideal circum-stances. Objects in the field would often fail to be recognized properly.


Name: Only Faces

61

Description: Only recognize people. If the picture of the person matches a picture of acontact, the application will say the name of the contact.

Positives : Facial recognition is established, and fairly accurate depending on lightingconditions and camera.

Negatives : Still error-prone. Requires taking a picture of everyone you want the phoneto recognize.

Requirement R-1.4.v1Name: Only Face DetectionDate Created : 2010-10-20 09:38:51Last Modified: 2010-11-11 06:42:50Priority : 1Problem : P-4Goal : G-4

The application will allow the user to take a picture of a person, and if that personmatches a contact, it will say the name of the contact aloud.

Alternatives used: A-2Justification: This seems to be the only feasible thing we can do.

Nonfunctional Requirement R-1.5Name: Color Accuracy, Precision, and RangeDate Created : 2010-10-20 09:40:46Last Modified: 2010-11-11 06:42:50Priority : 3Problem : P-3Goal : G-3

The color aide will have sufficiently accurate and precise estimations of color, and itwill have a wide range of colors that it reports.

Nonfunctional Requirement R-1.6Name: Facial Recognition AccuracyDate Created : 2010-10-20 09:43:50Last Modified: 2010-11-11 06:42:50Priority : 3Problem : P-4Goal : G-4

The facial recognition system will not mis-classify people.

Nonfunctional Requirement R-1.7Name: Currency Recognition AccuracyDate Created : 2010-10-20 09:45:19Last Modified: 2010-11-11 06:42:50Priority : 3Problem : P-1Goal : G-1

The currency recognizer will not report the wrong denomination of bill

62

Nonfunctional Requirement R-1.8Name: Currency Recognition SpeedDate Created : 2010-10-20 09:46:23Last Modified: 2010-11-11 06:42:50Priority : 3Problem : P-1Goal : G-1

The currency recognizer will recognize currency at a reasonable rate

63

11.2 Speech and Hearing

Requirement R-2.1Name: Speech SynthesisDate Created : 2010-10-20 16:39:34Last Modified: 2010-11-11 06:42:50Priority : 3Problem : P-5Goal : G-5

The application will convert user text input into speech.

Issue I-2.1.v0Name: ”Convert text input to speech” is too vague

How does the user convert his text into speech? What mechanism does the applicationprovide that facilitates this?


Name: Real time

Description: The application will display a text box, and the application will speakwords as the user types them in with the keyboard

Positives : Easy to understand

Negatives : The discontinuity of speech could be difficult to understand.


Name: Batch

Description: The application will display a text box, and the user will add everythingthey want the application to say. They will then press ‘OK’ and the application willspeak all of the text that the user has typed.

Positives : Provides better continuity of speech.

Negatives : Slightly less intuitive.

Requirement R-2.1.v1Name: User enters all text firstDate Created : 2010-10-20 16:57:50Last Modified: 2010-11-11 06:42:50Priority : 4Problem : P-5Goal : G-5

The application will provide the user with a text box, and the user may enter all thetext that he wants the application to speak. When the user indicates that he is done,the application will speak the text.

64

Alternatives used: A-2Justification: It is more important that the user is understood clearly

Requirement R-2.2Name: Call Nurse or CaregiverDate Created : 2010-10-20 17:02:50Last Modified: 2010-11-11 06:42:50Priority : 4Problem : P-6Goal : G-5

The application will play a tone to get the attention of a nurse when the user demands.

Issue I-2.2.v0Name: The tone might not be heard

The nurse might not have good hearing, or cannot otherwise hear the tone.


Name: Text Message

Description: The application will also alert the nurse with a text message.

Positives : The nurse does not need to be close to the user to get the alert. The nursecan even be away from her phone, and still get the message when she next checks herphone. Her phone may also use vibration to alert her as opposed to sound, which helpsif she is hard of hearing.

Negatives : The nurse may not have a text messaging plan. The nurse may not haveher phone on her. The nurse may not like the user running up her phone bill.


Name: Call Designated Contact

Description: The application will call a designated contact after the user presses thebutton several times.

Positives : The user can bypass the nurse if he/she is negligent. If the nurse is con-sistently not around, the user will be automatically redirected to someone that canprobably help.

Negatives : The designated contact may get tired of being called every time the userwants something badly. The designated contact may not actually be able to help theuser.


Name: Both

Description: The application will do both of the above.

Positives : The user has the highest chance of getting someone’s attention.

Negatives : The user ends up bothering the largest number of people.

65

Requirement R-2.2.v1Name: Send the Nurse a Text MessageDate Created : 2010-10-20 17:43:53Last Modified: 2010-11-11 06:42:50Priority : 3Problem : P-6Goal : G-5

The application will play a tone, and send a text message to the nurse, to get herattention when the user demands.

Alternatives used: A-1Justification: If the user is very demanding, he may end up getting frustrated and pressing the

button as many times as possible. If the application constantly alerted a contact every time thishappened, the contact would quickly start ignoring the user’s alerts.

Requirement R-2.3Name: Order Food or WaterDate Created : 2010-10-20 18:07:47Last Modified: 2010-11-11 06:42:50Priority : 4Problem : P-6Goal : G-5

The application will allow the user to inform their nurse or caregiver that they are arehungry, thirsty, or need to use the restroom.

Requirement R-2.4Name: MegaphoneDate Created : 2010-10-20 18:11:19Last Modified: 2010-11-11 06:42:50Priority : 3Problem : P-5Goal : G-5

The application will amplify the user’s voice through the built-in loudspeaker.

Requirement R-2.5Name: Sound CatcherDate Created : 2010-10-20 19:04:30Last Modified: 2010-11-11 06:42:50Priority : 3Problem : P-7Goal : G-6

The application will amplify and filter the sound in the user’s environment, and playit through the phone’s speaker.

Requirement R-2.6Name: Speech RecognitionDate Created : 2010-10-20 22:21:33Last Modified: 2010-11-11 06:42:50Priority : 3Problem : P-7Goal : G-6

66

The application will translate the speech of others into text for the user to read.

Nonfunctional Requirement R-2.7Name: Type of ToneDate Created : 2010-10-20 22:22:42Last Modified: 2010-11-11 06:42:50Priority : 4Problem : P-6Goal : G-5

The tone played will be easily recognizable and heard

Nonfunctional Requirement R-2.8Name: Speech Synthesis UnderstandabilityDate Created : 2010-10-20 22:26:13Last Modified: 2010-11-11 06:42:50Priority : 4Problem : P-5Goal : G-5

The Text-to-Speech system will be easy to understand

Nonfunctional Requirement R-2.9Name: Megaphone VolumeDate Created : 2010-10-20 22:39:53Last Modified: 2010-11-11 06:42:50Priority : 4Problem : P-5Goal : G-5

The megaphone will have a high enough volume that others can hear it easily

Nonfunctional Requirement R-2.10Name: Quality of Speech RecognitionDate Created : 2010-10-20 22:42:16Last Modified: 2010-11-11 06:42:50Priority : 4Problem : P-7Goal : G-6

The application will recognize speech correctly at least 90 percent of the time.

67

11.3 Memory

Requirement R-3.1Name: User SchedulesDate Created : 2010-10-20 22:43:48Last Modified: 2010-11-11 06:46:55Priority : 7Problem : P-8Goal : G-7

The application shall allow the user to enter events and alert the user when those eventsoccur.

Issue I-3.1.v0Name: No mention of date and time

How does the user enter the date and time of the event? By what mechanism? In whatformat?


Name: Manual Entry

Description: The application shall allow the user to manually enter the event by typinga date and time.

Positives : Easy to implement. Easy to enter if the user has an exact date in mind.

Negatives : Not very intuitive. Hard for the user to put an exact date to, for example,”next Tuesday”. Leads to user errors in scheduling. Requires a lot of typing for an oldperson.


Name: Calendar Entry

Description: The application shall display a calendar, and the user shall be able toselect a date on the calendar by clicking.

Positives : Easy to use. Easy to enter relative dates (”next Tuesday”). Very fast touse.

Negatives : Hard to enter dates that are far in the future. Can lead to errors andfrustration if the user must flip through several months to schedule an event. Requiresmore implementation.


Name: NL Entry

Description: The application shall allow the user to enter to enter a date and time asnatural language text (e.g. ”this Saturday at 5 in the afternoon”).

Positives : Very intuitive. Easy to see mistakes in the entry.

Negatives : Requires considerable implementation. User is at the mercy of the NLP,which may interpret the date incorrectly. Requires a lot of typing for an old person.

68

Requirement R-3.1.v1Name: Both Calendar and Manual EntryDate Created : 2010-10-20 23:09:56Last Modified: 2010-11-11 06:46:59Priority : 8Problem : P-8Goal : G-7

The application shall allow the user to enter events by either a calendar interface ormanual date and time interface, and alert the user when those events occur.

Alternatives used: A-1, A-2Justification: The NL alternative is simply too difficult and possibly a liability (if it interprets

a date or time incorrectly). A fast and easy interface, such as a calendar, is absolutely necessaryif the user is going to use the application on the spot. An exact interface is necessary to preventuser frustration for entering dates far in the future.

Issue I-3.1.v1Name: Doesn’t cover whether an event can reoccur.

Some events are recurring (”every Thursday at 8 PM”), and a schedule isn’t very usefulif it cannot represent these events.


Name: List of Dates

Description: The user can specify a list of dates that the event reoccurs on.

Positives : Useful if an event only reoccurs on a limited (and small) basis.

Negatives : Adds clutter and bloat. Not useful for most events.


Name: Recurrence Checkboxes

Description: The user can specify whether an event should be triggered again daily,weekly, monthly, or yearly

Positives : Easy to specify when an event reoccurs. Easy to implement.

Negatives : May be confusing to an elderly person: if they want something to trigger” every Sunday ” , it may be confusing to enter ” this Sunday ” for a date, and thenselect ” reoccurs every week ” .


Name: cron Recurrence

Description: The user can specify a recurring event simply by the time of day, day ofthe week, day of the month, or day and month of the year.

Positives : More natural. User simply specifies ”every Thursday” instead of ”thisThursday, and then on a weekly basis after that.”

Negatives : Requires two ways of entering dates. One for non-recurring events, one forrecurring events. This could be very confusing to an elderly person.

69

Requirement R-3.1.v2Name: Recurrence CheckboxesDate Created : 2010-10-20 23:19:24Last Modified: 2010-11-11 06:47:27Priority : 8Problem : P-8Goal : G-7

The application shall allow the user to enter events by either a calendar interface ormanual date and time interface, and alert the user when those events occur. The usercan specify events as recurring on an hourly, daily, weekly, monthly, or yearly basis.

Alternatives used: A-2Justification: Entering a list of dates simply isn’t useful enough to justify the clutter. Specifying

the event by when it recurrs is very natural, but the confusion caused by having a seperate interfacecould confuse and frustrate the user too much. Simply adding some checkboxes for when an eventrecurrs is probably the least confusing overall.

Issue I-3.1.v2Name: “alert the user” is too vague

How does the application get the user’s attention?


Name: Vibrate

Description: An alert shall vibrate the phone.

Positives : Easy for the hearing impaired to notice. Does not require a potentiallyobnoxious or disruptive sound.

Negatives : Doesn’t work very well when the user does not have the phone in physicalcontact with their body. May be frightening to the elderly.


Name: Ringtone

Description: An alert shall play a ringtone.

Positives : Easy for the user to notice.

Negatives : Can be disruptive, and may annoy the user.


Name: Visual Display

Description: An alert shall display the name and time of the alert on the screen.

Positives : Lets the user know what the alert is about.

Negatives : User doesn’t know that the alert has occured unless they are looking at thescreen.


Name: All of the above

Description: An alert shall be configurable to do all of the above.

70

Positives : User has the best chance of knowing that the alert has occured, and knowswhat the alert is about.

Negatives : More clutter in the application configuration.

Requirement R-3.1.v3Name: Configurable AlertsDate Created : 2010-10-20 23:33:36Last Modified: 2010-11-11 06:47:35Priority : 8Problem : P-8Goal : G-7

The application shall allow the user to enter events by either a calendar interface ormanual date and time interface, and alert the user when those events occur. The usercan specify events as recurring on an hourly, daily, weekly, monthly, or yearly basis.The user can configure the alert to either play a ringtone, vibrate, or display the alerton the screen.

Alternatives used: A-4Justification: If the application cannot alert the user effectively, he will not know the alert has

occured. If the user cannot turn off alert features that annoy him, he will not set alerts.

Requirement R-3.1.v3.1Name: Calendar EntryDate Created : 2010-10-20 23:35:52Last Modified: 2010-11-11 06:42:50Priority : 8Problem : P-8Goal : G-7

The application shall allow the user to enter event dates and times by a calendarinterface.

Requirement R-3.1.v3.2Name: Manual EntryDate Created : 2010-10-20 23:36:02Last Modified: 2010-11-11 06:42:50Priority : 8Problem : P-8Goal : G-7

The application shall allow the user to enter event dates and times manually, by typingthem in.

Requirement R-3.1.v3.3Name: Event RecurrenceDate Created : 2010-10-20 23:36:04Last Modified: 2010-11-11 06:42:50Priority : 8Problem : P-8Goal : G-7

71

The application shall allow the user to specify the recurrence of an event as hourly,daily, weekly, monthly, or yearly.

Requirement R-3.1.v3.4Name: Alert on EventDate Created : 2010-10-20 23:36:06Last Modified: 2010-11-11 06:42:50Priority : 8Problem : P-8Goal : G-7

The application shall alert the user when an event’s time and date occur.

Requirement R-3.1.v3.5Name: Alert - VibrationDate Created : 2010-10-20 23:36:08Last Modified: 2010-11-11 06:42:50Priority : 8Problem : P-8Goal : G-7

The application shall be configurable to alert the user by vibrating the phone.

Requirement R-3.1.v3.6Name: Alert - RingtoneDate Created : 2010-10-20 23:36:09Last Modified: 2010-11-11 06:42:50Priority : 8Problem : P-8Goal : G-7

The application shall be configurable to alert the user by playing a ringtone.

Requirement R-3.1.v3.7Name: Alert - Visual DisplayDate Created : 2010-10-21 00:37:55Last Modified: 2010-11-11 06:42:50Priority : 8Problem : P-8Goal : G-7

The application shall be configurable to alert the user by displaying the event on thescreen.

Requirement R-3.2Name: Memo RecorderDate Created : 2010-10-21 00:38:55Last Modified: 2010-11-11 06:42:50Priority : 5Problem : P-9Goal : G-8

The application will allow the user to speak a reminder into the phone, and have itplayed back at any time.

72

11.4 Medical

Requirement R-4.1Name: Alerts About MedicineDate Created : 2010-10-21 06:52:09Last Modified: 2010-11-11 06:51:30Priority : 9Problem : P-10Goal : G-9

The application shall keep a list of the user’s prescriptions and medications. When it istime for the user to take his medications, the system shall alert the user both verballyand visually, and indicate exactly which medication they should take and display apicture of the medication.

Issue I-4.1.v0Name: “Alert verbally and visually” is too vague

It matters how the application alerts the user. If the application just plays a chimeand displays an icon, it may not be apparent to the user what the application is tryingto tell them. They may think that they are getting a phone call.


Name: List single medication

Description: The system shall display a message on the screen saying “It is time foryour medication” and the name of medication will be shown. It shall also display apicture of the individual medication. There shall be a button to dismiss the alert. Theapplication shall also play a ringtone and a prerecorded voice that says “It is time foryour medication.” If there is more than one medication due, the next medication shallbe displayed when the user dismisses this alert.

Positives : This display method is easy to read and understand. The voice will be clearto understand. The user only needs to focus on one medication at a time.

Negatives : Only displaying one medication at a time makes this confusing. Theuser may think that the system is not working because it only displays one of theirmedication. They may also be confused when they dismiss the alert and another popsup.


Name: List multiple medications

Description: The system shall display a message saying “You need to take the followingmedications:” and list all medications that are due at that time. It will play the toneand voice as in (A1). If the user clicks on any one of the medications, the system shallexpand the entry by displaying a picture of the individual medication. Clicking on theexpanded entry shall collapse it again.

Positives : This method makes the notifications less confusing. The user can see all oftheir medications that are due at once.

Negatives : The interface becomes cluttered. The user can lose track of their placein the list of medications (and possibly skip one, or take the same one twice). The

73

user’s fingers may not be steady enough to select the correct medication. The idea ofexpanding entries may not be intuitive to the user.


Name: Vocal alert

Description: The system shall play the vocal alert by using a text-to-speech system tosay “Your medication is due: ” and shall speak the name of the medication.

Positives : The user can hear the name of the medication spoken, which may help them.

Negatives : Text to speech systems can be difficult to understand, and would definitelyhave trouble with complex medication names. The user may not be able to understandwhat the phone says, and be frustrated by it.

Requirement R-4.1.v1Name: List a single medicationDate Created : 2010-10-21 06:59:04Last Modified: 2010-11-11 06:42:50Priority : 9Problem : P-10Goal : G-9

The application shall keep a list of the user’s prescriptions and medications. Whenit is time for the user to take his medications, the system shall alert the user bydisplaying a message on the screen indicating the medication due and display a pictureof the medication. It shall also play a ringtone followed by a prerecorded voice thatwill indicate that medication is due. If the user has more alerts, the application shalldisplay the next one when the user dismisses the current alert.

Alternatives used: A-2Justification: Having a list of medications is too much of a liability: if the user takes a medi-

cation more than once, or misses a medication, it could be very harmful. Also, text to speech canbe very difficult for the elderly to understand, and introducing one would only serve to confuse.

Requirement R-4.1.v1.1Name: List of medicationsDate Created : 2010-10-21 07:00:17Last Modified: 2010-11-11 06:42:50Priority : 9Problem : P-10Goal : G-9

The application shall keep a list of the user’s medications, and when they should betaken.

Requirement R-4.1.v1.2Name: Display MessageDate Created : 2010-10-21 07:00:18Last Modified: 2010-11-11 06:42:50Priority : 9Problem : P-10Goal : G-9

74

When it is time for the user to take a medication, the application shall display a messagethat indicates a single medication is due, and the name of the medication.

Requirement R-4.1.v1.3Name: Auditory MessageDate Created : 2010-10-21 07:00:19Last Modified: 2010-11-11 06:42:50Priority : 7Problem : P-10Goal : G-9

When it is time for the user to take a medication, the application shall play a ringtone,and play a prerecorded voice that vocally indicates that a medication is due.

Requirement R-4.1.v1.4Name: Dismissing an AlertDate Created : 2010-10-21 07:00:19Last Modified: 2010-11-11 06:42:50Priority : 9Problem : P-10Goal : G-9

When an alert occurs, the user shall have a button which shall dismiss the alert.

Requirement R-4.1.v1.5Name: Display Next MedicationDate Created : 2010-10-21 07:00:20Last Modified: 2010-11-11 06:42:50Priority : 9Problem : P-10Goal : G-9

If there is more than one medication due, the next medication shall be displayed whenthe user dismisses this alert.

Requirement R-4.2Name: Alerts when a prescription needs refilledDate Created : 2010-10-21 07:07:28Last Modified: 2010-11-11 06:51:34Priority : 8Problem : P-11Goal : G-10

The application shall keep a list of the user’s prescriptions, and when they are to berefilled. When it comes time for the prescription to need refilled, the user shall havethe option of alerting the user or the user’s caretakers which prescriptions need to berefilled.

Issue I-4.2.v0Name: “Alerts the user’s caretakers” is too vague.

75

It matters how the phone tries to contact to the user’s caregivers–some methods aremore effective than others.


Name: Text Message

Description: The application shall send the contact a text message listing the prescrip-tion that the user needs refilled.

Positives : The contact will likely get the alert immediately, or as soon as possible.

Negatives : The contact may not have a text messaging plan.


Name: Email Message

Description: The application shall send the contact an email message listing the pre-scription that the user needs refilled.

Positives : This method has the least dependencies for a contact to get the message(email is free and easy to get).

Negatives : The user will only get the alert when they next check their email. For somepeople this could be weeks.


Name: Automated Phone Call

Description: The application shall call the contact and play an automated messagesaying, “The user at (phone number), who has listed this number as their contact,needs prescription (prescription name) refilled”

Positives : Since the contact is quite likely to have a phone, they are likely to be able toget the alert and they will get it immediately (or when they next check their voicemail).

Negatives : Contacts may miss the call, and neglect to check their voicemail for sometime. Also, they may hang up immediately upon hearing an automated voice (thinkingit is a telemarketer). It also requires implementation of a text-to-speech interface.


Name: Configurable for All of the Above

Description: The application shall be configurable to do any or all of the above simul-taneously.

Positives : The alternatives involved are fairly disjoint, and could be implementedindependently. The application can appeal to the best of all situations.

Negatives : Requires extra clutter in the application configuration. Requires consider-able extra implementation.

Requirement R-4.2.v1Name: ConfigurableDate Created : 2010-10-21 07:18:25Last Modified: 2010-11-11 06:42:50Priority : 7Problem : P-11Goal : G-10

76

The application shall keep a list of the user’s prescriptions, and when they are to berefilled. When it comes time for the prescription to need refilled, the user shall havethe option of alerting the user or the user’s caretakers which prescriptions need to berefilled. It shall be configurable to update the caretakers by either text message, email,or automated phone call.

Alternatives used: A-4Justification:

Issue I-4.2.v1Name: Sending prescription info is a security risk

Since prescriptions are private information, if the information that the application istrying to send ends up at the wrong recipient, it constitutes a breach of security.


Name: No prescription info

Description: The application does not send the name of the prescription–only that aprescription is due to be refilled.

Positives : More secure: less likelihood of leaking personal information to others ifcontact information is incorrect, or someone other than the intended recipient otherwisegets the alert.

Negatives : The contact will eventually need to know what medication they need topick up. Since this requires the contact to already know the user’s prescriptions, it isnot entirely useful.


Name: Security Question

Description: The application first requires the contact to answer a security questionbefore sending the prescription information

Positives : A random stranger likely cannot get the user’s prescription information(provided the security question is not obvious).

Negatives : People close to the contact may also know the answer, and can get theuser’s private information without his consent. Depending on the method used to alertthe contact, the answer to the question could be cached on their phone (e.g. storedin “Sent Text Messages”). Contacts might find this extra security annoying. Requiresextra configuration on the user’s part.


Name: Password

Description: The application first requires the contact to enter a password before send-ing the prescription information

Positives : Provided the password is secure and is not cached on the contact’s phone,the user’s information is very safe.

Negatives : The contact could forget the password. Still suffers from the possibility ofthe password being saved on the contact’s phone. Contacts may still be frustrated bythe extra security. Requires extra configuration.

77



Description: The application shall be configurable to do any of the above.

Positives : Provides security for the user if they desire it. Disables security if the userdesires that instead.

Negatives : Adds extra clutter to the application configuration. If the user is not surewhat they are doing while configuring the application, it may lead to a security risk.

Requirement R-4.2.v2Name: No prescription dataDate Created : 2010-10-21 07:22:05Last Modified: 2010-11-11 06:42:50Priority : 7Problem : P-11Goal : G-10

The application shall keep a list of the user’s prescriptions, and when they are to berefilled. When it comes time for the prescription to need refilled, the user shall havethe option of alerting the user or the user’s caretakers which prescriptions need to berefilled. It shall be configurable to update the caretakers by either text message, email,or automated phone call, and shall not send any prescription data.

Alternatives used: A-1Justification: It is important to allow the user to configure this; if the method of alert is

inconvenient for the contact, they will not use it. Also, since all of our alternatives for security arevery weak, it is better to not send any private data at all.

Requirement R-4.2.v2.1Name: List of prescriptionsDate Created : 2010-10-21 07:27:44Last Modified: 2010-11-11 06:42:50Priority : 7Problem : P-11Goal : G-10

The application shall keep a list of the user’s prescriptions, and when they are to berefilled.


When a prescription is due to be refilled, the application should trigger an alert.

Requirement R-4.2.v2.3Name: Configuration: Who to alertDate Created : 2010-10-21 07:27:46

78

Last Modified: 2010-11-11 06:42:50Priority : 7Problem : P-11Goal : G-10

The application shall be configurable to either alert the user or alert a contact.

Requirement R-4.2.v2.4Name: Configuration: Text MessageDate Created : 2010-10-21 07:27:47Last Modified: 2010-11-11 06:42:50Priority : 7Problem : P-11Goal : G-10

If configured to alert a contact, the application shall be further configurable to alertthe contact by text message

Requirement R-4.2.v2.5Name: Configuration: Email MessageDate Created : 2010-10-21 07:27:48Last Modified: 2010-11-11 06:42:50Priority : 7Problem : P-11Goal : G-10

If configured to alert a contact, the application shall be further configurable to alertthe contact by email message

Requirement R-4.2.v2.6Name: Configuration: Phone CallDate Created : 2010-10-21 07:27:48Last Modified: 2010-11-11 06:42:50Priority : 5Problem : P-11Goal : G-10

If configured to alert a contact, the application shall be further configurable to alertthe contact by an automated phone call

Requirement R-4.2.v2.7Name: Sending of medication dataDate Created : 2010-10-21 07:27:49Last Modified: 2010-11-11 06:42:50Priority : 7Problem : P-11Goal : G-10

Regardless of the alert method, the application should not send the name or type ofmedication to a contact

79

Requirement R-4.3Name: Alerts when the user does not take medication.Date Created : 2010-10-21 07:39:55Last Modified: 2010-11-11 06:51:39Priority : 9Problem : P-12Goal : G-9

The application shall keep a list of all the user’s medications, and their medicationschedule. When the application alerts the user that he should take his medication, itrequires confirmation that the user has received the alert. Otherwise the applicationtriggers an Emergency Contact Alert stating that the user may not have received thealert to take his medication, and which medications he may not have taken.

Issue I-4.3.v0Name: Sending medication info is a security risk

The medications that the user is taking is private information. Should this informationbe disclosed to the wrong person, it would constitute a security risk.


Name: No Medication Info

Description: The application does not send the name of the medication. It only alertsthat the user may have missed a medication.

Positives : Leaks little personal information

Negatives : The contact may want to know which medication might have been skipped.For instance, missing an osteoporosis drug is a minor event, but missing a Parkinson’sdrug can be a major issue.


Name: Medication Priorities

Description: The application shall be configurable to set priorities to medications, andwill only send the contact the priority number of the medication that might have beenmissed.

Positives : The contact can know whether a medication was important or not, but noprivate information is leaked.

Negatives : Requires the user to tag a priority to each medication. There are no guar-antees that a medication will be tagged correctly. Also causes additional configurationclutter.



Description: The application shall be configurable to do any of the above and config-urable to actually send the medication name.

Positives : Allows the user to choose whether security is an issue or not.

Negatives : Causes considerable configuration clutter and bloat.

80

Requirement R-4.3.v1Name: Configurable to either send medication name, or not.Date Created : 2010-10-21 08:03:08Last Modified: 2010-11-11 06:42:50Priority : 9Problem : P-12Goal : G-9

The application shall keep a list of all the user’s medications, and their medicationschedule. When the application alerts the user that he should take his medication, itrequires confirmation that the user has received the alert. Otherwise the applicationtriggers an Emergency Contact Alert stating that the user may not have received thealert to take his medication. The application shall be configurable to send medicationdata to the emergency contact.

Alternatives used: A-3Justification: Assigning priorities to medications is too error-prone and difficult. However, if

an elderly person constantly misses a trivial medicine, then the contact might stop responding tothe user’s alerts if the alert does not contain the medicine involved. It is important that we cancater to this type of user, while still providing the ability to be secure.

Requirement R-4.3.v1.1Name: List of MedicationsDate Created : 2010-10-21 08:04:29Last Modified: 2010-11-11 06:42:50Priority : 9Problem : P-12Goal : G-9

The application shall keep a list of the user’s medications, and their dosage schedule.

Requirement R-4.3.v1.2Name: Confirmation of AlertDate Created : 2010-10-21 08:04:30Last Modified: 2010-11-11 06:42:50Priority : 9Problem : P-12Goal : G-9

When the application alerts the user that he should take his medicine, it shall requireconfirmation that the user received the alert.

Requirement R-4.3.v1.3Name: Confirmation Failed AlertsDate Created : 2010-10-21 08:04:31Last Modified: 2010-11-11 06:42:50Priority : 9Problem : P-12Goal : G-9

If the user does not confirm, the application shall send an alert to the user’s caregiver.

81

Requirement R-4.3.v1.4Name: Configuration: Medication InfoDate Created : 2010-10-21 08:04:31Last Modified: 2010-11-11 06:42:50Priority : 9Problem : P-12Goal : G-9

The alert shall be configurable to either send medication data, or not send medicationdata to the caregiver.

Requirement R-4.4Name: Listing of user’s current medicationsDate Created : 2010-10-21 08:07:50Last Modified: 2010-11-11 06:51:43Priority : 7Problem : P-13Goal : G-11

The application shall list all the medications that the user is currently taking, whenthe user should be taking them, and what medications should currently be in the user’ssystem.

Issue I-4.4.v0Name: No mention of security

Unfettered access to the user’s medicine data is a significant security risk. Just anyoneshould not be able to read the user’s private data without being authenticated first.


Name: Password

Description: The user must enter a password to access the medical data.

Positives : Easy to implement. Not too difficult to understand. Low - High Security.

Negatives : The user has to remember a password. If the user is using this applicationbecause they have memory problems, the entire application is rendered pointless. Theuser may also choose a password that is too easy to guess.


Name: Biometrics

Description: The user must use some biometric sensor to access medical data.

Positives : Med - High Security (depending on biometric type and the device beingused). No need to remember anything.

Negatives : Requires a biometric sensor on the phone. The camera could be used inconjunction with facial recognition software, but this could easily be fooled. The usermay also be confused by the sensor, and not know how to use it.



82

Description: The user must answer a security question to access the medical data.

Positives : The user is more likely to remember this than a password.

Negatives : People close to the user could likely know the answer to the question. Theuser may still have trouble remembering. They may also be confused when they ask fortheir medical data, and instead are confronted with a personal question. The questioncould be ambiguous, and the user may answer differently at different times.

Requirement R-4.4.v1Name: Security QuestionDate Created : 2010-10-21 08:17:13Last Modified: 2010-11-11 06:42:50Priority : 7Problem : P-13Goal : G-11

The application shall list all the medications that the user is currently taking, whenthe user should be taking them, and what medications should currently be in the user’ssystem. The system shall only list this information if the user first correctly answers asecurity question.

Alternatives used: A-3Justification: It is important that the user be able to access their medical data when they need

to, and for the elderly, remembering a password is simply too difficult sometimes. Also, restrictingour application to only platforms with biometric sensors is simply too restrictive.

Issue I-4.4.v1Name: No access for medical professionals

If the user is incapacitated, there will be no one who can answer the security question.If this is an emergency, a doctor may need to know what medications the user is takingbefore he can be treated.


Name: DEA ID

Description: The application will list the medicine data if the user enters a valid DEAID number.

Positives : Only individuals trusted with handling drugs have DEA ID numbers, sothey are unlikely to be after the user’s prescription drugs.

Negatives : Does not solve the issue of whether the individual with the DEA ID is some-one the user trusts. Also, authenticating with a DEA database could be a feasibilityissue.


Name: Trusted SSN

Description: The application will list the medicine data when someone enters a trustedSSN.

Positives : SSN’s are not typically public knowledge, so the person who enters the SSNis probably the person that the user trusts.

83

Negatives : An untrusted user could get access to the trusted user’s SSN. The user hasaccess to someone else’s SSN, which is a security risk for that person. This trustedindividual may not be present in an emergency to unlock the medical data.


Name: Easily Accessible Security Answer

Description: The application’s security question will always be some piece of privateinformation that user would likely have on them at any time (e.g. SSN or DL number).

Positives : Few people should know this information outside the user, but the useroften has it in a purse or wallet. If the user were incapacitated, the information wouldlikely be close at hand.

Negatives : If someone were motivated enough, the answer to the security questionwould be easy to obtain. Also, this information may not be always present on the user.

Requirement R-4.4.v2Name: The security question is information that the user would have on them.Date Created : 2010-10-21 08:21:36Last Modified: 2010-11-11 06:42:50Priority : 7Problem : P-13Goal : G-11

The application shall list all the medications that the user is currently taking, whenthe user should be taking them, and what medications should currently be in the user’ssystem. The system shall only list this information if the user first correctly answers asecurity question. The system shall only allow security questions that could likely beanswered with information that the user could have on his person at any time.

Alternatives used: A-3Justification: For simplicity, this is the easiest way to ensure that a doctor could get the user’s

medical history on the spot if the user is incapacitated.

Requirement R-4.4.v2.1Name: Current Medication in SystemDate Created : 2010-10-21 08:22:14Last Modified: 2010-11-11 06:42:50Priority : 7Problem : P-13Goal : G-11

Given the user’s medication schedule and whether he has confirmed taking them, theapplication shall calculate what medicines should now be in the user’s body

Requirement R-4.4.v2.2Name: Medication ListingDate Created : 2010-10-21 08:22:15Last Modified: 2010-11-11 06:42:50Priority : 7Problem : P-13Goal : G-11

84

The application shall be capable of listing all medications that the user is taking, andwhich medications that the user probably has in their system.





Requirement R-4.5Name: Listing of user’s medical historyDate Created : 2010-10-21 08:24:24Last Modified: 2010-11-11 06:51:46Priority : 7Problem : P-14Goal : G-11

The user, or user’s caretakers shall be able to enter the user’s medical history into thephone. The application shall have the capability to list this data.

Issue I-4.5.v0Name: No mention of security

Unfettered access to the user’s medical history is a significant security risk. Just anyoneshould not be able to read the user’s private data without being authenticated first.


Name: Password

Description: The user must enter a password to access the medical history.

Positives : Easy to implement. Not too difficult to understand. Low - High Security.

Negatives : The user has to remember a password. If the user is using this applicationbecause they have memory problems, the entire application is rendered pointless. Theuser may also choose a password that is too easy to guess.

85


Name: Biometrics

Description: The user must use some biometric sensor to access medical history.

Positives : Med - High Security (depending on biometric type and the device beingused). No need to remember anything.

Negatives : Requires a biometric sensor on the phone. The camera could be used inconjunction with facial recognition software, but this could easily be fooled. The usermay also be confused by the sensor, and not know how to use it.



Description: The user must answer a security question to access the medical history.

Positives : The user is more likely to remember this than a password.

Negatives : People close to the user could likely know the answer to the question. Theuser may still have trouble remembering. They may also be confused when they ask fortheir medical data, and instead are confronted with a personal question. The questioncould be ambiguous, and the user may answer differently at different times.

Requirement R-4.5.v1Name: The user must answer a security question to access the medical history.Date Created : 2010-10-21 08:27:54Last Modified: 2010-11-11 06:42:50Priority : 7Problem : P-14Goal : G-11

The user, or user’s caretakers shall be able to enter the user’s medical history into thephone. The application shall list this data if the user correctly enters the answer to asecurity question.



Issue I-4.5.v1Name: No access for medical professionals

If the user is incapacitated, there will be no one who can answer the security question.If this is an emergency, a doctor may need to know any medical conditions that theuser has before he can be treated.


Name: DEA ID

Description: The application will list the medical history if the user enters a valid DEAID number.

Positives : Only individuals trusted with handling drugs have DEA ID numbers, sothey are unlikely to be after the user’s prescription drugs.

86

Negatives : Does not solve the issue of whether the individual with the DEA ID is some-one the user trusts. Also, authenticating with a DEA database could be a feasibilityissue.


Name: Trusted SSN

Description: The application will list the medical history when someone enters a trustedSSN.

Positives : SSN’s are not typically public knowledge, so the person who enters the SSNis probably the person that the user trusts.

Negatives : An untrusted user could get access to the trusted user’s SSN. The user hasaccess to someone else’s SSN, which is a security risk for that person. This trustedindividual may not be present in an emergency to unlock the medical data.


Name: Easily Accessible Security Answer

Description: The application’s security question will always be some piece of privateinformation that user would likely have on them at any time (e.g. SSN or DL number).

Positives : Few people should know this information outside the user, but the useroften has it in a purse or wallet. If the user were incapacitated, the information wouldlikely be close at hand.

Negatives : If someone were motivated enough, the answer to the security questionwould be easy to obtain. Also, this information may not be always present on the user.

Requirement R-4.5.v2Name: The security question is information that the user would have on them.Date Created : 2010-10-21 08:30:27Last Modified: 2010-11-11 06:42:50Priority : 7Problem : P-14Goal : G-11

The user, or user’s caretakers shall be able to enter the user’s medical history into thephone. The application shall list this data if the user correctly enters the answer to asecurity question. The system shall only allow security questions that could likely beanswered with information that the user could have on his person at any time.



Requirement R-4.5.v2.1Name: Entering Medical HistoryDate Created : 2010-10-21 08:31:11Last Modified: 2010-11-11 06:42:50Priority : 7Problem : P-14Goal : G-11

The user shall be able to list his medical history into the application.

87

Requirement R-4.5.v2.2Name: Listing Medical HistoryDate Created : 2010-10-21 08:31:12Last Modified: 2010-11-11 06:42:50Priority : 7Problem : P-14Goal : G-11

The application shall be capable of listing the user’s medical history on the screen.





Requirement R-4.6Name: Fast Interface to DoctorsDate Created : 2010-10-21 08:33:40Last Modified: 2010-11-11 06:51:49Priority : 7Problem : P-15Goal : G-12

The application shall display all of the user’s doctors, along with a button to call them.

Issue I-4.6.v0Name: Not specific on how the doctors will be displayed

“display all the user’s doctors” is too vague. Are all the doctors listed on one page?On separate pages?

88


Name: One doctor per page

Description: The application shall list each doctor on separate page. The user shall beable to navigate back and forth between pages.

Positives : The information about the doctor would be easy to read, not cramped orcluttered.

Negatives : With a lot of doctors, it could take a while to find the one the user wants.


Name: All doctors on one page

Description: The application shall list all doctors on a single page by name. The usercan select the doctor they want, and the application shall expand the entry to showmore information about the doctor, and to display a ‘call’ button.

Positives : More efficient interface.

Negatives : Interface is hard to read, and difficult for an old person’s less-than-nimblefingers.


Name: Search

Description: The application shall have a search interface for the doctor’s name

Positives : Extremely fast way of finding the doctor.

Negatives : The user must be able to recall the doctor’s name. Perhaps not the mostintuitive way from an old person’s perspective.

Requirement R-4.6.v1Name: One doctor per pageDate Created : 2010-10-21 08:39:44Last Modified: 2010-11-11 06:42:50Priority : 7Problem : P-15Goal : G-12

The application shall provide an interface to list the user’s doctors. The applicationshall display one doctor per page, and the user shall be able to navigate back and forthbetween pages. Each page shall have a button to call the doctor.

Alternatives used: A-1Justification: If the user is intimidated by a long list of names or a search bar, he will probably

not use the feature.

Issue I-4.6.v1Name: Elderly forget names

There is no guarantee the elderly can remember the doctor’s name when they want tocall them,

89


Name: Doctor’s picture

Description: The application shall display the doctor’s picture on each page

Positives : The user may forget the doctor’s name, but they are less likely to forget theface

Negatives : The user or the user’s caregiver has to add the doctor’s picture to the phone

Requirement R-4.6.v2Name: One doctor per page with the doctor’s pictureDate Created : 2010-10-21 08:46:11Last Modified: 2010-11-11 06:42:50Priority : 7Problem : P-15Goal : G-12

The application shall provide an interface to list the user’s doctors. The applicationshall display one doctor per page, and the user shall be able to navigate back and forthbetween pages. Each page shall have a button to call the doctor, and the doctor’spicture.

Alternatives used: A-1Justification: The address book is useless if the user cannot remember a doctor’s name.

Issue I-4.6.v2Name: Not specific on what information is displayed on each page

It matters what information is actually on the page. The requirement only lists thedoctor’s name and picture. More information would be useful.


Name: Office Address

Description: The page shall display the doctor’s office address

Positives : The information is useful if the user has an appointment with the doctor.

Negatives : Adds clutter to the page. Requires additional configuration by adding theaddress.


Name: Doctor Specialization

Description: The page shall display the doctor’s specialization

Positives : The user might have trouble remembering who his cardiologist is and whohis urologist is

Negatives : Adds clutter to the page. Requires some additional configuration.


Name: Phone Number

Description: The page shall display the doctor’s phone number

Positives : Useful if the user wants to share the number

90

Negatives : Adds clutter to the page.


Name: All of the Above

Description: The page shall display all of the above, but only displays what is configured

Positives : Maximizes the information that the user has about the doctor, but avoidsclutter if the user has not configured something

Negatives : Maximizes clutter.

Requirement R-4.6.v3Name: The page shall display all information availableDate Created : 2010-10-21 08:48:37Last Modified: 2010-11-11 06:42:50Priority : 7Problem : P-15Goal : G-12

The application shall provide an interface to list the user’s doctors. The applicationshall display one doctor per page, and the user shall be able to navigate back and forthbetween pages. Each page shall have a button to call the doctor. If they are entered,the page shall also display the doctor’s picture, and the doctor’s name, address andspecialization. If any of these things are not entered, the application shall not displaythem.

Alternatives used: A-4Justification: More information is better: the user might need it. Even if it is harder to read.

However, there is no point in unneccessary clutter, unconfigured entries should not be displayed.

Requirement R-4.6.v3.1Name: List DoctorsDate Created : 2010-10-21 08:51:42Last Modified: 2010-11-11 06:42:50Priority : 7Problem : P-15Goal : G-12

The application shall provide an interface to list the user’s doctors

Requirement R-4.6.v3.2Name: One per pageDate Created : 2010-10-21 08:51:43Last Modified: 2010-11-11 06:42:50Priority : 7Problem : P-15Goal : G-12

The application shall display one doctor per page

91

Requirement R-4.6.v3.3Name: Information DisplayedDate Created : 2010-10-21 08:51:44Last Modified: 2010-11-11 06:42:50Priority : 7Problem : P-15Goal : G-12

Each page shall display the doctor’s picture, phone number, address, and specializationif they are configured.

Requirement R-4.6.v3.4Name: Information Not DisplayedDate Created : 2010-10-21 08:51:45Last Modified: 2010-11-11 06:42:50Priority : 6Problem : P-15Goal : G-12

Each page shall not display the doctor’s picture, phone number, address, and special-ization if they are not configured.

Requirement R-4.6.v3.5Name: Call DoctorDate Created : 2010-10-21 08:51:45Last Modified: 2010-11-11 06:42:50Priority : 7Problem : P-15Goal : G-12

Each page shall have a button that shall call the doctor.

Requirement R-4.6.v3.6Name: Page NavigationDate Created : 2010-10-21 08:51:46Last Modified: 2010-11-11 06:42:50Priority : 7Problem : P-15Goal : G-12

The user shall be able to navigate back and forth between pages.

Requirement R-4.7Name: Pulse MonitorDate Created : 2010-10-21 08:54:27Last Modified: 2010-11-11 06:42:50Priority : 4Problem : P-16Goal : G-13

The application shall be capable of monitoring the user’s pulse when they require.

92

11.5 Location

Requirement R-5.1Name: Alerts about locationDate Created : 2010-10-21 08:59:57Last Modified: 2010-11-11 06:42:50Priority : 6Problem : P-17Goal : G-14

The device will be able to display location based on GPS or cell phone signal.

Issue I-5.1.v0Name: “Alerts about location” is too vague

How the system alerts the user or caregiver is not defined. Elderly persons suffer fromany number or ailments, each of which can limit recognition of what is displayed on thesystem. In order to properly cover this, descript and useful set of notifications must beaddressed. Additionally, how the caregiver is alerted is not defined.


Name: Map Display

Description: The system shall display on the touch screen a simple graphical map withthe users location indicated by an icon.

Positives : This makes the location easy to read by the individual user.

Negatives : The GPS service may be unavailable or not functioning. If the user is inan area without Cell coverage, how would the systems location be obtained.


Name: Notify Caregiver

Description: The system shall notify the designated caregiver by means of configurablenotification.

Positives : This allows for multiple methods of alert to be used when informing acaregiver of a user’s location.

Negatives : The GPS service may be unavailable or not functioning. If the user is inan area without Cell coverage, how would the systems be able to notify the caregiver?


Name: Existing Interface

Description: Use a market ready interface currently available.

Positives : The location mapping and tracking interfaces already exist. The systemmay also already be recognizable by the user.

Negatives : Integrating third party applications will remove the seamless feel of theHOPE application. Some interfaces may not provide exactly what is desired.

93




Requirement R-5.2Name: Alerts when the user leaves a designated areaDate Created : 2010-10-21 09:09:23Last Modified: 2010-11-11 06:42:50Priority : 6Problem : P-17Goal : G-14

When the user leaves a designated geographical area, an alert (containing the user’slocation) will be sent to an emergency contact. The application will continue to alertthe emergency contact until the contact responds that the application should stop.

Issue I-5.2.v0Name: “Alerts when the user leaves a designated area” is too vague

How the system alerts the caregiver is not defined. Multiple methods of communicationare available and can be used for notifications.



Description: The system will notify the designated caregiver by means of configurablenotification when a user leaves a designated area.

Positives : This allows for multiple methods of alert when notifying the caregiver ofthe user’s location.



Name: Web Server

Description: The system will report GPS coordinates to a web server and have thatdatabase instead of the phone provide functionality to determine if outside a designatedarea. This server can ping or alert phone and caregiver.

Positives : This allows for multiple methods of alert when notifying the caregiver ofthe user’s location.

Negatives : Requires considerable extra implementation

94

Requirement R-5.2.v1Name: Notify by configurable notificationDate Created : 2010-10-21 09:11:40Last Modified: 2010-11-11 06:42:50Priority : 6Problem : P-17Goal : G-14

When the user leaves a designated geographical area, an alert (containing the user’slocation) will be sent to an emergency contact. The application will continue to alertthe emergency contact until the contact responds that the application should stop. Themethod by which the application alerts the caregiver will be configurable to be a textmessage, email, or automated phone call.

Alternatives used: A-1Justification: If the method by which the application alerts the contact is inconvenient, it will

not be used.



Requirement R-5.2.v1.2Name: Alert LocationDate Created : 2010-10-21 09:12:20Last Modified: 2010-11-11 06:42:50Priority : 6Problem : P-17Goal : G-14





95






Requirement R-5.3Name: Alerts when the user enters a restricted areaDate Created : 2010-10-21 09:14:55Last Modified: 2010-11-11 06:42:50Priority : 5Problem : P-17Goal : G-14

When the user enters a restricted geographical area, an alert (containing the user’slocation) will be sent to an emergency contact. The application will continue to alertthe emergency contact until the contact responds that the application should stop.

Issue I-5.3.v0Name: “Alerts when the user enters a restricted area” is too vague

How the system alerts the caregiver is not defined. Multiple methods of communicationare available and can be used for notifications.



Description: The system shall notify the designated caregiver by means of configurablenotification when a user leaves a designated area.

Positives : This allows for multiple methods of alert to be used when informing acaregiver of a user’s location.


96


Name: Web Service

Description: The system shall report GPS coordinates to a web server and have thatdatabase instead of the phone provide functionality to determine if outside a designatedarea. This server can ping or alert phone and caregiver.

Positives : This allows for multiple methods of alert to be used when informing acaregiver of a user’s location. It also allows functionality that with constant web updatethe last known location can be sent when a signal is lost.

Negatives : Requires considerable extra implementation

Requirement R-5.3.v1Name: Notify by configurable notificationDate Created : 2010-10-21 09:17:25Last Modified: 2010-11-11 06:42:50Priority : 5Problem : P-17Goal : G-14

When the user enters a restricted geographical area, an alert (containing the user’slocation) will be sent to an emergency contact. The application will continue to alertthe emergency contact until the contact responds that the application should stop. Themethod by which the application alerts the caregiver will be configurable to be a textmessage, email, or automated phone call.

Alternatives used: A-1Justification: If the method by which the application alerts the contact is inconvenient, it will

not be used.



Requirement R-5.3.v1.2Name: LocationDate Created : 2010-10-21 09:19:10Last Modified: 2010-11-11 06:42:50Priority : 5Problem : P-17Goal : G-14


97









Requirement R-5.4Name: Directing user to a locationDate Created : 2010-10-21 09:21:55Last Modified: 2010-11-11 06:42:50Priority : 6Problem : P-17Goal : G-14

If the user leaves a designated area, or the user simply specifies that he is lost, thesystem will verbally and visually offer to help, and then guide the user on a step bystep basis until he is back at a designated area.

98

Requirement R-5.4.v0.1Name: Offer to helpDate Created : 2010-10-21 09:22:41Last Modified: 2010-11-11 06:42:50Priority : 6Problem : P-17Goal : G-14

When the user leaves a designated geographical area, the system will offer to help.

Requirement R-5.4.v0.2Name: Ask for helpDate Created : 2010-10-21 09:22:42Last Modified: 2010-11-11 06:42:50Priority : 6Problem : P-17Goal : G-14

When the user indicates to the application that he is lost, the system will offer to help.

Requirement R-5.4.v0.3Name: Offer typeDate Created : 2010-10-21 09:22:42Last Modified: 2010-11-11 06:42:50Priority : 6Problem : P-17Goal : G-14

The system’s offer to help will be both verbal and visual


The system will continue to guide the user, step by step, until he is back in a designatedarea

Requirement R-5.5Name: Identifying when the user is lostDate Created : 2010-10-21 09:24:16Last Modified: 2010-11-11 06:42:50Priority : 6Problem : P-17Goal : G-14

The application will notice when the user has moved around an area at car speeds, buthas not stopped for any lengthy period of time, and yet has not left the area for sometime. It will then send a message to the user’s emergency contact that the user maybe lost. If the emergency contact responds to the message, the system will send themthe location of the user.

99

Requirement R-5.5.v0.1Name: NoticingDate Created : 2010-10-21 09:25:29Last Modified: 2010-11-11 06:42:50Priority : 6Problem : P-17Goal : G-14

The application will notice when the user has moved around an area at car speeds, buthas not stopped for any lengthy period of time, and yet has not left the area for sometime.


If the application determines that the user is lost, it will send an alert to the user’semergency contact that the user may be lost.

Requirement R-5.5.v0.3Name: Send LocationDate Created : 2010-10-21 09:25:30Last Modified: 2010-11-11 06:42:50Priority : 6Problem : P-17Goal : G-14

If the emergency contact responds to the alert, the application will send the user’slocation to the contact

Requirement R-5.6Name: Identifying when the user may have lost the phoneDate Created : 2010-10-21 09:26:42Last Modified: 2010-11-11 06:42:50Priority : 6Problem : P-18Goal : G-15

The application will notice when the phone has not moved, nor been interacted withfor some time. It will then send an alert to a designated contact stating that the usermay have lost their phone.

Issue I-5.6.v0Name: “some time” is too vague

This amount of time is unverifiable. It needs to be a specific amount of time.

100


Name: One Day

Description: After one day, the application will send an alert

Positives : If the phone is actually lost, the user will find out about it quickly. Fastermay definitely be better depending on where the phone is lost.

Negatives : There will likely be many false-alarms depending on the activity level ofthe user. Many false alarms will lead to the contact ignoring the alerts.


Name: Two Days

Description: After two days, the application will send an alert

Positives : The user still will find out fairly quickly that the phone is lost.

Negatives : There will still likely be some false alarms.


Name: One Week

Description: After one week, the application will send an alert

Positives : The phone has a very high probability of being lost if it has not been usedor moved in a week.

Negatives : The battery may be dead by then. Someone (other than the user) mayfind the phone in that long interval and keep it. Many things can happen in a week,the user may need the phone.


Name: Configurable

Description: The length of time will be configurable by the user

Positives : The length of time can be tailored to the user’s activity level

Negatives : The user can choose the wrong length of time. Causes more clutter in theapplication configuration. Requires additional configuration.

Requirement R-5.6.v1Name: Configurable length of timeDate Created : 2010-10-21 09:31:42Last Modified: 2010-11-11 06:42:50Priority : 6Problem : P-18Goal : G-15

The application will notice when the phone has not moved, nor been interacted withfor a user-configurable length of time. It will then send an alert to a designated contactstating that the user may have lost their phone.

Alternatives used: A-4Justification: We can make few assumptions about the activity level of the user; it is best they

choose for themselves.

Requirement R-5.6.v1.1

101

Name: Noticing UseDate Created : 2010-10-21 09:32:07Last Modified: 2010-11-11 06:42:50Priority : 6Problem : P-18Goal : G-15

The application will notice when the phone has not moves, nor been interacted withfor a user-configurable length of time.


If the application determines that the phone has been lost, it will send an alert to adesignated contact. The alert will contain the phone’s location.

Nonfunctional Requirement R-5.7Name: Map ReadabilityDate Created : 2010-10-21 09:33:01Last Modified: 2010-11-11 06:42:50Priority : 6Problem : P-17Goal : G-14

The map application will be easy to read, and easy to understand for someone who isold.

Nonfunctional Requirement R-5.8Name: Map AccuracyDate Created : 2010-10-21 09:33:40Last Modified: 2010-11-11 06:42:50Priority : 6Problem : P-17Goal : G-14

The map application will be accurate as to the user’s location.

Nonfunctional Requirement R-5.9Name: Map PrecisionDate Created : 2010-10-21 09:34:15Last Modified: 2010-11-11 06:42:50Priority : 6Problem : P-17Goal : G-14

The map application will be precise as to the user’s location.

102

11.6 Family/User Web Services

Requirement R-6.1Name: Web service allowing remote configuration of app settings.Date Created : 2010-10-21 09:35:17Last Modified: 2010-11-11 06:42:50Priority : 7Problem : P-19Goal : G-16

After logging in to the web service and authenticating, the user may remotely selectanything from the phone configuration, and modify it

Requirement R-6.2Name: Web Service Contact ConfigurationDate Created : 2010-10-21 09:35:22Last Modified: 2010-11-11 06:42:50Priority : 6Problem : P-19Goal : G-16

The service will allow the user to read any contact information, and may add or changeany names, addresses, phone numbers, or pictures

Requirement R-6.3Name: Web Service Region ConfigurationDate Created : 2010-10-21 09:35:24Last Modified: 2010-11-11 06:42:50Priority : 7Problem : P-19Goal : G-16

The service will allow the user to view any designated or restricted locations, and willbe able to modify them or add new ones

Issue I-6.3.v0Name: Not specific on how to display or select regions.

How the web service shall show regions and how the user will enter new regions isunclear.


Name: Coordinates

Description: The web service will accept a list of GPS coordinates to define a region,and will display a list of regions as text with associated GPS coordinates.

Positives : Simple to design and implement. Very exact.

Negatives : Not everyone will have access to GPS data. Not user-friendly at all.


103

Name: GUI

Description: The web service will provide a GUI map view with controls to zoom,move, and draw a region.

Positives : Easier to use, far more intuitive.

Negatives : Implementing a map viewer will be difficult, and will require a mapdatabase.

Requirement R-6.3.v1Name: GUI mapDate Created : 2010-10-21 09:40:39Last Modified: 2010-11-11 06:42:50Priority : 6Problem : P-19Goal : G-16

The service will allow the user to view any designated or restricted locations, via a mapinterface, which will support zooming and panning. The application will allow the userto edit areas by drawing on this map.

Alternatives used: A-Justification:

Requirement R-6.3.v1.1Name: Display areasDate Created : 2010-10-21 09:41:12Last Modified: 2010-11-11 06:42:50Priority : 6Problem : P-19Goal : G-16

The service will display all restricted and designated areas

Requirement R-6.3.v1.2Name: Edit areasDate Created : 2010-10-21 09:41:13Last Modified: 2010-11-11 06:42:50Priority : 6Problem : P-19Goal : G-16

The service will allow the user to edit any restricted or designated area

Requirement R-6.3.v1.3Name: GUIDate Created : 2010-10-21 09:41:13Last Modified: 2010-11-11 06:42:50Priority : 6Problem : P-19Goal : G-16

The service will display areas on a map, which has controls to zoom and pan

104

Requirement R-6.3.v1.4Name: DrawingDate Created : 2010-10-21 09:41:14Last Modified: 2010-11-11 06:42:50Priority : 6Problem : P-19Goal : G-16

The service will edit and add areas by having the user draw on a map

Requirement R-6.4Name: Web Service Alert ConfigurationDate Created : 2010-10-21 09:43:04Last Modified: 2010-11-11 06:42:50Priority : 7Problem : P-19Goal : G-16

The service will allow the user to view any alert configuration, and can modify it

Requirement R-6.4.v0.1Name: Leave areaDate Created : 2010-10-21 09:44:12Last Modified: 2010-11-11 06:42:50Priority : 6Problem : P-19Goal : G-16

The service will allow the user to view and configure whether the application sendsalerts when the user leaves a designated area

Requirement R-6.4.v0.2Name: Enter AreaDate Created : 2010-10-21 09:44:13Last Modified: 2010-11-11 06:42:50Priority : 6Problem : P-19Goal : G-16

The service will allow the user to view and configure whether the application sendsalerts when the user enters a restricted area

Requirement R-6.4.v0.3Name: Location ContactDate Created : 2010-10-21 09:44:14Last Modified: 2010-11-11 06:42:50Priority : 6Problem : P-19Goal : G-16

The service will allow the user to view and configure the designated contact for locationalerts

105

Requirement R-6.4.v0.4Name: Location Alert TypeDate Created : 2010-10-21 09:44:16Last Modified: 2010-11-11 06:42:50Priority : 5Problem : P-19Goal : G-16

The service will allow the user to view and configure what type of alert is to be usedfor location alerts

Requirement R-6.4.v0.5Name: Alert on LostDate Created : 2010-10-21 09:44:17Last Modified: 2010-11-11 06:42:50Priority : 6Problem : P-19Goal : G-16

The service will allow the user to view and configure whether the application sendsalerts when the user appears lost

Requirement R-6.4.v0.6Name: Alert on Lost PhoneDate Created : 2010-10-21 09:44:18Last Modified: 2010-11-11 06:42:50Priority : 6Problem : P-19Goal : G-16

The service will allow the user to view and configure whether the application sendsalerts when it thinks that the phone is lost

Requirement R-6.4.v0.7Name: Lost Time ConfigDate Created : 2010-10-21 09:44:19Last Modified: 2010-11-11 06:42:50Priority : 6Problem : P-19Goal : G-16

The service will allow the user to view and configure the length of time by which theapplication gauges that the phone is lost

Requirement R-6.4.v0.8Name: Medication AlertsDate Created : 2010-10-21 09:44:19Last Modified: 2010-11-11 06:42:50Priority : 6Problem : P-19Goal : G-16

106

The service will allow the user to view and configure whether the application sendsalerts when the user’s medication is due

Requirement R-6.4.v0.9Name: Medication Confirm AlertsDate Created : 2010-10-21 09:44:21Last Modified: 2010-11-11 06:42:50Priority : 6Problem : P-19Goal : G-16

The service will allow the user to view and configure whether the application sendsalerts to a contact when the user does not confirm that they took their medication.

Requirement R-6.4.v0.10Name: Missed Medication ContactDate Created : 2010-10-21 09:44:21Last Modified: 2010-11-11 06:42:50Priority : 6Problem : P-19Goal : G-16

The service will allow the user to view and configure the designated contact for missedmedication.


The service will allow the user to view and configure whether the application sendsalerts when the user’s prescription is due to be refilled

Requirement R-6.4.v0.12Name: Prescription Alert ContactDate Created : 2010-10-21 09:44:23Last Modified: 2010-11-11 06:42:50Priority : 6Problem : P-19Goal : G-16

The service will allow the user to view and configure whether the application sendsalerts to a designated contact when a prescription needs refilled.

Requirement R-6.4.v0.13Name: Prescription ContactDate Created : 2010-10-21 09:44:24Last Modified: 2010-11-11 06:42:50Priority : 6Problem : P-19Goal : G-16

107

The service will allow the user to view and configure whether the designated contactfor prescription refills.

Requirement R-6.5Name: Web Service Medical HistoryDate Created : 2010-10-21 09:50:18Last Modified: 2010-11-11 06:42:50Priority : 7Problem : P-19Goal : G-16

The service will allow the user to view their medical history and modify it

Requirement R-6.6Name: Web Service Medicine ConfigurationDate Created : 2010-10-21 09:51:05Last Modified: 2010-11-11 06:42:50Priority : 7Problem : P-19Goal : G-16

The service will allow the user to view their medication list, and modify it

Requirement R-6.6.v0.1Name: Which MedicationsDate Created : 2010-10-21 09:51:53Last Modified: 2010-11-11 06:42:50Priority : 7Problem : P-19Goal : G-16

The service will allow the user to view and configure which medications they are taking.

Requirement R-6.6.v0.2Name: DosageDate Created : 2010-10-21 09:51:54Last Modified: 2010-11-11 06:42:50Priority : 7Problem : P-19Goal : G-16

The service will allow the user to view and configure the dosage of a medication.

Requirement R-6.6.v0.3Name: ScheduleDate Created : 2010-10-21 09:51:54Last Modified: 2010-11-11 06:42:50Priority : 7Problem : P-19Goal : G-16

108

The service will allow the user to view and configure the schedule of a medication.

Requirement R-6.7Name: Web Service Prescription ConfigurationDate Created : 2010-10-21 09:53:10Last Modified: 2010-11-11 06:42:50Priority : 7Problem : P-19Goal : G-16

The service will allow the user to view their prescription list, and modify it

Requirement R-6.7.v0.1Name: Which PrescriptionsDate Created : 2010-10-21 09:53:42Last Modified: 2010-11-11 06:42:50Priority : 7Problem : P-19Goal : G-16

The service will allow the user to view and configure which prescriptions they currentlyhave.

Requirement R-6.7.v0.2Name: End DateDate Created : 2010-10-21 09:53:42Last Modified: 2010-11-11 06:42:50Priority : 7Problem : P-19Goal : G-16

The service will allow the user to view and configure the end date of the prescription.

Requirement R-6.7.v0.3Name: Refill DateDate Created : 2010-10-21 09:53:43Last Modified: 2010-11-11 06:42:50Priority : 7Problem : P-19Goal : G-16

The service will allow the user to view and configure the date that the prescriptionnext needs to be refilled.

Requirement R-6.8Name: Web Service Calendar ConfigurationDate Created : 2010-10-21 09:54:48Last Modified: 2010-11-11 06:42:50Priority : 7Problem : P-19Goal : G-16

109

The service will allow the user to view their calendar events and reminders, modifythem, and add new ones

Requirement R-6.9Name: Web service to access device information.Date Created : 2010-10-21 09:55:24Last Modified: 2010-11-11 06:42:50Priority : 6Problem : P-19Goal : G-16

A user may remotely login to the web service and access all last known phone configu-ration settings and data, including location, last used, medical information and historyof medications taken.

Nonfunctional Requirement R-6.10Name: Security of Web ServiceDate Created : 2010-10-21 09:55:50Last Modified: 2010-11-11 06:42:50Priority : 8Problem : P-19Goal : G-16

The web service should only allow access to individuals that the user designates

Nonfunctional Requirement R-6.11Name: Intuitive Web ServiceDate Created : 2010-10-21 09:56:29Last Modified: 2010-11-11 06:42:50Priority : 7Problem : P-19Goal : G-16

The web service should be easy to use

110

11.7 Easy-To-Use Phone Interface

Requirement R-7.1Name: Touch pad dialerDate Created : 2010-10-21 09:57:13Last Modified: 2010-11-11 06:42:50Priority : 7Problem : P-20Goal : G-17

The application shall provide a touch pad dialer that allows the user to dial numbersdirectly, as well as buttons to start and end their call.

Requirement R-7.2Name: Contact StorageDate Created : 2010-10-21 09:57:14Last Modified: 2010-11-11 06:42:50Priority : 8Problem : P-20Goal : G-17

The application shall provide a small storage area for a limited number of contacts,as well as a few different ways of sorting the contacts. Using the Family/User WebServices portal, the contacts can be added and reconfigured as necessary. There is alsoa section for In Case of Emergency (ICE) if needed by the user or if the phone is foundby a third party.

Requirement R-7.3Name: Recent CallsDate Created : 2010-10-21 09:57:15Last Modified: 2010-11-11 06:42:50Priority : 7Problem : P-20Goal : G-17

The application shall provide a storage area for the calls placed, received, and missedby the user. The Calls Dialed list allows the user to see who they have called and allowsthem to call that person again, if desired. Calls that are un-answered are placed onthe Calls Missed list. When a call from a doctor or care-giver goes un-answered, thephone will make a noticeable alert every minute until they are acknowledged.

Requirement R-7.4Name: MessagingDate Created : 2010-10-21 09:57:15Last Modified: 2010-11-11 06:42:50Priority : 7Problem : P-20Goal : G-17

The application shall provide a messaging service for both text and voice messages.Important calls from doctors or care-givers are given special priority and play an alertuntil cleared by the user.

111

Requirement R-7.5Name: Volume AdjustmentDate Created : 2010-10-21 09:57:16Last Modified: 2010-11-11 06:42:50Priority : 7Problem : P-20Goal : G-17

The application shall provide a volume control that the user can use to change thevolume of the phone’s speaker

Nonfunctional Requirement R-7.6Name: Dialer Button SizeDate Created : 2010-10-21 10:01:21Last Modified: 2010-11-11 06:42:50Priority : 7Problem : P-20Goal : G-17

The size of the dialer’s buttons shall be large enough, and have big enough numbers,that they are easy to read and press for an elderly person

Nonfunctional Requirement R-7.7Name: Loudness of Message AlertsDate Created : 2010-10-21 10:01:24Last Modified: 2010-11-11 06:42:50Priority : 7Problem : P-20Goal : G-17

Message alerts shall be loud enough that an old person can easily hear them.

112

Helping Old People Easy Software Requirements …chung/CS4351/...Helping Old People Easy Software...

Documents

Transcript of Helping Old People Easy Software Requirements …chung/CS4351/...Helping Old People Easy Software...