Option 1 - model as operations
- Use getters/setters to access "attributes"
- Similar to JavaBeans pattern
- + no new concepts
- explosion of # messages, parts and operations in the
interface
- Relies on programmer adhering to a convention
- No simple multi-attribute query
- At best only hard coded queries
- No notion of "dynamic" state elements
