Continuous Architecture

Book description

 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

Table of contents

  1. Cover image
  2. Title page
  3. Table of Contents
  4. Copyright
  5. Dedication
  6. Foreword by Kurt Bittner
  7. Foreword by Peter Eeles
  8. Acknowledgments
  9. Chapter 1. Introduction to Continuous Architecture
    1. Abstract
    2. What Do We Mean by Architecture?
    3. Historical Perspective
    4. Current Challenges with Software Architecture
    5. Continuous Architecture Definition
    6. Structure of The Book
    7. Endnotes
  10. Chapter 2. Principles of Continuous Architecture
    1. Abstract
    2. Principle 1: Architect Products, Not Just Solutions for Projects
    3. Principle 2: Focus on Quality Attributes, Not on Functional Requirements
    4. Principle 3: Delay Design Decisions Until They Are Absolutely Necessary
    5. Principle 4: Architect for Change—Leverage “The Power of Small”
    6. Principle 5: Architect for Build, Test, and Deploy
    7. Principle 6: Model the Organization After the Design of the System
    8. Summary
    9. Endnotes
  11. Chapter 3. Getting Started with Continuous Architecture: Requirements Management
    1. Abstract
    2. Functional Requirements versus Quality Attributes
    3. Leveraging Value Chains to Understand the Functional Scope of a Product
    4. Using Architecture Scenarios for Quality Attribute Requirements
    5. Gathering and Managing Requirements
    6. Summary
    7. Endnotes
  12. Chapter 4. Evolving the Architecture
    1. Abstract
    2. Architectural Decisions
    3. Prioritizing: Using Quality Function Deployment
    4. Managing Change: Transitional Architectures
    5. Applying the Continuous Architecture Principles
    6. Summary
    7. Endnotes
  13. Chapter 5. Continuous Architecture and Continuous Delivery
    1. Abstract
    2. Continuous Architecture and the DevOps Process
    3. Continuous Architecture, Continuous Feedback, and Continuous Monitoring
    4. Continuous Architecture and the Continuous Integration Process
    5. Continuous Architecture and Continuous Release and Deployment
    6. Continuous Architecture and Continuous Testing
    7. Continuous Architecture and Hybrid Cloud Deployment
    8. Summary
    9. Endnotes
  14. Chapter 6. Validating the Architecture
    1. Abstract
    2. What Do We Mean By “Architecture Validation”?
    3. When Do We Need to Validate?
    4. Who Should Validate?
    5. How Should We Validate?
    6. Validation Process
    7. Summary
    8. Endnotes
  15. Chapter 7. Continuous Architecture in Practice: A Case Study
    1. Abstract
    2. How to Get Started with Continuous Architecture? Start Small
    3. How to Evolve Continuous Architecture Over Time?
    4. Summary
    5. Endnotes
  16. Chapter 8. Role of the Architect
    1. Abstract
    2. What Does an Architect Do?
    3. Who Is an Architect? Types of Personalities
    4. The Role of the Architect in Continuous Architecture
    5. Summary
    6. Endnotes
  17. Chapter 9. Continuous Architecture in the Enterprise
    1. Abstract
    2. Context for the Enterprise and Antipatterns
    3. Collaboration and Communication
    4. Common Language
    5. Decision Making in the Enterprise
    6. Architecture Process at the Enterprise Scale
    7. Summary
    8. Endnotes
  18. Chapter 10. What About Enterprise Services?
    1. Abstract
    2. The Role of Enterprise Services
    3. Product Management
    4. A Short Story of an Enterprise Service
    5. Delivering Enterprise Services
    6. Continuous Architecture and Enterprise Services
    7. Summary
    8. Endnotes
  19. Chapter 11. Conclusion
    1. Abstract
    2. What Was This Book About?
    3. Why Does Continuous Architecture Work?
    4. Putting Continuous Architecture in Practice
  20. Glossary
    1. Endnotes
  21. Index

Product information

  • Title: Continuous Architecture
  • Author(s): Murat Erder, Pierre Pureur
  • Release date: October 2015
  • Publisher(s): Morgan Kaufmann
  • ISBN: 9780128032855