Revision History

Version Changes Date Modified

0.1 Wrote introduction.Began writing Domain Issues.

01/25/2012

0.2 Continued with Domain Issues. 01/27/2012

0.3 Continued Domain Issues. Began FR Issues.

01/30/2010

0.4 Continued FR Issues. 02/05/2012

0.5 Continued FR Issues. Began NFR Issues.

02/09/2012

0.6 Completed NFR Issues. 02/14/2012

0.7 Finished NFR Issues.Began NFR Improved Understanding.

02/20/2012

0.8 Finished NFR Improved Understanding.Finished Domain Issues. Began Domain Improved Understanding.Wrote “why out proposal is the best” and the creeping rate.

02/28/2012

0.9 Finished Domain Improved Understanding.Finished FR Issues.

Began FR Improved Understanding.

03/01/2012

0.10 Finished FR Improved Understanding. 03/01/2012

0.11 Formatting and proofreading revisions. 03/01/2012

0.12 Converted word document into a Google Docs document 03/02/2012

1

0.13 Worked on adding and changing existing issues. 03/04/2012

0.14 Worked on adding additional issues.

Worked on “Why We’re Better” section.

03/05/2012

0.15 Worked on improving FR Improved Understanding wording.

Worked on operationalizing NFR’s.

Began work on improved category lists.

03/06/2012

0.16 Broke Improved Understanding FR’s down into more atomic units, integrated category lists.

03/15/2012

0.17 Improvised the understanding NFR’s and broke it down into functional units

03/17/2012

0.18 Worked on including the creeping rate that can be included in the project. Started work on Prototypes

03/19/2012

0.19 Finalised on the prototypes and made them GUI friendly.Started work on final document for Phase-1 Final submission

03/22/2012

0.20 Final document for submission of Phase-1 Final report 03/26/2012

2

Process

We, the Andromeda team have followed a definite process in creating this HOPE system. We had gathered and discussed the requirements from lot of resources like web, by taking to elderly people who might use our system and based on our own experience from our grandparents and from the elderly people we had come across.

Any requirements which use the term shall indicate that that functionality is critical core functionality that will be implemented in the first version of the HOPE system. Other functionality that is identified by our requirements gathering process that is not considered critical core functionality and may be implemented instead in a later version of the HOPE system will be referenced using the word ‘will’.

The software process that we are using in this system is V-process model. Change is inevitable in software projects so our process is designed to adapt to the changes and allow modification where necessary to the requirements and other documents.

Process Model

For the implementation of HOPE system, we will follow the Spiral Model.The spiral model is a software development process combining elements of both design and prototyping-in-stages, in an effort to combine advantages of top-down and bottom-up concepts. This model of development combines the features of the prototyping and the waterfall model. The spiral model is intended for large, expensive and complicated projects.The spiral model combines the idea of iterative development with the systematic, controlled aspects of the waterfall model. It allows for incremental releases of the product, or incremental refinement through each time around the spiral. The spiral model also explicitly includes risk management within software development. Identifying major risks, both technical and managerial, and determining how to lessen the risk helps keep the software development process under control.

3

START

The V- Model

4

Requirements Document and Validation Report

Informal Statement of Requirements

Agreed Requirements

Draft Requirements Document

Requirements Elicitation

Requirements Analysis and Negotiation

Requirements DocumentationRequirements Validation

Accept Document or Re-enter Spiral

Phase 1 Deliverable

Phase 2 Deliverable

Project Deliverables

Phase Deliverable Date

Phase 0 Preliminary Project Plan January 25nd, 2012

Phase 1 Interim Project 1

Requirement Specification

Requirement Analysis

Presentation

March 6th, 2012

Phase 1 Final Project 1

Improved Requirement Specification

Improved Requirement Analysis

Presentation

March 27th, 2012

Phase 2 Interim Project 2

Improved Requirement

Specification / Analysis

Implementation

Testing

Presentation

April 26th, 2012

Phase 2 Final Project 2

Modified Implementation

Modified Testing

Presentation

April 30th, 2012

5

Project Responsibilities

Phase 1 Deliverables Developers Reviewers Team Lead

Preliminary Definition

AarthiGiridharan

BalajiShanmugam

GovindarajanPanneerselvam

KumaranSenapathy

NehaMalloli

SriramSridharan

Vignesh Swaminathan

NehaMalloli

SriramSridharan

AarthiGiridharan

Documentation and Presentation

AarthiGiridharan

BalajiShanmugam

GovindarajanPanneerselvam

KumaranSenapathy

NehaMalloli

SriramSridharan

Vignesh Swaminathan

BalajiShanmugam

Vignesh Swaminathan

AarthiGiridharan

6

1 Introduction

1.1 Purpose

Unfortunately Old Age has now become a prevalent social problem in our society. In our modern society, where money is the scale of everything, old age people measured as an economic liability and a social load. In addition, old age is unavoidable and thus of concern to each of us. It is strange no one wants to grow old but everyone wants to live long. Old age watched as an inescapable, undesirable, problem- ridden stage of life that we compelled to live, marking time until our final exit from life itself. A statistics says, by 2050 there will be more people in the world who are 60 and over than children aged 14 and under. As people get older, they tend to experience difficulties with hearing, speaking, vision and memory loss, and muscle weakness.

Augmentative and Alternative Communication (AAC) is a branch of study to assist or help people with communication difficulties. It comprises of many techniques, including sign language, gestures, visual aids, pictures, symbols, text-to-speech electronic communicating devices, and so on. It was aimed to help people who only had difficulties in speaking or speaking clearly - in communication. It has found many potential applications in helping people with development disabilities, speech and hearing disorder, autism, dyslexia, aphasia, and so on. But to help elderly or anyone who have more than speech disorder we need to go in depth beyond AAC to find their problem and needs towards their physical and mental disorders and provide a way to live them pleasantly.

So, this project is intended for helping the elderly population suffering from communication difficulties, such as lack of hearing, speech impairment and unclear speech, as well as low vision, weak memory, muscle weakness and much more elderly problem. We are going to help elderly people with above problems with the mobile communication device which serves as multi-functional help device. We hope that our ‘HOPE” system will Helping Our Elder People Easily.

1.2 Project Scope

The broad scope of our HOPE project is,

To build an all-in-one solution where the user need not depend on any other device but the mobile phone to meet most of the basic needs and problem specified above.

To drastically reduce the level of dependency on a third person as many of the services are available in a pocket device.

To develop a user friendly application to support features like emergency contacts, speed dialing, drug reminders, speech recognition, profiles, etc.

7

1.3 Definitions, Acronyms, and Abbreviations

HOPE - Helping Our People Easily

1.4 Summary of Domain Requirements

DR0 A smart phone is required

DR1 The user needs basic knowledge about using the smart phone

DR2 The phone must have HOPE installed in it.

DR3 Click on the emergency icon displays list of emergency contacts to be called.

DR4 Click on icon will convert speech to text

DR5 Click on icon will convert text to speech.

DR6 Old people suffering from hearing problem will need a converter.

DR7 Phone must have an in-built microphone, typically to record the speech.

DR8 Old people can calculate the calories burnt by using a time-tracker function whenever they go for a walk. This helps them maintain a check on their health.

DR9 When 2 people have problems in oral communication, they can use pictograms for communication.

DR10 Some elderly people have the problem ‘Motor Aphasia’ i.e., they have problem with speech clarity. Our system must provide a feature for them to express their message clearly.

DR11 The contacts page should give a brief description of the picture selected.

8

DR12 When the user types a message, the person at the opposite must be able to realize the scenario and act to it

DR13 Person assisting the old people must be near the phone

DR14 User must know how to use message board

DR15 Old people suffering from memory loss due to ageing will need help remembering the location of everyday things placed at home

DR16 An application should store the location information of the basic things at home

DR17 The phone should have good sound quality, typically to reproduce clear sound

DR18 Old people suffering from memory loss due to ageing will need help remembering people and their relationships

DR19 Some elderly people who have memory loss will not remember to have their medicines at the correct time. This feature will generate reminders to help these people have their tablets at the correct time.

DR20 Old people may have issues with remembering bank details, SSN, etc.

DR21 Old people may have issues with choosing foods to eat and to avoid.

DR22 A Diet Manager feature should assist the user in choosing the foods to eat

DR23 Elderly people may need immediate assistance in case of emergency situations.

DR24 A Help Icon feature on all screens should sound an alarm to alert the care taker.

`

9

1.5 Summary of Functional Requirements

FR1 Displays list of Emergency contacts that could be called by a single touch.

FR2 Converts Voice input in to textual form and if possible in picture format.

FR3 Converts textual into a voice output.

FR4 Displays all personal information stored by the user.

FR5 Alerts the user at the stored time to consume the medicine and updates medicine stock.

FR6 Text to speech converter and sound output feature is for people with unclear speech.

FR7 Prompts the user about the location on selecting the item.

FR8 Displays the list of food items one should and should not consume.

FR9 Displays the distance covered and calories burnt in that session.

FR10 Displays and produces the sound for the chosen picture.

FR11 Elderly people can securely store Bank details, SSN details under the password protected MyPage feature.

FR12 Elderly people perform speed dial to their relatives or doctors.

FR13 Templates are used for Text2Speech as well as PicTalk features

FR14 PicTalkcreates a message and can either be displayed or sentto others.

1.6 Summary of Nonfunctional Requirements:Nonfunctional requirements are further sub divided in to user specific and system specific

NFR1 Speech to text converter should be able to convert spoken words to text quickly.

NFR2 The output audio should be clear.

NFR3 The icon names should be self-explanatory

NFR4 Words spoken by the person should be loud enough.

NFR5 The functionality of the message should be audible to the old person.

10

NFR6 The image icon when clicked should read its functionality aloud immediately.

NFR7 Conversion from text to speech must be as quickly as possible.

NFR8 Speech should be audible.

NFR9 The message should be clear to the listener.

NFR10 The font should be readable to the user.

NFR11 Emergency icon should always be one click away to provide high accessibility

NFR12 The retrieval of the photos should be fast.

NFR13 Store few photos to identify a contact, pet or an object.

NFR14 The reminder should be invoked at the correct time.

NFR15 The phone should display the name or image of the medicine at the correct time.

NFR16 The application should display appropriate food items based on health condition entered by the user

NFR17 The application should provide approximate calories burnt based the time spent walking

NFR18 User's personal and bank details should be password enabled to provide security

NFR19 The Help button feature in the application should sound an alarm when clicked

NFR20 The alarm sounded should be audible enough to the care taker

NFR21 The switching between two features in the application should be easy

NFR22 The medicine stock and reminder stored by the care taker should be accurate and precise since it is critical to patient’s health.

NFR23 The images should be large enough to be recognized.

11

2 Issues Related To Preliminary Project Definition Here we address the various incompleteness, inconsistency and irregularity in the preliminary project definition. The issues are related to domain, functional and non-functional objectives.

2.1 Domain IssuesThe domain issues in the project are explained below:

Here we address the various incompleteness, inconsistency and irregularity in the preliminary project definition. The issues are related to domain, functional and non-functional objectives.

2.2 Domain IssuesThe domain issues in the project are explained below:

2.2.1 Issue IDR-00: Requires SmartphoneDescription The old people should have access to smartphone to use HOPE application.Options Option A: Apple-iPhone

User friendly environment (+) Expensive (-) No choice in handset (-)

Option B: Android phone is required Comparatively Cheaper (-) Choices in handset (+) Frequent updates in software (+)

Option C: No Phone Requirement not satisfied

Decision Option B-Android platform to develop our application because it’s easier to develop and also give options in choosing handset.

2.2.2 Issue IDR-01: Basic knowledge in using the smartphoneDescription The user must have some knowledge on how to use the smartphoneOptions Option A: User manual to assist the elderly

Understand the working of the application (+) Time consuming in creating manual (-)

Option B: Assume the user know about the smartphone Reduces the effort in development (+) Saves development time (+) If the user does not know to use smartphone, he/she cannot use the

application (-)Decision Option A-Easily accessible to all users.

2.2.3 Issue IDR-03: Emergency and Help option in applicationDescription Emergency and Help is not clearly defined in the project definitionOptions Option A: State Emergency and Help option

Improves the project definition (+)

12

User is comfortable when Help is available (+)Option B : Remove Emergency and Help from project definition

Important aspect of the project is removedDecision Option A-We redefine the project description and give details about Emergency

and Help. We also mark them as important feature in the application.

2.2.4 Issue IDR-04: Click the icon to convert speech to textDescription Issue-Incompleteness

Does not specify the icon to be clickedOptions Option A: Remove the specification

Option B: Clearly indicate the name of the iconDecision Option B-Specify the name of the icon to be clicked to complete the statement

2.2.5 Issue IDR-05: Click on icon will convert text to speech.Description Issue-Incompleteness

Does not specify the icon to be clickedOptions Option A: Remove the feature

Option B: Clearly define the icon to be clickedDecision Option B-Specify the name of the icon to be clicked to complete the statement

2.2.6 Issue IDR-06: Elderly with hearing problem needs a converterDescription Issue-Incompleteness

Does not specify the name of the converterOptions Option A: Remove the conversion feature

Option B: Specify the name of the converterDecision Option B-Indicate the name of the converter that converts speech to text

2.2.7 Issue IDR-07: Smartphone should have microphone typically to record speechDescription Issue-Ambiguity

Implies there are many ways to use the microphoneOptions Option A: Remove ‘typically’ from the statement

Option B: Indicate all the possible ways to use the microphoneDecision Option A-After removing the word ‘typically’ the statement indicates that

microphone is for recording speech

2.2.8 Issue IDR-08: Calculationof CaloriesDescription Issue: Technical implementation.

Old people will be advised to walk in-order to maintain good health. They might want to track the calories burnt by walking.

Options Option A: Remove the feature Important functionality in the application is missed (-) Development time is reduced (+)

Option B: Make assumption on the average walking speed of elderly people and calculate calories burnt based on the assumption.

13

Increases the development time increases due to complicated calculation

Includes a feature to promote good healthDecision Option B-The old people mustbe able to track their healthy routine easily

2.2.9 Issue IDR-09: Use of Pictograms to communicateDescription Old people with speech disorder will find it difficult to convey their message.

They may need a pictogram to display images to assist them communicateOptions Option A: Remove the feature

Option B: Remove the word ‘may’ in order to indicate it is requiredOption C: Clearly define the meaning of ‘need’ and ‘speech disorder’

Decision Option C-State clearly the meaning of need and speech disorder. Develop the feature accordingly.

2.2.10 Issue IDR-10: Difficulty in SpeechDescription Some elderly people have the problem ‘Motor Aphasia’ i.e., they have problem

with speech clarity. Our system must provide a feature for them to express their message clearly.

Options Option A: The user writes a message on the phone using stylus and it is converted to speech

Ease of use (+) Difficult to implement (-)

Option B: Mechanism to type the message Easy to implement (+) Old people may not be expert in typing. Hence they will need time

to express their message (-)Decision Option B-Implementation is easy.

2.2.11 Issue IDR-11: When an image is clicked, the system tells about the image selectedDescription Issue-Incompleteness

Statement does not specify what kind of images must be clicked.Options Option A: Remove the statement

Option B: Specify the name of images to be clickedDecision Option B-Clarify the specification by specifying that the images are of the contacts

stored and the corresponding details of that contact is displayed when clicked

2.2.12 Issue IDR-12: Understand the situationDescription When the user types a message, the person at the opposite must be able to realize

the scenario and act to itOptions Option A: Remove the statement.

Option B: Clearly state the meaning of ‘scenario’Decision Option B-Clarify the statement

2.2.13 Issue IDR-13: Person assisting the old people must be near the phoneDescription Issue-Ambiguity

14

Options Option A: Clearly state the distanceOption B: Expand the statement by indicating that the person assisting the elderly must be able to understand the message

Decision Option B-Make the statement understandable

2.2.14 Issue IDR-14: User must know how to use message boardDescription Issue-AmbiguityOptions Option A: Define the message board such that it is understood by anyone

Option B: State clearly whether user must know typing or understand the optionDecision Option B-Message board clearly defined

2.2.15 Issue IDR-15: Old people with weak memory require a tool to remember location of everydaythings placed at home

Description Issue-IncompletenessDescribe the statement clearly for “everyday” things

Options Option A: Remove the featureOption B: MyShelf feature will be used to store location information for important household things like house keys, medical records.

Decision Option B-A prioritized list of things will be used to store location imformation for the things in the list.

2.2.16 Issue IDR-17: The phone should be able to reproduce clear soundDescription Issue-Ambiguity

The exact meaning of “clear” cannot be definedOptions Option A- Remove the statement

Option B- The statement should be redefined to express the exact meaning of “clear” sound.

Decision Option B- Define the speaker quality required to successfully run all applications.

2.2.17 Issue IDR-18: Remembering people and placesDescription Issue-Incompleteness.

The kind of help is not mentioned clearly.Options Option A: Remove the statement

Option B: Clearly specify the help needed.Decision Option B-Old people need this feature to identify people

2.2.18 Issue IDR-19: Help with medicinesDescription Old people may forget to take medicines at the right time. We need a feature to

remind to take medicine.Options Option A: Remove the feature

Reduces development time (+) People with memory loss find it difficult without this feature (-)

Option B: Display the name and(or) image of the tablet at the right time When a new medicine is prescribed, it must be added to the list (-) Assists the old people in taking tablets at right time (+)

15

Decision Option A-We need a feature to help old people with memory loss

2.2.19 Issue IDR-20: Any end-user may have difficulty in remembering bank detailsDescription The word ‘may’ do not specify the seriousness of the situation. Moreover

‘effectively’ adds vagueness to the application as it is perceived differently by different people

Options Option A: Remove the words "may" and "effectively”.Option B: Clearly define the statement

Decision Option B-Restructure the statement by merely changing the words that puts importance on the statement.

2.2.20 Issue IDR-21: Old people may have difficulty in choosing what to eatDescription The issue is vagueOptions Option A: Remove this feature

Option B: Implement this feature by integrating different choices of foods based on health condition.

Decision Option B-Integrating different choices of food helps the elderly people

2.2.21 Issue IDR-22: Diet Manager feature should assist the elderly people chose their foodDescription The word‘assist’ do not indicate the importance of this feature. It is difficult to

keep track of what the person should choose to eat or notOptions Option A: Remove this feature

Option B: Specify a range for the health conditions and suggest based on that.Decision Option B-Specifying a range helps in narrowing down to a critical level in

choosing different foods.

2.2.22 Issue IDR-23: Elderly people may need assistance in emergenciesDescription Issue-Incompleteness

The kind of emergency situations are not stated clearly.Options Option B: Remove the word “may”

Easy (+)Option A: Indicate the kind of emergencies

Give a specific requirement (+) Clearly state the original requirement (+)

Decision Option B-Define the words such that the stakeholders realize the emergency situations

2.2.23 Issue IDR-24: Help Icon sounds an alarm to alert the care takerDescription The word “alerts” is not clearly defined.Options Option A: Help icon should sound an alarm which is audible to the care-taker

Option B: Remove this feature. Do not use Bluetooth technology Reduces the cost (+) Decreases development time (+)

16

Removes an important feature (-)Decision Option A-Invest on speaker with audibility suitable to the care taker.

2.3 Issues with Functional Requirements

2.3.1 Issue IFR-01Description “Displays list of Emergency contacts that could be called by a single touch”

Problem: Issue-Incomplete, Ambiguity Who are intended people? Does this imply all the people or only a set of them or just one? Whom are they going to communicate with? What is the medium of communication (message or call)?

Options Option A: Elderly people are considered to be intended people. Elderly people suffering with difficulties communicate with people around

to perform day to day activities.Option B:

Younger people are considered as intended people. Younger people communicate with people around to perform daily

activities.Option C:

All the people are considered as intended. They are going to communicate with everybody.

Decision Option B - HOPE system is intended to help elderly people communicate effectively with other people carry out their routine with ease.

2.3.2 Issue IFR-02Description “Voice input into textual form.”

Problem: Issue- AmbiguityDoes not specify who provides speech. Also the term clearly is not quantified.

Options Option A: The speech of the elderly person has problems in clarity. Speech to Text converter is required to address this issue. The term clearly means every word being interpreted.Option B: Remove this requirement.

Decision Option A- Elderly person suffering from hearing issues cannot hear the speech of the other person and hence needs an external interface. Hence, this feature aids in easier communication.

2.3.3 Issue IFR-03Description “Converts text into voice output”

Problem: Issue- IncompleteDoes not specify what the problems are.

Options Option A: People suffering with loss of vision.

17

Option B: People suffering from memory loss.Option C: People suffering with hearing issues.

Decision Option C - Speech to text is used to help people suffering from hearing problems.

2.3.4 Issue IFR-04Description “Displays all personal information stored by the user.”

Problem: Issue – Ambiguity, Incomplete. Does not specify what the information is provided and who the user is.

Options Option A: Elderly person’s information like Name, address, phone number, etc.Option B: Younger person’s information.

Decision Option B: Elderly person’s information like Name, address, phone number, etc.

2.3.5 Issue IFR-05Description “Alerts the user at the stored time to consume the medicine and update the

medicine stock.”Problem: Issue- Ambiguity and IncompletenessDoes not specify who the user is and does not mention about how the stock is managed.

Options Option A: Old people are reminded of their medicines and they/ their caretaker update the stock whenever a new medicine is bought.Option B: Absent minded people.Option C: Young people with health issues.

Decision Option A: Old people are reminded of their medicines and they/ their caretaker update the stock whenever a new medicine is bought.

2.3.6 Issue IFR-06Description “Prompts the user about the location on selecting the item”

Problem: Issue- AmbiguityWhat location?

Options Option A: Prompts the location of the object inside the house/ office.Option B: Prompts the name of the city.

Decision Option A: Prompts the location of the object inside the house/ office.

2.3.7 Issue IFR-07Description “Displays the list of food items one should/ should not consume.”

Problem: Ambiguity and IncompletenessWho should not consume? On what basis does it say?

Options Option A: Elderly people enter the values for the asked parameters and corresponding diet to be followed is listed.Option B: Everyone can choose their favorite food as their diet.

Decision Option A: Elderly people enter the values for the asked parameters and corresponding diet to be followed is listed.

18

2.3.8 Issue IFR-08Description “Display the distance covered and calories burnt in that session”

Incomplete definition of the process.Options Option A: Input the distance covered manually and calculate burnt calories

Option B: Calculates the distance by the time spent on walking along with the average speed and hence computes calories burnt.

Decision Option B: Calculates the distance by the time spent on walking along with the average speed and hence computes calories burnt.

2.3.9 Issue IFR-09Description “Displays and produces the sound when a picture is chosen.”

Incomplete definition of the parameter used.Options Option A: Outputs sound of the name of the contact image or images stored in

pictalk.Option B: Outputs the sound of any image stored in the phone.

Decision Option A:Outputs sound of the name of the contact image or images stored in pictalk.

2.3.10 Issue IFR-10Description “Store secure information with password protection.”

Problem -AmbiguityWhat kind of information is considered secure?

Options Option A: DOB, Contact information, etc.Option B: Bank details, SSN, etc.

Decision Option B: Bank details, SSN, etc.

2.3.11 Issue IFR-11 Description “Should be able to call the emergency contacts using speed dial.”

Problem –AmbiguityWho are the emergency contacts?

Options Option A: Nephew, Colleague, etc.Option B: Doctor, Care taker, etc.

Decision Option B: Doctor, Care taker, etc.

2.3.12 Issue IFR-12Description “Templates are used for text to speech as well as pictalk.”

Issue-IncompletenessHow should the template be?

Options Option A: Textual/ Pictorial representation of thoughts that involves minimum editing to be done.Option B: Feed more input to the existing template.

Decision Option A:Textual/ Pictorial representation of thoughts that involves minimum editing to be done.

19

2.3.13 Issue IFR-13Description “Pictalk helps to display the message need to be conveyed or forward it to

someone through messaging.Problem :Ambiguous.What kind of a message could it send?

Options Option A: Text Message.Option B: Picture Message.

Decision Option A: Text Message.

2.4 Issues with Non-Functional Requirements

2.4.1 Issue INR-01: NFR1-Speech to text converter should be able to convert the spoken words to text quickly

Description Problem -Issue: Ambiguity: The term “quickly” is not specificOptions Option A: Remove the statement.

Option B: Define the time range for the conversion.Decision Option B - The time range should be specified in seconds.

2.4.2 Issue INR-02: NFR2-The output audio should be clearDescription Problem- Issue: Unsoundness

The term “clear” is not specificOptions Option A:Remove the Feature

Option B: Rephrase the statement as “The audio should not have any delay or distortion”.

Decision Option B - Speech to text converter provides an important interface for people to communicate clearly

2.4.3 Issue INR-03:NFR3- Icons used should be self-explanatory.Description Problem-Ambiguity: The phrase “self-explanatory” does not clearly define the

purpose of the icons.Options Option A: Have pictures depicting the purpose of the application.

Option B: Have icons carrying the name of the application.Decision Option A: Have pictures depicting the purpose of the application.

2.4.4 Issue INR-04:NFR4- Words spoken by the person should be loud enough.Description Problem: Vagueness The phrase “loud enough” does not specify the level of

loudness required.Options Option A: Merely specify the voice should be loud enough to be sensed.

Option B: The words spoken should be loud. This measure is given in decibels to make it more specific.

Decision Option B-It is indicates how loud the speech should be thereby removing the ambiguity

20

2.4.5 Issue INR-05:NFR5- The functionality of the message should be audible to the old person

Description Problem – Ambiguity. There is no way to assess if the feature is audible, as the audibility faculty varies from person to person

Options Option A: Remove the statement.Option B:Define the range for audio levels.

Decision Option B - The range of audio levels should be specified clearly to prevent ambiguity

2.4.6 Issue INR006:NFR6- The image icon when clicked should read its functionality aloud immediately

Description Problem: Incompleteness. The term immediately is not preciseOptions Option A: Remove the statement

Option B: Define the time range by which the functionality should be read aloud.Decision Option B - The time range should be specified in seconds thereby making the

requirement more specific

2.4.7 Issue INR007:NFR7- Conversion from text to speech must be as quickly as possible.Description Problem Issue: Unsoundness, Inconsistency. The phrase “as quickly as possible”

cannot be quantified.Options Option A: Remove this phrase

Option B: “As quickly as possible” implies fast. Hence a specified time bound must be specified.

Decision Option B - It is simple and does not show different behavior of the system.

2.4.8 Issue INR008:NFR8- Speech should be audible.Description Problem -Issues: Unsoundness, incompleteness. The word “should” does not

provide binding provision. NFR does not define audible.Options Option A: The use of word “should” is maintained in order to avoid binding

provision. Person assisting the user must be able to hear the words to communicate easily.Option B: Due to incompleteness, NFR is ignored.

Decision Option B- It is simple and does not show different behavior of the system.

2.4.9 Issue INR009:NFR9-The message should be clear to the listener.Description Problem: Issue-Ambiguity.

There is no specific sense clarity of the message.Options Option A: Remove the entire statement.

Option B: Make the message clear by keeping the screen wider.Decision Option B- The reader is going to see that the message in a wide screen, and hence

in bigger font, thereby addressing issues with reading.

2.4.10 Issue INR010:NFR10- The font should be readable to the userDescription Problem: Unsoundness - The degree of readability varies from person to person.Options Option A: Follow the standard font template for all applications.

Option B: Remove this requirement.

21

Option C: Have a resizing option to increase or decrease the font size depending upon the vision capability of the user.

Decision Option C - The resizing option will provide more flexibility to the application as it can be altered to cater to the user’s needs. Some people might not be comfortable with standard font levels and might have their priorities.

2.4.11 Issue INR011:NFR11- The emergency icon should always be one click awayDescription Problem - Ambiguity: The term ‘one click’ is not precise. Also, the term ‘always’

does not specify under what situations.Options Option A: Remove this requirement.

Option B: Display the emergency icon in all screens of HOPE application and the number of steps involved in accessing the emergency button should just be one.

Decision Option B: Display the emergency icon in all screens of HOPE application and the number of steps involved in accessing the emergency button should just be one.

2.4.12 Issue INR012:NFR12-The retrieval of the photos should be fast Description Problem- Issue: Incompleteness: There should be a set time bound to specify the

retrieval time of a picture from the albumOptions Option A: Do not address this requirement.

Option B: The retrieval of a picture should not take more than 5 MS.Decision Option B - This time bound though assumed makes the requirement more specific

and hence easier to implement.

2.4.13 Issue INR013:NFR13-Store few photos to identify a contact, pet or an objectDescription Problem: Issue – Vagueness

“Few” is not a quantifiable term.Options Option A: Do not implement this requirement.

Option B: Specify that there should not be more than 2 photos for a particular contact.

Decision Option B-As it removes the vagueness in the requirement, thereby making it more specific and hence addressable.

2.4.14 Issue INR014:NFR14- The reminder should be invoked at the correct timeDescription Problem: Issue – Vagueness

There is no such benchmark as Correct time. It is an ephemeral conceptOptions Option A: Specify a stipulated time at which the reminder must be sounded.

Option B:Do not implement this requirementDecision Option B -As it removes the vagueness in the requirement, thereby making it more

specific and hence addressable.

2.4.15 Issue INR015:NFR15- The phone should display the name or image of the medicine at the correct time.

Description Problem -Vagueness: There is no such benchmark as Correct time. It is an ephemeral concept

Options Option A:Do not implement this requirement

22

OptionB: Specify a stipulated time at which the name and image must be sounded.Decision Option B - On implementing Option A the requirement tends to become more

specific.

2.4.16 Issue IN0016:NFR16- Display appropriate food items.Description Problem : Issue –Ambiguity

The term appropriate does not give a clear picture on what is appropriate.Options Option A: Remove this requirement.

Option B: Specify the food items that match the input fed by the user.Decision Option B: Specify the food items that match the input fed by the user.

2.4.17 Issue IN0017:NFR17-Display approximate calories burntDescription Problem - Issues: Ambiguity. The word "approximate" is not clearly defined.Options Option A: Use the closest possible value to the actual calories burnt.

Option B: Use a randomly chosen value.Decision Option A: Use the closest possible value to the actual calories burnt.

2.4.18 Issue IN0018:NFR18-User's details should be secureDescription Problem-Issue: Incompleteness. There is an ambiguity in understanding the idea of

securityOptions Option A: All the details that need to be secured are listed explicitly to prevent any

assumptions. What might be considered trivial from the developer's perspective to protect might actually be considered vital for the user. Replace "Should" with "Shall"Option B: Replace "Should" with "shall". Define the security need by specifying that the bank details of the user are critical and should not be compromised to any third party

Decision Option A - As it entails highest degree of understanding.

2.4.19 Issue IN0019: NFR19- The help button should produce an audible alarm.Description Problem – Ambiguous. The word "audible" does not provide any clarity.Options Option A: The alarm should be audible enough to alert the care taker when he/ she

is in a closer range.Option B: Remove requirement.

Decision Option A: The alarm should be audible enough to alert the care takerwhen he/ she is in a closer range.

2.4.20 Issue IN0020: NFR20- Navigating between two features in an application should be easy.

Description Problem- Ambiguity. The word "easy" is not clearly defined.Options Option A: User friendly GUI and a limited number of steps in navigation.

Option B: Remove requirement.Decision Option A:User friendly GUI and a limited number of steps in navigation.

23

2.4.21 Issue IN0021 -NFR21- Accurate medicine reminders and stock updates.Description Problem – Issue: Vagueness. The word accurate is unclear in its definition.Options Option A: Prompt reminders on time and proper stock maintenance.

Option B: Remove requirement.Decision Option A: Prompt reminders on time and proper stock maintenance

2.4.22 Issue IN0022:NFR22- Large images in order to recognize.Description Problem: Issue - Inconsistency.

Images though large may include variable sizes.Option Option A:Consistent image size is image size is maintained by cropping very large

images when needed.Option B: Accept images of a standard size.

Decision Option A: Consistent image size is image size is maintained by cropping very large images when needed.

3 World Requirement Specification :

3.1 Decisions and Rationale: Integrated Model (for Improved Understanding)

This section will provide a better understanding of this domain’s requirements and discusses all the problems, goals, functional and non-functional aspects and requirements of this domain.

3.1.1 Problems:

Hearing:

1. Most of the elders have various hearing disorders such as partial deafness. They have difficulty in making out what’s being spoken to them. This affects their day – to – day activities.

2. Most of them suffering from hearing loss do not evince interest in wearing hearing aids.

3. People with severe hearing loss when conversing with others would find it difficult to understand unless the speech is accompanied by some relevant hand gestures or something that at least vaguely resembles the sign language.

4. People with hearing loss are a hazard to both themselves and others, they might not respond to the sounding horns on road that may lead to accidents.

5. They might not respond to fire alarms, emergency sirens that would once again lead to personal hazard.

Speech Clarity:

1. Elderly sometimes have problems in clearly conveying themselves to others.

24

2. This acts a barrier when they interact with others as well as their family members.

3. Sometimes they have to write it down, if they have to convey it to others.

4. They cannot shout out loud during an emergency, or speak properly on a phone to the emergency services.

Vision

1. Due to the old age, they sometimes experience loss in vision. This would seriously cripple their day – to – day abilities.

2. They would have trouble in reading things and making them out, or finding misplaced things.

3. They would not make out danger signs and may be a potential hazard on road, and off road.

Memory Loss

1. It would be difficult to remembering things as people age. Hence they need some kind of an aid to remember things.

2. They forget to take their medicines on time.

3. They miss out on certain important schedules.

4. They would not be fit to manage their finances as it would require a good memory to keep the complex password in mind.

Everyday Living

1. The elderly may not be able to drive themselves to the doctor. They might not be able to cook for themselves or tend to themselves.

2. To keep themselves updated on the news would be difficult for them.

3. They would definitely need a scheduler or task manager for their daily routine.

3.1.2 Goals:

G1: Assist someone with hearing loss in communicating with the other person

G2: Help someone with hearing loss in understanding the other person

G3: Help someone with difficulty in expressing his or her ideas through speech

G4: Help someone in emergency to be immediately assisted.

25

G5: Help someone with memory loss to remember the location of the everyday usage things.

G6: Help someone with memory loss to remember relatives and friends.

G7: Help an elderly person in reminding them to take their medicine on time.

G8: Allow an elderly person call for help from family, an assistant or the authorities

G9: Help an elderly person to track his metabolism.

G10: Help an elderly person choose his diet.

G11: Keep an elderly person up to date on their finances.

3.1.3 Improved Functional Understanding of the Domain: World

WF1: The user should have an Android phone

WF2: The user should know how to use the basic features of the Android phone

WF3: The phone must have HOPE services running on it.

WF4: Users with loss in memory and vision must be sure to keep the mobile always with them.

WF5: Old people suffering from hearing problem will need a speech to text converter

WF6: There should always be a person within 10 meters of the old person to help him.

WF7: The elderly who have trouble hearing will need a speech-to-text application to hear well

WF8: The images of the frequently used words are stored in the phone’s memory

WF9: The elderly who have trouble remembering will need an application to remember the location of everyday used things.

WF10:The user needs to keep the phone on their person to be able to use the system.

WF11:Old people suffering from speech disorders will need to be able to use images or icons to ask for help when in need.

WF12:People with extremely unclear vision will need things read aloud to them instead of being able to read text.

WF13:When two people have problems in oral communication they should use pictograms for communication.

WF14:Old people having speech clarity problems would benefit from a system that provides a user interface to type the message they want to express.

26

WF15:Old people with memory problems will need applications to remind them of the locations of the things used every day.

WF16:Old people with memory problems will need applications to remind them of medicines to be consumed every day.

WF17:The user requires a keypad to type text.

WF18:A text to speech application would help people who have trouble speaking clearly.

3.1.4 Improved Non Functional Understanding of the Domain: World

WNF1: The elderly expect their phone to respond to commands within 2 seconds.

WNF2: The elderly people expect any application to be installed within 30 seconds.

WNF3: It is helpful for an elderly person to alert his care taker to immediately attend to him with just one-click

WNF4: The user expects the charge on their phone to last for at least one day.

WNF5: Elderly people prefer to use applications that are user friendly.

WNF6: The user prefers systems that never crash.

3.2 Requirement Specification

3.2.1 Functional RS – Improved understanding of Software System Requirements: FRs                   

The objective of HOPE is to provide a platform for helping the elderly, the disabled having unclear speech, hearing loss, weak vision and/or memory loss, in day – to day communications. This platform helps the elderly, and this section deals with the domain: Functional requirements in Requirement Specification.

FR-01: Elderly people use HOPE to communicate effectively with other people and perform their day to day activities without a frustrating level of difficulty.

FR-02: HOPE shall assist users in the following activities:

FR-03: The speech to text converter is used to interpret every word spoken by the elderly person.

FR-04: The MyPage application will allow the user to store all personal information about the user

27

FR-05: Elderly people with memory problems will use the Pill-Tracker to remind them to consume medicines and also update medicine stock with the help of the care taker.

FR-06: An elderly person with unclear speech shall use text to speech converter to express messages to people within 5 meters.

FR-07: The care taker of the elderly person stores information of the location of the everyday things used at home so that it is easily accessible.

FR-08: The DietManager feature is used by all users to input the health condition rangeand obtain a list of food items to be consumed and to be avoided.

FR-09:The Walk-O-Meterapplication is used by the elderly person while walking to calculate the approximate calories burnt. A timer started at the beginning of a walking session computes the calories based on an average walking speed determined for elderly people.

FR-10: The applications for contacts with pictures and also elements of Pic-talk not only display the images but also read out the content aloud.

FR-11: The system will help the usersto store personal and secured information like Banck Account details, SSN, etc with a password protection feature in the MyPage feature of the HOPE application.

FR-12: The call for help feature allows the user to select from the emergency services, family and their assistant and puts them in touch within 10 seconds with just one-click reach

FR-13: The templates used for text messages and PicTalk are self-explanatory and help the elderly person frame his message easily and convey quickly.

FR-14: The Pic-Talk which is used as a message board creates a message which can be displayed as well as sent as a text message to others.

FR-15: The medication assistant reminds the user to take their medicines by displaying the name or image of the medicine at the time prescribed by the doctor.

28

3.2.2 Non-functional RS -Improved understanding of Software System Requirements: NFRs

This section deals with the non - functional requirements of the requirement specification.

NFR-01: The speech-to-text converter should be able to convert spoken words to text within 10 seconds.

NFR-02: The output audio should be without noise interference and be output within a 1 second delay.

NFR-03: Icon names follow a standard format and explain the functionality in a maximum of two words. Ex: PicTalk (Talking with the Help of Pictures) ,PillTracker (Keep a track ofmedicine to be consumed)

NFR-04: The system should be able to detect words spoken by the user at 60 dB and convert them to images within 2 seconds.

NFR-05: All sound produced by the system shall be within 80-100 dB.

NFR-06: Any image icon when clicked should read its functionality aloud within 2 seconds.

NFR-07: Conversion from text to speech must take place within 10 seconds.

NFR-08: The output audio from the system should be able to be heard correctly at least 99% of the time.

NFR-09:The speed of the audio output should not exceed 100 words per minute to the elderly people.

NFR-10:The font should be re-sizeable within the range of 12 to 30 according to the user’s convenience.

NFR-11: Emergency and Help icons are strategically placed on every screen of the HOPE application so that it can be reached with just one-click.

NFR-12:The retrieval of the photos should take place within 0.5 seconds.

NFR-13: The system should allow storage for at least 2 photos to identify a contact, pet or object.

NFR-14: The reminder should be sounded within 2 seconds of the time scheduled for medicine.

NFR-15: The phone should never display the wrong medicine image.

29

NFR-16: The application display food items suitable to the health condition range provided by the user.

NFR-17: The application should compute approximate calories burnt for a given walking session

NFR-18: All personal details stored in the MyPage feature of the system by the user should be secure from general access and be password protected. The care taker is aware of the password.

NFR-19: The HELP icon when clicked produces an alarm of 80-100db intensity.

NFR-20: The care-taker shall be present within a vicinity of 15 feet radius and will be able to hear the sound produced by the alarm. .

NFR-21: The user interface should be rated 4.5 out of 5 or higher when given to elderly people.

NFR-22: The medicine stock is constantly updated by the user or care-taker. The application accurately decrements the medicine count once the alarm has been triggered and the user has confirmed the consumption of the medicine.

NFR-23: The image size for all applications shall be consistent and will be fixed.

NFR-24: The elapsed time between the click of an icon and the sound generation should be less than 1 second.

NFR-25: Emergency calls should be completed within 10 seconds.

30

4. Preliminary Prototype

In this section we describe a prototype of the HOPE system. Here we describe samplepage for some features such a way that the user understands the working of the project.

4.1 Home ScreenThe home screen provides the user with various features for which the user needs assistance. The various features are ‘Emergency’, ’Speech2Text’, ‘Text2Speech’, ‘Facelook’, ‘Mypage’, ‘Myshelf’, ‘DietManager’, ‘Walk-O-Meter’, ‘PicTalk’.

31

4.2 Speech2Text

Speaking includes functionality for communication assistance. This has function to convert the spoken words to text.

32

4.3 Text2SpeechText2Speech includes functionality for communication assistance. This has function to converts the written text to speech for those users who have problem with speech.

33

4.4 Pill Tracker

The PillTracker alerts the user when he/she needs to take the medicine. For visually impaired the system reads aloud the name of the pill that should be taken.

34

4.5 MyShlef

The MyShelf is used by old people with loss of memory to keep track of their items. It consists of the list of items and when the user selects it, the system displays its location.

35

4.6 DietManager

The DietManager suggests food for old people according to their health condition. The DietManager consists of three signals in red, orange and green colors that indicate the severity of their health.

36

4.7 PicTalk

The PicTalk is a very useful application for old people who have difficulties in speaking. Here, we store the images of most frequently spoken words along with the name. Once the image is clicked an appropriate sentence is communicated to the other person. We have three tabs for food, hygiene and general with appropriate words in them.

37

4.8 MyPage

The MyPage displays the general information about the person who is using the smartphone. This stores the name, age, address, phone number and the emergency contact number related to the person. It also displays the blood group and other health information. The old people can also save information like SSN, Bank account number etc. which is protected using a passcode, that is known only to the person who owns the smartphone.

38

4.9 FaceLook

The FaceLook consists of contact information about the people who are related to the elder person along with their contact number. We also store the image of the person which is displayed. There is a call button and a text button, in case the old people want to call or text the person displayed. They can also search for a contact by typing the name in the search box.

39

5. Tracebility:

The Tracebility matrix describes the dependency of the functional and the non-functional requirements to the domain requirements.

DOMAIN REQUIREMENTS0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24

FR 1 x x x x x x xFR 2 x x x xFR 3 X X X x x x x x x x xFR 4 X X X x xFR 5 x x x x xFR 6 x x x x x x x x x x xFR 7 X X X x xFR 8 X X X x xFR 9 x x x xFR 10 x x x x xFR 11 x x x x x xFR 12 X X X x XFR 13 X X X x XFR 14 x x x X x xFR 15 x x X xNFR 1 x x x x x xNFR 2 X X X x X x x x x x xNFR 3 X X XNFR 4 x x x x x xNFR 5 x x x x x x x x x x xNFR 6 x x x X x X xNFR 7 X X X x x x xNFR 8 X X X x X x x X x x xNFR 9 x x x x X x x X x x xNFR 10 x x x xNFR 11 X X X x xNFR 12 X X X x x x x xNFR 13 x x x x x x x x xNFR 14 x x x xNFR 15 x x xNFR 16 X X X x xNFR 17 X X X xNFR 18 x x x x xNFR 19 x x x X XNFR 20 X X X x xNFR 21 X X XNFR 22 x x x x

40

References

1. Requirement Engineering –Advanced Requirement Engineering. CS/SE 6361, Section 001, Spring 2012. http://www.utdallas.edu/~chung/RE/syllabus.htm

2. Software Engineering (8thEdition) – Ian Sommerville3. Software Engineering, A practitioners approach (7th Edition)– Roger S Pressman4. http://www.psychpage.com/learning/library/assess/feelings.html 5. Dr. Sundar Raj All India Institute of Speech and Hearing, Mysore, Karnataka, India6. Dr. Jagadeesh R Malloli, ENT Surgeon, Vikram Hospital, Mysore, Karnataka, India7. Dr. Suma Harindra, Audiologist, JSS Institute of Speech and Hearing, Mysore, India

41

Appendix – A

Why we stand out of the crowd?

1. Our system consists of functions that make our project better. Some of them are:a) PillTracker and MyShelf are useful for old people with memory loss.b) Old people can’t manage their finances using our finance manager.c) DietManager suggests the food that should be taken by old people for healthy life.d) Every page has the emergency button.

2. Our project aims to attain all possible features that could help a person with difficulty, rather than working on a few restricted features.

(2. In our project we are using the spiral model. After implementation, the other stages go up to show the relationship between the various development stages and its associated testing. 3. Our application utilizes almost all the basic features of a smartphone for various unique features.

4. The Pareto Principle (also known as the 80/20 rule) the idea is that by doing 20% of the work you can generate 80% of the benefit of doing the whole job.We have used Pareto 80-20 principle for the measurement of the percentage of the changes in the requirements.

5. All icons are self-explanatory; the icon size is also larger enough to be easily identified.

6. The features and by whole, the application has been designed in a to be very user friendly and would take minimum time to learn and handle.

7. There is more compliance between our prototype and our requirements.

Future Scope of the project:

1. A one-touch text or voice message to contacts in case of an emergency.

2. Transmit the medical report of the user to anybody necessary through e-mail.

3. Use image recognition to recognize a person and retrieve the profile of that person from contacts.

42

Appendix – B: Requirements Prioritization

Out of the total 25 domain requirements, ten main requirements were considered and prioritized as below.

Domain Requirement

(DR)

Functional Requirement

(FR)

Priority Reason

DR-03 FR-01 High Emergency Service access.

DR-07 FR-02 Medium --

DR-03 FR-03 Medium --

DR-04 FR-04 Low --

DR-05 FR-05 Medium --

DR-19 FR-05 High Access to drugs.

DR-07 FR-07 Medium --

DR-22 FR-08 High Change in Pressure and Sugar levels

should be updated.DR-09 FR-09 Low --

DR-10 FR-10 Low --

Appendix C: Minutes of Meeting

43

Date Location & Time Agenda Summary

02/04/2012 Library4:00 PM

SRS Template,Requirements

Finalized the SRS template. Choose the process model & requirements. Distribute modules to the group.

02/11/2012 Library4:00 PM

Issues related to the requirements

Discussed the issues related to the requirements & their possible solutions.

02/18/2012 Library4:00 PM

Improvise on the initial requirements

Brainstorming on the initial requirements and improved them to suit the application.

02/25/2012 Library4:00 PM

Reviewed the rough draft of the documentation,Prepared a sample SRS Template

Reviewed the modules of each team member. Prepared a SRS template based on the team member’s feedback.

03/03/2012 Library4:00 PM

Prepared Presentation & Documentation and finalizing the SRS for Interim Phase - 1

Finalized the presentation & documentation for Interim Phase - 1

03/10/2012 Library4:00 PM

Document review cycle

Reviewed the work of individual team member. Finalized on the SRS template and sent to high end review.

03/17/2012 Library4:00 PM

Making changes to the documentation

Each team member was given a sub-section of the document to review & make modifications.

03/24/2012 Library4:00 PM

Final review of -Phase – 1 Documentation

The works of team members are reviewed and finalized the SRS document.

44

45