The purpose of this document is to collect, analyze, and define high-level needs and features of the HOPE Android system. It focuses on the capabilities needed by the stakeholders and the target users, and why these needs exist. The details of how the HOPE System fulfills these needs are detailed in the use-case and supplementary specifications.
This Vision document applies to the HOPE System which will be developed by Team Awesome as an Android application for mobile phones. The HOPE System provides a sentence generator, alarm system, and emergency contact features.The system supports phones that use the Android platform.
1.3 Definitions, Acronyms, and Abbreviations
Android: a mobile phone platform
Assistive person: caretaker or assistant who helps the elderly
Elderly: elderly people who might use the HOPE System to aid with memory and communication needs
HOPE: Help Our People Easily
2.1 Business Opportunity
The business opportunities for this HOPE project are aimed mainly towards nursing homes, hospitals, retirement homes, and anywhere elder people are needing care.
2.2 Problem Statement
The problem of
The amount of care-taking and amount of assistance needed for elder people with medical problems and other various problems associated with elder age
Difficulty and time which is required for care-taking elder people and overall well-being of elder person
a successful solution would be
A simple, yet effective mobile application that can used by an elder which can provide assistance to an elder person, which can not necessarily replace, however make the job of care-takers/nurses/family members much easier. The application will have reminders, emergency alerts, and various ways of communicating important messages to the elder person.
A simple mobile application that can used by an elder which would provide assistance to an elder person, which would make the day to day life of an elder simpler.. The application will have reminders, emergency alerts, and various ways of communicating important messages to the elder person
3. Stakeholder and User Descriptions
3.1 Market Demographics
The key market demographic is elderly people, presumably over the age of 60, that have some sort of disability in the at least one of the areas: vision, speech, hearing, or memory loss. These individuals are looking for some sort of assistance to compensate for these disabilities to help in their every day lives. Along with the elderly needing assistance those assisting them will also be a part of the market demographic. There are many individuals over the age of 60 that would benefit from and have access to the H.O.P.E. system. These individuals can spend thousands of dollars on aides and services in order to assist them such as hearing aides or other expensive technology systems. At this point in time because of the baby boomers more and more people are reaching the age to where they will start to need these type of services. The technology industry is becoming more and more mobile and accessible to everyone. Our organization is new to the market but are working to become familiar with the market and industry. We would like to be well received within the market and that people will be pleased with the product we are providing. Being that our goal is to assist those with disabilities and make their day to day lives easier, our product helps meet that goal by providing a way to communicate with others either for social reasons or for assistance, and help remember important dates, appointments, and to take appropriate medications at the correct times.
3.2 Stakeholder Summary
This stakeholder works with the other stakeholders to gather information about their needs.
Is in charge of gathering requirements and use-case modeling the different functions of the system. Identifies what actors exist and how they will interact with the system.
This stakeholder works with the System Analyst to translate the needs and requests in to requirements that will be used in the design.
Specifies the details of the functionality of the system by providing details about the requirements, including functional and non-functional.
Is responsible for reviewing the technical process and providing feedback within a timely manner.
This stakeholder is the leader of software development.
Responsible for the architecture of the software design. This includes technical decisions, implementation, and overall constraints. Responsible for making sure the system will fulfill all functional and non-functional requirements and that it is maintainable.
This stakeholder is in charge of the overall software development.
Responsible for determining priorities, deciding how resources will be allocated and used, initiating interactions with the users and customers, and managing the development team. Also determining the practices used to make sure a quality product is developed.
This stakeholder makes sure that the product is marketed correctly.
Responsible for making sure there is an actual market for the product and that there is a demand for a product with the features and services it provides.
3.3 User Summary
Primary end user of the system.
Inputs necessary information into the program. Use for communication and assistance with memory. Also use emergency services.
End user of the system.
Help elderly person install, set up, and input information as needed.
3.4 User Environment
Each task is designed to be able to be completed by the elderly person on their own. If necessary though the caregiver will be able to assist them in the tasks. How long each tasks takes to complete depends on the person using the device and what they are trying to do. The tasks are designed to take as few steps as possible to increase the speed of completion. As long as the device is on and working the H.O.P.E. system will be functional. The H.O.P.E. system is currently running on the latest Android Mobile Operating System and any future updates. The system only uses native Android applications.
3.5 Stakeholder Profiles
A private individual that will use the system for assistance with every day tasks.