| Feature | Feedback |
|---|---|
| Baseline | |
| Used git regularly | |
| Answer comprehension questions | |
| Design | |
| Each class is responsible for a single piece of the program | |
| Classes are loosely coupled | |
| Wave 1 | |
| List rooms | |
| Reserve a room for a given date range | |
| List reservations for a given date | |
| Calculate reservation price | |
| Invalid date range produces an error | |
| Test coverage | |
| Wave 2 | |
| View available rooms for a given date range | |
| Reserving a room that is not available produces an error | |
| Test coverage | |
| Wave 3 | |
| Create a block of rooms | |
| Check if a block has rooms | |
| Reserve a room from a block | |
| Test coverage | |
| Fundamentals | |
| Names variables, classes and modules appropriately | |
| Understanding of variable scope - local vs instance | |
| Can create complex logical structures utilizing variables | |
| Appropriately uses methods to break down tasks into smaller simpler tasks | |
| Understands the differences between class and instance methods | |
| Appropriately uses iterators and enumerables | |
| Appropriately writes and utilizes classes | |
| Appropriately utilizes modules as a mechanism to encapsulate functionality | |
| Wrap Up | |
| There is a refactors.txt file | |
| The file provides a roadmap to future changes | |
| Additional Feedback |