Some lessons from chapters 6 and 7.

* Problem decomposition (breaking big problems into smaller ones) is a
  good strategy.
  + It's particularly useful in object-oriented modeling
* Remember the basics of the OO process
  + Make sure your software does what the customer wants it to do
  + Apply basic OO principles to add flexibility
  + Strive for a maintainable, reusable design
* Feature lists are good, no matter what you call them
  + Mostly because they let you talk to the customer
* Stories are good, whether you call them use cases or