Incremental Software Architecture

Part FourEnd-State Architecture Verification

The process of end-state architecture verification comes last. After the architecture discovery, analysis, and decomposition activities have taken place, the verification process begins. This phase calls for a number of tasks devised to certify the enterprise grand-scale design. It is now time to substantiate the solidity of an end-state architecture. Without the verification process, no budgets should be allocated to support an unproven design.

When the verification process is launched to certify a computing environment that has been already operating in production, obviously there is no need for software development and integration activities. Certification tasks for an active environment like this ought to be conducted to spot troubling implementations and to correct them.

For new enterprise projects, however, an end-state architecture verification should include software development and integration of individual sections, pursued one at a time or even in parallel. Confirming that the software development efforts meet business and technical requirements is the ultimate proof that the design is reliable.

When pursuing the incremental software architecture approach, the traditional software development phase is no longer named construction; and the process of integration and delivery is no longer named transition. Here, they are part of the end-state architecture verification process.

Moreover, the incremental architecture method ...