Like I said this is an awesome book!! I finally bought it after borrowing it from my church library for 2 months!! This is one book that will not collect dust in your book shelf. I keep it on my bed and flip through it whenever possible, and everything in it just makes you stop and think. It's full of really good poetry and prayers (meditations). One of these days my family should start using it before meals. It's a great idea to discuss it through the meal.

We've all heard about the road to hell...
My own personal hell is canned grace and I vowed I would teach my kids to speak their thanks for the food before them from the heart. Nope, no rote prayers in our house.
Well it took about two weeks before they were lisping "Thank you for the food we're gonna eat," as fast as they could speak the words and in singsong just to make it worse.
Then enters The Grateful Heart. What a wonderful difference! The short, profound selections come from all over the world, from all faiths. We take turns, one reading per meal. Often the selection leads to discussions far more interesting than what used to be why we're having carrots or spinach AGAIN. And quite frequently, spontaneously, one of the children concludes the reading with the words "Thank you." Which is the point of grace to begin with.

This book does not live up to its title and subtitle. Very general material. For example, Denial of Service Attacks are in the news these days. Looking through the index, I find four references to DOS attacks. The first on page 45 tells me that DOS attacks can be costly. The second on page 85 describes some previous DOS attacks, including one that took place 12 years ago. The next reference is on page 304 and is a historical description of DOS attacks over the past three years. The last reference on page 452 tells me that I should conduct DOS testing for my web server. Most of the book's content is similar. If this is useful to you, please buy this book. For specific help in hardening your network, please look elsewhere.

I am a relative newcomer to the security field. I have been adding books to my library to help me in my job. I picked up Defending your Digital Assets and was pleasantly surprised. The sections on Security Verification of Systems and Networks and Cryptography were a rare read, and very enjoyable.

I also found the chapter on Biometric Countermeasures one of the clearest presentations on the subject, that I have found in print.

The authors clearly understand the INFOSEC field and their writing shows it. They make difficult concepts interesting. Too many books on this subject read like swiss cheese or with too much useless detail. Defending is the exception. I liked it. I recommend it.

As a neophyte I am tangentially aware of the importance of computer security, but reading "Defending Your Digital Assets" really brought the message home. As our world becomes more "wired", and our reliance on the information we receive through computers increases exponentially, the importance of computer security cannot be overstated.

This book is very approachable for the layperson and is an excellent primer for computer/information security overall. It was the only book I could find that that covered the topic so completely.

In addition, the book is very readable. The authors did a very commendable job in writing the book, i.e., it doesn't read like a text book.

Also, the book offers a large number of references/resources the reader can refer to for further study...as well as a glossary and a thorough appendix.

In sum, if you have a scintilla of interest in computer security, pick up this book. If you're a manager and concerned with computer security in your organization, pick up this book. If you are a student, pick up this book. In fact, if you use a computer at all, you should get this book.

The better informed we are, the harder it will be for hackers and crackers to wreak havoc on our computer systems and the information we rely on.

Thank you --Sean

I approached this book with an open mind, but after I stumbled upon a couple of obviously wrong and some nonsensical statements, I started reading it much more skeptically, and finding more and more problems with it. (However, it did provide more fun ;))

The book has a good premise, trying to explain information system with the factory metaphor. Although authors give some good insight in the way IS should or could be thought of and modeled, there are many instances in the text where you read something and say to yourself "what where these good people thinking". This then undermines your confidence in their vision and full understanding of the matter. And although I think this is a matter of personal preference, authors sometimes seem to be in love with their style, producing some beautiful nonsense like this: "The legacy environment is only a very small vestige of its former invincible self." (pg. 42)

Let me give you some more examples of what I'm talking about:
Authors create metaphors of user classes, calling them "tourist, farmer, explorer and miner", which in itself is not a bad idea, but then they go on to say "...farmers found at the ODS environment are quite different from the farmers found at the data mart". So why did you create the single metaphor then?

Also, check this out: "A miner will typically look over many, many rows of data...". As opposed to what, just a "many rows of data"? Whence some people might need "not so many rows of data"? Like I'm reading a book for my eight-year-old, for goodness sakes!

Then there is this graph showing the directional flow of data, but then it reads: by the way, in all this streams, data can sometimes ("in 1-5% of the cases" - authors never say how they got these numbers, it is all a slight of hand) flow in the opposite direction!!?(Pg. 24) And they go about giving 5 examples, 4 of which are wrong - there is no data flow in them at all!
Example:"...sales dept. notes that loans are slowing down. The decision is made to reduce home loan rates by 1/2 percent."
This is not the back flow of data, as authors assert, it is an information feedback loop that involves people (management), and their decisions. Data (loan rates) is not coming back from Data Mart. User is somehow entering it into Operational system (application). His decision is influenced by data analysis, but it does not reverse the data flow. The fundamental issue here is that authors ignored the fact that information processes in the company involve people as well as the data and systems, and should be modeled as such. To use their metaphor, users should be a part of the information ecosystem. Hence it is not true that, as the book claims, corporate information factory embodies the information ecosystem. (Pg.7)

"...'event' date ...reflects the moment in time when the data in the record was accurate". (Pg. 96) This is incorrect. 'event' date is just recording the time of that single event. Record is always accurate after that, it does not 'age' with time.

At pg. 191 it is asserted that Data Warehouse provides "depth" to the data. That is true only if it is built (modeled) with "depth" requirements in mind. Before I can get "deep" information from the DW, I must build it with my questions in mind, otherwise, it will not give me data. An abstractly deep DW does not exist. It is always an answer to a particular question, or number of questions.

"The Dimension of History" (pg. 193-194) is just plain good old nonsense, with example (life stages of an individual) being completely off the mark. Reminds me of the student who does not know the correct answer to the question so he tries to invent some plausible response, letting his imagination fly ... Sad.

And so on, and so on...

I saved the best ones for the end:
"...the external world is full of normal occurrences and normal events. The very ordinary nature of the external world makes us take it for granted." (Pg. 49) Very philosophically deep, indeed ;)
"The emergence of the integrated applications comes slowly and, in many cases, imperceptibly" (pg.42) Yeah, it just creeps on you when you're not looking... ;)
".. the back flow of the data is minuscule to the point that in some cases it is so small as to be unmeasurable". (Pg. 23) :0 Beg your pardon? This is not quantum physics, guys, this is computer science. Anything can be observed, perceived and measured to the level of a single bit. Or are we talking bit-quarks here? Informational principle of uncertainty?

It is disappointing to have this book co-authored by the "father of the data warehouse".

To the (prospective) readers: This is a fun book if you are an experienced data architect, bad if you wish to use it as a blueprint for your work, and dangerous if you are an IT manager and impose it on your staff.

To the authors: Give us a break, please go back and re-make a decent book around the good basic idea. Less poetic style would also be appreciated. Forget about quantum physics. And give it to some unbiased reviewers first. Remember, only the real friends will tell you the unpopular truth.

The very idea that all the technologies serve the purpose of businesses gets lost here in this book.

If one wants to look for help for their work, look somewhere else.
If one wants to learn some jargons to impress his/her date, this one is the ideal one.

Evaluating "overview" books such as these is difficult. If this is a new subject to you or you are a manager needing an overview, you'll probably find it a good introduction to the Inmon-style Data Warehouse (the other being Kimball-style). But after giving the book a "once-over", that's it. Nothing is handled in enough detail to make this any kind of reference or guide. So from the novice perspective this is a "must read" and as good an introduction to CIF as you will get, from the people that define the standards - give it 4 stars (why not 5 stars will be discussed later). If you have worked on Data Warehousing projects in the past but your environment was not particularly designed with much forethought, then by all means whiz through this book and you'll see that all the pieces can be part of a cohesive strategy - 3 stars. If you are experienced then you'll probably see this as a waste of time, too high level. You can get everything in here from various web sites, whitepapers or other books - 1 star. Regardless of where you're coming from though this is one of the few books that actually use pictures in a way that is detrimental to clarity. Some are repeated so many times, so inane or so large that you have to surmise that they are mostly there to thicken the book. The appendix, CIF Architecture Guidelines, is also the largest section of the book yet I have no idea what the point is. I think it would be more appropriately titled - Incomplete Ruminations on Random Topics.

I purchased this book expecting that it would present a coherent methodology for initially sizing a data warehouse and for planning for subsequent growth. What I got out of reading this book is some scattered ideas about data warehouse performance, which though many are sound, needed to be put into some overall context. The authors attempt to put some of their thoughts together in a case study in the last chapter, but I found that chapter missed the mark also.

There is no doubt the writers know their subject. They just failed to organize their knowledge in a way that many firms implementing and maintaining data warehouses would highly value.