Most Helpful Customer Reviews
|
|
5 of 5 people found the following review helpful:
4.0 out of 5 stars
A milestone in system analysis, July 9, 2004
This book changed the way I thought of system analysis when I first read it in 1984. Those ideas are still relevant today. Its key ideas include the notion of technology independent requirements and a rule of thumb (perfect technology) for recognizing them. It was the first book (that I read) to recommend the use of both Data Flow Diagrams and Entity Relationship Diagrams to provide a balanced depiction of business requirements. It distinguished between the essence (core requirements) of a system and its incarnation, this was an important refinement on the notions of logical and physical models which to this day are seldom well defined. It identified the "old physical tar pit" as a major risk area in structured analysis and suggested ways to avoid getting stuck. Finally it proposed the notion of blitzing requirements as a technique for dealing with real-world time constraints. This book was essentially a sequel to Structure Analysis and System Specification, the ground breaking book on structured analysis by Tom DeMarco. (The authors of this book were close business associates of DeMarco.) I still recommend this book, but it is no longer my first choice. That book is Complete Systems Analysis by James & Suzanne Robertson. (The Roberson's are also business associates of DeMarco.) Their Atlantic Systems Guild web site is worth visiting.
|
|
|
4 of 4 people found the following review helpful:
5.0 out of 5 stars
The definitive book on creating logical data flow diagrams, September 27, 1997
Gane and Sarson's original book on data flow diagramming said that you should convert your physical data flow diagram to a logical data flow diagram. It was a little like the New Yorker cartoon: "Miracle occurs here." McMenamin and Palmer finally tell us precisely and in detail exactly how to do that. Well done!
|
|
|
4 of 4 people found the following review helpful:
5.0 out of 5 stars
Cuts to the core on how to find and document requirements., February 11, 1997
By A Customer
The lessons in this book pass the test of time and are still
useful in the Object-Oriented era. The authors clearly describe how to separate routine and expected requirements (aka. "custodial" processes for validation and security) from the data, processes, and rules that make up the baseline business process a client wishes to assist with software.
There are several books on how to *draw* requirements models (ie. ERD, DFD, FDD, IDEF, et al.), but this book focuses more on *what* to put in the model. I have consulted on many projects where 100's of pages of "requirements" were documented, yet the documents actually contained 60% design preferences (in detail), 20% expected requirements (ie. performance, security, backup/recovery, installation, service, etc.), and (at most) 20% core, unchanging, business requirements. This book helped me guide these teams to discover and document what their customers needed and wanted, and separate these essential requirements from the typical fluff and "no-duh" staements that had previously been passed-off as their requirements document.
OO zealots can gain useful insights from this book on what makes up a "business requirement", if they can put aside their bias against traditional structured modeling techniques.
Mark Lucas, Houston, TX Feb 1997
|
|
|
Most Recent Customer Reviews
|
by Edward Yourdon
by Derek J. Hatley
See all 46 books citing this book
