The Process of Software Architecting [NOOK Book]


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 ...
See more details below
The Process of Software Architecting

Available on NOOK devices and apps  
  • NOOK Devices
  • Samsung Galaxy Tab 4 NOOK 7.0
  • Samsung Galaxy Tab 4 NOOK 10.1
  • NOOK HD Tablet
  • NOOK HD+ Tablet
  • NOOK eReaders
  • NOOK Color
  • NOOK Tablet
  • Tablet/Phone
  • NOOK for Windows 8 Tablet
  • NOOK for iOS
  • NOOK for Android
  • NOOK Kids for iPad
  • PC/Mac
  • NOOK for Windows 8
  • NOOK for PC
  • NOOK for Mac

Want a NOOK? Explore Now

NOOK Book (eBook)
$34.49 price
(Save 13%)$39.99 List Price


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.

Read More Show Less

Product Details

  • ISBN-13: 9780321617460
  • Publisher: Pearson Education
  • Publication date: 7/28/2009
  • Sold by: Barnes & Noble
  • Format: eBook
  • Edition number: 1
  • Pages: 432
  • Sales rank: 1,220,695
  • File size: 10 MB

Meet the Author

Peter Eeles is an IBM executive IT architect, working within the Rational brand of IBM’s Software Group. In this capacity he helps organizations improve their software development capability, with a particular focus on and interest in improving the architecting process. Peter has been in the software industry since 1985 and has spent much of his career architecting and implementing large-scale, distributed systems. Peter is coauthor of Building J2EE Applications with the Rational Unified Process (Addison-Wesley, 2002) and coauthor of Building Business Objects (John Wiley & Sons, 1998). He is a fellow of the British Computer Society (FBCS), a fellow of the Institute of Engineering and Technology (FIET), an IBM technical staff member, an Open Group Master Certified IT architect, and a Chartered IT Professional (CITP).

Peter Cripps
is an IT architect in IBM Global Business Services in the United Kingdom. He has been in the software industry since 1980, during which time he has worked as a programmer, real-time software engineer, and process engineer across a range of industries, including telecommunications, financial services, retail, and government. Peter’s particular areas of technical expertise and interest are the application of component- and service-based development techniques and the development of good architecture practice. He is a member of the British Computer Society (MBCS) and a Chartered IT Professional (CITP).
Read More Show Less

Table of Contents

Foreword      xvii
Preface      xix
Acknowledgments      xxiii
About the Authors      xxv

Chapter 1: Introduction      1
Applying the Process 2
The Process in Brief 2
Scope 8
Summary 8

Chapter 2: Architecture, Architect, Architecting      9
Architecture 9
Architect 21
The Benefits of Architecting 35
Summary 40

Chapter 3: Method Fundamentals      43
Key Concepts 43
Method Content 46
Process 50
Summary 59

Chapter 4: Documenting a Software Architecture      61
The End Game 62
Key Concepts 64
Viewpoints and Views 65
Models 72
Characteristics of an Architecture Description Framework 75
An Architecture Description Framework 81
The Software Architecture Document 87
Summary 88

Chapter 5: Reusable Architecture Assets      89
Sources of Architecture 89
An Architecture Asset Metamodel 90
Asset Types 94
Attributes of an Architecture Asset 103
Other Reuse Considerations 106
Summary 106

Chapter 6: Introduction to the Case Study      107
Applying the Process 107
Scope of the Case Study 110
Application Overview 115
The YourTour Vision 118
Summary 123

Chapter 7: Defining the Requirements      125
Relating Requirements to Architecture 128
Functional and Non-Functional Requirements 130
Techniques for Documenting Requirements 131
Applying the Process 132
Understanding the Task Descriptions 133
Define Requirements: Activity Overview 134
Task: Collect Stakeholder Requests 136
Task: Capture Common Vocabulary 141
Task: Define System Context 143
Task: Outline Functional Requirements 149
Task: Outline Non-Functional Requirements 156
Task: Prioritize Requirements 160
Task: Detail Functional Requirements 164
Task: Detail Non-Functional Requirements 171
Task: Update Software Architecture Document 174
Task: Review Requirements with Stakeholders 175
Summary 176

Chapter 8: Creating the Logical Architecture      179
Moving from Requirements to Solution 182
How Much Logical Architecture? 185
Applying the Process 188
Create Logical Architecture: Activity Overview 188
Task: Survey Architecture Assets 192
Task: Define Architecture Overview 194
Task: Document Architecture Decisions 200
Task: Outline Functional Elements 204
Task: Outline Deployment Elements 222
Task: Verify Architecture 228
Task: Build Architecture Proof-of-Concept 232
Task: Detail Functional Elements 234
Task: Detail Deployment Elements 245
Task: Validate Architecture 251
Task: Update Software Architecture Document 256
Task: Review Architecture with Stakeholders 258
Summary 260

Chapter 9: Creating the Physical Architecture      261
Moving from Logical to Physical Architecture 263
Applying the Process 265
Creating the Physical Architecture: Activity Overview 266
Task: Survey Architecture Assets 269
Task: Define Architecture Overview 270
Task: Document Architecture Decisions 273
Task: Outline Functional Elements 274
Task: Outline Deployment Elements 289
Task: Verify Architecture 292
Task: Build Architecture Proof-of-Concept 293
Task: Detail Functional Elements 294
Task: Detail Deployment Elements 296
Task: Validate Architecture 300
Task: Update Software Architecture Document 301
Task: Review Architecture with Stakeholders 301
Summary 302

Chapter 10: Beyond the Basics      303
The Architect and the Project Team 303
The Architect and External Influences 313
Architecting Complex Systems 318
Summary 330
In Conclusion: A Note from the Authors 331

Appendix A: Software Architecture Metamodel      333
Definition of Metamodel Terms 335

Appendix B: Viewpoint Catalog      339
Stakeholder Summary 340
Basic Viewpoints 341
Cross-Cutting Viewpoints 344
View Correspondence 347

Appendix C: Method Summary       351
Roles 351
Work Products 354
Activities 356
Tasks 356
Phases 362

Appendix D: Architectural Requirement Checklist      365
Functional Requirements 366
Usability Requirements 366
Reliability Requirements 367
Performance Requirements 367
Supportability Requirements 368
Constraints 368

Glossary 373
References 379
Index 385

Read More Show Less

Customer Reviews

Be the first to write a review
( 0 )
Rating Distribution

5 Star


4 Star


3 Star


2 Star


1 Star


Your Rating:

Your Name: Create a Pen Name or

Barnes & Review Rules

Our reader reviews allow you to share your comments on titles you liked, or didn't, with others. By submitting an online review, you are representing to Barnes & that all information contained in your review is original and accurate in all respects, and that the submission of such content by you and the posting of such content by Barnes & does not and will not violate the rights of any third party. Please follow the rules below to help ensure that your review can be posted.

Reviews by Our Customers Under the Age of 13

We highly value and respect everyone's opinion concerning the titles we offer. However, we cannot allow persons under the age of 13 to have accounts at or to post customer reviews. Please see our Terms of Use for more details.

What to exclude from your review:

Please do not write about reviews, commentary, or information posted on the product page. If you see any errors in the information on the product page, please send us an email.

Reviews should not contain any of the following:

  • - HTML tags, profanity, obscenities, vulgarities, or comments that defame anyone
  • - Time-sensitive information such as tour dates, signings, lectures, etc.
  • - Single-word reviews. Other people will read your review to discover why you liked or didn't like the title. Be descriptive.
  • - Comments focusing on the author or that may ruin the ending for others
  • - Phone numbers, addresses, URLs
  • - Pricing and availability information or alternative ordering information
  • - Advertisements or commercial solicitation


  • - By submitting a review, you grant to Barnes & and its sublicensees the royalty-free, perpetual, irrevocable right and license to use the review in accordance with the Barnes & Terms of Use.
  • - Barnes & reserves the right not to post any review -- particularly those that do not follow the terms and conditions of these Rules. Barnes & also reserves the right to remove any review at any time without notice.
  • - See Terms of Use for other conditions and disclaimers.
Search for Products You'd Like to Recommend

Recommend other products that relate to your review. Just search for them below and share!

Create a Pen Name

Your Pen Name is your unique identity on It will appear on the reviews you write and other website activities. Your Pen Name cannot be edited, changed or deleted once submitted.

Your Pen Name can be any combination of alphanumeric characters (plus - and _), and must be at least two characters long.

Continue Anonymously

    If you find inappropriate content, please report it to Barnes & Noble
    Why is this product inappropriate?
    Comments (optional)