REVISION HISTORY
Editor
Version
Comment
Vignesh
0.31
Initial template created
Neha
0.32
Updated section 2
Govindarajan
0.33
First draft of section 3
Aarthi
0.34
Updated functional requirements
Sriram
0.35
Cleaned up world issues
Kumaran
0.36
Introduced a section for testing
Balaji
0.37
Inserted Screenshots for all the features implemented
Sriram
0.38
Defined feature specific creeping rate
Neha
0.39
Cleaned up content in many areas and formatting
Aarthi
0.40
Final 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 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.
2
Figure 1: Spiral model
3
Project Deliverables
Phase
Deliverable
Date
Phase 0
Preliminary Project Plan
January 25nd, 2012
Phase 1
Interim Project 1
March 6th, 2012
 Requirement Specification
 Requirement Analysis
 Presentation
Phase 1
March 27th, 2012
Final Project 1
Improved Requirement Specification
Improved Requirement Analysis
 Presentation
Phase 2
April 17th, 2012
Interim Project 2
Improved Requirement
Specification / Analysis
Implementation
Testing
Presentation
Phase 2
Final Project 2
May 3rd, 2012
 Modified Implementation
 Modified Testing
 Presentation
4
Project Responsibilities
Deliverables
Developers
Reviewers
Team lead
User
Domain
Expert
1.Revised
WRS
document
2.Process
specification
Neha Malloli
Balaji
Shanmugam
Aarthi
Giridharan
Sriram
Sridharan
Neha Malloli
3.Vision
document
Kumaran
Senapathy
Balaji
Shanmugam
Kumaran
Senapathy
Sriram
Sridharan
Kumaran
Senapathy
Aarthi
Giridharan
Sriram
Sridharan
Balaji
Shanmugam
Vignesh
Swaminathan
Aarthi
Giridharan
4.Working
Vignesh
model of the Swaminathan
system
Govindarajan
Paneerselvam
5
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 make an efficient
TO-BE= AS-IS (HOPE-Phase-1) + Revised Requirement Elicitation

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.
1.3 Definitions, Acronyms, and Abbreviations
HOPE - Helping Our People Easily
6
1.4 Summary of Domain Requirements
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.
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
7
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.
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
Sounds alarm to 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.
8
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.
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.
9
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.
10
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 Issues
The 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 Issues
The domain issues in the project are explained below:
Issue IDR-00: Requires Smartphone
Description 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.
Issue IDR-01: Basic knowledge in using the smartphone
Description The user must have some knowledge on how to use the smartphone
Options
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.
Issue IDR-03: Emergency and Help option in application
Description Emergency and Help is not clearly defined in the project definition
Options
Option 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 definition
11
Decision
 Important aspect of the project is removed
Option 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 text
Description Issue-Incompleteness
Does not specify the icon to be clicked
Options
Option A: Remove the specification
Option B: Clearly indicate the name of the icon
Decision
Option B-Specify the name of the icon to be clicked to complete the statement
Issue IDR-05: Click on icon will convert text to speech.
Description Issue-Incompleteness
Does not specify the icon to be clicked
Option A: Remove the feature
Options
Option B: Clearly define the icon to be clicked
Option B-Specify the name of the icon to be clicked to complete the statement
Decision
Issue IDR-06: Elderly with hearing problem needs a converter
Description Issue-Incompleteness
Does not specify the name of the converter
Options
Option A: Remove the conversion feature
Option B: Specify the name of the converter
Decision
Option B-Indicate the name of the converter that converts speech to text
Issue IDR-07: Smartphone should have microphone typically to record speech
Description Issue-Ambiguity
Implies there are many ways to use the microphone
Options
Option A: Remove ‘typically’ from the statement
Option B: Indicate all the possible ways to use the microphone
Decision
Option A-After removing the word ‘typically’ the statement indicates that
microphone is for recording speech
Issue IDR-08: Display Calories burnt in a walking session
Description Issue: Infeasible Technical implementation and Incompleteness
Old 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.
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.

Increases the development time increases due to complicated
calculation
12
Decision
 Includes a feature to promote good health
Option B-The old people mustbe able to track their healthy routine easily
Issue IDR-09: Use of Pictograms to communicate
Description Old people with speech disorder will find it difficult to convey their message.
They may need a pictogram to display images to assist them communicate
Options
Option A: Remove the feature
Option B: Remove the word ‘may’ in order to indicate it is required
Option 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.
Issue IDR-10: Difficulty in Speech
Description 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.
Issue IDR-11: When an image is clicked, the system tells about the image selected
Description 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 clicked
Decision
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
Issue IDR-12: Understand the situation
Description When the user types a message, the person at the opposite must be able to realize
the scenario and act to it
Options
Option A: Remove the statement.
Option B: Clearly state the meaning of ‘scenario’
Decision
Option B-Clarify the statement
Issue IDR-13: Person assisting the old people must be near the phone
Description Issue-Ambiguity
Options
Option A: Clearly state the distance
Option 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
13
Issue IDR-14: User must know how to use message board
Description Issue-Ambiguity
Options
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 option
Decision
Option B-Message board clearly defined
Issue IDR-15: Old people with weak memory require a tool to remember location of everyday things
placed at home
Description Issue-Incompleteness
Describe the statement clearly for “everyday” things
Options
Option A: Remove the feature
Option 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 information for
the things in the list.
Issue IDR-17: The phone should be able to reproduce clear sound
Description Issue-Ambiguity
The exact meaning of “clear” cannot be defined
Options
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.
Issue IDR-18: Remembering people and places
Description 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
Issue IDR-19: Help with medicines
Description 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 (+)
Decision
Option A-We need a feature to help old people with memory loss
Issue IDR-20: Any end-user may have difficulty in remembering bank details
Description 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”.
14
Decision
Option B: Clearly define the statement
Option 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 eat
Description The issue is vague
Options
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
Issue IDR-22: Diet Manager feature should assist the elderly people chose their food
Description 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 not
Options
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.
Issue IDR-23: Elderly people may need assistance in emergencies
Description 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
Issue IDR-24: Help Icon sounds an alarm to alert the care taker
Description 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 (+)
 Removes an important feature (-)
Decision
Option A-Invest on speaker with audibility suitable to the care taker.
2.2 Issues with Functional Requirements
Issue IFR-01
Description “Displays list of Emergency contacts that could be called by a single touch”
Problem: Issue-Incomplete, Ambiguity
 Who are intended people?
15



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.
Issue IFR-02
Description “Voice input into textual form.”
Problem: Issue- Ambiguity
Does not specify who provides speech. Also the term clearly is not quantified.
Option A: The speech of the elderly person has problems in clarity. Speech to Text
Options
converter is required to address this issue. The term clearly means every word
being interpreted.
Option B: Remove this requirement.
Option A- Elderly person suffering from hearing issues cannot hear the speech of
Decision
the other person and hence needs an external interface. Hence, this feature aids in
easier communication.
Issue IFR-03
Description “Converts text into voice output”
Problem: Issue- Incomplete
Does not specify what the problems are.
Option A: People suffering with loss of vision.
Options
Option B: People suffering from memory loss.
Option C: People suffering with hearing issues.
Option C - Speech to text is used to help people suffering from hearing problems.
Decision
Issue IFR-04
Description “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.
Option A: Elderly person’s information like Name, address, phone number, etc.
Options
Option B: Younger person’s information.
16
Decision
Option B: Elderly person’s information like Name, address, phone number, etc.
Issue IFR-05
Description “Alerts the user at the stored time to consume the medicine and update the
medicine stock.”
Problem: Issue- Ambiguity and Incompleteness
Does not specify who the user is and does not mention about how the stock is
managed.
Option A: Old people are reminded of their medicines and they/ their caretaker
Options
update the stock whenever a new medicine is bought.
Option B: Absent minded people.
Option C: Young people with health issues.
Option A: Old people are reminded of their medicines and they/ their caretaker
Decision
update the stock whenever a new medicine is bought.
Issue IFR-06
Description “Prompts the user about the location on selecting the item”
Problem: Issue- Ambiguity
What location?
Option A: Prompts the location of the object inside the house/ office.
Options
Option B: Prompts the name of the city.
Option A: Prompts the location of the object inside the house/ office.
Decision
Issue IFR-07
Description “Displays the list of food items one should/ should not consume.”
Problem: Ambiguity and Incompleteness
Who should not consume? On what basis does it say?
Option A: Elderly people enter the values for the asked parameters and
Options
corresponding diet to be followed is listed.
Option B: Everyone can choose their favorite food as their diet.
Option A: Elderly people enter the values for the asked parameters and
Decision
corresponding diet to be followed is listed.
Issue IFR-08
Description “Display the distance covered and calories burnt in that session”
Incomplete definition of the process.
Option A: Input the distance covered manually and calculate burnt calories
Options
Option B: Calculates the distance by the time spent on walking along with the
average speed and hence computes calories burnt.
Option B: Calculates the distance by the time spent on walking along with the
Decision
average speed and hence computes calories burnt.
Issue IFR-09
Description “Displays and produces the sound when a picture is chosen.”
Incomplete definition of the parameter used.
Option A: Outputs sound of the name of the contact image or images stored in
Options
pictalk.
17
Decision
Option B: Outputs the sound of any image stored in the phone.
Option A:Outputs sound of the name of the contact image or images stored in
pictalk.
Issue IFR-10
Description “Store secure information with password protection.”
Problem -Ambiguity
What kind of information is considered secure?
Option A: DOB, Contact information, etc.
Options
Option B: Bank details, SSN, etc.
Option B: Bank details, SSN, etc.
Decision
Issue IFR-11
Description “Should be able to call the emergency contacts using speed dial.”
Problem –Ambiguity
Who are the emergency contacts?
Option A: Nephew, Colleague, etc.
Options
Option B: Doctor, Care taker, etc.
Option B: Doctor, Care taker, etc.
Decision
Issue IFR-12
Description “Templates are used for text to speech as well as pictalk.”
Issue-Incompleteness
How should the template be?
Option A: Textual/ Pictorial representation of thoughts that involves minimum
Options
editing to be done.
Option B: Feed more input to the existing template.
Option A:Textual/ Pictorial representation of thoughts that involves minimum
Decision
editing to be done.
Issue IFR-13
Description “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?
Option A: Text Message.
Options
Option B: Picture Message.
Option A: Text Message.
Decision
2.3 Issues with Non-Functional Requirements
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 specific
Option A: Remove the statement.
Options
Option B: Define the time range for the conversion.
18
Decision
Option B - The time range should be specified in seconds.
Issue INR-02: NFR2-The output audio should be clear
Description Problem- Issue: Unsoundness
The term “clear” is not specific
Option A:Remove the Feature
Options
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
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.
Option A: Have pictures depicting the purpose of the application.
Options
Option B: Have icons carrying the name of the application.
Decision
Option A: Have pictures depicting the purpose of the application.
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.
Option A: Merely specify the voice should be loud enough to be sensed.
Options
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
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
Option A: Remove the statement.
Options
Option B:Define the range for audio levels.
Decision
Option B - The range of audio levels should be specified clearly to prevent
ambiguity
Issue INR006:NFR6- The image icon when clicked should read its functionality aloud immediately
Description Problem: Incompleteness. The term immediately is not precise
Option A: Remove the statement
Options
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
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.
Option A: Remove this phrase
Options
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.
19
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.
Option A: The use of word “should” is maintained in order to avoid binding
Options
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.
Issue INR009:NFR9-The message should be clear to the listener.
Description Problem: Issue-Ambiguity.
There is no specific sense clarity of the message.
Option A: Remove the entire statement.
Options
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.
Issue INR010:NFR10- The font should be readable to the user
Description Problem: Unsoundness - The degree of readability varies from person to person.
Option A: Follow the standard font template for all applications.
Options
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.
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.
Issue INR011:NFR11- The emergency icon should always be one click away
Description Problem - Ambiguity: The term ‘one click’ is not precise. Also, the term ‘always’
does not specify under what situations.
Option A: Remove this requirement.
Options
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.
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 album
Option A: Do not address this requirement.
Options
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.
Issue INR013:NFR13-Store few photos to identify a contact, pet or an object
Description Problem: Issue – Vagueness
“Few” is not a quantifiable term.
20
Options
Decision
Option A: Do not implement this requirement.
Option B: Specify that there should not be more than 2 photos for a particular
contact.
Option 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 time
Description Problem: Issue – Vagueness
There is no such benchmark as Correct time. It is an ephemeral concept
Option A: Specify a stipulated time at which the reminder must be sounded.
Options
Option B:Do not implement this requirement
Decision
Option 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.
Description Problem -Vagueness: There is no such benchmark as Correct time. It is an
ephemeral concept
Option A:Do not implement this requirement
Options
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.
Issue IN0016:NFR16- Display appropriate food items.
Description Problem : Issue –Ambiguity
The term appropriate does not give a clear picture on what is appropriate.
Option A: Remove this requirement.
Options
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.
Issue IN0017:NFR17-Display approximate calories burnt
Description Problem - Issues: Ambiguity. The word "approximate" is not clearly defined.
Option A: Use the closest possible value to the actual calories burnt.
Options
Option B: Use a randomly chosen value.
Decision
Option A: Use the closest possible value to the actual calories burnt.
Issue IN0018:NFR18-User's details should be secure
Description Problem-Issue: Incompleteness. There is an ambiguity in understanding the idea of
security
Option A: All the details that need to be secured are listed explicitly to prevent any
Options
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.
Issue IN0019: NFR19- The help button should produce an audible alarm.
Description Problem – Ambiguous. The word "audible" does not provide any clarity.
21
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.
Issue IN0020: NFR20- Navigating between two features in an application should be easy.
Description Problem- Ambiguity. The word "easy" is not clearly defined.
Option A: User friendly GUI and a limited number of steps in navigation.
Options
Option B: Remove requirement.
Decision
Option A:User friendly GUI and a limited number of steps in navigation.
Issue IN0021 -NFR21- Accurate medicine reminders and stock updates.
Description Problem – Issue: Vagueness. The word accurate is unclear in its definition.
Option A: Prompt reminders on time and proper stock maintenance.
Options
Option B: Remove requirement.
Decision
Option A: Prompt reminders on time and proper stock maintenance
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.
22
3. DECISION AND RATIONALE: INTEGRATED MODEL (IMPROVED UNDERSTANDING)
Functional
Non-Functional
W
5.1.3
5.1.4
R
5.2.1
5.2.2
S
5.2.1
5.2.2
3.1 WORLD
The 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.
Vision
23
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.
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.
24
3.1.3
Improved Functional Understanding of the Domain: World with Backward Tracebility
WF1:
The user should have an Android phone ---- DR0
WF2:
The user should know how to use the basic features of the Android phone ---- DR1
WF3:
The phone must have HOPE services running on it. ---- DR2
WF4:
Users with loss in memory and vision must be sure to keep the mobile always with them----DR0
WF5:
Old people suffering from hearing problem will need a speech to text converter---- DR4
WF6:
There should always be a person within 10 meters of the old person to help him. ---- DR24
WF7:
The elderly who have trouble hearing will need a speech-to-text application to hear well----DR4
WF8:
The images of the frequently used words are stored in the phone’s memory---- DR18
WF9:
The elderly who have trouble remembering will need an application to remember the location of
everyday used things. ---- DR15
WF10:
The user needs to keep the phone on their person to be able to use the system. ---- DR13
WF11: 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 DR10
WF12: People with extremely unclear vision will need things read aloud to them instead of being able to
read text. ---- DR17
WF13: When two people have problems in oral communication they should use pictograms for
communication. ---- DR14 and DR10
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. ---- DR9
WF15: Old people with memory problems will need applications to remind them of the locations of the
things used every day. ---- DR15 and DR16
WF16: Old people with memory problems will need applications to remind them of medicines to be
consumed every day. ---- DR19
WF17:
A text to speech application would help people who have trouble speaking clearly. ---- DR5
25
3.1.4
Improved Non Functional Understanding of the Domain: World with Backward Tracebility
WNF1: The elderly expect their phone to respond to commands within 2 seconds. ---- NFR1, NFR7,
NFR12
WNF2: It is helpful for an elderly person to alert his care taker to immediately attend to him with just oneclick ---- NFR11, NFR19, NFR20
WNF3: Elderly people prefer to use applications that are user friendly.---NFR3,NFR10, NFR21,NFR23
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 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 user
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.
26
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.
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.
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.
27
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.
28
4. Sequence Diagrams to Represent the Functionality of the Features Implemented:
EMERGENCY:
MyPage:
29
HELP:
30
PicTalk:
MyShelf:
31
5. SIG FOR NON FUNCTIONAL REQUIREMENTS
5.1 Usability
5.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]
++
Customizable
++
Convenience[HOPE]
++
Readable Icons
Understandability[HOPE]
++
User manual
icons
32
++
Ease to learn
5.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]
Accurate response
++ Authentication[HOPE]
password check
33
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]
++
Accuracy in producing
Speech and text outputs.
++
++
Responsiveness[HOPE]
++
Minimum over head
++
All responses are
Searching time is less.
Fast.
34
6. KAOS MODELING
6.1 SECURITY
35
6.2 USABILITY
36
7. Testing
The 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 Screenshots
In 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 Screen
The 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’.
37
8.2 Emergency
The emergency feature consists of calling functionality to the doctor and emergency dial 911.
38
8.3 Help
The help feature sounds an alarm when the old person is in need of assistance. There is an alarm start and stop
button to
39
8.4 MyShelf
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.
40
8.5 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.
41
8.6 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.
42
8.7 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.
43
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 REQUIREMENTS
0
1
2
3 4 5 6 7 8 9
FR
1
x
x
x
x x
FR
2
x
x
x
x
FR
3
X X X
FR
4
X X X
FR
5
x
x
x
FR
6
x
x
x
FR
7
X X X
FR
8
X X X
FR
9
x
x
x
FR
1
0
x
x
x
FR
1
1
x
x
x
FR
1
2
X X X
FR
1
3
X X X
FR
1
4
x
x
FR
1
5
x
x
NF
R
1
x
x
1
0
1
1
1
2
1
3
1
4
1
5
1
6
1
7
1
8
1
9
2
0
2
1
2
2
x
2
3
x
x x x x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
X
X
x
X x
x
X
x
2
4
x
x x
44
x
NF
R
2
X X X
NF
R
3
X X X
NF
R
4
x
x
x
NF
R
5
x
x
x
NF
R
6
x
x
x
NF
R
7
X X X
x
NF
R
8
X X X
x
X x
x
X
x
x
x
NF
R
9
x
x
x
x
X x
x
X
x
x
x
NF
R
1
0
x
x
x
NF
R
1
1
X X X
NF
R
1
2
X X X
x
x
x
x
x
NF
R
1
3
x
x
x
x
x
x
x
x
NF
R
1
4
x
x
x
NF
R
1
5
x
x
x
NF
R
1
6
X X X
NF
R
1
7
X X X
NF
R
1
8
x
x
x
x
x
X x
x
x
x
x
x
x
x
x
x
x
x
x x
x
x
X x
X
x
x
x
x
x
x
x
x
x
x
x
x
45
x
x
NF
R
1
9
x
x
x
X
X
NF
R
2
0
X X X
x
x
NF
R
2
1
X X X
NF
R
2
2
x
x
x
x
46
10. References
1. Requirement Engineering –Advanced Requirement Engineering. CS/SE 6361,
2012.
http://www.utdallas.edu/~chung/RE/syllabus.htm
2.
3.
4.
5.
6.
7.
Section 001, Spring
Software Engineering (8thEdition) – Ian Sommerville
Software Engineering, A practitioners approach (7th Edition)– Roger S Pressman
http://www.psychpage.com/learning/library/assess/feelings.html
Dr. Sundar Raj All India Institute of Speech and Hearing, Mysore, Karnataka, India
Dr. Jagadeesh R Malloli, ENT Surgeon, Vikram Hospital, Mysore, Karnataka, India
Dr. Suma Harindra, Audiologist, JSS Institute of Speech and Hearing, Mysore, India
47
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) 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 features
3. 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.
48
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 Percentage
Final Phase-1: Final Product Specification.
Changes in Product requirements have to freeze
Interim Phase-2: Final Design. Changes in
requirement specification have to freeze
Final Phase-2: Final Implementation. Changes in
design have to freeze
15-40%
10-15%
0-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:
Feature
Creeping Rate
Emergency
0-10%
Help
0-10%
PicTalk
0-5%
MyPage
0-15%
DietManager
0-5%
MyShelf
0-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.
49
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
--
50
Date
04/18/2012
04/19/2012
04/22/2012
04/24/2012
04/28/2012
04/29/2012
05/01/2012
05/02/2012
APPENDIX B – MINUTES OF MEETING
Location & Time
Agenda
Summary
WRS Template,
Phase 4 Clubhouse
Initial
8:00 PM to 10:00 PM
Requirements
Finalized the WRS template.
Choose the process model &
requirements. Distribute modules
to the group.
EECS 4th Floor
4:00 PM to 6PM
Issues related to the
requirements
Discussed the issues related to
the requirements & their possible
solutions.
Improvise on the
initial requirements
Brainstorming on the initial
requirements and improved them
to suit the application.
Reviewed the rough
draft of the
documentation,
Prepared a sample
SRS Template
Prepared
Presentation &
Documentation and
finalizing the WRS
for Final Phase - 2
Document review
cycle
Reviewed the modules of each
team member. Prepared a WRS
template based on the team
member’s feedback.
Making changes to
the documentation
Each team member was given a
sub-section of the document to
review & make modifications.
Library
4:00 PM to 5:30 PM
th
ECSS 4 floor
5:00 PM to 8:00 PM
Library
4:00 PM to 8:00 PM
Waterview Apt 1531
4:00 PM
Library
12:00 PM to 2:00PM
Open Lab
Final review of
6:00 PM to 10:00 PM Final Phase – 2
Documentation
51
Finalized the presentation &
documentation for
Final Phase - 2
Reviewed the work of individual
team member. Finalized on the
SRS template and sent to high
end review.
The works of team members are
reviewed and finalized the WRS
document.