Re: How to apply (rather than understand) OO?

"Silas Justiniano" <silasju@xxxxxxxxx> writes:
Parsing the information to see if it will fit on a database, for
example?

Could we extend this example?

I have a table (so a class)

Don't assume this one-to-one relationship.

Customers with: address, fone, date_of_birth. How would my class and
object be?

Focus first on requirements, don't assume that you know what
abstractions you'll need up front. When you have a use case defined
from the business perspective, focus on the behavior you need to
provide. As you develop the system, repartition behaviors to minimize
coupling and maximize cohesion. Keep things that change for the same
reasons together. The classes that emerge may surprise you.

Regards,

Patrick

------------------------------------------------------------------------
S P Engineering, Inc. | The experts in large scale distributed OO
| systems design and implementation.
pjm@xxxxxxx | (C++, Java, Common Lisp, Jini, CORBA, UML)
.