Advertisement
Not a member of Pastebin yet?
Sign Up,
it unlocks many cool features!
- # IN4X 43 ZotMyHealth Requirement Notes
- ## Thursday quiz
- ### Use cases
- * what they are
- * what are the purposes of them (what they're good for, and not good for)
- * different parts of a use case, and use case model
- * actor
- * diagram
- * scenario
- * ...
- * flows
- * basic
- * alternative
- * exception
- * one question from textbook readings
- * steps of the requirements process presented in chapter 6
- * 6.1.2 - continue through rest of chapter 6
- * sort of goes back to the reading from the beginning of last week, which starts introducing that process
- ## Presentation
- director of technology at health beacon systems
- mission: achieve data standardization in the field of personal health monitoring systems
- so many apps we use to track workouts, calorie content from meals... sleep cycle correctness / amount
- -- track personal health
- built with the mission of creating technology to bring together all our apps so you can track all of this in a central location
- 10 or 15 years build systems which can directly tell you how good you are doing health-wise
- building an APP called ZotMyHealth
- * 3 basic kinds of data
- * sleep cycle, how much you sleep every day
- * calories burned in workouts
- * calories intaked through meals
- * handle all the user data involved with tracking all this
- not starting from scratch
- interface with 3rd party devices
- * fitbit
- ## QA
- target audience:
- * people who are already using apps such as fitbit who track their food or sleep cycle
- * not a specific target
- devices: android, iOS. if time, windows (phone) app. phones and tables. webapp (no create)
- out by the end of the quarter
- -- used as long as there is demand
- **login logout**
- username, gender, email, (optional, height, age weight)
- maybe later for "login with facebook"
- user specifies goals, e.g. "bring my calories intake down to 2000 per day"
- * set limit in settings
- * daily limit only
- * notification if you go over
- have a database of all dishes with calorie mappings, also need manual entry for dishes which aren't in database
- optional manual entry for everything, workout types
- no manual entry for sleep, but you can manually edit existing info, wtf?
- log in on web and see data. cannot register from web interface
- enter name of exercise, amount of time, calculate calories burned
- backend is already done
- graph of data, probably different types of graphs, with curves and shit... who knows...
- english for now
- use case: click on sleep tracking, click "View and analyze data"
- specify in preferences, which data proiders are prefered, only choose one dp per tracking type
- SI units
- manual deletion
- lookup data on a specific day, or range
- delete account
- priorities:
- 1. login
- 2. enter data
- 3. ...
- 4. limits, web portal
- logout stops import of data from data providers???
- manually import when relogin, do not automatically import
- no required updates
- burn graph shoes sum of exercises per day
- email temporary password
- notifications:
- * over consumed
- * under burned
- * overslept
- * underslept
- * things like that????
- enter names and amounts of ingredients to make a meal
- aws server with HA, don't worry about server availability or maintanence outages
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement