Continuous Architecture
Sustainable Architecture in an Agile and Cloud-Centric World
- 1st Edition - October 21, 2015
- Latest edition
- Authors: Murat Erder, Pierre Pureur
- Language: English
Continuous Architecture provides a broad architectural perspective for continuous delivery, and describes a new architectural approach that supports and enables it. As the pace of… Read more
Continuous Architecture provides a broad architectural perspective for continuous delivery, and describes a new architectural approach that supports and enables it. As the pace of innovation and software releases increases, IT departments are tasked to deliver value quickly and inexpensively to their business partners. With a focus on getting software into end-users hands faster, the ultimate goal of daily software updates is in sight to allow teams to ensure that they can release every change to the system simply and efficiently.
This book presents an architectural approach to support modern application delivery methods and provide a broader architectural perspective, taking architectural concerns into account when deploying agile or continuous delivery approaches. The authors explain how to solve the challenges of implementing continuous delivery at the project and enterprise level, and the impact on IT processes including application testing, software deployment and software architecture.
- Covering the application of enterprise and software architecture concepts to the Agile and Continuous Delivery models
- Explains how to create an architecture that can evolve with applications
- Incorporates techniques including refactoring, architectural analysis, testing, and feedback-driven development
- Provides insight into incorporating modern software development when structuring teams and organizations
enterprise/software architects, application designers, "DevOps" managers
- Dedication
- Foreword by Kurt Bittner
- Foreword by Peter Eeles
- Chapter 1. Introduction to Continuous Architecture
- Abstract
- What Do We Mean by Architecture?
- Historical Perspective
- Current Challenges with Software Architecture
- Continuous Architecture Definition
- Structure of The Book
- Endnotes
- Chapter 2. Principles of Continuous Architecture
- Abstract
- Principle 1: Architect Products, Not Just Solutions for Projects
- Principle 2: Focus on Quality Attributes, Not on Functional Requirements
- Principle 3: Delay Design Decisions Until They Are Absolutely Necessary
- Principle 4: Architect for Change—Leverage “The Power of Small”
- Principle 5: Architect for Build, Test, and Deploy
- Principle 6: Model the Organization After the Design of the System
- Summary
- Endnotes
- Chapter 3. Getting Started with Continuous Architecture: Requirements Management
- Abstract
- Functional Requirements versus Quality Attributes
- Leveraging Value Chains to Understand the Functional Scope of a Product
- Using Architecture Scenarios for Quality Attribute Requirements
- Gathering and Managing Requirements
- Summary
- Endnotes
- Chapter 4. Evolving the Architecture
- Abstract
- Architectural Decisions
- Prioritizing: Using Quality Function Deployment
- Managing Change: Transitional Architectures
- Applying the Continuous Architecture Principles
- Summary
- Endnotes
- Chapter 5. Continuous Architecture and Continuous Delivery
- Abstract
- Continuous Architecture and the DevOps Process
- Continuous Architecture, Continuous Feedback, and Continuous Monitoring
- Continuous Architecture and the Continuous Integration Process
- Continuous Architecture and Continuous Release and Deployment
- Continuous Architecture and Continuous Testing
- Continuous Architecture and Hybrid Cloud Deployment
- Summary
- Endnotes
- Chapter 6. Validating the Architecture
- Abstract
- What Do We Mean By “Architecture Validation”?
- When Do We Need to Validate?
- Who Should Validate?
- How Should We Validate?
- Validation Process
- Summary
- Endnotes
- Chapter 7. Continuous Architecture in Practice: A Case Study
- Abstract
- How to Get Started with Continuous Architecture? Start Small
- How to Evolve Continuous Architecture Over Time?
- Summary
- Endnotes
- Chapter 8. Role of the Architect
- Abstract
- What Does an Architect Do?
- Who Is an Architect? Types of Personalities
- The Role of the Architect in Continuous Architecture
- Summary
- Endnotes
- Chapter 9. Continuous Architecture in the Enterprise
- Abstract
- Context for the Enterprise and Antipatterns
- Collaboration and Communication
- Common Language
- Decision Making in the Enterprise
- Architecture Process at the Enterprise Scale
- Summary
- Endnotes
- Chapter 10. What About Enterprise Services?
- Abstract
- The Role of Enterprise Services
- Product Management
- A Short Story of an Enterprise Service
- Delivering Enterprise Services
- Continuous Architecture and Enterprise Services
- Summary
- Endnotes
- Chapter 11. Conclusion
- Abstract
- What Was This Book About?
- Why Does Continuous Architecture Work?
- Putting Continuous Architecture in Practice
- Glossary
- Endnotes
- Edition: 1
- Latest edition
- Published: October 21, 2015
- Language: English
ME
Murat Erder
Murat Erder is a Director at Deutsche Bank, and is currently working in Data Engineering group as part of the Chief Data Office. Prior to his current role, Murat was the Domain Architect for Reference Data. Before this role he led the Integration Services group at Deutsche Bank responsible for all managed services that dealt with integration; including core messaging, file transfer, ETL, Enterprise Service Bus, Workflow and Document Management. Murat also setup the Technology Standards group at Deutsche Bank and governed adoption of new technologies. Prior to joining Deutsche Bank, Murat worked for 13 years for management consulting organizations, including KPMG/BearingPoint and Deloitte providing architecture and technology strategy advice to leading Financial Services organizations. Murat started his career as a software developer in Silicon Valley and was employed as a Software Development Lifecycle and Object Oriented Analysis and Design specialist by Objectory and Rational. Murat has a MS degree in Electrical and Computer Engineering from the University of Massachusetts
Affiliations and expertise
Director, IT Architecture & Engineering for a leading financial services organization, London, UKPP
Pierre Pureur
Pierre Pureur is Vice President and Chief Enterprise Architect for Travelers. In his role, Pierre leads the Enterprise Architecture group that includes Application Platform Architecture, Information Architecture, Infrastructure Architecture, Performance Architecture and Security Architecture. Prior to his current role, Pierre was the Vice President of Architecture for Personal Insurance Business Technology at Travelers. Prior to joining Travelers, Pierre worked for a number of Financial Services and Consulting Organizations, including KPMG/Bearing Point, Citicorp, Bear Stearns, MetLife, Prudential, EXL, Republic National Bank of New York and People’s United Financial. During his career Pierre’s responsibilities have encompassed all phases of large-scale application development and technology rollout including strategic planning, architecture, design, development and deployment. Pierre has expertise in designing and implementing Service Based Architectures and Business Process Management solutions, and in enhancing processes related to application management, including design and development methodologies. Pierre is very familiar with continuous improvement approaches such as Six Sigma, CMM, ITIL and ATAM based techniques. Pierre is a graduate of the Ecole Nationale Superieure Des Mines (St Etienne, France), a member of the IEEE Computer Society and resides in Glastonbury, CT.
Affiliations and expertise
Vice President and Chief Enterprise Architect, Hartford, CT, USARead Continuous Architecture on ScienceDirect