HELPING ELDERLY LIVE PLEASANTLY



Revision HistoryEditorVersionCommentVignesh0.31Initial template createdNeha 0.32Updated section 2Govindarajan0.33First draft of section 3Aarthi0.34Updated functional requirementsSriram0.35Cleaned up world issuesKumaran0.36Introduced a section for testingBalaji0.37Inserted Screenshots for all the features implementedSriram0.38Defined feature specific creeping rateNeha0.39Cleaned up content in many areas and formattingAarthi0.40Final Phase-II WRS document 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 Spiral 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 ModelFor 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.Figure 1: Spiral modelProject DeliverablesPhaseDeliverableDatePhase 0Preliminary Project PlanJanuary 25nd, 2012Phase 1Interim Project 1 Requirement Specification Requirement Analysis Presentation March 6th, 2012 Phase 1Final Project 1Improved Requirement SpecificationImproved Requirement Analysis PresentationMarch 27th, 2012Phase 2Interim Project 2Improved Requirement Specification / AnalysisImplementationTestingPresentationApril 17th, 2012Phase 2Final Project 2 Modified Implementation Modified Testing PresentationMay 3rd, 2012Project ResponsibilitiesDeliverablesDevelopersReviewersTeam leadUserDomain Expert1.Revised WRS document 2.Process specification Neha MalloliAarthi Giridharan Balaji ShanmugamAarthi GiridharanSriram SridharanNeha Malloli 3.Vision document Kumaran SenapathyBalaji Shanmugam Kumaran SenapathySriram SridharanKumaran Senapathy4.Working model of the systemVignesh SwaminathanGovindarajan PaneerselvamAarthi GiridharanSriram SridharanBalaji Shanmugam Vignesh Swaminathan1. Introduction1.1 PurposeUnfortunately 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 ScopeThe broad scope of our HOPE project is to make an efficient TO-BE= AS-IS (HOPE-Phase-1) + Revised Requirement ElicitationTo 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.1.3 Definitions, Acronyms, and AbbreviationsHOPE - Helping Our People Easily1.4 Summary of Domain RequirementsDR1The user needs basic knowledge about using the smart phoneDR2The phone must have HOPE installed in it.DR3Click on the emergency icon displays list of emergency contacts to be called.DR4Click on icon will convert speech to textDR5Click on icon will convert text to speech.DR6 Old people suffering from hearing problem will need a converter.DR7Phone must have an in-built microphone, typically to record the speech.DR8Old 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. DR9When 2 people have problems in oral communication, they can use pictograms for communication.DR10Some 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.DR11The contacts page should give a brief description of the picture selected.DR12When the user types a message, the person at the opposite must be able to realize the scenario and act to itDR13Person assisting the old people must be near the phoneDR14User must know how to use message boardDR15Old people suffering from memory loss due to ageing will need help remembering the location of everyday things placed at homeDR16An application should store the location information of the basic things at homeDR17The phone should have good sound quality, typically to reproduce clear sound DR18Old people suffering from memory loss due to ageing will need help remembering people and their relationshipsDR19Some 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.DR20Old people may have issues with remembering bank details, SSN, etc.DR21Old people may have issues with choosing foods to eat and to avoid.DR22A Diet Manager feature should assist the user in choosing the foods to eatDR23Elderly people may need immediate assistance in case of emergency situations.DR24A Help Icon feature on all screens should sound an alarm to alert the care taker.1.5 Summary of Functional RequirementsFR1Displays list of Emergency contacts that could be called by a single touch.FR2Converts Voice input in to textual form and if possible in picture format.FR3Converts textual into a voice output.FR4 Displays all personal information stored by the user.FR5Sounds alarm to the user at the stored time to consume the medicine and updates medicine stock.FR6Text to speech converter and sound output feature is for people with unclear speech.FR7 Prompts the user about the location on selecting the item.FR8Displays the list of food items one should and should not consume.FR9Displays the distance covered and calories burnt in that session.FR10Displays and produces the sound for the chosen picture.FR11Elderly people can securely store Bank details, SSN details under the password protected MyPage feature.FR12Elderly people perform speed dial to their relatives or doctors.FR13Templates are used for Text2Speech as well as PicTalk featuresFR14PicTalkcreates 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 specificNFR1Speech to text converter should be able to convert spoken words to text quickly.NFR2The output audio should be clear.NFR3The icon names should be self-explanatory NFR4Words spoken by the person should be loud enough.NFR5The functionality of the message should be audible to the old person.NFR6The image icon when clicked should read its functionality aloud immediately.NFR7Conversion from text to speech must be as quickly as possible.NFR8Speech should be audible.NFR9The message should be clear to the listener.NFR10The font should be readable to the user.NFR11Emergency icon should always be one click away to provide high accessibilityNFR12The retrieval of the photos should be fast.NFR13Store few photos to identify a contact, pet or an object.NFR14The reminder should be invoked at the correct time.NFR15The phone should display the name or image of the medicine at the correct time.NFR16The application should display appropriate food items based on health condition entered by the userNFR17The application should provide approximate calories burnt based the time spent walkingNFR18User's personal and bank details should be password enabled to provide securityNFR19The Help button feature in the application should sound an alarm when clickedNFR20The alarm sounded should be audible enough to the care takerNFR21The switching between two features in the application should be easyNFR22The medicine stock and reminder stored by the care taker should be accurate and precise since it is critical to patient’s health. NFR23The images should be large enough to be recognized.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.Domain IssuesThe domain issues in the project are explained below:Issue IDR-00: Requires SmartphoneDescriptionThe old people should have access to smartphone to use HOPE application. OptionsOption A: Apple-iPhoneUser friendly environment (+)Expensive (-)No choice in handset (-)Option B: Android phone is requiredComparatively Cheaper (-)Choices in handset (+)Frequent updates in software (+)Option C: No PhoneRequirement not satisfiedDecisionOption B-Android platform to develop our application because it’s easier to develop and also give options in choosing handset.Issue IDR-01: Basic knowledge in using the smartphoneDescriptionThe user must have some knowledge on how to use the smartphoneOptionsOption A: User manual to assist the elderlyUnderstand the working of the application (+)Time consuming in creating manual (-)Option B: Assume the user know about the smartphoneReduces the effort in development (+)Saves development time (+)If the user does not know to use smartphone, he/she cannot use the application (-)DecisionOption A-Easily accessible to all users.Issue IDR-03: Emergency and Help option in applicationDescriptionEmergency and Help is not clearly defined in the project definitionOptionsOption A: State Emergency and Help option Improves the project definition (+)User is comfortable when Help is available (+)Option B : Remove Emergency and Help from project definitionImportant aspect of the project is removedDecisionOption A-We redefine the project description and give details about Emergency and Help. We also mark them as important feature in the application.Issue IDR-04: Convert speech to textDescriptionIssue-IncompletenessDoes not specify the icon to be clickedOptionsOption A: Remove the specificationOption B: Clearly indicate the name of the iconDecisionOption B-Specify the name of the icon to be clicked to complete the statementIssue IDR-05: Click on icon will convert text to speech.DescriptionIssue-IncompletenessDoes not specify the icon to be clickedOptionsOption A: Remove the featureOption B: Clearly define the icon to be clickedDecisionOption B-Specify the name of the icon to be clicked to complete the statementIssue IDR-06: Elderly with hearing problem needs a converterDescriptionIssue-IncompletenessDoes not specify the name of the converterOptionsOption A: Remove the conversion featureOption B: Specify the name of the converterDecisionOption B-Indicate the name of the converter that converts speech to textIssue IDR-07: Smartphone should have microphone typically to record speechDescriptionIssue-AmbiguityImplies there are many ways to use the microphoneOptionsOption A: Remove ‘typically’ from the statementOption B: Indicate all the possible ways to use the microphoneDecisionOption A-After removing the word ‘typically’ the statement indicates that microphone is for recording speechIssue IDR-08: Display Calories burnt in a walking session DescriptionIssue: Infeasible Technical implementation and IncompletenessOld people will be advised to walk in-order to maintain good health. They might want to track the calories burnt by walking. The walking speed may vary from age, health condition and time of the day. OptionsOption A: Remove the featureImportant 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.Increases the development time increases due to complicated calculationIncludes a feature to promote good healthDecisionOption B-The old people mustbe able to track their healthy routine easilyIssue IDR-09: Use of Pictograms to communicateDescriptionOld people with speech disorder will find it difficult to convey their message. They may need a pictogram to display images to assist them communicateOptionsOption A: Remove the featureOption B: Remove the word ‘may’ in order to indicate it is requiredOption C: Clearly define the meaning of ‘need’ and ‘speech disorder’DecisionOption C-State clearly the meaning of need and speech disorder. Develop the feature accordingly.Issue IDR-10: Difficulty in SpeechDescriptionSome 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.OptionsOption A: The user writes a message on the phone using stylus and it is converted to speechEase 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 (-)DecisionOption B-Implementation is easy.Issue IDR-11: When an image is clicked, the system tells about the image selectedDescriptionIssue-IncompletenessStatement does not specify what kind of images must be clicked.OptionsOption A: Remove the statementOption B: Specify the name of images to be clickedDecisionOption B-Clarify the specification by specifying that the images are of the contacts stored and the corresponding details of that contact is displayed when clickedIssue IDR-12: Understand the situationDescriptionWhen the user types a message, the person at the opposite must be able to realize the scenario and act to itOptionsOption A: Remove the statement.Option B: Clearly state the meaning of ‘scenario’DecisionOption B-Clarify the statementIssue IDR-13: Person assisting the old people must be near the phoneDescriptionIssue-AmbiguityOptionsOption A: Clearly state the distanceOption B: Expand the statement by indicating that the person assisting the elderly must be able to understand the messageDecisionOption B-Make the statement understandableIssue IDR-14: User must know how to use message boardDescriptionIssue-AmbiguityOptionsOption A: Define the message board such that it is understood by anyoneOption B: State clearly whether user must know typing or understand the optionDecisionOption B-Message board clearly definedIssue IDR-15: Old people with weak memory require a tool to remember location of everyday things placed at homeDescriptionIssue-IncompletenessDescribe the statement clearly for “everyday” thingsOptionsOption A: Remove the featureOption B: MyShelf feature will be used to store location information for important household things like house keys, medical records.DecisionOption B-A prioritized list of things will be used to store location information for the things in the list.Issue IDR-17: The phone should be able to reproduce clear soundDescriptionIssue-AmbiguityThe exact meaning of “clear” cannot be definedOptionsOption A- Remove the statementOption B- The statement should be redefined to express the exact meaning of “clear” sound.DecisionOption B- Define the speaker quality required to successfully run all applications.Issue IDR-18: Remembering people and placesDescriptionIssue-Incompleteness. The kind of help is not mentioned clearly.OptionsOption A: Remove the statementOption B: Clearly specify the help needed.DecisionOption B-Old people need this feature to identify people Issue IDR-19: Help with medicinesDescriptionOld people may forget to take medicines at the right time. We need a feature to remind to take medicine.OptionsOption A: Remove the featureReduces 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 timeWhen a new medicine is prescribed, it must be added to the list (-)Assists the old people in taking tablets at right time (+)DecisionOption A-We need a feature to help old people with memory lossIssue IDR-20: Any end-user may have difficulty in remembering bank detailsDescriptionThe word ‘may’ do not specify the seriousness of the situation. Moreover ‘effectively’ adds vagueness to the application as it is perceived differently by different peopleOptionsOption A: Remove the words "may" and "effectively”.Option B: Clearly define the statementDecisionOption B-Restructure the statement by merely changing the words that puts importance on the statement.Issue IDR-21: Old people may have difficulty in choosing what to eatDescriptionThe issue is vagueOptionsOption A: Remove this featureOption B: Implement this feature by integrating different choices of foods based on health condition.DecisionOption B-Integrating different choices of food helps the elderly peopleIssue IDR-22: Diet Manager feature should assist the elderly people chose their foodDescriptionThe 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 not OptionsOption A: Remove this featureOption B: Specify a range for the health conditions and suggest based on that.DecisionOption B-Specifying a range helps in narrowing down to a critical level in choosing different foods. Issue IDR-23: Elderly people may need assistance in emergenciesDescriptionIssue-IncompletenessThe kind of emergency situations are not stated clearly.OptionsOption B: Remove the word “may” Easy (+)Option A: Indicate the kind of emergencies Give a specific requirement (+)Clearly state the original requirement (+)DecisionOption B-Define the words such that the stakeholders realize the emergency situationsIssue IDR-24: Help Icon sounds an alarm to alert the care takerDescriptionThe word “alerts” is not clearly defined.OptionsOption A: Help icon should sound an alarm which is audible to the care-takerOption B: Remove this feature. Do not use Bluetooth technologyReduces the cost (+)Decreases development time (+)Removes an important feature (-)DecisionOption A-Invest on speaker with audibility suitable to the care taker. 2.2 Issues with Functional RequirementsIssue IFR-01Description“Displays list of Emergency contacts that could be called by a single touch”Problem: Issue-Incomplete, AmbiguityWho 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)?OptionsOption 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.DecisionOption B - HOPE system is intended to help elderly people communicate effectively with other people carry out their routine with ease.Issue IFR-02Description“Voice input into textual form.”Problem: Issue- AmbiguityDoes not specify who provides speech. Also the term clearly is not quantified.OptionsOption 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.DecisionOption 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.Issue IFR-03Description“Converts text into voice output”Problem: Issue- IncompleteDoes not specify what the problems are.OptionsOption A: People suffering with loss of vision.Option B: People suffering from memory loss.Option C: People suffering with hearing issues.DecisionOption C - Speech to text is used to help people suffering from hearing problems.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.OptionsOption A: Elderly person’s information like Name, address, phone number, etc.Option B: Younger person’s information.DecisionOption B: Elderly person’s information like Name, address, phone number, etc.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.OptionsOption 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.DecisionOption A: Old people are reminded of their medicines and they/ their caretaker update the stock whenever a new medicine is bought.Issue IFR-06Description“Prompts the user about the location on selecting the item”Problem: Issue- AmbiguityWhat location?OptionsOption A: Prompts the location of the object inside the house/ office.Option B: Prompts the name of the city.DecisionOption A: Prompts the location of the object inside the house/ office.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?OptionsOption 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.DecisionOption A: Elderly people enter the values for the asked parameters and corresponding diet to be followed is listed.Issue IFR-08Description“Display the distance covered and calories burnt in that session”Incomplete definition of the process.OptionsOption A: Input the distance covered manually and calculate burnt caloriesOption B: Calculates the distance by the time spent on walking along with the average speed and hence computes calories burnt.DecisionOption B: Calculates the distance by the time spent on walking along with the average speed and hence computes calories burnt.Issue IFR-09Description“Displays and produces the sound when a picture is chosen.”Incomplete definition of the parameter used.OptionsOption 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.DecisionOption A:Outputs sound of the name of the contact image or images stored in pictalk.Issue IFR-10Description“Store secure information with password protection.”Problem -AmbiguityWhat kind of information is considered secure?OptionsOption A: DOB, Contact information, etc.Option B: Bank details, SSN, etc.DecisionOption B: Bank details, SSN, etc.Issue IFR-11 Description“Should be able to call the emergency contacts using speed dial.” Problem –AmbiguityWho are the emergency contacts?OptionsOption A: Nephew, Colleague, etc.Option B: Doctor, Care taker, etc.DecisionOption B: Doctor, Care taker, etc.Issue IFR-12Description“Templates are used for text to speech as well as pictalk.”Issue-IncompletenessHow should the template be?OptionsOption A: Textual/ Pictorial representation of thoughts that involves minimum editing to be done.Option B: Feed more input to the existing template.DecisionOption A:Textual/ Pictorial representation of thoughts that involves minimum editing to be done.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?OptionsOption A: Text Message.Option B: Picture Message.DecisionOption A: Text Message.2.3 Issues with Non-Functional RequirementsIssue INR-01: NFR1-Speech to text converter should be able to convert the spoken words to text quickly DescriptionProblem -Issue: Ambiguity: The term “quickly” is not specificOptionsOption A: Remove the statement.Option B: Define the time range for the conversion.DecisionOption B - The time range should be specified in seconds.Issue INR-02: NFR2-The output audio should be clearDescriptionProblem- Issue: UnsoundnessThe term “clear” is not specificOptionsOption A:Remove the FeatureOption B: Rephrase the statement as “The audio should not have any delay or distortion”. DecisionOption B - Speech to text converter provides an important interface for people to communicate clearlyIssue INR-03:NFR3- Icons used should be self-explanatory.DescriptionProblem-Ambiguity: The phrase “self-explanatory” does not clearly define the purpose of the icons.OptionsOption A: Have pictures depicting the purpose of the application.Option B: Have icons carrying the name of the application.DecisionOption A: Have pictures depicting the purpose of the application.Issue INR-04:NFR4- Words spoken by the person should be loud enough.DescriptionProblem: Vagueness The phrase “loud enough” does not specify the level of loudness required.OptionsOption 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.DecisionOption B-It is indicates how loud the speech should be thereby removing the ambiguityIssue INR-05:NFR5- The functionality of the message should be audible to the old personDescriptionProblem – Ambiguity. There is no way to assess if the feature is audible, as the audibility faculty varies from person to personOptionsOption A: Remove the statement.Option B:Define the range for audio levels.DecisionOption B - The range of audio levels should be specified clearly to prevent ambiguityIssue INR006:NFR6- The image icon when clicked should read its functionality aloud immediatelyDescriptionProblem: Incompleteness. The term immediately is not preciseOptionsOption A: Remove the statementOption B: Define the time range by which the functionality should be read aloud. DecisionOption B - The time range should be specified in seconds thereby making the requirement more specificIssue INR007:NFR7- Conversion from text to speech must be as quickly as possible.DescriptionProblem Issue: Unsoundness, Inconsistency. The phrase “as quickly as possible” cannot be quantified.OptionsOption A: Remove this phraseOption B: “As quickly as possible” implies fast. Hence a specified time bound must be specified. DecisionOption B - It is simple and does not show different behavior of the system.Issue INR008:NFR8- Speech should be audible.DescriptionProblem -Issues: Unsoundness, incompleteness. The word “should” does not provide binding provision. NFR does not define audible.OptionsOption 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.DecisionOption B- It is simple and does not show different behavior of the system.Issue INR009:NFR9-The message should be clear to the listener.DescriptionProblem: Issue-Ambiguity. There is no specific sense clarity of the message.OptionsOption A: Remove the entire statement.Option B: Make the message clear by keeping the screen wider.DecisionOption B- The reader is going to see that the message in a wide screen, and hence in bigger font, thereby addressing issues with reading.Issue INR010:NFR10- The font should be readable to the userDescriptionProblem: Unsoundness - The degree of readability varies from person to person.OptionsOption A: Follow the standard font template for all applications.Option B: Remove this requirement.Option C: Have a resizing option to increase or decrease the font size depending upon the vision capability of the user. DecisionOption 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.Issue INR011:NFR11- The emergency icon should always be one click awayDescriptionProblem - Ambiguity: The term ‘one click’ is not precise. Also, the term ‘always’ does not specify under what situations.OptionsOption 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.DecisionOption 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.Issue INR012:NFR12-The retrieval of the photos should be fast DescriptionProblem- Issue: Incompleteness: There should be a set time bound to specify the retrieval time of a picture from the albumOptionsOption A: Do not address this requirement.Option B: The retrieval of a picture should not take more than 5 MS. DecisionOption B - This time bound though assumed makes the requirement more specific and hence easier to implement.Issue INR013:NFR13-Store few photos to identify a contact, pet or an objectDescriptionProblem: Issue – Vagueness “Few” is not a quantifiable term.OptionsOption A: Do not implement this requirement.Option B: Specify that there should not be more than 2 photos for a particular contact.DecisionOption B-As it removes the vagueness in the requirement, thereby making it more specific and hence addressable.Issue INR014:NFR14- The reminder should be invoked at the correct timeDescriptionProblem: Issue – VaguenessThere is no such benchmark as Correct time. It is an ephemeral conceptOptionsOption A: Specify a stipulated time at which the reminder must be sounded.Option B:Do not implement this requirementDecisionOption B -As it removes the vagueness in the requirement, thereby making it more specific and hence addressable.Issue INR015:NFR15- The phone should display the name or image of the medicine at the correct time.DescriptionProblem -Vagueness: There is no such benchmark as Correct time. It is an ephemeral conceptOptionsOption A:Do not implement this requirementOptionB: Specify a stipulated time at which the name and image must be sounded.DecisionOption B - On implementing Option A the requirement tends to become more specific.Issue IN0016:NFR16- Display appropriate food items.DescriptionProblem : Issue –AmbiguityThe term appropriate does not give a clear picture on what is appropriate.OptionsOption A: Remove this requirement.Option B: Specify the food items that match the input fed by the user.DecisionOption B: Specify the food items that match the input fed by the user.Issue IN0017:NFR17-Display approximate calories burntDescriptionProblem - Issues: Ambiguity. The word "approximate" is not clearly defined.OptionsOption A: Use the closest possible value to the actual calories burnt.Option B: Use a randomly chosen value. DecisionOption A: Use the closest possible value to the actual calories burnt.Issue IN0018:NFR18-User's details should be secureDescriptionProblem-Issue: Incompleteness. There is an ambiguity in understanding the idea of securityOptionsOption 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 partyDecisionOption A - As it entails highest degree of understanding.Issue IN0019: NFR19- The help button should produce an audible alarm.DescriptionProblem – Ambiguous. The word "audible" does not provide any clarity.OptionsOption A: The alarm should be audible enough to alert the care taker when he/ she is in a closer range.Option B: Remove requirement.DecisionOption A: The alarm should be audible enough to alert the care takerwhen he/ she is in a closer range.Issue IN0020: NFR20- Navigating between two features in an application should be easy.DescriptionProblem- Ambiguity. The word "easy" is not clearly defined.OptionsOption A: User friendly GUI and a limited number of steps in navigation.Option B: Remove requirement.DecisionOption A:User friendly GUI and a limited number of steps in navigation.Issue IN0021 -NFR21- Accurate medicine reminders and stock updates.DescriptionProblem – Issue: Vagueness. The word accurate is unclear in its definition.OptionsOption A: Prompt reminders on time and proper stock maintenance.Option B: Remove requirement.DecisionOption A: Prompt reminders on time and proper stock maintenanceIssue IN0022:NFR22- Large images in order to recognize.DescriptionProblem: Issue - Inconsistency. Images though large may include variable sizes.OptionOption A:Consistent image size is image size is maintained by cropping very large images when needed.Option B: Accept images of a standard size.DecisionOption A: Consistent image size is image size is maintained by cropping very large images when needed.3. DECISION AND RATIONALE: INTEGRATED MODEL (IMPROVED UNDERSTANDING)FunctionalNon-FunctionalW5.1.35.1.4R5.2.15.2.2S5.2.15.2.23.1 WORLDThe words World, Domain and Environment all refer to things in the environment (application domain) that are true regardless of the proposed system.This section includes the improved understanding of the domain requirements. It breaks down the problems, goals, and functional and nonfunctional aspects of the domain requirements.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. 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. Vision1. 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 Loss1.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.2GoalsG1:Assist someone with hearing loss in communicating with the other personG2:Help someone with hearing loss in understanding the other personG3:Help someone with difficulty in expressing his or her ideas through speechG4:Help someone in emergency to be immediately assisted.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 authoritiesG9: 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.3Improved Functional Understanding of the Domain: World with Backward TracebilityWF1:The user should have an Android phone ---- DR0WF2: The user should know how to use the basic features of the Android phone ---- DR1WF3: The phone must have HOPE services running on it. ---- DR2WF4: Users with loss in memory and vision must be sure to keep the mobile always with them----DR0WF5: Old people suffering from hearing problem will need a speech to text converter---- DR4WF6: There should always be a person within 10 meters of the old person to help him. ---- DR24WF7: The elderly who have trouble hearing will need a speech-to-text application to hear well----DR4WF8: The images of the frequently used words are stored in the phone’s memory---- DR18WF9: The elderly who have trouble remembering will need an application to remember the location of everyday used things. ---- DR15WF10:The user needs to keep the phone on their person to be able to use the system. ---- DR13WF11:Old people suffering from speech disorders will need to be able to use images or icons to ask for help when in need. ---- DR14 and DR10WF12:People with extremely unclear vision will need things read aloud to them instead of being able to read text. ---- DR17WF13:When two people have problems in oral communication they should use pictograms for communication. ---- DR14 and DR10WF14:Old people having speech clarity problems would benefit from a system that provides a user interface to type the message they want to express. ---- DR9WF15:Old people with memory problems will need applications to remind them of the locations of the things used every day. ---- DR15 and DR16WF16:Old people with memory problems will need applications to remind them of medicines to be consumed every day. ---- DR19WF17:A text to speech application would help people who have trouble speaking clearly. ---- DR53.1.4Improved Non Functional Understanding of the Domain: World with Backward TracebilityWNF1: The elderly expect their phone to respond to commands within 2 seconds. ---- NFR1, NFR7, NFR12WNF2: It is helpful for an elderly person to alert his care taker to immediately attend to him with just one-click ---- NFR11, NFR19, NFR20WNF3: Elderly people prefer to use applications that are user friendly.---NFR3,NFR10, NFR21,NFR233.2 Requirement Specification3.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 difficultyFR-02: HOPE shall assist users in the all 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 userFR-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 reachFR-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.3.2.2 Non-functional RS -Improved understanding of Software System Requirements: NFRsThis 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.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 30sp 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.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 sessionNFR-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.4. Sequence Diagrams to Represent the Functionality of the Features Implemented: EMERGENCY: MyPage: HELP: PicTalk: MyShelf:5. SIG FOR NON FUNCTIONAL REQUIREMENTS5.1 Usability5.1.1 Changeability: System should allow the user to change the size of the icons and also the range of speech output according to his requirements.5.1.2 Convenience: All the icons are clearly readable to the user.5.1.3 Understandability: For the easier understandability, user manual was provided. Usage of the system is easier. Usability[HOPE] ++ ++ ++ Changeability[HOPE] Convenience[HOPE] Understandability[HOPE] ++ ++ ++ ++ Customizable Readable Icons User manual Ease to learnicons5.2 Security:5.2.1 Reliability: System will provide the accurate and faster responses.5.2.2 Authentication: In HOPE system MyPage contains the password authentication which can be added by the user for his convenience. So, the unknown person cannot use the system. Security[HOPE] ++ ++ password may be stolen ++ Reliability[HOPE] ++ Authentication[HOPE] Accurate response password check 5.3 Performance:5.3.1 Accuracy: HOPE is able to provide the accurate results 5.3.2 Responsiveness: All the responses are available within seconds.5.3.3 Minimum overhead: Navigation through the icons is easier as they are divided into related categories. Searching the required icon takes very less time. Performance[HOPE] ++ ++ ++ Accuracy[HOPE] Responsiveness[HOPE] Minimum over head ++ ++ ++ Accuracy in producing All responses are Searching time is less.Speech and text outputs. Fast. 6. KAOS MODELING6.1 SECURITY6.2 USABILITY7. TestingThe HOPE system by Andromeda followed the spiral model for software development. The two spirals concentrated on the Process Specification as well as Product Specification. The second spiral which incorporated the actual development of the product was successfully carried out by Team Andromeda by following the flavors of Agile Methodology. The development, testing, debugging and integrating the changes where all carried out concurrently. 8. Implementation ScreenshotsIn this section we describe a implementation of the HOPE system. Here we describe activity page for some features such a way that the user understands the working of the project.8.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’.8.2 EmergencyThe emergency feature consists of calling functionality to the doctor and emergency dial 911. 8.3 HelpThe help feature sounds an alarm when the old person is in need of assistance. There is an alarm start and stop button to 8.4 MyShelfThe 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. 8.5 PicTalkThe 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. 8.6 MyPageThe 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.8.7 FaceLookThe 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. 9. TRACEABILITY This section describes the traceability of our requirements analysis. The Tracebility matrix describes the dependency of the functional and the non-functional requirements to the domain requirements.DOMAIN REQUIREMENTS0123456789101112131415161718192021222324FR1xxxxxxxFR2xxxxFR3XXXxxxxxxxxFR4XXXxxFR5xxxxxFR6xxxxxxxxxxxFR7XXXxxFR8XXXxxFR9xxxxFR10xxxxxFR11xxxxxxFR12XXXxXFR13XXXxXFR14xxxXxxFR15xxXxNFR1xxxxxxNFR2XXXxXxxxxxxNFR3XXXNFR4xxxxxxNFR5xxxxxxxxxxxNFR6xxxXxXxNFR7XXXxxxxNFR8XXXxXxxXxxxNFR9xxxxXxxXxxxNFR10xxxxNFR11XXXxxNFR12XXXxxxxxNFR13xxxxxxxxxNFR14xxxxNFR15xxxNFR16XXXxxNFR17XXXxNFR18xxxxxNFR19xxxXXNFR20XXXxxNFR21XXXNFR22xxxx 10. ReferencesRequirement Engineering –Advanced Requirement Engineering. CS/SE 6361, Section 001, Spring 2012. Engineering (8thEdition) – Ian SommervilleSoftware Engineering, A practitioners approach (7th Edition)– Roger S Pressman. Sundar Raj All India Institute of Speech and Hearing, Mysore, Karnataka, IndiaDr. Jagadeesh R Malloli, ENT Surgeon, Vikram Hospital, Mysore, Karnataka, IndiaDr. Suma Harindra, Audiologist, JSS Institute of Speech and Hearing, Mysore, IndiaAppendix – AWhy 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) Sophisticated applications to manage finances cannot be handled by Old people. Hence we have reduced the complexity of the application by just allowing the user to store the bank account details with a secure password which the care-taker can assist with. d) Every page has the emergency button.2. Our project aims to attain maximum possible features that could help a person with difficulty, rather than working on a few restricted and highly sophisticated features3. In our project we are using the spiral model to design the requirements specifications of both phase-1 and phase-2. The actual android application development will follow an agile development process as this is a small project with rapid deliverables. 4. Our application utilizes almost all the basic features of a smartphone for various unique features.5. 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.Creeping Rate: The changes can be easily incorporated in the requirements stage. Once the requirements are finalized and implementation has started, introducing changes during the implementation phase proves expensive.Project Status (completed stage)Accommodation PercentageFinal Phase-1: Final Product Specification. Changes in Product requirements have to freeze15-40%Interim Phase-2: Final Design. Changes in requirement specification have to freeze10-15%Final Phase-2: Final Implementation. Changes in design have to freeze0-10%Feature specific creeping rate is also specified for vulnerable features developed by Team Andromeda.The features and their corresponding creeping rate threshold at Final Phase-2 stage of project is shown below:FeatureCreeping RateEmergency0-10%Help0-10%PicTalk0-5%MyPage0-15%DietManager0-5%MyShelf0-10%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.Requirements PrioritizationOut of the total 25 domain requirements, ten main requirements were considered and prioritized as below. Domain Requirement(DR)Functional Requirement(FR)PriorityReasonDR-03FR-01HighEmergency Service access.DR-07FR-02Medium--DR-03FR-03Medium--DR-04FR-04Low--DR-05FR-05Medium--DR-19FR-05HighAccess to drugs.DR-07FR-07Medium--DR-22FR-08HighChange in Pressure and Sugar levels should be updated. DR-09FR-09Low--DR-10FR-10Low--APPENDIX B – MINUTES OF MEETINGDateLocation & TimeAgendaSummary04/18/2012Phase 4 Clubhouse8:00 PM to 10:00 PMWRS Template, Initial RequirementsFinalized the WRS template. Choose the process model & requirements. Distribute modules to the group.04/19/2012EECS 4th Floor 4:00 PM to 6PMIssues related to the requirementsDiscussed the issues related to the requirements & their possible solutions.04/22/2012Library4:00 PM to 5:30 PMImprovise on the initial requirementsBrainstorming on the initial requirements and improved them to suit the application.04/24/2012ECSS 4th floor5:00 PM to 8:00 PMReviewed the rough draft of the documentation, Prepared a sample SRS TemplateReviewed the modules of each team member. Prepared a WRS template based on the team member’s feedback.04/28/2012Library4:00 PM to 8:00 PMPrepared Presentation & Documentation and finalizing the WRS for Final Phase - 2Finalized the presentation & documentation for Final Phase - 204/29/2012Waterview Apt 15314:00 PMDocument review cycleReviewed the work of individual team member. Finalized on the SRS template and sent to high end review.05/01/2012Library12:00 PM to 2:00PMMaking changes to the documentationEach team member was given a sub-section of the document to review & make modifications.05/02/2012Open Lab6:00 PM to 10:00 PMFinal review of Final Phase – 2 DocumentationThe works of team members are reviewed and finalized the WRS document. ................
................

In order to avoid copyright disputes, this page is only a partial summary.

Google Online Preview   Download