The Solution Design phase builds on the analysis model, and adds detail related to the eventual implementation of the application. In this phase, solution constructs are added, but in each, the solution constructs are built on the existing participants as defined in the analysis model. Consequently, each analysis participant will have at least one corresponding design entity. Additional entities and behaviors will be added as required for infrastructure and solution-specific entities.

    We have found that at least two iterations through this phase are beneficial. The first pass (high-level design) introduces the primary solution constructs, and begins to map the analysis behaviors into patterns of implementation. The second pass (detailed design) introduces low-level details required to guide the actual implementation. The multiple passes are identified by those subsystems which do not yet have enough detail to move on to implementation. Note that all details are NOT specified, as the source code is expected to contain the greatest level of detail.

(select any activity or artifact for more information)