Requirement Document

Revision History

Revision Description Date Author
1.0 Original draft created June 05, 2011. Peyton, Steven, Brian, Hank, Ivan
2.0 Fixed grammar, some formatting,
Added tutorials, glossary.
June 05, 2011. Brian, Peyton, Ivan, Steven.
3.0 Edited glossary.
Edited example tutorials.
Final check.
June 06, 2011. Brian, Steven, Hank, Ivan, Peyton.
4.0 Updated the information related to the changes in the development July 1,2011 Ivan
4.1 Final check July 4, 2011 Ivan

1, Introduction

1.1 Purpose

  • This software requirements specification (SRS) document describes the software requirements for the DailyHelper system in details. The document will present the purpose and major features of the system, the interface of the system, how the system will react to external input and the constraints under which it must operate. This document will play a role as a user manual for end users and a functional guideline for the system developers.

1.2 Scope

  • DailyHelper is aiming to help mentally handicapped people, seniors or seriously injured patients. By providing solutions to the accessibility issues related to essential needs of those
    people, DailyHelper will bring convenience to their everyday life.
    The interface of DailyHelper is very intuitive to use, with several specially designed buttons related to the essential needs of those people. Once buttons are clicked, the device will
    notify the caretaker with corresponding needs. This application will no doubt bring a lot of convenience to both the mentally handicapped people and their caretakers.

1.3 Overview

  • The remaining parts of this document are organized in the following ways:
    Section 2 provides the intended audience list. It specifies users for this systems and analyzes the experience, knowledge and goals that users are assumed to have.

    Section 3 and 4 present and specify the functional requirements and non-functional requirements of the system. Section 3, the most important part of this document, describes
    the functionality that the system is expected to provide. Every feature of the DailyHelper system is cataloged there.

    Section 5 teaches end users to use the system by providing step by step tutorials with diagrams.
    Section 6 is a glossary for all the technical terms, acronyms and abbreviations that are used in this document. Their meaning in the document is precisely defined to avoid ambiguity.

__2, Intended Audience List __

The primary targets of this application are those who are mentally handicapped, senior people or patients that are seriously injured. With the easy buttons that fulfill their essential needs, one can have very fast access with their caretaker and not having to wait for a long time. DailyHelper will bring convenience to both caretakers and patients.

2.1 Features:

  • - Four daily basic needs instant message
  • - Emergency button
  • - Text-to-speech
  • - Customized buttons creation

2.2 Intended Users:

  • For seniors, seriously injured patients they might not be able to move freely as they wish. In the case that when they need something where the caretaker is not beside them, they can press one of the easy buttons according to their need, the device will then notify the caretaker and hence saves time from having to walk over and ask what they need.
    For mentally handicapped people and people with cognitive impairment, they might not be able to represent themselves thoroughly and thus situations like misunderstanding might happen. With the clear pictures on the button, mentally handicapped people should be able to distinguish what they are easily. A mentally handicapped people should have no problem using the application after one hour of practical training.
    For people with speaking impairment, who are not able to speak properly, often times they need pen and papers to draw what they need. Now they can just simply press the buttons to directly tell the caretaker what they need. Moreover, they can also use the text input system to help the caretaker to understand their special needs. In addition, we have a text-to-speech function that allows the device to speak for them. For example in a coffee shop scenario, they can type whatever they wish to buy beforehand, and let the device speak for them to the cashier. This might avoid awkward situations like having to wave the fingers and play the guessing game.

__3, Features, Functional Requirements __

This part outlines every feature that the DailyHelper system is expected to provide.

3.1 Four basic needs buttons:

  • From the side of people who are taken care of:
    Four basic needs buttons are “Food”, “Water”, “Medicine” and “Washroom”. By clicking one of the four basic needs button, users can instantly send a text message to notify caretaker about what they want at that time. So users do not have to dial the telephone number and talk with the caretakers on phone. The communication is instant, clear and convenient.

3.2 Emergency button:

  • From the side of people who are taken care of:
    The emergency button is designed to make a direct call to the caretaker instead of sending the message, so the caretaker can know the users are in emergency situation and can call emergency service center for users. The reason for that is because the patient might not be able to speak to the officer in some special circumstances.

3.3 Customized button:

  • From the side of people who are taken care of:
    Users can customize their own button if there are any other needs, it will store the desired text description in the application and its functionality is the same as the default buttons. There is no limitation for the maximum amount of customized buttons.

3.4 Text to speech :

  • From the side of people who are taken care of:
    This feature mainly aims to help people with speaking-impairment.

This feature will enable users to input the sentences they want to deliver in text format. When they press the “talk” button, the device will convert text into sentences in human voice and send out it to people to whom the user communicates with.
Users can choose between “male vocal” and “female vocal” in the settings. The system also provides “history log” and “repeating” feature. User can choose to save the sentences they use frequently as templates. They can also send out the voice of the sentences if people to whom the user communicates with do not get it clearly.

One user case: in the coffee shop:
Users choose from history log or type the name of the coffee they would like to order into the device.
Users press the “talk” button.
The device will send out the voice to the shop assistant.
If the shop assistant does not get it clearly, user can press “repeat” to send out the voice again or show the message on the screen of the device to the shop assistant.
System will ask User whether to save the name of the coffee if it is not in the templates

The application can also help users in scenarios like restaurants, public transportation … etc.

4.0 Non-functional Requirements

4.1 Caretaker Mode

  • User information: the format of the user information (i.e. patient’s name, room number) that stores in this application is limited. For example, the length of the patient’s name and room number is limited to maximum of 20 characters and 6 characters. The reason for this limitation is to reduce the memory usage in SQL database.
  • Each message sent from the default button (i.e. food, water, washroom, medicine) have the same ringtone. However, the special needs button will have a different notification ringtone, so the caretaker can visit their patient directly.
  • A notification window will pop up before each message is sent, this design is to prevent user from mistakenly press the undesired button.
  • Each text message should be sent to the caretaker’s side in at most five seconds.

4.2 Text to speech Mode

  • Constraints:
    • Languages: English
    • Limitation to the length of the text input is 165 characters per input.
  • I/O device requirement:
    • Speaker, iPod touch/ iPhone/ iPod
  • Platform:
    • iOS (objective C is required)
  • Reliability:
    • Basic spell check and correct
    • The invalid input will be alerted and asked for the re-enter
  • Interface:
    • One main menu, several click buttons.
    • Readability: display the sentence/text in larger fonts for users to read
    • User friendly: This should be as simple as possible.
  • Expected execution speed: Instant

5.0 Example Tutorials

1.jpg Click the icon to start the application (Figure 1).
Figure 1 The application icon that displays on the device main page.
2.jpg After clicking the icon, you will reach the main
page three buttons named “5 basic needs” (Figure 3.1),“text to speech” (Figure 3.2) and “emergency ONLY!”
Choose the option that you would like to use by clicking the appropriate icon. In the case of using the emergency
option, a message box shall pop up to confirm whether the user really needs to make an emergency call to your caretaker.
Choose the option that you would like to use by clicking the button accidentally.
Figure 2. The title page of the application.
3.jpg If you clicked the “5 basic needs” button shown in figure 2, you will reach here (Figure 3.1). You should see four default basic
need buttons, and a “create your own” button. By clicking one of those four default buttons,
a message will be sent to your caretaker notifying your need.
If you would like to create your own custom button that fits your special need for future convenience,
you may click the “create your own” button, and go to figure 3.1.1 for further instructions.
Figure 3.1 The “5 basic needs” page.
4.jpg This is the “create your own button” panel (Figure 3.1.1).
Input the name that you wish to appear on the icon in the “button name” field, and choose one of the colors
you desire from the list of colors. Enter the text message content that you would like to send to your caretaker. Then click the “Submit” button,
a new button should appear on the “5 basic needs” page (See figure 3.1.2).
Figure 3.1.1 New button creation panel.
5.jpg The new “5 basic needs” homepage with the new button on it.
Figure 3.1.2 New “5 basic needs” homepage.
6.jpg This feature (Figure 3.2) is designed for people who have speaking impairment.
Type in the message that you would like the device to speak for you, and click the “Talk!” button, the device shall read the sentence for you.
You may also save the sentence for future convenience by clicking the “Save!” button.
This will allow you to do the quick text input from having to type in the sentence that you will be using over and over again.
Figure 3.2 The “text to speech” page.

6.0 Glossary

  • Constraint - a limitation or restriction that the application has.
  • Customized button - One of the functions of this application that gives the user an opportunity to design their own buttons for any other necessary needs.
  • Emergency button - The button that will call directly to the care take when pressed.
  • Execution speed - the speed with which a computational device can execute instructions.
  • Five basic need buttons - the buttons that will send the text message of the user’s need to their caretaker.
  • Functional requirements - calculations, technical details, data manipulation and processing and other specific functionality that define what a system is supposed to accomplish.
  • I/O - the communication between an information processing system (i.e. iPhone), and the outside world (i.e. human).
  • Mentally handicapped - a generalized disorder appearing before adulthood, characterized by significantly impaired cognitive functioning and deficits in two or more adaptive behaviors.
  • Non-functional requirements - requirements that specify criteria that can be used to judge the operation of a system.
  • Platform - framework on which applications may be run.
  • Reliability - the probability of failure-free software operation for a specified period of time in a specified environment.
  • Speaking impairment - a type of communication disorders where 'normal' speech is disrupted.
  • Special need button - The button that will send a text message to notify the caretaker a visit is needed.
  • Software requirements specification (SRS) - description of the behavior of a system to be developed.
  • Text to speech - a function that will convert a sequence of meaningful string into human voice.
  • User information - The name, room number and general information about the patients who are stored in caretaker’s device.