<< 1 >>
Rating:  Summary: Brace yourself for confusion Review: Although the premise of the book is very attractive, I found the author's presentation to be absolutely horrible. I have already spent around 8 hours reading and rereading the first few chapters trying to figure out exactly how the notation works. What is missing is a flow chart or state machine describing the exact logic behind the iterative nodes, but instead you get a rambling, scattered, informal description of their operation. The author repeatedly admits to the informality of the description, but since the result is still unintelligible, I find it hard to forgive. It seems as though the author's great excitement for the subject matter caused him to rush through the basics to get to the conclusions. Because I'm still hooked on the premise, however, I'll keep checking the website to see if a lucid specification of the GOO notation ever arrives.
Rating:  Summary: At last, a good diagramming method for Software. Review: Electrical Engineers agreed decades ago how to communicate their ideas with universally agreed upon schematic diagrams, while Software Engineers still flounder around with various ad-hoc diagramming methods or have religious wars over any of several touted schemes. As a practicing SE for more than 20 years, I am still on the lookout for one grand software diagramming technique that combines the best of data flow, control flow, state machine, structured and object oriented methodologies.With this one book, I have found it. At first, the author's informal first-person style seemed amateurish. But I became more tolerant as he admitted to the same shortcomings I have yet tend to cover up for the sake of professional image. Then moving beyond the informal writing style and bizarre names he gives his creations, I discovered the GOOFEE software diagramming technique. It is absolutely wonderful. It can completely capture all aspects of a software system in a 2-D diagram. Its scope can range from high-level design through automated code generation as desired. And yet it is so simple, with only a dozen or so basic symbols, I can actually remember it after putting the book down! I highly recommend this book to any practicing SE or programmer looking for a diagramming tool to capture and communicate their ideas.
<< 1 >>
|