TODO:
- look at our requirements and evaluate
- requirements table too broad
- user specific requirements
- use cases should be based on actions and what the system does, not things in the system.
- project design
- learn ncurses
- learn asio
- learn readline
- tab completion
- class diagram w/ methods and attributes
- for each class, provide a written description
- "" "" "" , list if client, server, or both
- update requirements table
- code
- testing requirements and report
- presentation