Every once in a while a book is put together that should be read by every
person with a relationship to software development. This book is one of them.
Everyone dreams of automating their software testing, but few make it a
reality. This down to earth book is the stories of 28 teams that went for it.
It includes both successes and failures. That is not something you see
everyday.
Many books simply provide you the success path. This book also provides you
with the steps you could possibly be taking that could lead to failure
helping you to change your path before fully failing.
The book starts with a nice overview of the case studies and an introduction
to the key issues addressed by the case studies. Besides each case study
being summarized, it also includes introducing the topics and pointing out
the chapter they can be found in. They are broken down into management ... (more)
There are not too many systems being created today that I would consider more
than interfaces to a data structure. Meaning most systems today rely on
people to provide the intelligence behind them. The systems themselves are
viewed as a necessary evil by the people who use them. I find this to be
especially true in organizations with a long history. Their attitude is they
were built by people, and people will continue to be their most valuable
asset.
The author of this book challenges us to take our systems to the new level of
existence. One where they are responsive partners in ... (more)
I really like the CERT books. This one is no different, however, it is not
one to read from cover to cover, at least not for me. It contains a catalog
of rules for programming secure java code. What I have been doing is using it
to look up rules about topics found in other resources that I have been using
to learn the java environment.
Although the book contains a great index, there is an online version of this
book which is really nice. It contains a really sweet search. I have been
using that a lot to find the topics I am interested in, marking them in the
book, and then readin... (more)
This book is truly a holistic view of software architecture.
This book structures the book around an Architecture Orientation Framework.
The framework is based on open question words. A chapter has been dedicate to
each. The framework provides a nice common vocabulary that makes team
communication easier.
The chapters of the book include Architectures and Architecture Disciplines
(WHAT), Architecture Perspectives (WHERE)' Architecture Requirements (WHY),
Architecture Means (WITH WHAT), Organizations and Individuals (WHO), and
Architecture Method (HOW).
Each chapter is laid out in t... (more)
This is a very well put together book. It includes a single example company
that the book grows and changes throughout the book. Sometimes examples get
on my nerves. They are either too lightweight to mean anything, or sometimes
too complex, and end up distracting you to the point of not wanting to
continue read the book. The authors do an awesome job with the case study in
this book. It really made it an enjoyable read.
The book begins with a nice introduction to ODP. It introduces viewpoints,
viewpoint languages, viewpoint correspondences, fundamental concepts, and
UML4ODP.
Aft... (more)
Dan Stolts
Joe Zeto
John Baker
Vincent M. Schiavo
Chris Pentago
Kevin Remde
Yung Chou
