Start reading The Process of Software Architecting on your Kindle in under a minute. Don't have a Kindle? Get your Kindle here or start reading now with a free Kindle Reading App.

Deliver to your Kindle or other device


Try it free

Sample the beginning of this book for free

Deliver to your Kindle or other device

Anybody can read Kindle books—even without a Kindle device—with the FREE Kindle app for smartphones, tablets and computers.
The Process of Software Architecting

The Process of Software Architecting [Kindle Edition]

Peter Eeles , Peter Cripps
5.0 out of 5 stars  See all reviews (1 customer review)

Print List Price: £34.99
Kindle Price: £27.80 includes VAT* & free wireless delivery via Amazon Whispernet
You Save: £7.19 (21%)
* Unlike print books, digital books are subject to VAT.


Amazon Price New from Used from
Kindle Edition £27.80  
Paperback £34.99  
Kindle Daily Deal
Kindle Daily Deal: At least 60% off
Each day we unveil a new book deal at a specially discounted price--for that day only. Learn more about the Kindle Daily Deal or sign up for the Kindle Daily Deal Newsletter to receive free e-mail notifications about each day's deal.

Special Offers and Product Promotions

  • Purchase any Kindle Book sold by and receive £1 credit to try out our Digital Music Store. Here's how (terms and conditions apply)

Product Description


“The role of software architect has really come into its own in the last few years and is now recognized as a key determinant of project success. However, even today there is little common understanding of how to do the job: analyze requirements, understand concerns, evaluate alternatives, and construct and document an architectural description that is fit for purpose. Eeles and Cripps have filled this gap in their useful and practical book. The material is clearly and simply laid out, and follows a logical progression from inception through delivery, with tasks and work products clearly explained and illustrated using a real-world case study. This is a vital handbook for everyone from brand new architects to seasoned professionals.”
—Nick Rozanski, coauthor of Software Systems Architecture

“If you need a thorough and authoritative reference for a complete software architecture process, then look no further. Peter Eeles and Peter Cripps have produced a definitive guide and reference to just such a process. Being precisely defined using a metamodel, illustrated with a realistic case study, and clearly related to key standards such as UML, RUP, and IEEE 1471, the process presented in this book provides a valuable guide for those developing software architectures for large projects. I have no doubt that it will become a valued reference for many software architects.”
—Eoin Woods, coauthor of Software Systems Architecture

“Eeles and Cripps distill years of experience into a single guide that helps the reader understand not just what architects produce, but how they produce it. The Process of Software Architecting is a very practical guide filled with lessons learned and pitfalls to avoid. Practicing architects will want to refer to it as they hone their skills, and aspiring architects will gain key insights that otherwise could take painful years of experience to acquire.”
—Bob Kitzberger, program director, Strategy, IBM Software Group

“For most of my career in this field, software architecture has had the feel of being a black art that only a select few gurus and wizards had a talent for. This book follows on from industry best practice and a wealth of author experience to bring solutions architecture into the realms of being a true engineering discipline. Now I have a real guide I can pass on to new practitioners, a guide that embodies what used to require years of trial and error.”
—Colin Renouf, enterprise architect and technology author, vice chairman, WebSphere User Group, UK

Product Description

A Comprehensive Process for Defining Software Architectures That Work

A good software architecture is the foundation of any successful software system. Effective architecting requires a clear understanding of organizational roles, artifacts, activities performed, and the optimal sequence for performing those activities.

With The Process of Software Architecting , Peter Eeles and Peter Cripps provide guidance on these challenges by covering all aspects of architecting a software system, introducing best-practice techniques that apply in every environment, whether based on Java EE, Microsoft .NET, or other technologies. Eeles and Cripps first illuminate concepts related to software architecture, including architecture documentation and reusable assets. Next, they present an accessible, task-focused guided tour through a typical project, focusing on the architect’s role, with common issues illuminated and addressed throughout. Finally, they conclude with a set of best practices that can be applied to today’s most complex systems.

You will come away from this book understanding
  • The role of the architect in a typical software development project
  • How to document a software architecture to satisfy the needs of different stakeholders
  • The applicability of reusable assets in the process of architecting
  • The role of the architect with respect to requirements definition
  • The derivation of an architecture based on a set of requirements
  • The relevance of architecting in creating complex systems
The Process of Software Architecting will be an indispensable resource for every working and aspiring software architect—and for every project manager and other software professional who needs to understand how architecture influences their work.

Product details

  • Format: Kindle Edition
  • File Size: 5815 KB
  • Print Length: 432 pages
  • Simultaneous Device Usage: Up to 5 simultaneous devices, per publisher limits
  • Publisher: Addison-Wesley Professional; 1 edition (14 July 2009)
  • Sold by: Amazon Media EU S.à r.l.
  • Language: English
  • ASIN: B002L9MZ06
  • Text-to-Speech: Enabled
  • X-Ray:
  • Average Customer Review: 5.0 out of 5 stars  See all reviews (1 customer review)
  • Amazon Bestsellers Rank: #307,794 Paid in Kindle Store (See Top 100 Paid in Kindle Store)
  •  Would you like to give feedback on images?

More About the Author

Discover books, learn about writers, and more.

What Other Items Do Customers Buy After Viewing This Item?

Customer Reviews

4 star
3 star
2 star
1 star
5.0 out of 5 stars
5.0 out of 5 stars
Most Helpful Customer Reviews
2 of 2 people found the following review helpful
5.0 out of 5 stars Broad and practical 12 Sep 2009
It is refreshing to have a book that relates the role of "Software Architect" to every aspect of Software Development. Important concepts, practices and pitfalls are drawn out appropriately. It is clearly written with an easy-going first person style. It is not technology specific - nevertheless the principles described in this book apply to most modern day development technologies. The hot topics of patterns, views, models and re-use are dealt with very well. The book both tells a story (in terms of a process) and acts as a valuable reference. Good architects are grown, not trained. This is an essential book for any architect at any stage of growth.
Comment | 
Was this review helpful to you?
Most Helpful Customer Reviews on (beta) 4.4 out of 5 stars  5 reviews
22 of 23 people found the following review helpful
5.0 out of 5 stars It is the story of how it is supposed to be... 1 Sep 2009
By T. Anderson - Published on
Format:Paperback|Verified Purchase
About a year ago I finished up putting together a new Software Engineering Process for the state of PA. It included the best of the best, from those that gave us permission to use their content. You can check out the resources by googling "bscoe sep" (no links allowed on amazon).

A lot of the content was related to architecture. I would have loved to have had this book back then to refer people too as an educational resource. This book puts the process of Software Architecting into a very understandable format and does a great job of explaining process fundamentals.

It is hard to train people in Software Architecture, and then add a ton of Software Process Engineering concepts to it and you really begin to lose people. We had very little success in finding anyone who wanted to go through the learning exercise. Only our team used the process for the most part.

This book starts out with a great overview of Software Architecture, the Architect, and Architecting. Even if you are familiar with these concepts, they are a good read and they get the context laid for the rest of the book from the perspective the authors take on the concepts.

Next the authors give a great introduction to method fundamentals. They pull from the industry's best practices which include the RUP, OpenUP, XP, SCRUM, FDD, and use the SPEM to do their process diagrams. The do a great job of pulling out the important information that relates to software process engineering and putting it into a very organized and easy to understand format. The chapter is short and to the point.

The authors then cover documenting software architectures. In this chapter they outline an architectural description framework based on Rozanski and Woods viewpoints and perspectives, the Zachman Framework, and the 4 +1 view model.

The next chapter on reusable architecture assets provides an architecture asset metamodel for development -time assets and one for run-time assets.

The rest of the book is a detailed, real world, case study that puts the architecture method to use.

The book ends with appendixes, Software Architecture Metamodel, Viewpoint Catalog, Method Summary, and Architectural Requirement Checklist.

Two guys from IBM authored a non IBM centric book. Although he authors both work for IBM they didn't include or use tools from IBM.

The book stays within the scope of process engineering as related to software architecture, which produced a more effective book than if they had not. For example, if they would have tried to provide a treatment of tactics instead of referring us to the best resources available on tactics. The book stay process focused.

The appendixes are very valuable references.

They use industry standard best practices for all their content. They are not inventing any new wheels here, or trying to sell a new silver bullet. They are simply picking out the best of what has worked in the industry and putting it into a very organized and usable format.

I like that they include the requirements gathering phase as part of the architecture process. You usually find the requirements discipline treated as though the architecture team has nothing to do with it. That is just not the case in a healthy process.

I really do not have any. The only thing I would like to see is the process content in the book put into the Eclipse Process Framework Composer. That way it could be offered as a plug-in and we could include it in our process configurations.

If you are involved in software development in anyway, you should read this book. It is the story of how it is supposed to be.
5 of 6 people found the following review helpful
2.0 out of 5 stars Not what I expected 21 Feb 2013
By Tim - Published on
Format:Paperback|Verified Purchase
I bought this book because of the many 5 star reviews here, and was excited to read and learn about software architecture. I am an experienced developer that has been asked to step into a role of architect, and since this is new to me and new to the company I thought it would be best to read up on the practices used in the industry.

First off let me say this book is awful to read. Regardless of actual content the writing style is unnatural and boring at best. The entire book is filled to the brim with jargon, and there are more sentences defining terms than there are actually talking about the architecture itself. I literally had to force myself to read this, and I am an avid and proficient reader usually.

The book talks about countless work products that are meaningless aside from their definition. This list of ten work products feeds into this step. Now two pages of definitions of the work products. Not only that but the sheer number of documents the book reccomends for each step is staggering. Maybe that is industry grade, but I was blown away.

All in All an informative and yet extremely tedious and painful read. While it may serve as a good long term reference, I cannot reccomend it as a reading material for someone trying to learn the basics.
4 of 9 people found the following review helpful
5.0 out of 5 stars really makes you think 13 Nov 2010
By Jeanne Boyarsky - Published on
"The Process of Software Architecting" looks like it could be read in one sitting. Don't be fooled. It is one of the most informative and thought provoking "job discussion" type books I have read in a long time. I made notes in the margins on page 1 and continued to the end.

Another surprise was the preface saying both architects and students are the target audience. True. Students won't get the deepness of it, but they will still learn a lot. Finally, the authors are both IBM'ers but it doesn't read like an IBM book or have an IBM slant. While the case study uses JEE, the authors summarize relevant knowledge beforehand.

Ok. Enough with the surprises. This approachable book is visual and list heavy which makes for easy understanding. Consistent bold keywords help readability. I found myself skimming some parts where the visual said it all. The appendices provide a tabular summary of much content.

For the 200 page case study, they have tasks defined in a summary box. Each task has steps along with checklists/pitfalls/best practices where applicable. I REALLY like this format. I particularly liked the emphasis on providing a mental map/thinking as an architect.

While the case study is simpler than real life, it is supplemented by examples later. My only complaint was the term "right-sizing" to mean scaling small vs large teams. Since this word was hijacked to mean layoffs, it is emotionally charged. But that being my only issue with the book is still pretty good.

I strongly recommend this book for anyone who is an architect or wants to be one day.

Disclosure: I received a copy of this book from the publisher in exchange for writing this review on behalf of CodeRanch.

A contrasting opinion from Jan de Boer via [...]
Ah sorry but I really do not like this book. Now first I must say, I can have very different opinions then the crowd. Sometimes I dislike movies for example that other love. I can remember a movie called oceans' number 12, I think. Lots of famous stars in it, but I just hated it. I can remember certain music records as a teenagers my friends loved, I hated them. I am kinda strange and independent.

But what I don't like about the book is, what I already stated in the previous post, it tries to over define all kinds of things. I don't like that because the process of architecture, software development, uses very inconsistent vocabulary. But if this is the case, why not just agree on the fact that these words are used in a different way in different environments? Why on every term quote all kinds of books? Just agree to disagree, and try to explain certain pitfalls and good practises by some examples instead? Also the definitions are useless I think when in all software developing environments they are used differently. You should know what it means in your environment, and this is not the same as tried in any book anyway.

Then it gives a certain empty cabinet, procedures you could follow. But if I work in a company, this is mostly already decided for me, in a method the company has chosen. And the exact organization of the shells is not that important. It is important you put something logical inside it. And then it kicks in some open doors like: this procedure could be simpler if your project is small, and more thorough if the project is complicated. Now really? And also it comes with remarks like: the order of the process in not exactly defined. Yes I know that too. It never is.

So it really did not tell me much new stuff. And what it did told me, was packed in what I think a over academic style that in the end really irritated me. In fact, I stopped reading the book at page 260 of about 300. I learned a few new terms from it. There is a check list as appendix I think is useful to check if you have thought of everything. But I would rather read a book that tells me what I can put 'on the shells of the cabinet'. The books states that this is not such a book and that there are other books who explain design and architecture paradigms. I think I will read those books then.

I will still give it a six, since it's not badly written or something. In the fact that there are a lot of errors in it. But I find the aim of the book useless, and the style over academic. Again and again some quote from some study like the writers want to prove they read all those
3 of 11 people found the following review helpful
5.0 out of 5 stars This book helped me 22 Jun 2010
By Iulian Stoica - Published on
This book showed me a perspective of the architecting process and opened new perspectives.
I appreciate the clarity of the book.
2 of 10 people found the following review helpful
5.0 out of 5 stars A pick for any advanced computer library 16 Nov 2009
By Midwest Book Review - Published on
The Process of Software Architecting is for any library strong in software engineering, and provides a solid guide to architecting a software system. From the architect's role in creating reusable assets that fit into requirements present and future to how to architect in a complex system, The Process of Software Architecting is a pick for any advanced computer library.
Were these reviews helpful?   Let us know
Search Customer Reviews
Only search this product's reviews

Customer Discussions

This product's forum
Discussion Replies Latest Post
No discussions yet

Ask questions, Share opinions, Gain insight
Start a new discussion
First post:
Prompts for sign-in

Search Customer Discussions
Search all Amazon discussions

Look for similar items by category