Software Architecture in Practice, 4th Edition
The fidelity of the system increases as extensions are added, or early versions are replaced by more complete versions of these parts of the software. In some cases, the parts may be low-fidelity versions or prototypes of the final functionality; in other cases, they may be surrogates that consume and produce data at the appropriate rates but do... See more
Paul Clements • Software Architecture in Practice, 4th Edition
enabling incremental development
If you want your implementation to conform to an architecture, then it must conform to the design decisions prescribed by the architecture. It must have the set of elements prescribed by the architecture, these elements must interact with each other in the fashion prescribed by the architecture, and each element must fulfill its responsibility to... See more
Paul Clements • Software Architecture in Practice, 4th Edition
architecture should prescibe constraints on implementation
The benefits of incremental development include a reduction of the potential risk in the project. If the architecture is for a family of related systems, the infrastructure can be reused across the family, lowering the per-system cost of each.
Rick Kazman • Software Architecture in Practice, 4th Edition
enabling incremental development
This point follows from the previous two: Architecture not only imbues systems with qualities, but does so in a predictable way.
Rick Kazman • Software Architecture in Practice, 4th Edition
the two earlier points are: 1) a system ability to meet desired or required quality attributes is mostly determined by its architecture 2) the ease of makcing chnages (modifiability) is a quality attrbute
The software development community is coming to grips with the fact that roughly 80 percent of a typical software system’s total cost occurs after initial deployment. Most systems that people work on are in this phase. Many programmers and software designers never get to work on new development—they work under the constraints of the existing... See more
Rick Kazman • Software Architecture in Practice, 4th Edition
once the architecture has been agreed upon, it becomes very costly—for managerial and business reasons—to significantly modify it. This is one argument (among many) for analyzing the software architecture for a large system before settling on a specific choice.
Paul Clements • Software Architecture in Practice, 4th Edition
influences on organizational structure
- If your system requires high performance, then you need to pay attention to managing the time-based behavior of elements, their use of shared resources, and the frequency and volume of their interelement communication.
- If modifiability is important, then you need to pay attention to assigning responsibilities to elements and limiting the
Paul Clements • Software Architecture in Practice, 4th Edition
Decisions at all stages of the life cycle—from architectural design to coding and implementation and testing—affect system quality. Therefore, quality is not completely a function of an architectural design. But that’s where it starts.
Paul Clements • Software Architecture in Practice, 4th Edition
This practice gained attention in the early 2000s through the ideas of Alistair Cockburn and his notion of a “walking skeleton.” More recently, it has been adopted by those employing MVP (minimum viable product) as a strategy for risk reduction.
Paul Clements • Software Architecture in Practice, 4th Edition
enabling incremental development