1. An easy-to-use memory management smartphone application
ReCall
An easy-to-use memory management
smartphone application
David

2. Members Andrew Brantley Susan Christian Ryan Duan David Easaw
Michelle Farina
Marina George
Baheru Iemesa
Fahman Khan
Marriam Khan
Hiten Patel
Kyle Parrott
Jerome Raymond
Cesar Zambrano
Ismat Zareen
David

3. Problem Statement The problem of affects the impact of which is
Forgetting about important information that is daily lives.
affects
People with memory loss
the impact of which is
Uncertainty of remembering important information
a successful solution would be
a flexible, cost effective mobile application system configured by a person with memory loss. This can involve saving pictures in a secure manner. In addition, ReCall (the other features included). The user would be able to access the system using their Android phone. It will be able to utilize usability.
Problem Statement
Cesar

4. Product Position Statement
For
People with memory loss.
Who
Fulfill the need of a person with memory loss to help them remember important information.
ReCall
is that it helps people with memory loss remember important information by having a mobile application that saves pictures of what the person needs to remember
That
can help them remember important information especially because memory loss is a huge problem in our society. By having this mobile application, people will feel better knowing that they have pictures that they can customize to remember information in a better way.
Unlike
Other products in HIPAA that are not flexible enough for a person with memory loss to customize their photos.
Our product
monitors, controls, and coordinates a wide variety of phone applications such as the picture gallery in Androids.
Product Position Statement
Cesar

5. As-Is Scenario
My great aunt Yasuko
My mom
Little Susan
Susan

6. To Be Scenario Help with moderately severe memory loss HIPAA Compliant
Extremely easy to use
Drew: What we are proposing is an app that will relate photos with people and places. Instead of your loved one having no idea who a person is, they will be able to navigate our app to help them remember important people in their lives. Instead of wondering if your grandmother will get lost when she leaves her home, she will be able to look at her mobile device and remember where she is going and where she should go when she is finished

7. Revisions Splash Screen Login Screen Gallery Screen Details Screen
We’ve changed a lot since our last presentation!
Take a look at the pre-alpha version of our application and all the previous revisions of it
Splash Screen
Login Screen
Susan
Gallery Screen
Details Screen

8. our app
Susan

9. splash screen main menu detail page pin entry settings page
Susan

10. Process Specification: Spiral Model with Phases
Requirements
Elicitation
PMP, Goals, Scope, WRS initialization
Analysis & Negotiation
use case development, FR/NFR traceability
Requirements
Elicitation
Vision doc, FO/NFO traceability
Analysis & Negotiation
alpha development and implementation
Validation
forward/backward traceability, next phase prep, rework groups
Testing & Documentation
ensure traceability, refactor requirements, pre-alpha
Validation
finalize WRS, vision doc, and other deliverables
Testing & Documentation
testing, product and process specs, update deliverables
Susan
Planning Group
WRS - FR Group
WRS - FR Group
Elaboration Group
Design Group
Implementation
Group
Website Group
WRS Group

11. PIG DIAGRAM: Problem Interdependency Graph
Ryan

12. SIG DIAGRAM: Software Interdependency Graph
Drew

13. Improved Functional Requirements
Improved FR
Objective ID
Objective Description
Alleviates Problems
Achieves Goals
IFRO1
The application shall provide the user with information about the people they know and the places they’ve been P1
G3, G4
IFRO2
The application shall allow the user the ability to record information about people and places to be referenced later
G2, G3
FR_ID
Functional Requirement Description
FR01
The system shall provide a user interface that displays the application’s saved contacts and locations, referred to as the main screen.
FR01.1
The system shall display two tabs on the app’s home screen, one titled “Contacts” and the other titled “Places” when the app starts after the user has completed the initial one time configuration.
FR01.2
The system shall display images and associated descriptions of the saved contacts under the Contacts tab.
FR01.3
The system shall display images and associated descriptions of the saved places under the Places tab.
FR01.4
The system shall display the detailed user-created description of a picture when an image is selected.
FR02
The system shall prompt first time users to create an account and collect the user’s name, address and a four digit PIN number.
FR02.1
The system shall have a system in place to allow another user to have access to the main user’s account by giving the new user a duplicate PIN.
FR03
The system shall allow the user to create and edit the details of a contact or location.
FR03.1
The system shall prompt the user for their account’s PIN number before allowing editing permissions
FR03.2
The system shall allow a user to specify a location’s name, address, and “other details”
FR03.3
The system shall allow the user to specify a contact’s name, address, relationship, and “other details”
WRS team

14. Improved Functional Requirements
FR04
The system shall allow the user to delete and restore a contact or location.
FR04.1
The system shall prompt the user for their account’s PIN number before allowing deletion permissions
FR04.2
The system shall move all deleted ‘contact’ and ‘location’ items into a temporary location titled ‘recently deleted’ before permanently deleting an item.
FR04.3
The system shall provide functionality to restore items from the ‘recently deleted’ location.
FR04.4
The system shall have a button to permanently delete items from the ‘recently deleted’ location.
FR05
The system shall allow users to take and save pictures of contacts and locations
FR05.1
The system shall allow the user to add a custom name for the location of a photo that is taken with the app’s camera function
FR05.2
The system shall allow the user to add a custom description associated with a photo that is taken with the app’s camera function.
FR05.3
The app shall record the details (time and location) and store these details when a photo is taken.
WRS team
FR06
The system shall have a splash screen that is displayed when the app is launched.

15. Improved Nonfunctional Requirements
Improved NFR
Objective ID
Objective Description
Alleviates Problem
Achieves Goal
INFRO1
Create an android application to aid those with memory loss P1 G2
INFRO2
Create an application that will be secure and HIPAA compliant
N/A G4
INFRO3
Create an application that is simple to use P2
G2, G3
NFR_ID
Non-Functional Requirement Description
NFR01
The system shall demonstrate easy usability to the user.
NFR01.1
The system’s text should be readable.
NFR01.2
The system’s color scheme should be complementary colors and shouldn’t camouflage with one another.
NFR02
The system shall be extensible.
NFR02.1
The system shall be able to handle updates which includes extra added on features to the system.
NFR02.2
The system source code must be well documented to make the editability of the code easier for the developer.
Hiten

16. Improved Nonfunctional Requirements
NFR03
The system shall be able to run on any kind of Android device.
NFR03.1
Compatible with Android version 4.1 (Jellybean) and above.
NFR04
The system shall be reliable.
NFR04.1
The system shall store data locally in case if the system crashes.
NFR05
The system shall be understandable
NFR05.1
The system’s 80% of novice users should be able to operate major use cases of the software without outside assistance.
NFR06
The system shall be secure
NFR06.1
The system’s data shall be encrypted.
NFR06.2
The system shall ask for a PIN for authentication.
Hiten

17. Product Features - Object Creation
WRS team
Create a Contact Object
Create a Location Object

18. Product Features - Interaction with Objects
Accessing a Contact or Location Object
Deleting a Contact or Location Object
WRS team
Updating a Contact or Location Object

19. Creeping Rate / Justification
The creeping rate is expected to be about 10%
Justification
Explain why rate is so low
Ismat and Jerome
creeping rate is to allow for any unexpected changes that need to be made due to software or hardware limitations or unplanned ideas

20. Competition
Unus Tactus - Keeps contacts with photos - Ability to ask for help Why our app is better - Include relationships of these people - Important locations included - Minimalistic and easier to use
Michelle and Marina

21. our website
Website team (fahman)

22. presented by our development/implementation team
demo
presented by our development/implementation team
implementation team (kyle, jerome)