Object Oriented View LO7092

John Paul Fullerton (jpf@mail.myriad.net)
Tue, 30 Apr 1996 23:48:33 +0000

Replying to LO7057 -- Was: A global possibility ...

> re OO mapping
> I have used a lot of flow
> charting, process mapping and systems mapping. My experience has always
> been that the users gain a lot of insight from any mapping tool. Can
> anyone comment on the inherent value of one tool over another?

David Taylor gives an account in one of his books of a team doing
beginning OO design. The participants sit in a room around a table.
One of them may be modeling the object "customer", one may be
modeling "salesman", one might be modeling "database", another

Then the people try to account for business in terms of those
objects. If more domain objects are needed, they are added.
Eventually, the objects and their attributes or properties and
methods should be sufficient to allow modeling of all business

Once a model of that kind is developed, everything has been named and
the way everything interacts directly should be accounted for. In
terms of business understanding, it seems like a different viewpoint
for understanding and decision making. Designers don't have to
account for the complexities of system interactions; they just design
the objects and then the objects interact.

Computer programs could be designed - that's the direct purpose of OO
- based on the business and design understanding, and the capability
of the parts is built within the parts. There's the possibility that
the program could just be started and allowed to test interactions.
David Taylor said that that would be one neat way to use extra
computer time.

Have a nice day
John Paul Fullerton


"John Paul Fullerton" <jpf@mail.myriad.net>

Learning-org -- An Internet Dialog on Learning Organizations For info: <rkarash@karash.com> -or- <http://world.std.com/~lo/>