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.
|
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.
|
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.