Du kanske gillar
The Process of Software Architecting
Fri frakt inom Sverige för privatpersoner.
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 architects role, with common issues illuminated and addressed throughout. Finally, they conclude with a set of best practices that can be applied to todays 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
Passar bra ihop
De som köpt den här boken har ofta också köpt Building J2EE Applications with the Rational Un... av Peter Eeles (häftad).Köp båda 2 för 995 kr
Fler böcker av författarna
Building J2EE Applications with the Rational Unified Process
Two of the most significant technological development trends of the past few years have been the Java 2 Platform, Enterprise Edition (J2EE), a platform specifically geared to the needs of enterprise systems, and the Rational Unified Process (RUP),...
Relating System Quality and Software Architecture
Ivan Mistrik, Rami Bahsoon, Peter Eeles, Roshanak Roshandel, Michael Stal
System Quality and Software Architecture collects state-of-the-art knowledge on how to intertwine software quality requirements with software architecture and how quality attributes are exhibited by the architecture of the system. Contributions fr...
Recensioner i media
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
Bloggat om The Process of Software Architecting
Peter Eeles (UK), Executive IT Architect at IBM Rational Software, has spent much of his career architecting and implementing large-scale, distributed systems. He currently assists organizations in adopting the Rational Unified Process and the IBM Software Development Platform. He is coauthor of Building J2EE Applications with the Rational Unified Process and Building Business Objects. Peter Cripps (UK) is a Senior IT Architect in IBM Global Business Services. He specializes in applying component and service-based development techniques, and propagating superior architecture practices throughout IBM. He was recently involved in the development of the IBM Unified Method Framework.
About the Authors xxv
Chapter 1: Introduction 1
Applying the Process 2
The Process in Brief 2
Chapter 2: Architecture, Architect, Architecting 9
The Benefits of Architecting 35
Chapter 3: Method Fundamentals 43
Key Concepts 43
Method Content 46
Chapter 4: Documenting a Software Architecture 61
The End Game 62
Key Concepts 64
Viewpoints and Views 65
Characteristics of an Architecture Description Framework 75
An Architecture Description Framework 81
The Software Architecture Document 87
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
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
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
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 Architectur...