4. Composition
Your software system’s reason for being is to service the business by addressing its customers’ requirements and needs. The previous two chapters discussed how to decompose the system into its components to create its architecture. The decomposition into components is inherently a static layout of the system, like a blueprint. During execution, the system is dynamic, and the various components interact with each other. But how do you know the composition of these components at run-time adequately satisfies all the requirements? Validating your design has to do with requirements analysis, system design, and your added value as the architect. Design validation and composition, as you will see, are intimately related. You can and ...
Get Righting Software now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
