validation on client side and server side (ex. When adding a new entry, server checks for existing dates and client side checks that it’s not in the future)
front end does cycle calculating. No need to store that information
Improvements (CAITLIN)
consistent variable names across classes (ex. Daily, daliyEntry, dailyInfo)
code reuse: opportunity for re-use with daily edit and daily form components
The presentation should take between 7.5 and 15 minutes.
Minimally, you should:
Show a scenario with your sequence diagram or narration.
Demonstrate the 'shown scenario' with your working program.
Show the class diagrams describing the program architecture.
You do not need to show the source code unless you wish.
You may simply show your video instead of presenting if you wish!