The Elaboration Phase

The primary goal of the Elaboration phase is to prove the architecture for the system to be developed. The point is to ensure that the team can actually develop a system that satisfies the requirements, and the best way to do that is to build a end-to-end, working skeleton of the system called an "architectural prototype". This is actually a poor term for the concept because many people think that you throw prototypes away. Instead, your goal is to write high-quality, working software which meets several high risk (from a technical point of view) use cases to show that the system is technically feasible.

It is important to note that the requirements are not specified completely at this point. They are detailed only enough to understand architectural risks and to ensure that there is an understanding of the scope of each requirement so that subsequent planning can be carried out. Architectural risks are identified and prioritized; the significant ones are addressed during Elaboration. Addressing architectural risks may take several forms: research into similar system(s), a stand-alone test suite, a working prototype, etc. In most cases, a working prototype showcasing the architecture is completed. Your system level architecture should also reflect your overall enterprise architecture.

During Elaboration, the team is also preparing for the Construction phase. As the team gains a handle on the architecture of the system, they begin setting up the environment for Construction by purchasing hardware, software, and tools. From a project management point of view, staffing is addressed; resources are requested and/or hired. Plans for communication and collaborating are finalized (especially important if the team is to be physically distributed).

To exit the Elaboration phase the team must pass the Lifecycle Architecture (LCA) milestone. The primary issues addressed with this milestone is whether the team has shown that they have a working end-to-end prototype which shows the team has a viable strategy to build the system and that the stakeholders are prepared to continue funding the project. If the team passes this milestone the project moves to the Construction phase, otherwise the project may be re-directed or cancelled.

Work By Discipline

Discipline	Major Activities
Model	Identify technical risks Architectural modeling User interface prototyping
Implementation	Prove the architecture
Test	Validate the architecture Evolve your test model
Deployment	Update your deployment plan
Configuration Management	Put all work products under CM control
Project Management	Build the team Protect the team Obtain resources Manage risk Update your project plan Close out the phase
Environment	Evolve the working environment Tailor the process materials

Page last updated: May 13, 2006

This page is tailored with permission from Ambysoft Inc.'s Agile UP Product