The description of the book has more meat than the book itself. This disappointing book is a 15 short chapter breeze through a multitude of subjects, and does not linger long on any single subject. There are some nice diagrams and ten thousand foot views crammed into 374 total pages (the page count vs. chapter count alone should indicate how superficial this book is). An example is the 21 pages devoted to weighty subjects encompassing project management tasks, configuration management, verification and validation, quality assurance, decisions and risks. Any one of the topics would have merited at least 20 page in a serious book on systems engineering. Useful to sales and marketing types who are selling systems engineering services, and executive management who might like a quick overview of systems engineering. This book is useless for technical professionals.

This book is a great introduction to the system engineering process. It might be lightweight for a practicing system engineer, but for an IT professional whose background is service delivery, production support and data center operations this book opened a whole new world.

An example of how this book opened my eyes is the way configuration management is explained, and how it fits within the system engineering process. IT professionals with my background are subject matter experts in change control; however, few of us (certainly myself) realize that change control is a subset of a much larger picture. Every part of system engineering it covered in sufficient detail to understand the basics. This understanding created, in my case, a desire to further research some areas in greater detail. Overall, seeing the process from a high-level view provided some unique insights about what is missing in IT management that can be filled by borrowing from our system engineering brothers and sisters.

I found this book valuable because I did not have to wade through a dry manual and sort out the details in order to get a big picture of system engineering. The brief, succinct chapters and excellent illustrations provided me with a coherent approach to my own job. In fact, I personally believe that applying system engineering principles to IT service delivery and operations management will significantly improve the IT profession. As such I highly recommend this book to my peers and anyone else who needs to see the big picture of the system engineering and how its principles can be related to their job.

Stevens' Systems Engineering looks at the place ofrequirements in a world which consists of complex systems in a highlycompetitive marketplace. This may be the commercial world or equally the military-industrial world in which systems must literally do battle with their rivals.

Stevens and his co-authors (two of them from the UK's Defence Evaluation and Research Agency) know that in this environment, many systems fail, very often because they were inadequately thought out, and often also because their development projects were poorly managed. Chapter 1 begins "The world is currently gripped by changes more intense and rapid than those triggered by the ndustrial revolution..." : we are at once swept into the rich, complex, and dangerous life of real system development.

For Stevens, the problem in systems engineering is complexity, and its mastery is, as the subtitle implies, the key to success. The design of complex systems demands hierarchy - of organisations, of projects, of contracts, of documents. Hierarchy implies interfaces: if you split a system into three, you probably create three interfaces between the component subsystems. Interfaces in turn imply specialisation: someone develops the hardware; someone else, the software. Similarly, someone (the customer) writes the requirements specification, while someone else (the developer) tries to meet those requirements. This, like the prime contractor - subcontractor relationship, consists of a customer and a supplier: the marketplace reaches right into the core of system engineering.

The book therefore covers a startling breadth of subjects, but always with the same practical vision and with the same conceptual tools. The first few chapters broadly follow the European Space Agency's now-classical PSS-05 software engineering standard life-cycle phases: user requirements, system requirements, architectural design, integration (of subsystems) and verification, management.

(Requirements are involved in every one of these phases.) Once the reader is grounded in the basics, the next chapter discusses how to tailor the simple life-cycle just presented. A tell-tale section entitled 'smaller systems' gives the game away: the systems in the authors' minds are a great deal larger than the PC 'systems' beloved of advertising copywriters.

The second part of the book (chapter 8 onwards) starts by looking at more realistic life-cycles, based on the management of risk: when is it sensible to go ahead with something? The answer is, when success can be assured even if the bad risks materialize. That can only be guaranteed if the risks have been quantified. Concepts of requirement priority and benefit, risk, and cost loom much larger in the marketplace than technical issues.

The remaining chapters examine management in multi-level projects (hierarchy again), software and systems, prototyping (to control risk), information modeling, projects and the enterprise, a chapter on how to improve and a summary.

Each chapter consists of a double-page title/table of contents, overlaid on some crisp pencil artwork on the theme of engineering progress (from Leonardo's hang-glider to an agile jet). The text is broken up by plenty of simple flow diagrams illustrating life-cycles, trade-offs, business processes and information models, as well as short summaries of what the most important system documents should contain. Key points are highlighted or bulleted within the text. The chapters end with a page or two of realistically tricky exercises: the answers cannot be coded in C.

The helpful appendices include a list of websites: Systems Engineering comes with its own website which contains pointers to several related sites, and itself includes 'proposed' answers to the exercises which end each chapter. Students will find the glossary helpful and comprehensive. There is an extensive list of very varied references, and a detailed index. This book is a carefully worked out description of the process of developing any large, complex, and risky system. The book can also be read as a polemic: an impassioned plea for the discipline to graduate from its narrow roots, whether in academia or in quality control. The concluding paragraphs make it clear that system engineering is a human process, a 'game' in which there are losers as well as winners, something that can be played well, and that absolutely must be played better to limit the risks and losses that are still all too common....

The book will be of interest to several quite different communities: in particular development managers, clients having large systems developed, and students of system and software engineering will all find much that is of interest here. The book may also be a useful supplement (or perhaps an antidote) to the academic perspective on RE. Everyone should have access to a copy.

My Old french teacher gave me this book to read when i was about 14. He was of the opinion that reading helped improve concentration - he was right. The book, i do not think, would appeal to the average reader today, it is very long and heavey going - but not taking anything away from the writer - it is exquisitly written. However, there is a part in the book, i think it is a father telling a son a story, or something like that and it will go with me to my grave. It's about an adventurer who, once he has summeted one mountain, moves on to the next and when he has traversed one desert looks for another, and so on. He is never content unless he is moving, seeing new things and having new exoeriences, but then he runs out of mountains to climb and forrests to explore. I will not give anymore away except to say that i would read the book again - just for that one little story.

Shortly before Richard Jefferies first became ill he wrote two children's books, Wood Magic and Bevis, published in 1881 and 1882. The latter has been widely regarded as a classic boys' book and, based on Jefferies' own childhood at Coate, it follows the adventures of two boys, Bevis and Mark. They first 'discover' a large lake close to their home which they imagine to be a vast inland sea surrounded by a jungle inhabited by savages and wild beasts. After re-fighting the Battle of Pharsalia (between Julius Caesar and Pompey) with their friends, Bevis and Mark build a raft and cross to an island in the lake. Equipped with a few provisions and their own home-made shotgun, they live among nature for several days, learning the arts of survival and much about themselves in the process. Bevis is a celebration of the vigour and freedom of a childhood spent in the countryside, 'where there was magic in everything, blades of grass and stars, the sun and the stones upon the ground'.

This is a collection of essays which compare [homosexuals] in the US with those in Latin America. It looks at male homosexuality from a historical, pre-colombian, and tribal perspective as well. Murray is an erudite anthropologist and therefore does not fall into the loopholes in scholarship that many white men who "study" homosexuality in Latin America have. The author is a bit of an essentialist and that may rub constructionists the wrong way. Of his books on international male homosexuality, this is the best one buy far. I think every [homosexual] Latino who wants to know their own [homosexual] Latino history should own a copy.

There are some excellent books on male homosexuality in particular sites (Hector Carrillo and Joseph Carrier on Guadalajara, Mexico; Richard Parker on (Rio) Brazil; Manuel Fernandez on (San Pedro, Honduras)) but this collection ranges much more widely, including material on indigenous cultures as well as the dominant machista one that varies only slightly from Texas to Tierra del Fuego, and incipient "modern gay" homosexuality.

About half the chapters are by Stephen Murray, who has considered reports from many societies and done fieldwork in Mexico, Guatemala, and Peru. He is very critical of the romantic view of "tolerance" ("anything goes"/ "there's no sin south of the border") but includes chapters by the two main purveyors of that view (Paul Kutsche and Richard Parker). The book contains a multiplicity of scholarly views and data ranging from the usual literary texts to ethnography and survey research on sexual behavior of males who have sex with males in Latin America.

These are the proceedings of a science conference. The book contains a great many separate papers by specialists in not all that closely parallel fields. This is a book for libraries and specialists only.

In a recent past times, the knowledge about the organisms was based upon morphological characters. They were agruped or separeted by yours diferences or similarities. Today, the morphological features yet posses a great amount, but the molecular data about the organisms in general sense, and the plants in a specific vision, bring to discussion a new view about the plant organization. The Hollingsworth et al. book's brings to botanical community, the most recent concepts about plant phylogeny and evolution. It serve to all botanists that wish maintain up-to-date in general plants systematics

I found this book highly intriguing. I could somewhat relate to this novel because I am a college student myself. I am interested in crime novels so I found myself doing my own research on Richard Herrin. Herrin was released early from prison in 1995 when he was due to be released in 2003. His prison facility cannot release information where he is now leaving. This is pretty scary. Let's just hope nothing triggers him to do an awful crime like what he did to Bonnie that summer of July 1977. Where are you Mr. Herrin or shall I call you Mr. James?

This book was about Richard Herrin, who at 24 murders his 20 year old girlfriend, Bonnie Garland. This crime was especially shocking because they were students at Yale, and Bonnie came from a upper-class family and a nice community. The crime was brutal, (he smashed her skull with a hammer) and in my opinion, Richard Herrin should have recieved life in prison for the murder. Because this was a "high society, high profile" case he got much less. A good book!

Richard Bradley hits us with a brick of facts, and when we awaken we find the truth of the last 40 years. We learned from our recent President that along with getting this job, one must lose his privacy. Mr. Bradley show us that every President must also lose their humanity. JFK the great king? The evil Richard Nixon? Wake up and smell the coffee?

Richard Bradley serves it up piping hot!

Every american that watches those Sunday Washington talk shows should read this book.

Richard Price does an wonderful job touching on the theology of Bishop Augustine, as well as giving a simplistic introduction to the Saint.

Augustine of Hippo wrote some of the most influential Christian doctrine, but it was, and is, very difficult reading for the layperson.

This book puts forth Augustine's difficult topics like Original Sin, Relations within the Church, and the Trinity in an easily read format. The book is dry at times, but is still a most enlightning read.

If you are looking for a beginner book on Saint Augustine of Hippo, or if you are looking for a brief review of this Holy Doctor of the Church, than this is a very good resource.

Finally, a complete, comphrensive FIELD guide to the birds of India! Gone are the days of hauling 2 or 3 hardcover bird books to the subcontinent just to be able to identify relatively common species. The drawings in this book are excellent, the descriptions very detailed, and the range maps very helpful. My two criticisms are that birders familiar with the common names in Salim Ali's "The Book of Indian Birds" will be confused with the revised nomenclature in this guide (based on the Inskipp's Indian Checklist); some changes are relatively minor, while others are so dramatically different (and frankly puzzling) that cross-referencing is a chore. The second involves the seperation of many of the range maps from the plates and descriptions, sometimes by many pages. This was due to the large number of species featured on some plates- there just wasn't enough room for the maps also. A better strategy might have been to put them all in the back of the book. But the benefits of this book far outweigh the shortcomings- my next trip to India promises to be more rewarding and productive bird-wise (as well as easier on my back)due to this excellent and overdue field guide.

This is a quite comprehensive book. The authors cover a wide variety of insightful information and research in the child welfare field. Very good for anybody who will be working in a public child welfare setting or conducting research in this area. As with most academic reading, it tends to be a little dry. And, because there is so much information, sometimes it doesn't flow very well.

I inititally bought this text in my second year of medical school. It was both an exceptionally detailed text and also a good reference on a wide variety of subjects. I have continued to use it into my surgical residency and expect to do so until I finish. My only detractions are that on occasion it is too densely packed with information, and that the section on peptic ulcer disease and the surgical treatment of the same is a little dated. Otherwise, any topic that a student needs to know about on a general surgical service is _well_ covered by this text.