Senior Reminder System Project

Transcription

1 Senior Reminder System Project Vision Document SE 4351 Requirements Engineering, Section 001 September 28, Fall 2015 Milton Bland, Zachary Calman, Ridge Frederick, Grant Freeman, Brad Gracy, Jeanie Handler, Maria Haney, Justin Keeling, Mazen Lawand, Maryellen Oltman, Kevin Szwagiel, Andrew Vaccaro, Dalton Wooley, Phillip Yellott, Team Website:

2 Revision History Version Date Comments Author 1.0 November 1st, 2015 Initial Version. Milton Bland, Dalton Wooley

3 Introduction Purpose The purpose of this document is to compile all documentation on the SE 4351 Preliminary Project Phase II, or the Senior Reminder System Project. This documentation will include the Requirements Specification containing the functional and nonfunctional requirements for this project, the Program Specification containing the implementation of the project, and the User Manual. Having all of this documentation will outline for the reader the motivations and decisions that shaped the development of this project. Scope The project is defined by the boundaries of the selection process and our narrowing of the project definition. Project selection was completed by meeting together and each person suggesting an idea. After discussion of the upsides and downsides of the various ideas, our team came to a unified agreement on a reminder system. Review of the project goals, deliverables, tasks to complete, their associated costs and deadlines, further narrowed our project to a precise application idea. Objectives and Success Criteria The goal of this project is to create an Android App to help elderly people manage events and important tasks like taking their medicine. In order to better define the behavior of this system, we devised a Requirements Specification further clarifying what functionality this system is required to fulfill, such as functionality and constraints. Furthermore, we specified that this system was to be implemented using an SQLite database. Problems The largest problem in successfully creating an App for the domain of this project is that inherently as age increases, familiarity with the latest technology decreases. Our team will have to create an App that is extremely easy to use, even for users with declining motor skills, eye sight, and memory. The App will have to be easy to access, easy to use, while avoiding letting the user unintentionally modify items. Goals As a group we have decided that our two main goals are to create an App that is effortless to access and very intuitive to use. If the user can t remember the exact workings of the app, we want it to be intuitive and natural to use so they are still able to use it. This will be a tremendous

4 goal because it means that the user only needs to remember they have the App and none of the details of use. Some of our lesser goals are: creating object persistence that supports useful features, giving a caregiver an easy to way to supplement the user s use of the App, and easy ways to navigate the app like voice search. Definitions SR Senior Reminder The formal title of our phase 1 project abbreviated for ease of writing and reading. Android Mobile Operating System developed by Google Inc. Object Oriented A methodology that enables a system to be modeled as a set of objects that can be controlled and manipulated in a modular manner. App A program or piece of software designed and written to fulfill a particular purpose of the user. Category A category is a descriptor containing the multi dimensional vocabulary items having a similar meaning, relation and/or purpose. Reminder A small collection of data about an important event that includes a task and time. Disjoint Category A disjoint category is one that does not have its items overlap with any other category. Overlapping Category An overlapping category is one that has one or more of its items overlap with items in other categories. Categories can be either activity based or item based at the root level e.g. items as in Food, Drink, People etc. and activities like I want to eat, I want to go etc.

5 Positioning Business Opportunity Remembering important tasks becomes a more challenging goal as people get older. Elderly people often develop health problems or symptoms such as Alzheimer's and loss of the senses. A system that can be simple and intuitive yet dynamically manage tasks is of great aid to those who have a hard time remembering things. In addition, if the interface is simple and has large easy to identify buttons, then the system will not be an additional burden on the elderly users. The users will be spread out amongst the affected elderly, as well as their loved ones. The system will provide task tracking functions and a simple ease of use focused interface to achieve user satisfaction. Problem Statement The problem of affects the impact of which is a successful solution would be loss of memory, senses and ability to remember tasks elderly people with moderate Alzheimer s disease lower quality of life, loss of independence, and increased burden on the elderly and their caretakers a cheap cost effective system that allows users to track and complete tasks without difficulty. The product should support a primary mobile user to view, adjust, and supplement the user's task list. The product should have reminders to create a simple way for information to be displayed across multiple views (mobile through SQLite). Product Position Statement For Who Senior Reminder System (SRS) That elderly people with moderate Alzheimer s disease suffer from loss of memory, senses and ability to remember tasks Is a mobile software application provides the ability of reminder persistence and management in a simple interface

6 Unlike Our Product current mobile applications that do not focus on user interface for elderly users utilizes a simplistic and easy to use interface for creating, retrieving, updating, and deleting reminders. The system supports authorized access to reminders through SQLite. Stakeholder and User Descriptions Market Demographics The targeted market segment includes elderly people who have difficulty remembering tasks and are in need of a way to keep track of tasks. Users will have to be consumers who already own and know how to operate a smartphone. Stakeholder Summary Non User Stakeholders Name Description Responsibilities Project Manager Documentation Team Member Development Team Member This stakeholder leads and directs all non user team stakeholders to help in completing the project. This stakeholder works to gather requirements, create the proper deliverables, and also create any other diagrams or documents needed for system completion This stakeholder works with project managers to complete the implementation and program specification. Project Managers shall be responsible for managing the deliverable schedule and ensuring completion by due date. Documentation Team Members shall be responsible for all documentation and documentation control. Development Team Member shall be responsible for the entirety of design and implementation of the software system. The

7 Testing Team Member This stakeholder creates test cases to validate the requirements of the system. developer shall also be responsible for meeting all scheduling as designated by the Project s Managers. Testing Developers shall work with the Documentation Team Members and Project Managers to create, document, and save test cases and their results. User Summary Name Description Responsibilities Stakeholder Elderly User Primary end user of system creating, retrieving, updating, and deleting tasks in the system as they are needed and completed. Self User Environment Direct access is through a mobile device that supports Android API 15/Version The following operating systems are supported by our team: Android (mobile), Chrome, and Microsoft Windows. Stakeholder Profiles Elderly User Representative Description Type Responsibilities An elderly individual with issues of memory loss,visual impairment, and/or other impairments of senses. This is a user that is heavily reliant upon the system to remind the user to complete important tasks. Ensure that the user creates reminders for tasks that need to be completed and that the user verifies that the task is completed.

8 Success Criteria Involvement The tasks that the user set reminders for are completed in a timely fashion without the intervention of a caretaker. The user will not be involved with the development of the system. Deliverables Comments/Issue Key Stakeholder and User Needs Need Priority Concerns Current Solution Proposed Solution Secured Access Moderate to High Access only by authorized users to view reminders Persisting reminders in SQLite puts data behind Google/SQLite authorization methods and built in security. None needed at this time. Easy to Use High User is unable to use system Responsive Low User should not be confused by having to way for system to respond Flexible Moderate Ability to customize access to system through multiple views Portability Low Access of information across devices None None None None. Focusing on simple and high contrast interface that is intuitive and easy to navigate. Operations modifying reminders need to use known efficient algorithms. Create a simple and minimalistic view for the app. None needed.

9 Product Overview Product Perspective Summary of Capabilities Customer Benefit Supporting Features Reminders will be shown in a simple tile interface with minimal buttons System will create, retrieve, update, and delete reminders In the event of an a missed reminder, an emergency contact will be notified System will notify the mobile user of approaching reminders User can associate an image or graphic with a individual tile. User can edit the color of an individual tile. Button usage will be minimal and use icons in place of words. System supports regular text keyboard entry or voice to text entry of reminders Time selection is done using Google s clock wheel to avoid clumsy manual entries of time. All reminders will be persisted using SQLite and will have an interface to create, retrieve, update and delete reminders. To avoid accidental changes, all destructive modifications will require a second confirmation action. System will alert caretaker and authorities in the event of a missed reminder or critical importance System will use SMS to make sure that the alert can be received by most devices. Reminders will have a time associated with them and the system will push a notification out to the user to remind them of an impending task so that they have time to prepare to complete the task if they have forgotten. Reminders will play an alarm when the task reaches notification time, this will alert the user to complete the task.

10 A emergency button will be available for contacting 911 services. Assumptions and Dependencies Assumptions Any difficulty with an assigned task is to be communicated to the other team member The professor/end customer shall not make changes in the requirements or scope Professor/end customer shall clarify any doubts, concerns, or uncertainties Dependencies Each CPM is reliant upon the developer to finish their duties on schedule Each developer is reliant upon the CPM to clearly delegate their tasks and their schedule The Webmaster is reliant on the DM to provide the deliverables to upload to the team website Cost and Pricing The application is free to install. Licensing and Installation This product requires installation on to the user s smartphone device from the Google Play Store. Product Features Start System The elderly user needs to be able to start the system locally on their smartphone. Shutdown System The elderly user needs to be able to exit the system without causing error. View System The elderly user needs to be able to view the system locally on their smartphone.

11 Create Reminders The elderly user needs to be able to create reminders. Retrieve Reminders The elderly user needs to be able to retrieve reminders. Update Reminders The elderly user needs to be able to update reminders. Delete Reminders The elderly user needs to be able to delete reminders. Image or Graphic Tile Association The elderly user must be able to use large graphic tiles to identify and relate reminders to image tiles Tile Color Editing The elderly user can personalize the color of the tiles to support different preferences. Emergency Contact Notification In the case of an emergency, the system can contact the emergency contact using a SMS message detailing the emergency situation. Push Notifications The elderly user needs to receive local phone notifications of impending tasks. Support for Voice to Text The elderly user needs to be able to speak the task information if they are not able to accurately type in information on the phone. Reminder Search Function The elderly user needs the system to be able to search for a specific reminder.

12 Auto Reminder Sorting The elderly user needs reminders displayed in a meaningful way as opposed to order of creation. Constraints Security Usability Security should be well implemented outside the view of the user. Security will use Google backed authentication, access control, data integrity, and data privacy. Authentication of the user is done by the android system. If the user is not logged in on their Android phone, authentication will fail. Elderly users can view and change the reminders. Transmissions will not be encrypted by the application, any encryption will be native to the Android and SQLite API. Easy to use User Friendly interface with large graphic tiles and text Request for an ambulance, police, or fire truck needs to be a tile to be pushed or caretaker needs to be alerted of potential emergency Responsiveness Capacity System responds quickly to user requests or changes in the environment System responds within 0.5 seconds on average to local user requests and changes in the environment. System responds within 0.5 seconds on average to remote user requests and changes in the environment. There is no maximum for the number of reminders Maximum reminder capacity is limited by the SQLite database capacity. View of reminders is limited by the frame of time being viewed. Maximum number of active notifications is limited by Android API Maximum number of active alerts/alarms is limited to one (1). Maximum number of emergency contacts is limited to one (1).

13 Appendix References [1]Chung, Lawrence. 'Requirements Engineering', Utdallas.edu, [Online]. Available: [Accessed: 27 Aug 2015]. [2]Chung, Lawrence. 'Communication Assistive Technology Project'. N.p., Web. 27 Aug [3]Chung, Lawrence. 'H.O.P.E (Helping Our People Easily) System'. N.p., Web. 27 Aug [4] T. Berners Lee, Uniform Resource Identifier (URI): Generic Syntax, RFC 3986, January [5] L. Chung, Project Phase I: Requirements Elicitation: Initial Understanding, 1st ed. Richardson, TX: Lawrence Chung, 2015, pp [6] L. Chung, Project Phase II: Requirements Elicitation, Specification, and Validation, 1st ed. Richardson, TX: Lawrence Chung, 2015, pp [7] L. Chung, K. Cooper, S. Courtney, RUP Vision Document for the Home Appliance Control System: Defining Stakeholders, Goals, and COTS Components, [Online]. Available: doc UTDCS pdf [Accessed: 1 Nov 2015].