The core of things

The OOA-paradigm has been around for 20 years. It merged at the switch of the decades from 80’s to 90’s. The first three books that I know from that time were Peter Coad: “Object oriented analysis”, Grady Booch: Object-Oriented Design and Jim Rumbaugh: OMT.

All of these presentation clearly emphasized the difference between procedural and OO: the analysis of behavior and its place was profoundly different. The two important things here are encapsulation and collaboration!  These things doesn’t exist in procedural. This is totally crucial.

My approach and these early writes approaches differ also. These writers quite unanimously model the system ( the 3-tier system) with OO-model. My approach starts with creation of only the domain model with little or no knowledge about the application. When done in this way we need nearly no requirements of the application. The only thing that we need is the business focus in the reality – the interesting structural and behaviour subset of the world. This will postpone the digging of most of the details connected to application usage and workflows and takes it up at much later state in the agile development process.

When you read my model examples and if you catch up the idea in my collaboration diagram then you have seen the light.

The collaboration diagrams are the core of the core!


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: