
As my headline suggests, this book is more suitable for the classroom environment than for the professional systems analyst or systems developer.
What the author did was to basically take the Zachman Framwork with all the columns and rows and explain every possible combination by using the usual modelling techniques (UML, DFDs, IDEF0, ERMs, CRUD matrix etc.). You therefore get a very - and I really mean VERY - broad overview over many of the current, state-of-the-art methods available to systems analysts (from data normalization to analyzing objectivied relationships).
I recommend you to read this book if you are someone from the academic world who wants to get a very good overview of the Zachman Framework. Especially if you are specifically interested in data analysis you will find this book to be very helpful.
Summary: aggreed there is no OOA
Rating: 5
OOA is some “super magic� that uml people found it for commercial reasons.As Mr.Hay mentions there is no OOA.there is only “analysis� of the bussiness.
I am a bussiness owner and a coder for a long long time.The concept that david hay is talking about will take developers life time period to understand.
The most simple explanation is for the reviewer to look at his/heer database tables and see the replication places as they had no abstraction in mind when they were coding the “thing�(prefered design over analysis).
David Hay’s,Len Silverstone’s and Martin Fowlers(analysis patterns) should be read over and over again.it is like swimming u do not pick it up in the first try.
PS:These books are for an analists who can understand the meaning of polymorfism
PS2:By the way OO people even could not agree about compostion over aggregation ,method over operation.Keep in mind UML is a design tool should not be used like a “golden hammer�
