Project Total Recall
Team Total Recall
www.utdallas.edu/~axp120531
Overview
1. Project Goal
2. Domain, Stakeholders, Objectives
3. Organization Structure
4. Project Management
5. Project Deliverable Schedule
6. Without Application Scenario
7. With Application Scenario
8. Prototype Mockups
9. Traceability
10.Conclusion
Project Goal
The Original Project Goal Statement:
“This project is intended for helping the elderly population suffering from communication
difficulties, such as lack of hearing, speech impairment, unclear speech, low vision, weak
memory, etc. to communicate in better manner.”
Total Recall’s Project Goal Statement:
“[....] to create an application, running on a mobile
device, capable of aiding a user suffering from memory
loss (category 3, Mild Dementia) in recalling pertinent
information to facilitate communication.”
Domain, Stakeholders, Objectives
The HopeSOFT Domain: “[...] communication difficulties, muscle weakness [...]”
vs
Our Domain: [IDR1] = “[...] communication difficulties related to mild dementia
(Stage 3) [...]”
Domain, Stakeholders, Objectives
The HopeSOFT System Scope: “[...] lack of hearing, speech impairment,
unclear speech, low vision, weak memory, muscle weakness [...]”
vs
Our System Scope: [DR2] = “[...] those suffering from stage 3 dementia [...]”
Domain, Stakeholders, Objectives
The HopeSOFT Stakeholder user group: “[...] the elderly [...]”
vs
Our Stakeholder user group:: [IDR3] = “[...] any user who can operate a mobile
device [...]”
Domain, Stakeholders, Objectives
The Hopesoft Objective: “This project is intended for helping the elderly
population suffering from communication difficulties, such as lack of hearing,
speech impairment, unclear speech, low vision, weak memory, etc. to
communicate in a better manner. [...] This project is also intended for helping
people with muscle weaknesses, which could lead to (frequent) falls.”
vs
Our Objective: [IFO1] = “[....] to present a system to the user so that the user may
find the object he or she cannot remember..”
Organization Structure
Organizational Structure:
Physical: 3 teams (4 per team), 1 management team comprised of 3 team leaders + phase leader.
Management: 1 phase leader, 3 team leaders.
Teams and Members
Phase Lead I - F: Michael Raibick
Team 1: Andrew Pohlmann (L), Michael Muggler, James Williams
Team 2: Michael Raibick (L), Joe Brown, Oscar Reyes, Desmond Lee
Team 3: Bennilyn Quek (L), Travis Chun, Guiseppe Mastrolorenzo, Robert Lockwood, Ryan Chen, Blessing Osakue
Team Roles:
Team 1: The Architecture Designers: Implement high-level package views as well as the low-level class diagrams.
Team 2: The UI/UX Designers: Implement the user interface as specified in the specifications.
Team 3: The User Manual / Testers: Generate the user manual, as well as test the prototype against specifications.
Project Management
Management Pattern: Chain of Command
Development Method: Spiral
Work Unit Specifics: Agendas and Assignment documents on Google Drive
Communication Methods: Email, VOiP, Text, In-Person meetings
Mondays: Management Meeting 1-3:00pm. Assimilate all teams’ previous week work units into applicable evolving
phase deliverables, and decide new work-units based on phase schedule.
1: Ensure individual team work conforms to project vision for that specific deliverable.
2: Ensure that new work units which do go out conform to the project vision for that specific deliverable.
Tuesdays/Wednesdays: Individual team meetings and team leaders assign decided-upon work-units.
1: Ensure individual team members understand the nature of their work assignments.
Fridays: Internal Due Date of each team’s work units.
Sat/Sun: Team leaders test team member output for conformance to project
1: Ensure individual team member work conforms to the specifications of the work unit.
Phase Deliverable Schedule
“As-Is” Scenario:
User forgets restaurant
….and does not have TotalRecall.
Scenario: User forgets restaurant name
Without Application
Scenario: User forgets restaurant name
Without Application
Scenario: User forgets restaurant name
Without Application
“To-Be” Scenario: User
forgets restaurant name
…but has TotalRecall.
Scenario: User forgets restaurant name
With Application
Scenario: User forgets restaurant name
With Application
Scenario: User forgets restaurant name
With Application
Scenario: User forgets restaurant name
Steps of Execution
Scenario: User forgets restaurant name
Steps of Execution
Scenario: User forgets restaurant name
Steps of Execution
Scenario: User forgets restaurant name
With Application
Prototype Mockup Walk-Through
The current prototype mockup is a vision of the
specifications.
Prototype Mockup (Root Level)
IFR1 = “The system shall
provide menus, forms, and
buttons for navigation.”
INFR1 = “The system shall not display
more than three layer of panels or windows
above root layer.”
INFR3 = “The system shall give
accessibility to each menu, form, or button
with at most two taps or clicks.”
INFR9 = “The system shall process a user
navigational request in under two seconds.”
Prototype Mockup (Root Level)
IFR3 = “The system shall create
dedicated categories where
emergency objects shall be
placed.”
INFR14 = “Emergency contacts must
be accessible from any location in the
system within 5 seconds.”
Prototype Mockup (Root Level)
IFR11 = “The system shall present
object categories on the upper main
menu.”
INFR4 = “The system shall require a
form of organization upon all objects at
all times.”
Prototype Mockup (Root Level)
IFR11.5 = “The system shall
always display all objects
associated with their respective
categories on screen.”
INFR4 = “The system shall require
a form of organization upon all
objects at all times.”
Prototype Mockup (Root Level)
IFR9.2 = “The system shall show
the View <Object> inner frame
screen the moment an object
icon has been single-tapped or
single-clicked.”
INFR4 = “The system shall require
a form of organization upon all
objects at all times.”
Prototype Mockup (Root Level)
IFR9.3 = “The system shall
allow the creation of new
Objects.”
INFR4 = “The system shall
require a form of organization
upon all objects at all times.”
Prototype Mockup (Root Level)
IFR9.4 = “The system shall
provide a method to update
the information of an object.”
INFR4 = “The system shall
require a form of organization
upon all objects at all times.”
Prototype Mockup (Root Level)
IFR9.5 = “The system shall
provide a method to delete
the information of an object.”
INFR4 = “The system shall
require a form of organization
upon all objects at all times.”
Prototype Mockup (Root Level)
IFR5 = “The system shall
provide a search interface for
objects.”
INFR = “The system search
mechanism shall return results
within 3 seconds.”
Prototype Mockup (Root Level)
IFR8 = “The system shall
present frequently selected
objects within a recent time
period disjointly from other
objects.”
INFR4 = “The system shall
require a form of organization
upon all objects at all times.”
Traceability Matrices
Conclusion
Why Team Total Recall?
Effective Organization Practices...
❏ Accountability: Work units are completed before internal deadlines.
❏ Accuracy: Work units are traced against the requirements.
❏ Quality Assurance: Work units are tested against the requirements.
❏ Communication: Management is always available.
...produce to Clear Project Objectives and High Quality Deliverables.
❏ Specific System Domain and Concise Scope Declarations.
❏ Traceable System Functional and non-Functional Objectives.
❏ Accurate Functional Requirements Modeling.
❏ Superior Documentation of Deliverables.