
In software systems design, we typically split requirements into two camps:
- Functional requirements - what a system should do ("display the current weather")
- Non-Functional requirements - how a system should perform ("data should be encrypted on transmit")
There is sometimes debate on what is Functional vs Non-Functional.... so I didn't bother categorizing my requirements. That being said, I want to be sure that my requirements were true requirements and not design decisions. For example, I need to be able to connect to the internet to get periodic weather updates, but that doesn't automatically mean that Wifi is a requirement.
Anyway, here's my initial list of requirements
Must Haves Functions
- Alarm
- Timer
- Calendar
- Habit Tracker
- Weather
- To Do List
Nice to Have Functions:
- Heath tracking
- To Do List
- Shopping List
- News
Stretch Goals
- Alexa integration
- Multi-user
- Music control
In addition, there were a few non functional requirements that I captured:
- Easily hackable
- Open Source
- Low Power (go 9-12 months between replacement or recharge of batteries)
Discussions
Become a Hackaday.io Member
Create an account to leave a comment. Already have an account? Log In.