Google Glass Virtual Memory App Requirements

Download 110.92 Kb.
Date conversion08.07.2018
Size110.92 Kb.
1   2   3


1. Introduction 3

1.1 Project overview 3

1.2 Goals 4

1.3 Project deliverables 4

1.4 Evolution of this document 5

1.5 Definitions, acronyms, and abbreviations 5

1.6 Web Link 5

2. Project Organization 5

2.1Process model 5

2.2 Organizational structure 5

2.3 Organizational boundaries and interfaces 6

2.4 Project responsibilities 6

3. Managerial Process 6

3.1 Management objectives and priorities 6

3.2 Assumptions, dependencies, and constraint 7

3.3 Risk management 7

3.4 Monitoring and controlling mechanisms 7

3.5 Division of work 7

4. Technical process 7

4.1 Methods, tools, and techniques 7

4.2 Software documentation 8

4.3 Project support functions 8

5. Work elements, schedule, and budget 8

5.1 The domain 8

5.2. Stakeholders 8

5.3 Non-functional objectives 10

5.4 Functional objectives 10

5.5 Schedule 10

5.6 Budget 11

5.7 Creeping Requirements 12

6. Requirements Specification 12

6.1 Non-functional Requirements Specifications 12

6.2. Software System: Functional Requirements 13

Project Phase I: Requirements Elicitation: Initial Understanding
The hardest single part of building a software system is deciding precisely what to build. No other part of the conceptual work is as difficult as establishing the detailed technical requirements, including all the interfaces to people, to machines, and to other software systems. No part of the work so cripples the resulting system if done wrong. No other part is more difficult to rectify later. [Brooks, 1987]

1. Introduction

1.1 Project overview

There are many technologies available today that allow a wide range of people greater accessibility to the world. People benefiting from accessibility technology range from travelers that do not speak the local language to those suffering temporary or permanent auditory or visual impairment, which may include disabled children and adults, and the elderly. The problem is how these individuals can be helped, in a manner as to maximize their abilities towards that of the average individual, yet at the minimum apparent difference from their peers. For example, a person who requires help to hear can be helped via hearing aid technology to allow them to hear almost as well as an individual with no appreciable hearing loss. Yet the hearing aid device is small and subtle so as to make the individual appear no different than anyone else. There is no large device with a battery pack strapped to them, which is easily identifiable. Modern hearing aids allow the affected individual the freedom to “blend into society.” The same is not true for all ailments. Neurological conditions that affect memory and cognition for example, require multiple dimensions of stimuli; more than just auditory.

The technology required to aid with multiple needs is required to be quite more advanced than the above example of a hearing aid. Technology providing real world accessibility is typically triggered by some types of stimuli. Information can be static and/or passive, like a proximity sensor triggering a prerecorded message for the visually impaired letting them know transportation information. Passive information is generally static, meaning it doesn’t change per user. It isn’t custom to that person’s needs. To have interactive information, most existing technology requires the user to provide stimuli input information in some way. This indicates the information desired. This can be as simple as typing words or symbols, to more complex recent solutions using breath or eye movements, but the custom information is triggered in some way.

Our project is to combine a passive stimuli for the user, where the user is not required to do anything at that moment, with customized information. Google Glasses are technology that people wear similar to glasses. The Google Glasses see the world and help interpret it for the wearer. There are many commercial applications for the technology, but our team is focusing on improving real world accessibility for dementia/Alzheimer’s patients. For the wearer, the glasses must be worn, but that is the extent of user stimuli. The glasses interpret the world and provide customized information to the wearer. The customized information is entered by care givers at any time, and can be actively maintained.

The development of this project has involved a detailed development and scoping of the functional and non-functional requirements needed to address the daily needs of individuals with early on-set Alzheimer’s. The users will be those affected by the disease. However their family and caregivers will also be required to learn the use of both the application we are developing as well as Google Glass. This will allow the customization of the application’s functions to meet the changing needs of the affected individual to fit into their “normal route” and social group. As the disease progresses, adjustment may also be required to be made by the family or caregiver, such as reminders for the medication regimen.

The domain of our application is limited to the software and hardware platforms established by Google for their Google Glass project. An android smartphone communicates with Google Glass, and provides real-time connectivity to the cellular data network. Our application is downloaded onto the Android smartphone from the Google Play application store, and services Google Glass with an assistive technology for the wearer. The family or caregiver customizes the app via the Android smartphone to meet the unique needs of the patient. The environment of the patent is all-inclusive of the real-world, ranging from a care-facility on one extreme with limited range of activities, to active individuals still engaged with relative degrees of independence.

The requirements process began with extensive research of the needs of Alzheimer’s patients and their caregivers. Our resources included, the Alzheimer’s foundation as well as interviews with primary caregivers. The goal being to develop a tool that can not only manage all the necessary data associated with the care of the patient but also to provide several useful applications for the patient’s use via the Google Glass platform such as customized reminders for the patient that will have audio and picture of a familiar trusted person reminding them to take their medicine.

1.2 Goals

  • Google Glasses will improve real world accessibility for early stage dementia/Alzheimer’s patients.

  • Provide a total solution for the family/caregivers of patients to use the application for the joint benefit of their lives and the patient’s

  • Integrate successfully of the app with Google Glass platform

  • Capture market share in accessible technology market

1.3 Project deliverables

  • High-level functional and technical requirements for a Google Glass application which would use the Google Glass platform. Would provide a specialized application for the use of people with real world accessibility challenges.

  • User interface for caregiver to load customized content for the individual wearer.

  • High-level marketing and sales requirements

1.4 Evolution of this document








Initial version of document




Second version with additional sections




Third version with additional edits, content, and format changes




Evolution from outline to formal document



Nik, Ben, Dylan

Edits for Part 2 class submission

1.5 Definitions, acronyms, and abbreviations

Not applicable at this time

1.6 Web Link

Location of project website: (Shortcut)

Ergonomic link address:

2. Project Organization

    1. Process model

Our group has implemented the Agile approach to development of our requirements. The Agile approach is based on iterative and incremental development, where requirements and solutions evolve through collaboration between self-organizing and, cross-functional individuals. We chose this approach because it promotes adaptive planning, evolutionary development and delivery, a time-boxed iterative approach, and encourages rapid and flexible response to change. It is a conceptual framework that promotes foreseen interactions throughout the development cycle.

2.2 Organizational structure

  • Stakeholders: Early onset Alzheimer’s patients and their primary caregivers

  • Engineering Requirements Development Dylan Brandt & Ben Smiley

  • Software Development – Ben Smiley Dylan Brandt

  • Test- Ben Smiley Dylan Brandt

  • Support – Randi Craig

  • Maintenance – Randi Craig

  • Marking requirements – Nikolaus Walch

  • Sales requirements – Nikolaus Walch

1   2   3

The database is protected by copyright © 2016
send message

    Main page