AnyBook4Less.com	Find the Best Price on the Web Order from a Major Online Bookstore
Home  |  Store List  |  FAQ  |  Contact Us  |
Ultimate Book Price Comparison Engine Save Your Time And Money Keyword AuthorISBN

Title: Essential Systems Analysis by Stephen M. McMenamin, Palmer John F. ISBN: 0-13-287905-0 Publisher: Prentice Hall Pub. Date: 01 July, 1984 Format: Paperback Volumes: 1 List Price(USD): $71.00

Your Country USA Canada United Kingdom Australia Austria Belgium France Germany Italy Netherlands Switzerland Currency AutoUSD CAD GBP EUR AUD CHF Delivery Only cheapest delivery All delivery options Include Used Books Are you a club member of: Barnes and Noble Books A Million Chapters.Indigo.ca

Average Customer Rating: 5 (2 reviews)

Rating: 5
Summary: The definitive book on creating logical data flow diagrams
Comment: 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!

Rating: 5
Summary: Cuts to the core on how to find and document requirements.
Comment: 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