Pattern-Oriented Software Architecture Volume 1: A System of Patterns

Amazon.com

Pattern-Oriented Software Architecture: A System of Patterns looks at how patterns occur on three different levels--in software architecture, in everyday design, and in idioms (which describe how a particular design pattern is implemented in a programming language like C++). This synthetic approach is a little theoretical at times, but the authors also present over a dozen patterns and provide real-world examples wherever possible.

For architectural patterns, the authors look at the Layers pattern, used in operating systems such as Windows NT and virtual machines. They also consider Pipes and Filters, which process streams of data. (This pattern, the authors point out, is a lynchpin of Unix.) Their Blackboard pattern shows how a complex problem, such as image or speech recognition can be broken up into smaller, specialized subsystems that work together to solve a problem. (For recognizing words from a raw waveform input, a Blackboard approach might have separate processes to find phonemes, then words, then sentences.)

This book also looks at today's distributed systems in considering the Broker pattern, which is used on the Internet and in Microsoft's OLE technology. This section also presents several powerful patterns for building effective graphical user interfaces, such as Model-View-Controller.

The authors define several well-known design patterns, such as the Proxy and Command patterns, and also basic, far-reaching patterns, such as Whole-Part and Master-Slave, which are widely used throughout computing. Their survey ends with a discussion on the way objects can communicate (using such patterns as Forwarder-Receiver, Client-Dispatcher-Server, and Publisher-Subscriber), which many developers will recognize as familiar patterns, but are codified here as "official" patterns. The book then discusses some idioms in C++ and a more far-reaching role for patterns in software design and architecture. By fitting patterns into traditional software engineering practices, the authors of Pattern-Oriented Software Architecture successfully argue that the role for patterns will only continue to diversify and enrich tomorrow's software engineering tools and methodologies. --Richard Dragan

Book Description

Pattern - Oriented Software Architecture A System of Patterns Frank Buschmann, Regine Meunier, Hans Rohnert, Peter Sommerlad, Michael Stal of Siemens AG, Germany Pattern-oriented software architecture is a new approach to software development. This book represents the progression and evolution of the pattern approach into a system of patterns capable of describing and documenting large-scale applications. A pattern system provides, on one level, a pool of proven solutions to many recurring design problems. On another it shows how to combine individual patterns into heterogeneous structures and as such it can be used to facilitate a constructive development of software systems. Uniquely, the patterns that are presented in this book span several levels of abstraction, from high-level architectural patterns and medium-level design patterns to low-level idioms. The intention of, and motivation for, this book is to support both novices and experts in software development. Novices will gain from the experience inherent in pattern descriptions and experts will hopefully make use of, add to, extend and modify patterns to tailor them to their own needs. None of the pattern descriptions are cast in stone and, just as they are borne from experience, it is expected that further use will feed in and refine individual patterns and produce an evolving system of patterns. Visit our Web Page http://www.wiley.com/compbooks/

Customer Reviews:

Amazing book.......2006-09-06

This book uses an easy way to explain system patterns. I think every software developer has to read this book; it's a nice reference to help software architects doing a well-done job. Another great reference that you may have in your list of references is the classical book "Design Pattern", also at Amazon.com.

#2 best book about patterns ? yes........2005-11-20

A lot of the reviewers have said that this is the #2 best book about patterns : just trust them. I have bought it with the hope to learn more about patterns, finally it has given me a larger point of view about the subject and has improved a lot my creativity during software designing processes.

If your new to patterns just read the GoF, then buy this one. I think you will then have a nice knowledge about the subject.

The second best pattern book.......2005-10-22

Second best isn't bad when the #1 book changed forever the way software architecture is talked about. GoF is not only well-written, but it covers all the basic, most-used patterns. Everybody thereafter is going to have to either re-hash GoF, criticize it, or come up with new patterns which are not as fundamental.

This book is full of new patterns, and fortunately they are good ones: Command, Broker, Layers and worth the price of the book in itself Presentation-Abstraction-Controller.

PAC can be seen as a generalization and extension of Model/View/Controller. The Abstraction is the domain-specific part of the architecture, effectively the Model. The Presentation exposes the Model in some interesting way, either as a user-interface in which case it is a View, or as an API, in which case the Presentation becomes a new Abstraction used by the next level up. The Controller is left with the job of coordinating the Presentation and the Model. The key to the pattern is that PAC agents can be built up into layers with the Presentation API of each lower agent creating a higher abstraction for the next level. Thus PAC becomes MVC for all or your architecture, not just the UI.

The book goes into this at length and adds useful discussion of MVC. Highly recommended.

Not concrete enough.......2005-07-07

First of all, you need to understand the patterns in the gang of four book before you attempt to read this one. They talk about them all over the place without explaining them. That's a warning, it didn't affect my review.

The major thing I don't like about this book is the abstractness with which they talk. They give you a high level description of a pattern and leave you with that fogginess.

I think the examples were poorly chosen. I would have prefered to have examples that are only as complicated as they needed to be. Unfortunately the book uses examples like, "We're going to make a voice recognition application" or "We're going to make an OS that can run applications that were built on Unix or WinNT or Linux". I think the intent was to have some real-world-I've-been-working-for-six-years examples... it would have been smarter to put the real world examples in a separate chapter and keep the design pattern explanations simple.

Also, I hate the diagrams. They should have just copied the diagrams in the GoF book! Instead they chose these diagrams that give less info and IMO are downright ambiguous in some situations. Another thing the GoF book does is have 2 separate diagrams, one that's a (simple) real world example and another that's a diagram of the actual pattern. This book only has the diagram of the actual pattern.

I disagree with those that say this book is better than the GoF book. I think what they like is the material covered. Material aside, the GoF book presents the information in a much clearer way. That's why I prefer the GoF book over this one.

Clear and wide-ranging.......2004-06-25

This is an unusual book in the pattern genre. It presents a number of patterns, categorized by archtiectural level. That's just the first part of the book, though. The third of the book is about the process of using, relating, collecting, and distributing patterns.

Only chapter 2 really addresses patterns for the strategic, architectural level of a software system. It does a very adequate job, using a variety of notations, examples, and analysis steps. This book is from 1996, so time has changed our view of some patterns. "Reflection," for example, has become pervasive in applications based on plugins and software components. It is also a fundamental API in the major langauges (Java and C#) released since this book was published - perhaps reflection should be downgraded to an "idiom". That's just nitpicking, though, since reflection is even more important now than when the book was written.

For contrast, the authors present additional design patterns (including some from Gamma's book) for use at tactical design levels. They also discuss idioms patterns that typically involve just a few lines of code within on function. The contrast between the three different levels of implementation and design gives a useful discussion. The authors also present a weak chapter on "systems" or "langauges" of patterns The discussion is OK as far as it goes. The weakness is in what it omits. After reading this brief chapter, the programmer has very little practical information about choosing patterns from some library for some task. The poor programmer has no information at all about how to link patterns together, and that's a real stumbling block for beginning pattern users.

The final section of the book is really sociology. It's about the pattern community, what that community is for, and how to be a working member. I find the discussion un-helpful, but I expect opinions to differ.

Book Description

Recorded history is a finely-woven magic fabric of intricate lies about events predating the sixteenth century. There is not a single piece of evidence that can be reliably and independently traced back earlier than the eleventh century. This book details events that are substantiated by hard facts and logic, and validated by new astronomical research and statistical analysis of ancient sources.

Customer Reviews:

Calculations are only as good as your numbers.......2007-08-03

Yes, we can all agree that mainstream history is nearly 100% BS due to politics, economics, ego, problems with dating techniques, and various conspiracies. Agreed. But, I've been researching the distinct possibility that human history (in terms of civilizations) are much more ancient than we've been told, so coming across this book was very interesting to me. I wondered how Fomenko could be wrong (if at all) because he is very persuasive in his presentations. Then it dawned on me. If at previous times in prehistory, due to the various catastrophies that are well documented (comets, asteroids, planetary disruptions, plasma discharge, pole reversals, etc) the Earth was in a different position in relation to the sun, different tilt on its axis, different orbit, different rotation (in terms of velocity and DIRECTION), and the continents were in different positions, then would this not cause the ancients to see the sky (constellations) differently? In other words, is Fomenko making erronious assumptions about the physics of the Earth in pre-history, which then corrupt his data with regards to dating the relevant astrology? The last event to seriously disrupt our planet occured roughly 3500 years ago, according to other good researchers, so is it possible Fomenko has been confused by this? The vastly different physics of our planet in the not so distant past may explain this confusion, which is not to say the "mainstream" version of history is correct; on the contrary. I am not an expert in these fields, but wanted to see if this idea could spark discussion.

Pants on fire?.......2007-07-19

Will people ever read before spamming? Yes, Jesuits could not rewrite world history alone, they had help. Anyway, Dr Prof Acad A.Fomenko does not point to jesuits as the driving force of world wide history manipulation in published volumes 1,2,3;, actually he barely mentions the poor devils. Check it with 'Search inside' feature, please. China is rarely mentioned either, in fact, Dr Fomenko is completely eurocentric. Right, his theory contradicts all mainstream schools of history, because in their actual state they are all built on blatantly erroneus chronology. You don't need a mysterious cabal (conspiracy) to falsify history, the falsification is its modus operandi. It is inherent to history(ians) to falsify (distort) events, as it is inherent to humans to boast as it is inherent to power (authority) to legimize itself by referrring to glorious past made to its own order. Dr Prof Fomenko and team have identified scores of instances of such manipulation in Russian, European, etc.. history, and delivered valid statistical proof thereof. His own 'reconstruction' is completely another story. Forget c14 as a valid method of dating. W.Libby has initially discovered a brilliant method of INDEPENDENT dating. Too bad, c14 method has become a joke after a forced marrige with dendrochronology with consensual chronological scale inbuilt. Radiocarbon method can't stand blind tests, but is so very productive as a rubberstamp.

Accepted History & Chronology Must Be Changed. .......2007-04-09

There is no doubt that history as most know it is a sham, & institution's version of History both University & Church is fradulent & inaccurate. Everything was established with an agenda, The real "Dark Ages" are now when we have access to incredible amounts of information past authorities & more important 'common folk' didn't have but our institutions & educators are slow to evolve because of what has ignorantly & arrogantly been taught for too long. This is on many subjects not just Chronology.

For anyone to question "Why would a Mathematician have anything credible to say of History?" The answer is from Dr. Fomenko's preface in the book: "It would be worthwhile to remind the reader that in the XVI-XVII century Chronology was considered to be a subdivision of Mathematics." These volumes could possibly be some of the most important works to date & should be read by everyone with an interest in History, especially professors & educators who have a duty to the public. I have read both books & must say that 'Chronology 1' has some very eye opening & revolutionary information. Even if these volumes are part true the implications are profound & opens the doors to further investigations & questions which must be done. I speak several different lanquages & must say the logic Dr. Fomenko uses with "inflection" of words & words being read from left to right in one region & right to left in another then written backwards, the removal of vowels & get down to basics of words, or different cities & locations having the same name etc. is correct. Vowel usage has always been optional & varied, actually complicating linquistics & study. The first thing one has to understand is that words never had a fixed spelling in history like we do now, the spelling of words was mutable & regional, as well as names & titles of people were vast, varied & changed, NOTHING WAS FIXED or understood linear. Matters of Life & Death as well as financial profiteering yesterday & today were & are made with ignorant, illogical & conspiratorial views of history & reality, it's time people get closer to the Truth & society collectively grow up.

Very Interesting.......2007-03-07

It is a good proposal and I believe it will mature into something even better in the future. I think it deserves to be read.

History as Science Fiction.......2007-01-10

Anatoly Fomenko has written a very intriguing book, full of pictures, charts, and computer 'proof' of his thesis: backwards of AD900 we don't really know what happened or when. Between AD900 and AD1600 there is more certainty, but there is still a lot of fuzzy ground, and things don't get reliable until we get past the 1600's where the printing press made it very difficult for the perpetrators of this timeline manipulation to change anything that had been committed to print. The Dark Ages did not happen. Books were burned for a reason. One organization has doubled the actual length of its existence by expanding the real chronology. Read why.

I had always wondered why Christ died about AD33 and yet men waited until the 11th century to form the Knights Templar, the Cathars, etc and go after the Holy Land by force. Why the 1000 year gap? Turns out there wasn't more than a 10-12 year gap and he proves it using astronomy. This also implies that the planet is not as old as we have been told, and current Christian and other creationist scientists are already championing that idea without being aware of Fomenko's book. The two groups, creationist scientists and the Russian mathematical analysts corroborate each other. Fascinating.

Of course, all this flies in the face of what we have been told traditionally is the 'proper' chronology of western civilization, and most readers will experience 'cognitive dissonance' in reading this book. It means that our history going backwards from AD1600 becomes progressively more incorrect and unreliable until it cannot be trusted at all... in the space of 700-800 years.

Naturally, the curious, open-minded reader will want to know WHO did this, WHY, and did any of the events we think of as really ancient ever happen?
Dr. Fomenko is a respected scientist/mathematician at Moscow State University who has already answered these questions to the satisfaction of his initially skeptical colleagues. Most of them are now believers, a few still refuse to believe (the usual diehards), and of course the western press has ignored Fomenko's work -- for obvious reasons when you read the book. The ones who perpetrated this chronology ruse have a lot to answer for. They are still with us. That's why this book is a well-kept secret.

I gave the book a 4-star rating because I was unable to check out some of his claims; those I checked were as he said. But if even 1/3 of his claims are true, this punches a big hole in what we think is our history, the meaning of western civilization, our educational process (for repeating the ruse as gospel), and the trustworthiness of the organization that perpetrated this ruse, well-intentioned or not.

This book relates to current research into a Young Earth paradigm, to John Keel's discoveries about our planet, and Fr Malachi Martin's insights (in his now out-of-print books). We are indeed sheep who are manipulated and kept ignorant -- for a reason. While knowing what these men have to say may be the "booby prize" (as in: 'what can you do with this knowledge?'), it will provide interesting reading. Didn't someone say: "...and the Truth will set you free."?? For you to judge if this book contains the truth.

Pattern-Oriented Software Architecture Volume 2: Patterns for Concurrent and Networked Objects

Average customer rating:

Essential reading for programmers in its domain
Simply the best
Good information badly written
Good Patterns Hidden in Excessive Verbiage
Size does matter

Pattern-Oriented Software Architecture Volume 2: Patterns for Concurrent and Networked Objects
Douglas Schmidt
Manufacturer: John Wiley & Sons
ProductGroup: Book
Binding: Hardcover

Parallel Processing Computers | Hardware | Computers & Internet | Subjects | Books

Design & Architecture | Hardware | Computers & Internet | Subjects | Books

General | Certification Central | Computers & Internet | Subjects | Books

General | Computers & Internet | Subjects | Books

General | Medicine | Subjects | Books

All Amazon Upgrade | Amazon Upgrade | Stores | Books

Computers & Internet | Amazon Upgrade | Stores | Books

Medicine | Amazon Upgrade | Stores | Books

All Titles | Qualifying Textbooks - Fall 2007 | Stores | Books

Computers & Internet | Qualifying Textbooks - Fall 2007 | Stores | Books

Medicine | Qualifying Textbooks - Fall 2007 | Stores | Books
Similar Items:

ASIN: 0471606952

Book Description

Designing application and middleware software to run in concurrent and networked environments is a significant challenge to software developers. The patterns catalogued in this second volume of Pattern-Oriented Software Architectures (POSA) form the basis of a pattern language that addresses issues associated with concurrency and networking.

The book presents 17 interrelated patterns ranging from idioms through architectural designs. They cover core elements of building concurrent and network systems: service access and configuration, event handling, synchronization,

and concurrency. All patterns present extensive examples and known uses in multiple programming languages, including C++, C, and Java.

The book can be used to tackle specific software development problems or read from cover to cover to provide a fundamental understanding of the best practices for constructing concurrent and networked applications and middleware.

About the Authors

This book has been written by the award winning team responsible for the first POSA volume "A System of Patterns", joined in this volume by Douglas C. Schmidt from University of California, Irvine (UCI), USA.

Visit our Web Page

Customer Reviews:

Essential reading for programmers in its domain.......2006-08-11

I recently finished reading Pattern Oriented Software Architecture Vol 2: Patterns for Networked and Concurrent Objects. Believe it or not, it took me just one night to read this book cover to cover. The main reasons behind this are that a) the techniques described in this book are already well known to people working in a company that deals with some of the largest network applications in the world, and b) the book itself is very well written.

The really nice thing about this book is the way in which the patterns are presented. I was thoroughly impressed with how, for each pattern, the authors start with describing the problems and constraints. The solution is then presented with a static, object view. This is follwed by a dynamic view with a UML sequence diagram that shows how the pattern works at run-time. This is followed by detailed textual description of the steps required to implement the pattern, along with code snippets. Lastly, there's a list of real-world software implementations that have used the respective patterns, and one example from real life. The real life example is on occasion so instrumental in understanding the purpose and/or workings of the pattern that it could make you exclaim, "a-ha!".

Many of the patterns, like Wrapper Facade, Scoped Locking Idiom, Thread-safe Interface, Half-Sync/Half-Async, Leader/Followers, etc. are easy to follow and likely already known to people dealing with networked applications. The most insane patterns that I found were Proactor (for asynchronous demultiplexing and handling of events) and Interceptor (for event based access to the internals of a framework in a safe manner). They have the potential of making you start hating frameworks! About half of the patterns were new for me.

Simply the best.......2006-03-10

If you really want to understand concurrent networked systems, this is the book. It codifies things that have only been known as "black magic" in the past. I have used these concepts in code that I have written, and the results are amazing. It is quite focused on ACE, so you will get the most benefit out of it if you use ACE, but the concepts are presented generally so that using ACE is not required.

Good information badly written.......2005-04-08

This book summarizes some important distributed systems patterns researchers have identified in recent years. In that sense it is a necessary contribution to the software engineering literature.

However, the examples are at times unclear and the author does not always motivate them convincingly. From a technical writing perspective, the passive voice plagues this book from start to end, forcing readers to stop and reread sections to make sense of convoluted prose.

Good Patterns Hidden in Excessive Verbiage.......2004-11-22

First, the patterns in this book are very good. It was nice to see some coverage of low level networking patterns. As an experienced programmer, I was vaguely familiar with many of the patterns already, but it is really helpful to see the lines drawn in the sand, to hear why the authors chose to break things up as they did, and to understand the ramifications of the patterns in greater detail (eg, their clarification of the difference between Observer and Interceptor was quite helpful). I even got to learn some new patterns! (The Leader / Followers pattern was new to me.)

That said, the writing style about drove me BANANAS! I have never lost my place in a sentence when reading a book so many times. I must have read every line twice. Look, I'm a computer geek - I LOVE dense technical books, but this is something else. It's like reading Shakespear, or Charles Dickens. The authors must have been paid by the word. The specific implies the general! Have mercy! I don't need the difference between an interface and its concrete implementation belabored every time it comes up (and in a patterns book, believe me it's often!)

Size does matter.......2004-10-27

Big problems really are different from small problems. Solutions to small problems rarely scale well - the big solution often has to be different in kind from the small one. This book is about solutions to big problems, the kind that may involve hundreds of servers and thousands of clients, or more.

This gives a clear, thorough description of about 15 design patterns that work well large, performance-sensitive applications. Some (like "Scoped Locking") depend on the specific semantics of C++, but may work in Java or C# if used carefully. Others are highly specialized implementations of more general patterns. The "Leader/Followers" pattern, for example, is a one implementation of the "Object Pool" pattern (see Grand, 'Patterns in Java', 1998) used for a particular purpose. On the whole, the authors did a fair job of relating these patterns to others in the literature. I was only occasionally frustrated that I did not have that literature at hand when reading this.

The authors go into extreme detail in describing implementations based on each pattern, something sure to help some readers. There is often a C++ implementation as well, at least in skeletal form. The descriptions go on at great length, averaging almost thirty pages of discussion for each pattern. More isn't necessarily better, though, and some descriptions would have benefitted from a slimming program. I would also have been grateful for more differential discussion - comparing patterns, in terms of the specific decision critieria that argue for one pattern vs. another.

The back matter in this book takes about 100 pages - glossary, bibliography, and indices by pattern, topic, and author names. Very helpful stuff. If it's going to be that long, however, a sentence or two about the more important references would have added little bulk but lots of value to the bibliography.

The book is a good one, giving lots of practical information about the patterns it discusses. It's aimed at an experiecned reader, someone already conversant with OO programming, patterns, and at least a taste of problems bigger than classroom exercises or solo projects. A bit less mass chosen a bit more carefully would have improved this book, but it's still a worthwhile addition to my technical library.

//wiredweird

Software Product Lines : Practices and Patterns

Average customer rating:

An Impressive book
The Product Line Engineering Bible
very good book
Great book if you already know Software Product Lines, but..
If you're already doing this, a great book; otherwise, not

Software Product Lines : Practices and Patterns
Paul Clements , Linda Northrop , and Linda M. Northrop
Manufacturer: Addison-Wesley Professional
ProductGroup: Book
Binding: Hardcover

General | Architecture | Professional & Technical | Subjects | Books

General | Computers & Internet | Subjects | Books

General | Software | Computers & Internet | Subjects | Books

All Titles | Qualifying Textbooks - Fall 2007 | Stores | Books

Computers & Internet | Qualifying Textbooks - Fall 2007 | Stores | Books

Professional | Qualifying Textbooks - Fall 2007 | Stores | Books
Similar Items:

ASIN: 0201703327

Customer Reviews:

An Impressive book.......2007-02-12

This is a very good book on product line development. I learned a lot, especially in the area of design patterns and architectures. I would definitely recommend it.

The Product Line Engineering Bible.......2005-12-20

This is the leading authority on Product Line Engineering (PLE). No other book comes close. This book breaks down the three PLE practice areas of Software Engineering, Technical Management, and Organizational Management and describes each in great detail. The book provides guidelines on each area and how to achieve institutionalization of your PLE process.

The book has a great patterns catalog, Software Product Line Practice Patterns. The catalog includes The Essentials Coverage pattern, Each Asset pattern, Build pattern, Product Parts pattern, Assembly Line pattern, Monitor pattern, Product Builder pattern, Cold Start pattern, In Motion pattern, Process pattern, and Factory pattern.

If you are involved with Product Line Engineering or Software Factories at all, this is a must have. You cannot do without it. If you aren't involved with Product Line Engineering or Software Factories, this is still a great read because it covers a process that should be implemented on every project. Implementing PLE makes a project reusable, predictable, maintainable, and manageable. Overall it adds measurable metrics to all the assets of a project.

very good book .......2005-09-26

simple to understand language. Nice diagrams and the content is really arranged in a nice way

Great book if you already know Software Product Lines, but.........2004-05-21

If you have the concept of software product lines down, this is a great book, but if not you can easily get lost or confused, so it becomes difficult reading. If you want to explore software product lines, buy this book, then while you are waiting for the book to arrive read the website http://www.softwareproductlines.com to get up to speed on the concepts.

Software product lines will become a must whether you develop enterprise software or embedded software. This is so much more than we ever discussed about software resue.....

If you're already doing this, a great book; otherwise, not.......2003-12-22

So, if you've already made the decision to go with software product lines, this is an excellent book. It's got a huge amount of reference material, is well-edited, and clearly has the benefit of a lot of practical experience.

Unfortunately, if you're debating with or just want to learn about software product lines, this book isn't for you. I didn't see a single example of when software product lines are *not* appropriate for a set of work that needs to be done and, in general, this just assumes that you already have the sort of work that fits this model and dives right into the details. Also, the "29 practices" are spread over just under 300 pages, and make it hard to understand the big picture. It would've been nice to see even one-page descriptions of the patterns in context to be able to pull it all together more easily.

Average customer rating:

Not the Full Monty.

Vulcans Should Read This Book

Question your assumptions and challenge what you think you know

Should Have Been Better Than It Was

Required for all psychology students!!!

How We Know What Isn't So: The Fallibility of Human Reason in Everyday Life
Thomas Gilovich
Manufacturer: Free Press
ProductGroup: Book
Binding: Paperback

Logic & Language | Philosophy | Nonfiction | Subjects | Books
Development | Child Psychology | Psychology & Counseling | Health, Mind & Body | Subjects | Books
General | Psychology & Counseling | Health, Mind & Body | Subjects | Books
Social Psychology & Interactions | Psychology & Counseling | Health, Mind & Body | Subjects | Books
Cognitive | Psychology & Counseling | Health, Mind & Body | Subjects | Books
Cognitive Psychology | Behavioral Sciences | Professional Science | Professional & Technical | Subjects | Books
Cognitive Science | Behavioral Sciences | Professional Science | Professional & Technical | Subjects | Books
Cognitive Psychology | Behavioral Sciences | Science | Subjects | Books
General | Behavioral Sciences | Science | Subjects | Books
All Titles | Qualifying Textbooks - Fall 2007 | Stores | Books
Nonfiction | Qualifying Textbooks - Fall 2007 | Stores | Books
Professional | Qualifying Textbooks - Fall 2007 | Stores | Books
Science | Qualifying Textbooks - Fall 2007 | Stores | Books
Similar Items:

Why People Believe Weird Things: Pseudoscience, Superstition, and Other Confusions of Our Time

Why Smart People Make Big Money Mistakes And How To Correct Them: Lessons From The New Science Of Behavioral Economics

The Psychology of Judgment and Decision Making

Don't Believe Everything You Think: The 6 Basic Mistakes We Make in Thinking

The Winner's Curse

ASIN: 0029117062

Customer Reviews:

Not the Full Monty........2007-10-08

My main interest in this subject lies in a search for answers to the question of why perfectly sane and intelligent people put faith in God above reasoning. Why do so many choose to believe so strongly with so little evidence? Unfortunately Thomas Gilovich absolutely refuses to cast light on religious delusions, but mainly states that theists and atheist "both need to develop the habit of thinking more broadly." Not helpful at all and sort of a faux pas to include this lame comment in the book.

Never the less, the book is a good and thorough introduction to the subject of our penchant for faulty reasoning, but also somewhat dry and repetitive. I wasn't exactly rolling on the floor with laughter, which might be too much to ask; but the many examples and anecdotes could be presented with greater vigour without harming the seriousness and validity of the study.

May I recommend: "Don't Believe Everything You Think: The 6 Basic Mistakes We Make in Thinking" by Thomas E. Kida, which is very similar in content and reference a lot of the same sources, but is also more playful and entertaining.

Vulcans Should Read This Book.......2007-06-02

Hello, my name is Mr. Spock. You may know me from the TV series StarTrek. For years I've been tormented by the illogic of humans. Let's face it, Captain Kirk and Dr. McCoy are not the sharpest phasers in the intergalactic utility belt!

Then I read Gilovich's book. It helped me realize that humans are most illogical in times of uncertainty when there is no clear trend and not enough information upon which to make a good decision. In such cases, especially when a decision must be made, logic is not going to be of much help. As a result, people develop simple, but often inaccurate, theories to help them through painful states of indecision. The decision may be good or not, but at least a decision has been made, and that alone provides comfort.

Unfortunately, humans also have a strong desire to justify their theories, and this is where they get into trouble. Data that proves the theory is retained and emphasized, and data that doesn't is heavily discounted. So the theory takes on a life of its own despite the facts, which admittedly may themselves be ambiguous at times.

The bottom line is that this book gave me a greater understanding of humans. As a result, I feel more comfortable communicating with them, and just being around them in general. If you're part Vulcan like I am, or even a logical human, I strongly suggest you read this excellent book about human thinking and decision making. You won't be sorry. Live long and prosper!

Mr. Scot, I have completed my Amazon review, and have obtained the Chinese food and pornography magazines the Captain has requested. Please beam me up now.

Question your assumptions and challenge what you think you know.......2006-08-24

This book provides a well-organized survey of issues that limit our reasoning abilities:

- Our misperception of random events, as in the "clustering illusions" that lead us to believe in the hot hand, for example.

- Our misunderstanding of statistical regression, which, for instance, affects our perception of the roles of reward and punishment in education.

- Our tendency to seek confirmatory information, as in the justification of our choices.

- Our inability to see what could have happened under different circumstances, as in self-fulfilling prophecies (e.g. a negative first impression or the presumed insolvency of a financial institution).

- Our own biases that make us expose inconsistent information to more critical scrutiny than consistent information.

- Asymmetries that distort what we recall and, thus, what we take into account to evaluate the validity of beliefs (as in multiple endpoints situations or one-sided events).

- Our tendency to believe what we want to believe (specially about ourselves), as if beliefs were possessions.

- The distortions present in secondhand information (a.k.a. sharpening and leveling).

- The influence of what we think others believe (and also of the inadequate feedback we often receive about that).

These limitations make us draw incorrect conclusions and bolster erroneous beliefs. Being aware of them helps us in distinguishing what we know well from what we only think is true. Just this is of utmost importance for thinking clearly. Could there be a better reason for reading this book?

Should Have Been Better Than It Was.......2006-07-29

Gilovich starts this book of with a real bang! After reading the Introduction, I thought this book would be really interesting and change the way I look at the world. He writes in a college-teacher tone that will not be approachable to those he most needs to reach. In other words, I really don't need a book to tell me to avoid holistic cretins, ESP, psychics, mysticism, and all that other garbage.

The first half of his book is concerned with a review of the psychology literature from the '70s and '80s on how people arrive at their beliefs. This is boring and somewhat like a set of lecture notes. The information in it is useful, but it could be summarized and edited. The second half of the book is devoted to why people shouldn't believe in the topics I mentioned above. Most people who read his book wouldn't even dream of subscribing to these beliefs, so the whole second half is pretty boring.

Gilovich finishes the book by telling us that psychologists are best at understanding the world and are the most perceptive professionals out there, bar none. While admitting that the core thought processes that lead to logical decision making come from hard science, Gilovich wants us to believe that the softies have perfected clear thinking about the world. He should have reread that portion of the book when he wasn't overheated and realized how silly it would sound to attorneys, physicians, scientists, and other thoughtful people.

Required for all psychology students!!!.......2006-06-21

This book is a contemporary classic that should be required reading in all psychology programs. As a psychologist, I am regularly appalled by how few trained psychologists know of the research discussed in this book, indeed, of decision science in general!! It only goes to show, there's scientific psychology (of which this book qualifies), and then, well, there's the other 99%...the crap, fluff, unsupported, unscientific, claims and practices that arise out of pseudo-scientific approaches, misinterpretations of data, and fallacious assumptions and conclusions. As an exemplar of what's good in a field rife with methodological manure and hocus pocus B.S. (e.g. psychotherapy, psychiatry, etc.), this book really shines. Read it and discover why some of psychology really is a science.

Building Application Frameworks: Object-Oriented Foundations of Framework Design

Average customer rating:

Good starting point but...
The number one guide for the development of O-O Software!
An essential three-volume reference on Application Framework
Great book for professionals in industry and academia
Excellent books to learn how to develop OOA Frameworks

Building Application Frameworks: Object-Oriented Foundations of Framework Design
Ralph E. Johnson
Manufacturer: John Wiley & Sons
ProductGroup: Book
Binding: Hardcover

General | Computers & Internet | Subjects | Books

General | Computer Science & Information Systems | New & Used Textbooks | Stores | Books

Object-Oriented Software Design | Computer Science & Information Systems | New & Used Textbooks | Stores | Books

All Titles | Qualifying Textbooks - Fall 2007 | Stores | Books

Computers & Internet | Qualifying Textbooks - Fall 2007 | Stores | Books
Similar Items:

ASIN: 0471248754

Book Description

Object Technology The first experience-based guide to building object-oriented frameworks Building Application Frameworks By providing reusable skeletons on which to build new applications, frameworks can save you countless hours and thousands (even millions) of dollars in development costs. Written and edited by some of the top names in the object-oriented programming world, this is the first complete study of building frameworks. Using examples drawn from successful implementations worldwide, it walks you through all the steps of a framework development project. Providing guidance on all key technical and business issues surrounding framework construction, it covers:
* Techniques for developing, integrating, and adapting frameworks
* Leveraging existing design and code
* Selecting and utilizing frameworks
* Tracking, controlling, and documenting framework development
* Maintaining, measuring, and controlling framework quality
* Training developers in the effective use of frameworks
* Evaluating frameworks and framework investments

Customer Reviews:

Good starting point but..........2002-05-30

For one that works on frameworks and tools almost every day, I'm one that understands the production of frameworks and the OO methodology very well - however I got this book on a recommendation for its rich content and ideas, but I was left dissappointed.

First of all, the book is more of an academic book. I have no problem with this as the Design Patterns book produced by the GoF was written in the same manner, but the language and tone could have more informal to make it a more enjoyable read for the working architect rather than the university student.

That not really being the real issue, there are many chapters in this book that are almost useless to read. I understand this book shouldn't be read from cover-to-cover (seeing as the chapters have hardly any real order to them - another bad point), but reading about a smalltalk framework for something so trivial and talking about it's significance for a hundred pages or so doesn't make me learn anything - simular to the Mythical Man Month. I'm sure these kinds of chapters or books even are an important, integral part of computer science and should be captured, but this isn't the book I'm afraid.

The chapters on example frameworks, although helpful, didn't tell the reader a lot of inforamtion. For instance, the Hypermedia framework was written as it was being told with an overview. Although the patterns and some driving design decisions were made, the actual purpose of the framework was unclear until the end of the chapter that I put in the missing pieces myself. The author wrote it like a review or an abstract to a larger case study - which doesn't help those that truly want to understand what's going on.

The chapters on formalizing and understanding frameworks, although I appreiciate the academic effort to describing frameworks, were useless reads as well. As an architect that has built many frameworks and continues to do so, their so-called "simplified model" couldn't even potentially describe half the frameworks i've built. For a book that is supposed to be the "definitive guide/reference" on frameworks, it most surely doesn't meet to the level of frameworks being produced in the enterprise today. Perhaps volumes 2 and 3 can clear this up.

Given all this, however, the book has some good chapters, albeit reviews and abstracts of white papers and other books. If you really want to start building frameworks, maybe this would be a good start, but I'd recommend Design Patterns: Elements of Reusable Software, Refactoring, EJB Design Patterns and many other books about advanced OO and designing software that focus on the "smaller" elements of producing frameworks instead. If you truely understand these works, learning how to build frameworks is almost trivial and you won't really need to read this book. Maybe I'm just smart too, I dunno - you decide.

Just my thoughts - hope that helps someone's buying decision.

The number one guide for the development of O-O Software!.......2002-03-04

Before the advent of frameworks (MFC, JDK, etc.) developing software systems of any size was hard, and large system development was close to impossible, with a harrowing failure rate. This book lights the way toward a future in which the development of large software systems can be thought of as a much more workable activity, one with a reasonable chance of success.
"Building Application Frameworks" is a book that has been designed to be extremely useful as a reference for experienced software developers or as a textbook highly suitable for a wide variety of graduate level courses in the Computer Science field. The book comes complete with well thought out question sections and a large variety of real world examples. I highly recommend it!

An essential three-volume reference on Application Framework.......2002-02-28

This three-volume reference is a good collection of articles that provide theoretical concepts and practical experience in designing, implementing, and documenting application frameworks.

Volume 1, "Building Application Frameworks", addresses several problematic topics crucial to the success of object-oriented application frameworks. It presents a complete reference on how to develop a good application framework and provides guidelines for dealing with issues related to application frameworks.

Volume 2, "Implementing Application Frameworks", illustrates the development and use of frameworks technology in several domains, such as business, artificial intelligence, agents, tools, environments, and system applications. It describes diverse application frameworks and discusses real-world experience.

Volume 3, "Domain-Specific Application Frameworks", provides valuable insight into successful application framework examples. All the material is presented in a practical, easy-to-understand manner.

I strongly recommend this three-volume reference for anybody planning to use the hottest technologies related to software reuse, frameworks, in the software development process.

Great book for professionals in industry and academia.......2002-02-28

I was quite impressed by the book as it spans a wide range of academic and industrial issues. As a matter of fact, I recommend Dr. Fayad's publications to my graduate students as well to professionals. His writing is clear, concise, inspiring and evocative.

Excellent books to learn how to develop OOA Frameworks.......2002-02-27

This book in conjunction with the books "Domain-Specific Application Frameworks: Frameworks Experience by Industry" and "Implementing Application Frameworks: Object-Oriented Frameworks at Work" are a series of three books that constitute a complete and necessary guide for the design and implementation of application frameworks. They are based on multiple academic and industrial contributors experience building a wide range of domain-specific application framework. These books are very easy to read and understand and you can learn from them not only what a framework and an application framework are, but also how to apply this technology to real world domains, like manufacturing, health care, distributed computing, real-time systems, simulation environments, ...

First book, "Building Application Frameworks: Object-Oriented Foundations of Framework Design" introduces application frameworks, their benefits and problems. It addresses all the fundamental concepts behind OO application frameworks and provides guidelines for OO application framework development. It is organized in eight parts. Part one provides a complete overview of OO application framework technology describing what is an application framework, what are the problems and benefits of application frameworks and how to use, develop and evaluate an application framework. Part Two presents some historical application frameworks and discusses some general guidelines to increase the reusability of application frameworks. Part Three describes how to build a framework analysing a concrete domain. The rest of the book provides all the necessary information to completely build an application framework. It presents all the concepts managed in framework development, which are the different development approaches, how to test the resulting frameworks, the problems derived from integration and a question sometimes forgotten but very important, the framework documentation.

Second book, "Domain-Specific Application Frameworks: Frameworks Experience by Industry" is focused in the experience of industrial and academic contributors in the development of OO application framework in different domains. Each chapter covers step by step the complete development of an application framework in manufacturing, distributed systems, real-time systems, telecommunication, multimedia, chemistry and data visualization domains. It includes the motivation developers founded to choose application framework technology, the problems they had to solve and the final solutions they developed.

Third book, "Implementing Application Frameworks: Object-Oriented Frameworks at Work", shows step by step how to implement application frameworks in different domains. It is organized in six parts covering examples about i) Business Frameworks with different examples in sales and administrative domains, ii) Artificial Intelligence, iii) Agent Application Frameworks, presenting interesting frameworks for speech recognition, neural networks and agents. iv) Specialized tool frameworks, v) Language Specific Frameworks, vi) System Application Frameworks, which present and analyse the application of OO frameworks in combination with other methodologies as component-oriented programming, language constructs or constraint programming and vi) Experiences in Application Frameworks. This last section is very useful because analyse the lessons learned using the application framework technology.

Average customer rating:

Good Gems

CEO Logic

Understand What is Important to the CEO and Your Career

CEO Logic: How to Think and Act like a Chief Executive by C. Ray Johnson.

The REAL DEAL!! A Guide for becoming a "Level 5" manager

CEO Logic : How to Think and Act Like a Chief Executive
C. Ray Johnson
Manufacturer: Career Press
ProductGroup: Book
Binding: Paperback

Strategy & Competition | Management & Leadership | Business & Investing | Subjects | Books
Leadership | Management & Leadership | Business & Investing | Subjects | Books
Management | Management & Leadership | Business & Investing | Subjects | Books
Guides | Job Hunting & Careers | Business & Investing | Subjects | Books
General | Business & Investing | Subjects | Books
General | Skills | Business & Investing | Subjects | Books
Similar Items:

CEO Tools: The Nuts-n-Bolts of Business for Every Manager's Success

Speak Like a CEO: Secrets for Commanding Attention and Getting Results

How to Think Like a CEO: The 22 Vital Traits You Need to Be the Person at the Top

Secrets of a CEO Coach: Your Personal Training Guide to Thinking Like a Leader and Acting Like a CEO

How to Become CEO: The Rules for Rising to the Top of Any Organization

ASIN: 1564143511

Customer Reviews:

Good Gems.......2007-07-21

This book has some good gems in terms of dealing with the challenges of being a CEO. It comes from a place of knowledge unlike several more academic business books.

I liked this book and recently finished another book that I think is also an excellent CEO primer and tool-kit for CEOs called, "Kiss Theory Good Bye" by Bob Prosen. It was published last year and offers some very actionable takeaways in each chapter as well.

CEO Logic.......2007-01-04

This is a great primer for a new CEO...someone in a small company moving into the role because of being a top producer or maybe by buying in but has never had any serious management experience. It is an easy read, and because of that, doesn't have a lot of depth. However, if the new CEO has what it takes to grow into the job, this book should spark an interest to acquire more knowledge.

Understand What is Important to the CEO and Your Career.......2006-12-31

A lot of times when a person starts out at an entry level job, he sees only his direct working environment but sometimes doesn't understand why certain departments or people have priorities over others. CEO Logic is a great reference for those who want to understand what goes on or should go on in the CEO's mind.

I highly recommend it to a new or young CEO to understand what their priorities should be and how to handle them accordingly. Some of the questions answered:

Why is it so imiportant to have and operate a company by a set of principles?

Why is it so important to have an open dialogue with workers and staff in a non-threatening environment?

Why is cash flow so important?

These and many other questions are posed to provoke the reader to think and most of the answers are used in real life examples of CEOs who have either made the mistake and corrected it or those who belong to the business obituaries page. The book is broken down into 4 parts with 19 Chapters:

Part 1: The Foundation
Ch1: Thinking Like a CEO
Ch2: Planning Strategy and Making Decisions
Part 2: Manageing Organizations and Execution Discipline
Ch3: Business Operations Plannning: Define the Risks Worth Taking
Ch4: People Management: Never Try to Teach a Pig to Think
Ch5: Career Management: Control Your Own Desitny
Ch6: Sales: Keep it Simple and Understand it Completely
Ch7: Numbers: Don't be Fooled by the "Accounting"
Part3: Cash, Crisis and Opportunity
Ch8: Banking: Master Their Rules
Ch9: Cash Management: Keep the Lifeblood Flowing
Ch10: Tough Times and Turnarounds: Match the Cure to the Illness
Ch11: Acquisitions: Don't Bujy it if You Can't Improve it
Part4: Character, Ethics, Communication and Wisdom
Ch12: Leadership: Nothing Mystical, Nothing Magical
Ch13: Secrets: Wit and Wisdom from the Trenches
Ch14: Final Thoughts: Simple Truths from Great Compelexities

CEO Logic: How to Think and Act like a Chief Executive by C. Ray Johnson........2005-07-12

The reason I read this book is that I wanted to learn to be an effective chief executive officer (CEO) and how CEOs think and make decisions, as I aspire to be one in the next two to three years.
CEO Logic provides a wide perspective about the challenges of being at the top of an organisation. C. Ray Johnson provides the knowledge of how to rise to the top of an organisation; how to think like a successful CEO, how to run an organisation successfully and how to turn a faltering organisation around from a loss making company, to a profitable entity, among other interesting topics.

CEO Logic explains what drives the actions of successful CEOs. It explains how to think clearly and perceive the fundamental management issues that influence business decisions and the habits of mind needed to achieve success in business.

The book gives an exposition of the foundations of business success, development of a business philosophy that works, and the strategic application of that philosophy in an organisation. CEO Logic teaches the operating disciplines required to establish and grow a business.

What I particularly liked in the book was the information on how a CEO can effect a turnaround. Ray Johnson provides, in chapter 10 of CEO Logic, ten steps of turning an organisation around. Based on the ten steps, those responsible for changing the fortunes of a company have an excellent blue print they can rely upon.

The REAL DEAL!! A Guide for becoming a "Level 5" manager.......2002-04-16

As the back cover of this book says, go ahead, read those other books by high-profile celebrity CEOs to get motivated. Then read this book to see HOW it is done. I say, skip the celebrity CEO du jour books, and go straight to this 5-star book for "Level 5" people.

This is a clear, consise, and exceptionally well proofread and published book (not one error in this book - as opposed to Moore's Crossing the Chasm - a terrible proofreading job). C. Ray Johnson cuts to the chase as to just what and how an effective CEO does and conducts him/herself, and in so doing convinces the reader quickly that anyone has the capacity to do pursue the principles of CEO logic if they really have the will and desire.

Johnson's incredibly clear early chapters lay out the effective CEO melds business understanding with personal principles. From there he goes through each aspect of key business functions and uses his CEO Logic approach for the right direction in each. His chapter on turnaround management is great.

Another very important note, this book and Jim Collins' Good to Great compliment each other. Collins makes the key point early on that companies that go from good to great are rarely run by celebrity big-ego CEOs brought in from the outside, but are instead run by generally quiet, unassuming people who are nevertheless deeply rooted in their convictions and desire to be great and have a winning team working with them. This is what Collins refers to as a "Level 5" leader.

Book Description

Expert solutions for securing network infrastructures and VPNs

Build security into the network by defining zones, implementing secure routing protocol designs, and building safe LAN switching environments
Understand the inner workings of the Cisco PIX Firewall and analyze in-depth Cisco PIX Firewall and Cisco IOS Firewall features and concepts
Understand what VPNs are and how they are implemented with protocols such as GRE, L2TP, and IPSec
Gain a packet-level understanding of the IPSec suite of protocols, its associated encryption and hashing functions, and authentication techniques
Learn how network attacks can be categorized and how the Cisco IDS is designed and can be set upto protect against them
Control network access by learning how AAA fits into the Cisco security model and by implementing RADIUS and TACACS+ protocols
Provision service provider security using ACLs, NBAR, and CAR to identify and control attacks
Identify and resolve common implementation failures by evaluating real-world troubleshooting scenarios

As organizations increase their dependence on networks for core business processes and increase access to remote sites and mobile workers via virtual private networks (VPNs), network security becomes more and more critical. In today's networked era, information is an organization's most valuable resource. Lack of customer, partner, and employee access to e-commerce and data servers can impact both revenue and productivity. Even so, most networks do not have the proper degree of security. Network Security Principles and Practices provides an in-depth understanding of the policies, products, and expertise that brings organization to this extremely complex topic and boosts your confidence in the performance and integrity of your network systems and services. Written by a CCIE engineer who participated in the development of the CCIE Security exams, Network Security Principles and Practices is the first book that provides a comprehensive review of topics important to achieving CCIE Security certification.

Network Security Principles and Practices is a comprehensive guide to network security threats and the policies and tools developed specifically to combat those threats. Taking a practical, applied approach to building security into networks, the book shows you how to build secure network architectures from the ground up. Security aspects of routing protocols, Layer 2 threats, and switch security features are all analyzed. A comprehensive treatment of VPNs and IPSec is presented in extensive packet-by-packet detail. The book takes a behind-the-scenes look at how the Cisco PIX(r) Firewall actually works, presenting many difficult-to-understand and new Cisco PIX Firewall and Cisco IOS® Firewall concepts. The book launches into a discussion of intrusion detection systems (IDS) by analyzing and breaking down modern-day network attacks, describing how an IDS deals with those threats in general, and elaborating on the Cisco implementation of IDS. The book also discusses AAA, RADIUS, and TACACS+ and their usage with some of the newer security implementations such as VPNs and proxy authentication. A complete section devoted to service provider techniques for enhancing customer security and providing support in the event of an attack is also included. Finally, the book concludes with a section dedicated to discussing tried-and-tested troubleshooting tools and techniques that are not only invaluable to candidates working toward their CCIE Security lab exam but also to the security network administrator running the operations of a network on a daily basis.

Customer Reviews:

Great book to learn Cisco's implementation of IPSec - not just for CCIEs.......2006-02-03

CiscoPress's "Network Security Principles and Practices" by Malik is truly an awesome work. The book weighs in at over 750 pages, and not a page is wasted. The book is split up over multiple sections (Intro to Network Security, Building Security into the Network, Firewalls, VPNs, IDS, AAA and ISP Security). I have found this book of value as I pursue my CCIE Routing & Switchng lab and to better enhance my basic understanding of Cisco's vision towards network security. I also used this book to prepare for my CCSP and CISSP studies.

Practically on every page is either a diagram or detailed configuration explaining the subject at hand. In particular, the configuration examples are extremely helpful as the configs, themselves, are appended with detailed notes of their syntax. Chapter 13, IPSec, is probably the best one-chapter discussion on Cisco's implementation of IPSec and VPN I have found anywhere (and I have over 50 CiscoPress books). Another testament to it's superb level of expertise is the few and far between typos or errors that I have found.

One item to note - you will need to block off a few weeks (or months) to fully understand and appreciate the value of this book. I reference this book often, as I find information in this book I cannot find documented or presented the same way in other books.

I give this book 5 pings out of 5:
!!!!!

Lucid, clear, and useful.......2005-08-19

Very clear explanations of the core security technologies. The author doesn't shy away from the hard subjects, and makes them quite accessible. The IPSec chapter is the best explanation of the subject I have seen anywhere.

I used this book to pass the CCIE security written exam, and highly recommend it. It is also a very good reference for practicing consultants and network security architects.

To be added to your 'essentials' list of books.......2005-06-09

Very, VERY good. The IPSec chapter alone is worth the book, and the AAA chapters are _great_. Saadat has been able to explain in a great technical level and very clearly subjects which you're going to find in your day to day work - if working with Cisco and security. But not only that: chapters about IPSec, RADIUS, TACACS, are of value even if you do not use Cisco gear.

Missing from the book: a better chapter on NAT, PPTP. Saadat should write the 2nd edition adding those two topics, updating the IDS section, IPSec (including NAT-T), maybe add a little something about SSL VPNs, PIX 7.0 ? The section on ISP security could also benefit from a refresher (CoPP, uRPF?)

4.5 starts because it shows it age - otherwise, 5 stars for sure.

A must read for Cisco Security Certifications.......2005-04-26

This is one of the first books I read for anyone preparing for CCIE Security. I found this book to be very comprehensive in its approach. The author has combined all the network security technologies in one book and now this is tough. It starts with an Introduction and then builds on that. It covers the whole nine yards VPN's Firewalls, IDS, Access Control. The Troubleshooting part of the book is very helpul to working professionals as it starts with troubleshooting NAT and then covers everything from Firewalls (PIX and IOS), VPN's, IDS and AAA. A lot of issues can be resolved just using this part of the book. I recommend this book as it will surely help everyone looking for everthing about security. This book is a must read for professionals pursuing the CCSP and CCIE Security Certifications.
Niloufer Tamboly, CISSP

Best ever book from Cisco.......2004-09-18

Not only for exam preparation, this book is for every Cisco lover. Covers a lot of stuff, took me over 2 months to finish but I feel way more knowledgeable now.

Beyond Software Architecture: Creating and Sustaining Winning Solutions

Average customer rating:

News you can use, but a bit annoying
Reinventing the wheel
Very unique, yet not gripping
AND?
Software Startup 101

Beyond Software Architecture: Creating and Sustaining Winning Solutions
Luke Hohmann
Manufacturer: Addison-Wesley Professional
ProductGroup: Book
Binding: Paperback

Design & Architecture | Hardware | Computers & Internet | Subjects | Books

General | Programming | Computers & Internet | Subjects | Books

General | Computers & Internet | Subjects | Books

General | Software | Computers & Internet | Subjects | Books

All Titles | Qualifying Textbooks - Fall 2007 | Stores | Books

Computers & Internet | Qualifying Textbooks - Fall 2007 | Stores | Books

Professional | Qualifying Textbooks - Fall 2007 | Stores | Books
Similar Items:

ASIN: 0201775948

Customer Reviews:

News you can use, but a bit annoying.......2006-08-29

Hohmann presents a fair amount of useful folk wisdom on enterprise software architecture. IMHO, this information is useful enough to try to struggle beyond the annoyances that Hohmann needlessly creates: (a) inventing annoying buzzwords like "tarchitecture" and misusing perjorative slang like "marketecture" (synonym: vaporware); (b) politocorrectoid smarm (all people in positions of responsibility are "she" and all low-level drones are "he"); and (c) Hohmann's very high opinion of himself.

I wish this book was on softcopy so that I could edit this stuff out. I'd have had an easier time reading it. As it is, I've had to take the book in small doses.

Reinventing the wheel.......2006-05-08

I had great hopes for this book, but for any industry veteran it is basically a repackaging of what many other "experts" have written before. The book is needlessly verbose, but yet glosses over key points with literary hand waving. The lack of significant examples, business cases, and real world process development gives one the feeling the book is merely the presentation of a thesis or philosophy devoid of concrete real world application.

For someone just starting out in the industry they may glean some basic concepts, but there are so many more publications that do a better job and do it cleaner.

Very unique, yet not gripping.......2006-01-24

One of the first things authors are asked by their agents, editors, or prospective publishers is to present an analysis of the other books in the genre that cover the same material as their books. Here, Luke must have had it very easy. He addresses a truly unique market niche (the interaction between technical architecture and marketing) in a way that really no one has done before or attempted to do since.

A book that handles both market segmentation and software product management in 300 odd pages is going to cover a whole lot of real estate and risks spreading the information pretty thin. Things important to folks in product management are not always the same things that are interesting to marketers. This facet of writing a book, target audience identification, is also frequently the subject of discussion with editors and publishes. Not having a clear target audience is where this book comes up a bit short.

Luke attempts to address such a breadth of software product concerns that it's hard for any one target group (technical architects or marketers) to get really interested. Although this book might be good for an entrepreneur or someone new to the field of software product management, it is, at best, a catalog of knowledge for tarchitects and marchitects and is unlikely to include anything that they haven't stumbled across in the field. A number of my colleagues have agreed with my final assessment that this is an easy book to peruse and become familiar with, yet a tough book to dive into and love.

AND?.......2005-08-14

Perhaps I'm missing something, but it seems that while this book might provide a nice skeleton for managers straddling the line between development (techitecture) and business strategy (marketecture), the meat is simply not present. So many opportunities for REAL examples went either unaddressed completely, or worse, were answered with meaningless little 2-paragraph sidebars filled with sentences like, "then we sat down to talk about things and we decided to approach things from a different angle, blah, blah, blah." Thanks. I can't say this book was a complete waste of time but it certainly wasn't the best use of my time, either, sadly. And the coining of these ridiculous terms like "techitecture" were truly hard to take.

Software Startup 101.......2004-07-19

Beyond Software Architecture should be required reading for anyone starting a software company - that is unless one prefers the school of hard knocks!

Luke does a fabulous job of going beyond the many books written on software and technology and beyond the many books, classes, and seminars addressing how to create a successful startup and get funded.

Hohmann's keen insight and practical advice can make an enormous difference for any group of bright and knowledgeable software engineers and/or visionary entrepreneurs with the "killer" application - a difference that can mean success. He clearly defines the space between the technology and the market and draws them together so that technologist and business person alike can gain a necessary understanding for what it takes to bring to market and sustain a successful software product.

Book Description

Is there room for improvement in the way your network SOA enables applications to communicate and perform services for one another? Then you'll want to take a serious look at Enterprise Services Architecture (ESA), which is fast becoming the leading SOA technology. With ESA, monolithic enterprise applications are broken apart into layers and offered as components that make extensive use of web services. With these components, companies gain the flexibility to craft the optimal IT infrastructure, eliminating bottlenecks and reducing the cost of implementation.

Our new guide, Enterprise Services Architecture: Designing IT for Business Innovation, demonstrates how your enterprise can transform current solutions into technology that will better serve the needs of your customers. Commissioned by the German software development company SAP, this definitive book is ideal for architects, developers and other IT professionals who want to understand ESA in a detailed way-especially those of you who want to move on the technology now, rather than in the next year or two.

Each chapter in the book is organized as a set of theoretical and practical questions with answers and examples that offer a clear story. To partition ESA into digestible portions, the authors boiled everything down into five concepts:

"Conceiving a Vision for ESA" - This section delves deep into the technical aspects of ESA.
"Consuming Services"-Using services to solve IT problems within the organization: This business-focused material shows you how services can be consumed immediately to configure standard software to solve a much larger set of problems.
"Composing with Services"-Assembling new applications and services from existing services: This section demonstrates how services can extend standard software by building on existing functionality as much as possible.
"Creating Services"-Creating new web services from scratch: How new services are created is described to provide technologists a deeper understanding of the tools and processes involved.
"Controlling Services" -discusses new forms of governance based on services as well as lifecycle management, operations, security, and standards.

ESA is already changing the way vendors build applications and the way companies use them. Enterprise Services Architecture: Designing IT for Business Innovation presents a forward-looking approach that you can use to meet future development challenges with ease and agility.

Customer Reviews:

Very Helpful Book on SOA.......2006-07-11

This is a very helpful book on SOA because it provides the business case for SOA, an excellent technical overview, and real-life examples of how to use it.

While it is written from an SAP perspective, any IT group that is investigating SOA will find value in this book -- as it describes how SOA impacts different layers of the IT stack (from persistence to business objects, to process orchestration, and uesr interfaces). It also provides actual case studies.

SOA - reality today!.......2006-07-02

Being a student of business and information management, I had heard about SOA before, both from a technical perspective (XML, Web services) and from a business standpoint (shiny visions of flexible processes). This book is like the missing link between the two areas! It does not only tell you that SOA will change organizations but it also shows *how* exactly this is going to happen. The authors describe all relevenat aspects, starting from organizational change down to the SAP tools that can be used to model processes and to create your own service-oriented applications.
What surprised me most was that ESA - SAP's flavour of SOA - is business-ready today! This is illustrated with numerous real-world examples from a wide range of corporations. The case studies give a good idea of useful ESA applications and show how the transition to a service-oriented infrastructure could take place.
"Enterprise SOA" is suited for everybody interested in information management, even without any previous knowledge in the SOA field. After reading through the book, you'll finally know how SOA is changing the business environment and how SAP is bringing the concepts to life based on open standards. Although you won't know every technical detail, you'll have learned enough to plan your organization's future in a service-oriented world.

Books:

Books Index

Books Home

Recommended Books