Architecture for Continuous Delivery
Architectural Quality Factors Revisited... for CD
In an initial post on architectural quality factors, we describe the...
availability, modifiability, performance, security, testability, and usability
... of software intensive systems [Bass et al, 2013].
The goal of Continuous Delivery is for systems to be able to 'continuously demonstrate their state of production readiness' [ . . .
Molly Dishman and Martin Fowler
An interesting keynote from Molly Dishman and Martin Fowler, on the changing role of architecture.
- Diffusion of Architectural Responsibility
- We no longer need architects, technical leads are doing the architecture?
Q. How do we make sure that 'architecture' is still happening?
It is important to pay that continuous . . .
Testability Quality Factor for Continuous Delivery in Digital Systems
TL;DR; When we architect systems using automated testing and test-first approaches, we quickly see testability constraints move to our system boundary. Low testability quality factor in external services is a key constraint on our ability to continuously prove our system is in a state of production readiness. We require external systems to . . .
Manual Test Teams and Testability Architectural Debt
The architecture of specification subsystems has always been critical to quality factors like cycle time -
Industry estimates indicate that between 30 and 50 percent (or in some cases, even more) of the cost of developing well-engineered systems is taken up by testing. If the software architect can reduce this cost, the payoff is large. . . .
This describes the concept of a functional-only architectural focus, an extreme example, where architects consider only their functional domain. Here, only half of the system being built is actually being consciously 'designed', the remainder is being evolved by development teams (who may or may not know how to architect large suites . . .
Service-Oriented Architecture and Architectural Quality Factors
In the context of Service-Oriented Architecture, early work from [O'Brien et al, 2005] discusses the importance of quality attributes -
Software architecture is the bridge between mission/business goals and a software-intensive system. Quality attribute requirements drive software architecture design. Choosing and designing an . . .