Systems Books

As a medical student, I found this book to be extremely useful. It is well referenced and offers some simple, but powerful techniques about how to best interact with patients.

What I liked best about Communicating with Today's Patient: The practical suggestions that can be used often and right away. For example, when broaching a difficult subject, ask "What has been your experience with (topic)?" This gives you a reading on the patient's perspective and prevents incorrect assumptions. Dozens of techniques like this make the reader a better communicator right away. Two thumbs up!

Many doctors take their communication skills for granted, but the sad fact remains that most of us do not do a good job talking to our patients. Learning how to improve your bedside manner is extremely difficult to do, but this book shows you how you can do so. Reading this book is likely to be one of the best investments of your time you can make - and it's full of practically useful stuff you can implement immediately !

I'm not a doctor, but I'm often a patient. This book has shown me how to communicate better with my doctor. In fact, I think it has excellent and helpful information for everyone, as we all try to make others understand our desires and comply with them.

This book is terrific. It zeros in on so many of the problems caused by a lack of understanding the needs for proper communication when dealing with people involved in a usually stressful situation. It presents these problems in a simple and direct manner and then shows in common sense language how to solve them. I majored in communication in college and was involved in the health care industry for over 30 years. I would strongly recommend this book for anyone involved in that industry or in a position where dealing with people is a priority.

Planguage is a word and concept that combines Planning and LANGUAGE and is rooted in the author's experience since 1960. The core tenant of Competitive Engineering is that well structured specifications have a dramatic cost reduction over down-stream error correction. The defect prevention process (DPP) is used to clean up early stages specs, or preferably measure defects and motivate lower defect injection, in specifications and the attendant issues instead of relying solely on defect detection andcorrection once actual development has begun. Competitive Engineering provides focus and skills to dramatically increase how productive many of us have been in the past.

The centrality of quality specifications means significant gains for the broadest spectrum of stake-holders who stand to win with the System Of Interest (SOI). Take this specification as an example to clean up:

"The new system will use Foo language running on OS Bar and ensure top industry quality response time on web requests."

People in the field have seen specs like these. Hopefully you aren't writing them. There are what Gilb classifies as "Major defects" in this spec. Which web requests, the front page or all of them pulling from the various databases? Can the old system be incrementally upgraded instead of an entirely new development environment? Why use Foo and Bar if something else gets the job done better, faster, and with less resource utilization? Just how fast is "fast", anyway?

In Competitive Engineering you're told to get measureable quality requirements, record who requested that requirement, and exactly what "success" is defined as. That allows you to go back to the requester with notes such as "If we use OS Baz we'll get a 27% increase in CPU performance" and let them make a decision or escalate to the project funder. You're also encouraged to weed out "design constraints"; at least out of the mandatated and into the labelled area "Design Constraint". Wouldn't it be great if you got a specification that let you design the best you could without technical input from someone that can't use a web-browser?

See if you can understand my re-write of the above spec into Planguage.

Response Time on Front Page of Company Website.

Type: Performance Requirement
Version: 1.2
Status: Draft
Owner: F. Flintstone

Stakeholders: Marketing, Server Support, Corporate Intelligence, ,

Ambition: The front page of the corporate website should respond fast enough to keep the viewer's attention.

Description: Marketing research indicates the typical business website viewer makes an opinion on the website, and thus the company, within 20 seconds. Our corporate site pulls data from three different databases and a sizeable image library, taking an average of 26.87 seconds on a home DSL/Cable modem equivalent network. Marketing advantage can be gained if we can grab viewer attention noticibly faster than our two nearest competitors who average 23.43 and 26.09 seconds, respectively.

Vision: Enough accurate information provided quickly enough to keep the customer on our site.

Scale: Time, in Seconds, to a complete front page load on the equivalent of a 250K network connection.

Past [Front page, 1 Apr 07]: 26.87 seconds

Goal [1 November 07]: 19 seconds <- Marketing Director: BR

Stretch: 15 seconds

Wish: 9 seconds

Design Constraint: Supportability <- Server Support Manager WF Must utilize .

Design Constraint: Security <- Corporate Intelligence BB Must meet .

------------------------ end of spec example --------------------

Probably the only thing that might confuse you about that specification is the use of text within "<...>". Planguage uses that to denote a "fuzzy requirement"; something that is defined but not with the concreteness you'd like. In this example, however, it would be relatively simple to query B. Rubble for the specific guidelines her team seeks to enforce. The use of fuzzy requirements also allows for change over time; more OS versions may become supported while others are obsolete.

When I read part of an electronic copy of the text I had a problem. My antiquated home printer could not print it and if I used the work printer I view the output as a possession of my employer. The book is written as part instruction, part reference manual; I bought my own copy because I know I'm going to use it for the next few years and several employers.

This is one the books which has caused a great impression on me. It helps to get away from high-level, gut-feeling, fuzzy goals and descriptions to very concrete targets, unambiguous requirements and rational decisions. This strikes a chord at the heart of systems design and architecture, which consists in maximizing a set of business goals with limited resources (time, budget, personnel). I highly recommend it.

Building software systems is not easy, this book can help you to do a better job.

In a period where the trend is to follow agile approaches with condensed guidance (see the 12 principles of the Agile Manifesto for instance), it could seem strange to publish a book on software development with more than 500 dense pages. You should however not be frightened by this book. Beneath the size and the structured form lies an approach based on practical experience that incorporates change and flexibility without abandoning the quest for precision and delivering value.

The main concept of Competitive Engineering is Planguage, a word created mixing plan and language. Communication is the basis for working together. This is why Tom Gilb emphasises first the creation of a common vocabulary. He states that his glossary could be considered as the best contribution of this book. Beneath the definition of a common language, for me the "hidden agenda" of the book is to help us to think... further. The common language is only a tool that helps us express our thoughts more precisely and completely.

Fortunately for us, Tom Gilb didn't only write a dictionary of system engineering. A large part of the book is devoted to the activities of system engineering and project management. Based on Planguage, Gilb gives us a framework to elicit clearer requirements. He emphasises a measurable vision ("bad numbers beat good words") and presents tools to achieve this objective. He also helps us separate requirements from design. He devotes an entire chapter to quality control. Finally, there is a presentation of the techniques of evolutionary project management that supports incremental development based on the priority and impact techniques described in previous parts of the book.

In every chapter you will find examples and case studies that help to visualise how the concepts translate into practice. There is also an "additional ideas" part that presents material for further thinking. Beneath the seriousness of the topic, Gilb also manage to place some lighter parts and you will find how to compare seriously apples with oranges.

At the end, your realise that you have a book where process is not opposed to people, structure is not opposed to flexibility, precision is not opposed to allowing change, documentation is not opposed to active refinement, Gilb's proposed solution is not opposed to customisation for your needs. It is just a book that gives you new inspiration to deliver better software solutions to your customer.

If you are interested in software process improvement, you can read this book from the beginning and find practical material to examine your current practices with a different vision. If you are a lonesome project manager or developer, you could begin by just using the index to get Gilb's view on your current activity or problem. Be cautious, because there are many chances that you will be tempted to read more material ;o)

After reading this book, I browsed again my old copy of "Principles of Software Engineering" that I bought when it was published in 1988. I saw that many ideas from "Competitive Engineering" were already presented in this book. Tom Gilb just applied to his ideas the same concepts he proposes for system engineering. He refined, expanded and structured them to get a better product. The printing industry has just prevented evolutionary delivery, but you can bet that he will find a way to include this in the future.

My interest in the topic of competitive engineering (CE) was piqued several years ago when I heard very favorable comments about Tom Gilb's tutorial on that subject at the INCOSE 2002 Symposium in Las Vegas.

The book's subtitle is "A Handbook for Systems Engineering, Requirements Engineering, and Software Engineering Using Planguage". The term "Planguage" is central to an understanding of the book. Planguage, which is derived from a union of "plan" and "language", is the methodology for implementing CE. Much of the book is devoted to describing the generalized processes, rules, and vocabulary of Planguage. Tom notes, "Planguage should be viewed as a powerful way to develop and implement strategies that will help your projects to deliver the required competitive results." Fundamentally, the book presents a new take on best practices in systems engineering and management.

The book is useful on several levels. For organizations without a formal or documented process, tailoring of Planguage would jump start the process at a high level of maturity. For organizations that have achieved CMMI level 3 status, Planguage by itself is not as useful. However, many of the ideas of CE-the Planguage methods-are worth considering for enhancement of existing organizational processes. Tom states that CE is "about technological management, risk control, and breakthrough improvement in complex business systems, projects, and processes." CE is a believable approach for delivering complex projects on time and within budget.

The book passed my value-added test, when I realized that I was photocopying several pages for future reference, to be part of my "toolkit" of helpful tips and techniques. I particularly enjoyed reading the 10 often witty, summary principles in each chapter. Two examples are:

* The Principle of `Storage of Wisdom': "If your people are not all experienced or geniuses, You need to store their hard-earned wisdom in your defined process. Capture wisdom for reuse, Fail to write it, that's abuse!"

* The Principle of `The early bird catches the worm': "Your customers will be happier with an early long-term stream of their priority improvements, than years of promises, culminating in late disaster."

About 30% of the book is the Planguage Concept Glossary, which Tom views as a central contribution of the book. I focused my attention on the other, more interesting, parts of the book, which describe the main CE/Planguage methods of Requirement Specification (RS), Design Engineering (DE), Impact Estimation (IE), Specification Quality Control (SQC), and Evolutionary Project Management (EVO, also known as Evo). RS describes an approach for identifying all types of requirements while avoiding ambiguity and also planning for change. Functional and performance requirements are distinguished. DE deals with identifying, choosing, and prioritizing the order in which design ideas are implemented and delivered. In conjunction with Evo, DE selects the design ideas most likely to provide a significant benefit for early delivery.

SQC is an eminently practical approach for evaluating the quality of any technical document via sampling measurements. An hour of SQC early in a project can save almost 10 hours of rework. SQC also provides a means to assess the success of process improvement efforts. IE provides a realistic method for evaluating-in quantitative terms-the effectiveness of designs in meeting both the requirements, especially critical performance attributes, and the resource budgets.

Evo focuses on early, frequent delivery of project results via a series of high-value, small evolutionary steps. An ideal Evo approach would divide the project into a series of cycles. Each cycle would consume 2-5% of the total financial budget and 2-5% of the total project time-while delivering some measurable, required results to the stakeholders. The next cycle is selected to deliver the best stakeholder value for its cost (highest ratio of value to cost, or highest ratio of performance to cost). Although an ideal approach can't always be realized, Tom provides some convincing examples to argue that there is always a solution to making a project evolutionary (small steps with critical deliveries first).

Perseverance pays off with Competitive Engineering. The book is not a quick read, which Tom acknowledges. You have to carefully study some of the pages to understand the concepts being presented. The reward occurs when you glean the nuggets of wisdom from the numerous practical examples, case studies, and Planguage examples. Tom's way of presenting the CE concepts makes the book a useful addition to the systems engineer's library.

Most texts on industrial control are long on theory and short on practice. This book is a rare gem that presents the theory (without overloading you on details) and then explains how to actually use the theory in practice. (One note: the practical applications are focused on electric motor control, which is the author's background.) If I had to have only one book on controls in my library, this would be the one.

This is a really good book that simplified control system for the real world. Most text spend too much time on theory and analysis and end the discussion with a bunch of equations and graphs without explaining how to implement the design. This book covers both analog and digital control, and lets you download a software from the author's web site. This software, ModelQ, lets you play with various parameters so you can see how the system behaves when it is not optimized.

One drawback with the book is it only covers PID control and its variants, but doesn't cover state-space control. While state-space control may be considered "overkill" by many control engineers, state-space is used in industry. The decision to use state-space is often not in the hands of individual engineers, so it may not be an option to ignore state-space. It would be nice if Mr. Ellis could cover state-space in his next edition of the book.

I had three main reasons for buying this book:
1. To bridge the gap between the control theory from school and the systems that I now design and build
2. To gain insight on how to improve the performance and reliability of real motion systems
3. To find ways to apply advanced techniques to help meet challenging performance requirements

I got all of this and more from this book. The topics covered clearly and concisely in this book span three courses I took at Cal Poly SLO: basic controls, digital controls, and modern/advanced control theory. Mr. Ellis does a great job of quickly introducing these topics and getting straight to the practical implications.

The free software and examples work well to illustrate his points quickly and easily while helping to commit the insights to memory. I also hope to use it as a training tool for our techs.

I highly recommend this book to anyone working with control systems, especially grad students and people getting started in the field. I look forward to reading his book on observers.

The author attempts to bridge the gap between theory and practice, and does a good job at it. Familiarity with control concepts will help one to get more out of the book, because the book focuses more on the practical aspects. The explanations in some of the sections can definitely be more complete, and thus I have to give it only a 4 star rating. Overall it is a good book.

Ellis has made a fantastic book on PID and similar control loops. He takes a very different tact than most controls books -- he writes with a voice similar to a handbook, but delivers enough content to compete with more traditional textbook-style controls books. It is light on the math in comparison, but I don't find myself wanting for more math.

I do a lot of controls design, consulting, and teaching. I recommend this book often and find that people that buy it uniformly track me down and thank me for the recommendation. I can't think of much higher praise for this book.

If you're looking for a guide on writing e-mails in a business setting, look no further. This book covers every aspect of writing e-mails and even some tips on how to organize your e-mail as well. The chapters take you through different topics regarding e-mail and at the end of each chapter are some activities that you can do to help build your awareness of your e-mail writing skills and how examining the messages you receive from others can help improve your awareness of writing skills. This book is perfectly designed for training courses, since each chapter could be completed in one training session. I recommend this if you are looking to write e-mails as professionally as you can.

Like it or not, we live in a world of electronic communication. E-Mail: A Write It Well Guide is a practical and helpful guide for those who aren't totally familiar or comfortable with the medium as well as for those who use it routinely, but perhaps not always effectively or appropriately. Most important, it urges people to take their e-mail communication as seriously as their other written communication - and tells them how.

This book is exactly what every e-mail should be (and so few are): clear, sensible and pointed. Compare the advice here to the emails you receive daily and you will agree that it is filled with uncommon good sense. You'll find yourself trying to figure out how to secretly get copies to your colleagues! Jim Knutsen, President, Boatz Knutsen Communications

Like it or not, all of us are up to our eyeballs in emails everyday. We feel pressed for time yet need to write coherent emails that effectively communicate important information. This guide is an excellent resource on how to write readable emails that come to the point quickly without leaving any of the important stuff out. After going through the material, I recognized a lot of mistakes that our company frequently commits in our frequent volleys of emails with clients. I wish I would have had this book sooner! Thanks for cutting through the jungle for us, Write it Well!
Thanks,
Mike O'Quin
PowerPointPartners.Com

As the author of an English reference guide/workbook, I think this book is exceptionally helpful to everyone needing to send out professional e-mails. E-mail has just about replaced informal memos and even reports. Therefore, we all need to learn how to convey the right tone, present a professional image, get our messages across clearly, learn the etiquette of e-mail, and avoid the pitfalls and hazards that e-mail technology poses. The author provides excellent, relevant examples and lays the material out in a logical, easy-to-understand fashion. I highly recommend it to individuals, HR departments, and training professionals.
Jane Straus
Author of The Blue Book of Grammar and Punctuation
and
Enough Is Enough! Stop Enduring and Start Living Your Extraordinary Life

WOW! What a great book! Stephanie tells her story with courage and grace. Her story is the story of everyone who experiences seizures or any disability for that matter. Her honesty and clarity are to be admired. She has hit the nail on the head when it comes to what it is like to live with seizures. I am one of those who can relate to the meaning of seizure confinement. But her book emphasizes the faith and restoration that can come when you act on your personal courage. If you are looking for a book to give you courage to encounter the fear of the unknown then this is the book for you. A MUST READ!!!

As Ms. Sawyers husband, I am repeating my previous review and changing my review up from 4 * to 5* Even since "Facing Me" was published, I have become more aware of the role societal influences, drug effects, and psycho/social effects play in the person struggling with epilepsy. My earlier 4 star (repeated below) allowed room for others to advance the review. They have appropriately done so, and I acknowledge the rightness of the 5 star rating.

For anyone struggling with epilepsy, either as a patient (as my wife) or as someone who loves an epilepsy patient, this is a must read. For anyone affected by a chronic medical condition, either as a patient or as a family member, it is a must read.
For the one carrying the heavy burden, you will hear the voice of one who has "been there." For those of us who deeply love one so afflicted, you will learn much of what it means to be in your partners shoes (something you must learn).
Twenty years ago, we would have given almost anything to hear this story from another. You should listen.

Here is my original review:

"An excellent tale of struggle with epilepsy (which mostly means struggling with society's view of epilepsy) and the self-accepted stigma which often accompanies it. This is not a technical medical story, as much as it is a patients account. As such, it is less involved with precise medical details than "what is it like" to go through metamorphosis. As the tale continues through brain surgery, and the author's effort to understand her place in the world without epilepsy, there is a freshness and genuineness which comes from a patient's point of view, illuminated by her faith in God's active presence.
A great read for anyone with a chronic medical condition, those in relationship with them, and for anyone who could use a dose of hope."

R. Eric Sawyer

Facing Me is the story of Stephanie S. Sawyer's struggle with epilepsy, a medical condition that takes many forms. Stephanie struggles with daily seizures that leave her feeling disoriented, humiliated and depressed. While she struggles to hold her world together, she starts to have a spiritual awakening that gives her the strength she needs to endure societal pressures and being fired from her job.

During a time in her life when she needs the most support, she endures misunderstanding, a lack of support from her community and overwhelming nights of the soul. After undergoing surgery she has new challenges, unexpected surges in her creativity and entire new worlds to explore. She is mentally unprepared for all the changes that start to occur, and as the seizures disappear, an overwhelming depression threatens to undermine all her previous efforts at healing.

Will her faith in God give her the strength she needs to overcome her fear and discouragement? Will the surgery be a success and will she be able to live a fulfilling existence and find hope in a seemingly hopeless situation?

Stephanie S. Sawyer's story is fascinating because she reveals many aspects about epilepsy that are essential for understanding the fear, struggles and discouragement this invasive challenge presents. Stephanie's writing is vivid, inspiring and informative.

Since 181,000 new cases of epilepsy are diagnosed each year and ten percent of the American population will experience a seizure in their lifetime, this book is essential reading.

~The Rebecca Review

Facing Me is one of those books that you cannot start without finishing. If you put it down to go to sleep, the first thing you'll do in the morning is pick it up again.
Even if you're not much of a book reader, you'll find yourself clutching Facing Me, which details Stephanie Sawyer's personal struggle with Epilepsy. She displays incredible courage dealing with the disorder, the brain surgery she endured and the post-operative experiences that followed.
Epilepsy is a frightening disorder. It strikes anytime and anyplace. It can leave you exhausted and embarrassed and its threat is something the epileptic never forgets. The epileptic is on-guard every minute of every day attempting to hide a constant concern.
But in spite of the never-ending challenges, the author never gives up. She maintains a positive attitude, refuses to give up and has brain surgery. With the surgery comes depression, a dark and frightening ordeal when the simplest task can be overwhelming.
Five years after the surgery - just as Stephanie was certain her seizure disorder was gone for good - she had another seizure. The thought of another seizure after certain victory had to be devastating, but Stephanie didn't give up. She continued to share her musical talents, graduated from Moores School of Music in 1999 and has proven an incredible inspiration.
I know about Epilepsy and I also know about the surgery. I, too, suffered from the disorder and had the same surgery as Stephanie. That said, I can say first-hand that Facing Me is a phenomenal book written by a spirited and courageous person who has refused to give up against all odds.

Mike Henle, author

I had intended to save Stephanie Sawyer's Facing Me to read on an upcoming road trip, but I made a couple of mistakes. First, I took it out of the box; next, I opened it. Once I did this, I couldn't lay it down. This book is so compelling I had to keep reading. I think everyone at times feels inadequate, but to have had to overcome the stigma that this woman faced as a child and into adulthood, gave me a new insight into how much prejudice hurts. That she should have triumphed over this thing, which was so shameful her own family refused to name it, hiding it and her away until she could be "normal" again, gives hope to all who suffer from being "different," whether it's because of some physical or emotional impairment. Not only has the author overcome her epilepsy, she has used her experience to become the remarkable woman she is today.

Friedman is not rehashing old work here. This is a new application of the Bowen Family Systems work as applied to leadership within the culture. I think his insights on anxiety in the culture are right on, and as always there is more hope where there is more understanding.
I recommend this to book to preachers, teachers, writers and analysts because these insights are distinctive and helpful.

After reading this book, I am now clear on why I am so frustrated with corporate and non-profit companies in the US. It's excellent and I plan to use it in my consulting practice - I've ordered copies for my clients!

I found Friedman's work very interesting and insightful. I am a parent and manager, so the concept of leadership is important to me. He puts his sometimes radical concepts into easy to digest sections, without watering in down at all. This is not your average management mumbo-jumbo, step-by-step, how to book.

At times it reads like a textbook, and some of his analogies with scientific discovery and history are long-winded, but all in all this was a book that made me think differently about how I act as a leader. It's very different from the standard stuff I have read before on leadership, managing and parenting. This is a book of well thought theory and examples. There is a lot of meat in this thing and it requires active reading skills.

Not for the weak of mind or self-help junkies.

Other reviewers have described well about this book. I am just joining in with my vote to add that this is a must have systemic leadership book. I don't know when this paperback started available, but I paid mine last year for $65 plus shipping from the Amazon market place, but it was worth it. After I bought mine, the remaining copy was listed for nearly $200. I am glad that the family decided to reprint this book.

A Failure of Nerve presents a unique approach on leadership among the books I have read on the topic. Friedman concentrates on several themes throughout the book that combine lessons learned from decades of experience and research.

The themes include the necessity of a sense of adventure and the possession of courage in leaders, the importance of self-differentiation, focusing on strengths instead of catering to weaknesses, the destructive nature of relationship triangles and the challenges leaders face among followers.

He highlights some negative practices of leaders in our culture, mainly the over-dependence on data and information and the misplaced emphasis on emphathy over action.

In this book, readers will find practical, simple ways to improve leadership. This book will challenge some of the accepted practices of organizational leadership today and should open readers' eyes to necessities of effective leadership.

All of Friedman's themes are applicable to families, congregations, businesses, government, etc. This is an especially useful book for parents and pastors/rabbis.

The downside of the book is that it was published posthomously, so the last three chapters were collected by colleagues who also edited the book. The effect is that it is not as cogent and concise as it might have been if Friedman had lived long enough to complete the writing himself.

This is a dense book on leadership that is definitely worth the effort of reading, as it will change the way you lead and relate to others.

i really like this book. touching stories that open your brain to different dilemmas in medical ethics, a subject i enjoy reading about. i lent it to several friends, all of whom loved the book.

I enjoyed the book. Makes you think about ethics a bit and the reality of financial constraints on the practice of medicine.

Despite the major advances in knowledge, skills, and technology in the field of medicine, this book shows that ultimately life and death fall back on the human touch. Following the workings of an Ethics Committee in a major urban hospital over several months, Belkin clearly shows that medicine continues to be as much an art as a science and in many cases there are no "right" answers, even when decisions can affect whether a patient lives or dies.
This is not a dry, mechanical review of how ethical decisions are made. Quite the opposite, the book captures your full attention from the very first page. You become fully involved in the heart-wrenching lives of actual hospital patients, as well as the no-win situations health care professionals and family members find themselves in when struggling with decisions that literally have life or death consequences.
For example, when she describes the process in which the life support devices are withdrawn from a young patient you feel you are there in the room witnessing the tragedy. Some readers might scream within their minds not to do it - perhaps there is something else can be done? Others may feel a sense of loving compassion over the ending of someone's suffering. Both types will feel incredible compassion for those who had to make the actual decision and hopefully will never have to make such a choice in their own lives.

Lisa Belkin has created an amazing book here - she definitely did her research. The book consists of a few case studies of patients who pose ethical dilemas. Belkin takes you inside meetings of the ethics committee at the hospital, she takes you to the patient's bedside to see what the patient actually wants. Some of the patients she follows are a young kid who has been hospitalized for 15 years with a terminal condition, beating all odds by staying alive that long, several premature babies, and a man who was paralyzed almost completely after getting shot in the spine. It's a great look at medical ethics - Lisa Belkin's book asks all the right questions.

The book is in a very easy-to-read format - the stories of the patients she follows are all intertwined throughout the book. For example, you'll read about Patrick for 30-or-so pages, and then she'll switch over to update you on Taylor's story. She does this because you are reading the stories in "real time" as they happened; all of this took place in a certain time span in the hospital. It's exciting and fast-paced non-fiction - I read it in two days and didn't put it down.

It will break your heart, because often the ethics committee has to bring money into the discussion, as much as they would like to treat every patient as if money was not an issue. This book is SO worth reading, for anyone who is interested in medicine and healthcare at all.

This book will keep you wanting to turn the page and make it hard to put down the book. This is a great explanation of real life situations that patients and hospitals face everyday. Some of the situations that are hard for some people to understand why hospitals are concerned with matters like money and certain treatments of patients can be explained.

The book opens with a history of the state of Iraq from its establishment after WWI to the present time. An understanding of this history is vital in coming to an understanding of the present difficulties facing the country. Two very salient points demonstrated persuasively by Iraq's history are that violence as a political instrument was institutionalized in Iraq long before the regime of Saddam Hussein. His regime was more a logical culmination of events which preceded it than a historical aberration. The second point relates to the primary reason for the development of institutionalized violence. The state of Iraq was constructed from disparate ethnic, religious and cultural groups to serve the political ends of the British at the time. This political expediency has lead to a state that has never been able to develop the sense of unity necessary to become a nation. Violence has been the primary means of keeping forces in line that could tear the state apart.

The history is followed by an examination of the perspectives of each of the three major groups that make up the state of Iraq - the Sunni Arabs, the Shi'a Arabs and the Kurds. Though this structure entails a certain amount of repetition of information from the first section of the book ( especially in the section on the Shi'a), it does help us understand the position of each of the three groups and what they stand to gain or lose as a result of different potential constructions of their future.

The third section of the book is devoted to examining the options available for the future of Iraq, including their potential positive and negative consequences and the likelihood of prevailing conditions allowing each option to become reality.

All three major groups in Iraq are shown warts and all. The book shows no favoritism in its analysis. The issues are analyzed with penetrating depth and the belief of the American government that the people of Iraq would welcome Western style democracy with open arms is scathingly laid bare as the ludicrously naïve position it is. A must read for all who truly want to understand the situation in Iraq.

Anderson and Stansfield have written a wonderful book that will appeal to both general readers and students. Its calm tone is a welcome change from a lot of the polemics about Iraq and it provides the reader with clear analysis of Iraqi history. My only complaint is that it is out of date. Hopefully a new edition will come out soon.

This is an interesting book. Anyone who is interested in an alternative to the right wing talk radio and tv news should seriously consider checking out the Thom Hartmann radio show opposite Rush Limbaugh weekdays at: thomhartmann dot com / showlisten.shtml

Whether democrat, republican, or indepedent, so many of the facts out there are completely ignored by the mainstream media and talk shows. This show is one strong example of an examination of the facts regardless of your political affiliation. I am not affiliated with the show in any way, just struck by the facts so many seem to ignore.

This book is structured in a very simple manner, following the history of this country:

First, the monarchy from 1920-1958;

Second, the revolution from 1958-1968;

Third, the Ba'ath Regime from 1968-1988;

Fourth, the wreck of Iraq from 1988-2003.

These chapters recount the history of Iraq from its beginnings after World War I--when the British created a country where none has existed before--with three parties holding very different views--Sunnis, Shiites, Kurds.

Each of these three groups is examined as the basis for speculation as to what is to come in the future. The authors wonder if Iraq might end up splintering into three distinct countries--Sunni, Shia, and Kurd. Questions emerge from this scenario: Is this desirable? Would the needs of all three groups be optimized in this manner? Will this encourage additional "ethnic cleansing"? Even beyond what we have seen? Would such a solution mark success--or failure--of the American intervention?

The future? America's role in that future? We cannot say at this point. However, it does appear that the American intervention never really understood the historical and cultural context. We can only hope that the Iraqi incursion turns out well. But it is also clear that Americans sadly misunderstood the context into which they entered. . . .

This book should have been required reading for those eager to enter Iraq, overthrow Saddam Hussein, and install a Western-style democracy. The book has three main points: (a) a history of Iraq from its flawed beginnings after World War I; (b) an analysis of each of the three main groups--Sunnis, Shia, and Kurds; (c) an examination of different scenarios that might illuminate the future of Iraq.

Each element is well done and provides context for the reader interested in something more than current events weith respect to Iraq. The end result of reading this book is to wonder at the arrogance of the war planners who apparently did not consider historical and ethnic and religious context as that critical for the outcome of the war. As one of the neocons once mentioned, reality is not so important to the United States; the country can create its own reality. To this point, the reality being created on the ground in Iraq is far different than it might have been had history acted as a guide.

This book is amazing!! I bought it about two weeks before my parents bought me a bearded dragon. It told me everything i need to know. It tells you everything about making terrariums and what to feed them. It also has sections on breeding and general information on the different species. This is a must buy if you are planning to raise a bearded dragon.

I bought this book when my parents bought me a baby bearded dragon. this has everything you need to know about raising dragons. it tells you all the feeding instructions and it also has an extensive list of diseases and ailments and there respective symptoms. it tells you all about how to create a good terrarium. it also has information on breeding and overall care of the dragons. this is an amazing book and i would recommend it to anyone that is looking to buy a bearded dragon.

what do you expect...this book was written by a man who breeds bearded dragons and it is a book about bearded dragons. It is a wonderful book and tells you everything you need to know about keeping a bearded dragon whether you are breeding them or not. I personally own a 1 year old dragon, and this has been like the bible to me. Whenever something is wrong i consult this book and it will always have the answer you need. All the other books are written by herpotologists who have never actually owned, bred, or loved a bearded dragon. This book is amazingly helpful and comes from a person who knows what he is doing. I would recommend it to anyone who is planning on owning and loving a bearded dragon.

This is a very through book on the care and maintenance of Bearded Dragons. It is excellent for the beginer lizard keeper. I highly recommend this book if you want to take good care of your Bearded Dragon(s).It contains information on their diet, vivarium design, and other very useful information. It is one of the most reliable reptile books I have read.

I don't like this book at all, the authors only writes about keeping the bearded dragons in big outdoor vivariums, and not about having just 1-3 bearded dragons as pets.

Very little information about feeding, housing and everything you really want to know. The authors also doesn't seem to think about the bearded dragons as pets, to cuddle with and have fun with, but only as something you can breed.

I almonst never read or look in this book, and I regret that I bought it.

I rekommend Liz Palikas book "Your Bearded Dragon's Life" and the book "The guide to a owning a BD" by David Zoffer and Tom Mazorlig instead!