How can Business Objects in Code help us tell stories?

A business object can be set up to offer our code structure an actor. We should endeavor to keep our actor and its associated UML User Story actions from our programmatic plumbing, the functions like "save to the database" and "serialize to xml."

Encapsulation tells us that we should engage in data hiding practices, so that programmatic plumbing functions can be held in base classes and that functionality can be inherited, keeping the implementation details out of our User Stories. Once we get the implementation details out of our utilization code, we can get closer to representing the User Story directly in our.

Personally I think this would go along way in keeping our thinking from getting muddled and also saving us from spaghetti code.