or
Sign in to turn on 1-Click ordering.
More Buying Choices
Have one to sell? Sell yours here
Sorry, this item is not available in
Image not available for
Colour:
Image not available

 
Tell the Publisher!
I’d like to read this book on Kindle

Don't have a Kindle? Get your Kindle here, or download a FREE Kindle Reading App.

Requirements Analysis: From Business Views to Architecture [Paperback]

David C. Hay
5.0 out of 5 stars  See all reviews (1 customer review)
RRP: £51.99
Price: £42.91 & FREE Delivery in the UK. Details
You Save: £9.08 (17%)
o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o
Only 1 left in stock (more on the way).
Dispatched from and sold by Amazon. Gift-wrap available.
Want it tomorrow, 3 Oct.? Choose Express delivery at checkout. Details

Formats

Amazon Price New from Used from
Hardcover --  
Paperback £42.91  

Book Description

23 Aug 2002 0132762005 978-0132762007 1

Hay presents a comprehensive overview of the world's best requirements analysis practices, organized into a coherent architectural framework that helps analysts choose the best approach for each project, and execute it successfully. Hay helps current and prospective analysts focus more clearly on their goals: to accurately represent the business's fundamental structures, identify key information processing gaps, and discover which information technologies may best address them. He addresses requirements analysis from two viewpoints: the system development life cycle (the steps required to build and implement a system) and the architecture framework (the perspectives of key players in the development process).



Product details

  • Paperback: 458 pages
  • Publisher: Prentice Hall; 1 edition (23 Aug 2002)
  • Language: English
  • ISBN-10: 0132762005
  • ISBN-13: 978-0132762007
  • Product Dimensions: 23.1 x 18.2 x 2.7 cm
  • Average Customer Review: 5.0 out of 5 stars  See all reviews (1 customer review)
  • Amazon Bestsellers Rank: 2,601,680 in Books (See Top 100 in Books)
  • See Complete Table of Contents

More About the Author

David Hay was born in Grand Junction, Colorado, mid-way through the last century, when it was significant that his home town was some 250 miles from any city of any size. Back in those days, it mattered. His knowledge of the outside world was limited to magazines, movies, and the public library. (OK, he'd had some friends who'd been there, but he didn't believe a word of what they said.) It was all fiction. This valley was the whole world to him.

Then one beautiful September day, he took his first plane ride. Three hours later, he was by himself in the middle of Los Angeles International Airport at 5:00 on a Friday afternoon--trying to find his way to college.

Pretty much the rest of his life has been spent recovering from that afternoon.

The college was Claremont Men's College (now Claremont McKenna College) in the heart of the smoggy San Gabriel Valley. He remembers it as being pretty traumatic for him, but then this was Southern California in the late 1960s and life was traumatic--and exciting--for everyone. And this "outside world" business was pretty intriguing, too. So much so that when he graduated, he decided that the only logical thing to do was to move to New York City. Why not?

So, with no money, no job, no experience, and a degree in Philosophy, he set out to find his fortune in the big apple.

From there he discovered the rest of the world. Among other things, in 1973, he had a life-changing trip through Eastern Europe during the height of the Cold War. OK, that one wasn't quite so traumatic. He went back to Warsaw the following year to marry the single most wonderful woman he'd ever met.

He got his MBA from New York University the year after that.

In the late 1980s, he discovered data modeling. He took to it in a big way. But not the way most people did. Rather than viewing it as a vehicle for database design, he viewed it as a way to crack open the secrets of a company's semantics, and with that, its very nature. He discovered, among other things that if you model the underlying nature of a business, you have just modeled the underlying nature of pretty much any business.

From this experience came "Data Model Patterns: Conventions of Thought", a groundbreaking book describing a set of standard data models for standard business situations.

At about the same time, he created a consulting practice, Essential Strategies, Inc. (http://essentialstrategies.com), that offers data modeling services to a wide range of industries all over the world. He uses data modeling to support strategic planning, requirements analysis, analysis of semantics and business rules, and data warehouse design. His clients have included representatives of oil (both production and refining), pharmaceutical research, television and movies, banking, among others. In each case, he goes into the company knowing only what he'd learned as a customer, and within a very short time (thanks to the model patterns) understand more about its underlying structure than many who worked there.

In 2003, he wrote "Requirements Analysis: From Business Views to Architecture", his unique approach to that subject. This is a compendium of some thirty years' worth of analytical techniques, organized according to his version of John Zachman's "Framework for Enterprise Architecture".

Then, in 2006, he published "Data Model Patterns: A Metadata Map", the only book available that describes a complete schema of metadata--encompassing all aspects of both business and technical views. Moreover, it not only describes data from these various points of view, but also covers functions and processes, people and organizations, locations, timing, and motivation.

He has been an active participant in DAMA International, various Oracle user groups, the Object Management Group, and the Business Rules Group. He has given presentations on various data and methodological subjects all over the world.

A library of his articles may be found at http://articles.essentialstrategies.com. Thanks to the World-wide Web, his writings are read by practitioners from all over the world.

Not bad for a kid from Grand Junction, Colorado, eh?

Product Description

From the Back Cover

The complete guide to requirements analysis for every system analyst and project team member.

Thousands of software projects are doomed from the start because they're based on a faulty understanding of the business problem that must be solved. The solution is effective requirements analysis. In Requirements Analysis: From Business Views to Architecture, David C. Hay gives you a comprehensive overview of the world's best requirements analysis practices, organized coherently to help you choose and execute the best approach for every project. In addition, he guides you through the process of defining an architecture–from gaining a full understanding of what business people need to the creation of a complete enterprise architecture.

Practical solutions will help you:

  • Focus more clearly on the goals of requirements analysis
  • Represent the fundamental structures and systems environment of any enterprise more accurately
  • Identify key information processing gaps and discover which information technologies can best address them
  • Clarify the goals of your new system and reflect them more accurately in your models
  • Understand crucial people-related issues that impact requirements
  • Plan smooth transitions to new systems

Requirements Analysis: From Business Views to Architecture provides the complete process of defining an architecture–so that you can build a rock-solid foundation for your next software project.

About the Author

David C. Hay has been developing interactive, database-oriented systems since the days of punched cards, paper tape, and teletype machines. He is president of Essential Strategies, Inc., a Houston, Texas-based worldwide consultancy that uses modeling techniques to help construct information strategies and architectures, and defines requirements in a wide range of organizations, including pharmaceutical researchers, news-gathering and broadcasting firms, oil refiners, and government agencies.


Sell a Digital Version of This Book in the Kindle Store

If you are a publisher or author and hold the digital rights to a book, you can sell a digital version of it in our Kindle Store. Learn more

Customer Reviews

4 star
0
3 star
0
2 star
0
1 star
0
5.0 out of 5 stars
5.0 out of 5 stars
Most Helpful Customer Reviews
1 of 1 people found the following review helpful
Format:Hardcover
This is a great reading. Based on Zachman Framework Mr Hay walks us thrugh all columns with numerous examples and discussions. I also appreciate the clear comparision of modelling techniques in the end. It's a lot to read, and maybe not the EA book to start with. But when needing to get further it increases your understanding and helps make things consistent and connected.
Comment | 
Was this review helpful to you?
Most Helpful Customer Reviews on Amazon.com (beta)
Amazon.com: 4.3 out of 5 stars  9 reviews
59 of 59 people found the following review helpful
4.0 out of 5 stars It will broaden your horizons, but it is not a cookbook. 14 Nov 2003
By Craig Kenneth Bryant - Published on Amazon.com
Format:Hardcover|Verified Purchase
_Requirements Analysis_ is just the opposite of a book like Craig Larman's _Applying UML and Patterns_ or Ed Yourdon's _Modern Structured Analysis_. Both of those books--in fact, most books on analysis--present a single methodology and a single set of tools and notations, then walk you through the steps of the analysis process according to DeMarco or according to Jacobson or whatever.
David Hay is after larger fish in this book, or at least more fish: in these 400 pages, you will find a survey of more techniques and models than you probably could have dreamed of, from the very old to the very new, from the flashy to the obscure: data flow diagrams, UML, Object-Role Modeling, cybernetics, business rules, IDEF0, and on and on. This book will teach you a little bit about a whole lot of analysis techniques and what they can accomplish.
The material is all organized and discussed from the point of view of the Zachman Framework, a beautiful and expansive system that shows us how various techniques fit in to the "total picture" of the who, what, when, where, why and how of enterprises and information systems. It gives us a broader perspective, and often shows us where we are focusing too much on one or two aspects of a system, to the detriment of the others.
But this book is not a cookbook or a procedural guide to performing analysis. There is very little prescriptive advice, and relatively little on the nuts and bolts of what you should do and when. I don't want to suggest that is a shortcoming: it is intrinsic in the very nature of a survey-type book. If you have done some analysis work or studied one or more particular methodologies, this book will give you context and perspective and introduce you to new possibilities you probably weren't even aware of before.
But if you are approaching analysis for the first time, you need guidance more than you need options, and you may find this book more confusing than useful. You might, instead, want to look at _Applying UML and Patterns_(Larman) if you are approaching analysis from an object-oriented programming perspective; _Modern Structured Analysis_ (Yourdon) if you are coming from a more traditional Data-Flow and Entity-Relationship shop; or _Mastering the Requirements Process_ (Robertson)for a more generalized, but still procedural, perspective on requirements definition. Then, in six months or a year, open Mr. Hay's book and feel the horizons rushing back from your eyes. This is basically what I have done, and I'm very happy I did. David Hay has given me a larger context at a time when I can start to appreciate it, and new options at a time that they can be useful to me.
I should point out that I feel the book is not without its shortcomings.
--Mr. Hay gives pretty short shrift to Use Cases, which are emerging as a really useful technique for discovering and capturing functional requirements. This book talks about use cases, but clearly considers them of secondary value, burying them in a fairly obscure corner of the Framework. Craig Larman, Alistair Cockburn, Ivar Jacobson and Doug Rosenberg all have good titles out that place Use Cases in a more central role.
--Certain object-oriented techniques seem to have a pretty low opinion of Analysis work, or call things "analysis" that are more properly considered design. Mr. Hay makes some good points in response, but I can't help feeling he's going a little too far when he says things like "there is no such thing as object-oriented analysis." No less a figure in the world of methodology than Ed Yourdon would seem to disagree, unless the title of his book, "Object-Oriented Analysis," is some kind of very subtle joke. You may want to pick up an OO title or two, and see what conclusions you come to.
--Last of all, I found the treatment of some of the areas of the Framework to be esoteric and difficult to follow. Most notable here is the discussion of business rules that makes up the book's treatment of the Motivation, or "why," column. I realize that business rules thinking is still in its infancy, but the presentation in the book is too nebulous, academic and abstract to come to any kind of grips with--it was like trying to learn the UML by looking at the "meta-model" documents. Another example is in the People, or "who," column, which consists of a very academic treatment of the science of "cybernetics." Intriguing, but darned if I got much of practical use out of it. Shouldn't the People column have something to do with characterizing and categorizing users, their preferences, environments, levels of experience? Perhaps all the stuff on cybernetics _does_ that, but it was all a little too rarefied for me to follow.
In summary, this was a very valuable book for me. I'm a better analyst for having read it, and I have a whole list of new things to think about and learn about (including the above-mentioned business rules and cybernetics). I can't recommend this as a _first_ book on analysis, but I can heartily recommend it to anyone who wants to learn _more_ about analysis.
23 of 25 people found the following review helpful
5.0 out of 5 stars Work of a dream team 7 Oct 2002
By Mike Tarrani - Published on Amazon.com
Format:Hardcover
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.
14 of 15 people found the following review helpful
5.0 out of 5 stars A Classic Read and Must-Have Reference ! 8 Jan 2003
By Margaret Tompkins - Published on Amazon.com
Format:Hardcover
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.
15 of 18 people found the following review helpful
5.0 out of 5 stars A Broader Perspective on Requirements Engineering 3 Feb 2003
By Gary Michael Zimmer - Published on Amazon.com
Format:Hardcover
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.
11 of 13 people found the following review helpful
5.0 out of 5 stars Must read for software industry thought leaders 28 Jan 2003
By Brian Rosenthal - Published on Amazon.com
Format:Hardcover
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.
Were these reviews helpful?   Let us know
Search Customer Reviews
Only search this product's reviews

Customer Discussions

This product's forum
Discussion Replies Latest Post
No discussions yet

Ask questions, Share opinions, Gain insight
Start a new discussion
Topic:
First post:
Prompts for sign-in
 

Search Customer Discussions
Search all Amazon discussions
   


Look for similar items by category


Feedback