Continuous Integration

Iterative development produces the architecture first, allowing integration to occur as the verification activity of the design phase and enabling design flaws to be detected and resolved earlier in the life cycle. This approach avoids the big-bang integration at the end of a project by stressing continuous integration throughout the project. Figure 15-1 illustrates the differences between the progress profile of a healthy modern project and that of a typical conventional project, which was introduced in Figure 1-2. The architecture-first approach forces integration into the design phase through the construction of demonstrations. The demonstrations do not eliminate the design breakage; instead, they make it happen in the engineering stage, when it can be resolved efficiently in the context of life-cycle goals. The downstream integration nightmare, late patches, and shoe-horned software fixes are avoided. The result is a more robust and maintainable design.

Figure 15-1. Progress profile of a modern project
Table 15-1. Differences in workflow cost allocations between a conventional process and. a modern process

Was this article helpful?

0 0
Project Management Made Easy

Project Management Made Easy

What you need to know about… Project Management Made Easy! Project management consists of more than just a large building project and can encompass small projects as well. No matter what the size of your project, you need to have some sort of project management. How you manage your project has everything to do with its outcome.

Get My Free Ebook

Post a comment