Talk:Asaf Shelly/@comment-89.139.196.176-20181119114810

Thank you for your reply.

The purpose of the post was to say that object oriented modeling is only one way to model your software. I'm not sure it's correct to say "modeling" only for object oriented modeling. There are other models.

Software is made of tasks that travel between work-objects (service?), carrying context-objects (session?), to handle Events.

If we only use objects, we can't really keep track of tasks. It's OK if you have a single task and you can use the CPU stack, but if you have multiple tasks, objects can't show you problems with the execution flow.

Procedural programming was looking mainly at operations and Object design was mainly looking at objects. Need to use both.

Both procedural and object oriented fail to describe the following simple business process:

Take a cup, Add sugar, Add water, Take a spoon and mix. What is mix?

- a method of sugar? do you need sugar to know all liquids?

- a method of cup? should cup know all mixing instruments?

- a method of spoon? what if we mix using a stick?

Mix is a task, spoon is an object. They don't mix...

Best,

- Asaf Shelly