This is the second part in continuation to my earlier post Goal Management – Goal partitioning for Inception phase
While the team identifies requirements in the inception phase and also find out the business risk of the project during the same, the elaboration phase is the time when the technical risks are supposed to be unearthed and mitigated. So definitely the goal in this phase is to elaborate the system technically. This includes:
* To elaborate the system's technical requirements
* To establish the architecture (establish different views of the system).
* To establish the QOS and all non-functional requirements
* To take judgemental approach to meet the non-functional requirements optimally
* To make sure that the change in the mix of the factors of non-functional requirements can be done in future
* To unearth any possible technical bottlenecks or hurdles (by taking up proof of concepts)
The Elaboration phase is the second of six phases — Inception, Elaboration, Construction, Transition, Production , and Retirement — that a system experiences throughout its complete lifecycle. This phase has several goals:
* To produce a proven, architectural baseline for your system
* To evolve your requirements model to the "80% completion point"
* To develop a coarse-grained project plan for the entire Construction phase
* To ensure that the critical tools, processes, standards, and guidelines have been put in place for the Construction phase
* To understand and eliminate the high-priority risks of your project