Rating: 
Summary: Giving the Zachman framework a new lease on life
Review: 'Rather than reviewing requirement analysis from the perspective of a particular implementation of technology, this book views it as fundamentally an architecture process. This books premise is that requirements analysis is the translation of a set of business owners' view of the enterprise to a single, comprehensive architectural view of that enterprise'
David inspired by the Zachman framework shows how various methodologies and techniques can be organised for a omprehensive requirements analysis approach leading to an architecture solution. This book really brings forward the briliance of the Zachman framework. It gives a new perspective on Zachman and brings the framework back into the contempory enterprise strategies framework. David shows not only how to avoid the common mistake of building an architecture from a single business view but also how to integrate various views into a common architectural view. The book keeps to it focus on "Requirement analysis" and the reader is not really helped to go beyond the requirement analysis phase into the design and implementation phases. A good reference to have for people with an appetite for enterprise architecture strategies
Rating: 
Summary: Must read for software industry thought leaders
Review: As the Chief Technology Officer at MyBestHealth, Inc., a Los Angeles based software company, I am in charge of the development of twelve different software products. Our product development has been successful because we have based our methodology on David Hay's book "Requirements Analysis, from Business Views to Architecture." We have adopted David Hay's modeling techniques, to the letter, and they are directly responsible for many of our software design decisions. Their clarity has so crystalized our understanding of our business that they have allowed us to automate a vast amount (90% or so) of our software implementation process. This book is the best text I have ever seen on how to conceptualize applications at the requirements phase. It outlines a comprehensive approach, based on the Zachman Framework, on how to drill down at the different perspectives of an application to make sure that the application is designed, such that it will be successful if implemented according to its design. It is a textbook masterpiece, the authoritative text on product development planning, and I believe that any software developer who reads it will save years and years of time because the only other way of learning these skills is to make mistake after mistake, over and over again. Every software developer has a deeply rooted suspician that his / her work has in some way been done before. With every new account system, every new e-commerce package, every new document management system, or workflow automation infrastructure, we dream of one day being able to conceptualize a way were new applications only require configuring old ones. We dream of a world in which if we have to write a new application, we at least can skip the iterations and iterations of development that it takes to make a product successful in the market. Most of the time, though, we resign ourselves, not only to re-building customized solutions to the same problems over and over again, but the solutions themselves are inadequate in some way, and require more time and budget to finish. In the next few decades, the software industry will become more efficient at addressing these issues, and those who read this book will be the earliest designers of the techniques that will emerge. I should also note that David Hay's previous book, "Data Model Patterns: Conventions of Thought," is also a must-read.
Rating:
Summary: Must read for software industry thought leaders
Review: As the Chief Technology Officer at MyBestHealth, Inc., a Los Angeles based software company, I am in charge of the development of twelve different software products. Our product development has been successful because we have based our methodology on David Hay's book "Requirements Analysis, from Business Views to Architecture." We have adopted David Hay's modeling techniques, to the letter, and they are directly responsible for many of our software design decisions. Their clarity has so crystalized our understanding of our business that they have allowed us to automate a vast amount (90% or so) of our software implementation process. This book is the best text I have ever seen on how to conceptualize applications at the requirements phase. It outlines a comprehensive approach, based on the Zachman Framework, on how to drill down at the different perspectives of an application to make sure that the application is designed, such that it will be successful if implemented according to its design. It is a textbook masterpiece, the authoritative text on product development planning, and I believe that any software developer who reads it will save years and years of time because the only other way of learning these skills is to make mistake after mistake, over and over again. Every software developer has a deeply rooted suspician that his / her work has in some way been done before. With every new account system, every new e-commerce package, every new document management system, or workflow automation infrastructure, we dream of one day being able to conceptualize a way were new applications only require configuring old ones. We dream of a world in which if we have to write a new application, we at least can skip the iterations and iterations of development that it takes to make a product successful in the market. Most of the time, though, we resign ourselves, not only to re-building customized solutions to the same problems over and over again, but the solutions themselves are inadequate in some way, and require more time and budget to finish. In the next few decades, the software industry will become more efficient at addressing these issues, and those who read this book will be the earliest designers of the techniques that will emerge. I should also note that David Hay's previous book, "Data Model Patterns: Conventions of Thought," is also a must-read.
Rating: 
Summary: Good on data modeling, but little else
Review: I had a good book on OO analysis and the UML, but though it weak on data modeling and business rules. So I went looking... I read the 4 reviews on this page and purchased the book. Given the reviews and the fact that it was just published, I thought I would be getting a book that unifies a broad sweep of modern analysis techniques (OO, UML, Data Modeling, Design Patterns, Business Rules, Requirements Gathering Techniques, Iterative Development, etc.). On the contrary, I received a book that is 90% data modeling biased and steeped-in analysis techniques of the pre-OO era, such as data flow diagrams (people still use these?). This looks like a book I had in school 10 years ago. There are passing and, at best, cursory references to UML modeling approaches, but that is all that is in this book with respect to modern OO approaches. There is absolutely nothing said with regards to Design Patterns nor an iterative approach to building systems and mitigating risk. I find this lack of coverage absolutely incredible in a software requirements analysis book published in 2003. Unbelievable! Ten years ago, this book might have been considered a good benchmark. Not today. This author's sole idea of architecture is the data model and functional decomposition. Ugh. If you are weak on relational data modeling, this book has redeeming value. Otherwise, if you are trying to figure-out how to elaborate requirements and transform them into a working OO system using UML, Design Patterns, and an iterative approach, I highly recommend Craig Larman's top-notch "Applying UML and Patterns: ...". It really sets the standard. The Larman book is weak on data modeling and business rules - which I thought Hay's book would address better (and is why I bought it sight unseen). It does, but at the expense of everything else.
Rating:
Summary: Work of a dream team
Review: I had to buy this book when I saw the authors' names on the cover, both of whom I hold in the highest regard and both of whose previous books have deeply impressed and influenced me (Hay's "Data Model Patterns: Conventions of Thought" (ISBN 0932633293) and von Halle's "Business Rules Applied: Building Better Systems Using the Business Rules Approach" (ISBN 0471412937). As in their other books the authors prove they have a deep understanding of their subject matter, which is the case of this book is the Zachman Framework. The Zachman framework is quickly introduced in Chapter 1, followed by a process model for analysis. Their combined and complementary knowledge of planning and managing implementation projects are evident in the second chapter. This chapter is essential because implementing an architecture based on the Zachman framework is complex and requires careful planning (not to mention selling to stakeholders). The remaining chapters dissect each view of the Zachman Framework (displayed in columns in the formal model), and provide sufficient information with which to elicit the business requirements and develop the architecture. What I like about this book is the way the authors make what is a complex undertaking seem straightforward - and it is straightforward if you follow the approach outlined in the book. Another thing I like is the fresh look at the Zachman Framework - the last book of any importance on the topic was [in my opinion] "Enterprise Architecture Planning: Developing a Blueprint for Data, Applications and Technology" by Steven H. Spewak and Steven C. Hill (ISBN 0471599859), published in 1993. This newer book continues where Spewak and Hill left off. Regardless of whether you plan to espouse the Zachman Framework, or if your goal is to assure that you capture requirements that are meaningful to the business domain, this book will provide you with insights and a structured approach.
Rating:
Summary: A response . . .
Review: I realize that it is a little irregular for an author to review his own book, but I feel compelled to respond to the reader from Centerville, GA who said that my analysis book was "Good on data modeling, but little else." It is important for anyone buying this book to understand what it is and what it is not. A very important point made in the book, which was apparently missed by our "reader", was that analysis is fundamentally different from design. Analysis is about understanding the true nature of the enterprise. Design is about specifying artifacts, using a particular technology, to do useful work. The two are not the same. This book is a compendium of techniques for analyzing the nature of a business. It is not concerned with object-orientation for the simple reason that object-orientation is an approach to design. It does not address "object-oriented analysis" because there is no such thing. There is only "analysis" of an enterprise. The results of that analysis may be used for designing object-oriented systems, COBOL systems, or any other kind you wish. The book describes UML, but it points out that only a sub-set of the notation is appropriate for analysis. UML was originally intended to support design. The book is organized around my version of the Zachman Framework, which means that it addresses not only data modeling, but also the modeling of activities, locations, people and organizations, timing, and business rules. In each case, it characterizes analysis as the process of translating a set of business owners' views of the enterprise into a single, coherent architectural view. It is true that the state of the industry now is such that there is much more to say about data than there is for any other subject, but I did make an honest attempt to describe as many modelling techniques as I could find for all of them. The book is an attempt to present a comprehensive picture of requirements analysis. If you are looking for a book on object-oriented design, this is not the book.
Rating:
Summary: A response . . .
Review: I realize that it is a little irregular for an author to review his own book, but I feel compelled to respond to the reader from Centerville, GA who said that my analysis book was "Good on data modeling, but little else." It is important for anyone buying this book to understand what it is and what it is not. A very important point made in the book, which was apparently missed by our "reader", was that analysis is fundamentally different from design. Analysis is about understanding the true nature of the enterprise. Design is about specifying artifacts, using a particular technology, to do useful work. The two are not the same. This book is a compendium of techniques for analyzing the nature of a business. It is not concerned with object-orientation for the simple reason that object-orientation is an approach to design. It does not address "object-oriented analysis" because there is no such thing. There is only "analysis" of an enterprise. The results of that analysis may be used for designing object-oriented systems, COBOL systems, or any other kind you wish. The book describes UML, but it points out that only a sub-set of the notation is appropriate for analysis. UML was originally intended to support design. The book is organized around my version of the Zachman Framework, which means that it addresses not only data modeling, but also the modeling of activities, locations, people and organizations, timing, and business rules. In each case, it characterizes analysis as the process of translating a set of business owners' views of the enterprise into a single, coherent architectural view. It is true that the state of the industry now is such that there is much more to say about data than there is for any other subject, but I did make an honest attempt to describe as many modelling techniques as I could find for all of them. The book is an attempt to present a comprehensive picture of requirements analysis. If you are looking for a book on object-oriented design, this is not the book.
Rating: 
Summary: Writing review for your own book Mr. David C. Hay 8=))
Review: It OK(!) that you answer another reviewer, but giving yourself 5 stars... What a shrewdness So I think my single star will balance the equation again
5+1 = 3
Rating:
Summary: A Broader Perspective on Requirements Engineering
Review: The author Dave Hay has written a book that should be read by any one doing requirements engineering. It gives arguably the most comprehensive coverage of requirements analysis techniques available in any recent publication, and probably in any publication to date in this area. The focus is to show how the various cells of John Zachman's framework for enterprise architecture can lead to asking and getting the correct answers for all critical analysis questions. The focus is on the second and third rows of the framework, with a particular emphasis on moving from the row two perspective to the row three perspective. For those who are unfamiliar with the breadth of techniques available for analysis, this book should be an eye-opener. Use-cases and Class models are not the whole world (although they are covered.) For those unfamiliar with the Zachman framework, or who know of it, but had no idea how to apply it in actual projects, Dave gives some great practical advise. He manages to show how having a framework such as this will allow us to improve the efficiency and results of our endeavors. In fact, it shows how many modern methods only scratch the surface of analysis, since they are very weak on some of the Zachman columns (the Who column for instance). Add this to your library.
Rating:
Summary: A Classic Read and Must-Have Reference !
Review: What an extraordinary new book David Hay has given us! Ever since I got my hands on this book, I've been recommending it to every applications developer, designer, and analyst I know. This is honestly a book that can reduce the cost of re-work due to inadequate and incomplete requirements definition by getting it right the first time. Regardless of tools that are used for implementation or the repositories or vendors whose products you may use, you will benefit tremendously from this book! Requirements Analysis, all 450+ pages, is excellent. Barbara von Halle in the forward says that this book "is destined to become the authoritative source for defining roadmaps from vision to architecture." I agree completely! I appreciated the discussion of the Zachman Framework and the rich sense of history that Dave brings to the topic. He is quick to give credit where credit is due and provides the substantial details on how we got from point A to point B. People like me who are deeply engrossed in producing software and database applications with assorted CASE tools will particularly appreciate this complete view. We don't always understand the theory behind the tools we use. Dave is completing our missing education with his excellent work. Systems rarely fail due to implementation. Almost always the points of failure can be found in the requirements analysis phase of development. As Dave says, "requirements analysis is the translation of a set of business owners' views of the enterprise to a single, comprehensive architectural view of that enterprise." Our failures are in not correctly capturing the business owners' views and in the translation. This outstanding work provides the focus on how requirements analysis can be done productively and correctly. This will greatly reduce those points of failure. The 45 pages devoted to a comparison of data modeling techniques at the end of the book are well worth the cost of the entire book all by itself. For me, it was lots of notations (some automated in a tools and others not) coming full circle. What a treat!! It also is an excellent transition to newer notations in XML and object oriented techniques that I'm still learning. The index is excellent! It's quite extensive, complete, and well organized. The bibliography is also exceptional and very complete. The glossary of terms is first rate! I especially liked the notations of chapters where the terms were documented. All of these excellent features point to the superb organization of the book. It's a classic read and a must-have reference! Maggie Tompkins is a lead Designer/Developer with the Defense Finance and Accounting Service, specializing in database design integration for corporate database projects. She is Editor-in-Chief of the Oracle Development Tools User Group (ODTUG) Technical Journal and a member of their Board of Directors.
| 
