In the Visualize Phase, everse analyzes the client's problem, establishes a sound architectural foundation, revises the project plan, and eliminates the highest risk elements of the project.
While a project must always accommodate changes, this phase ensures the architectural requirements and plans are stable enough, and the risks are sufficiently mitigated, to determine the cost of and the schedule for solution development.
The outcomes of the Visualize Phase include:
- A use-case model.
- Supplementary and non-functional requirements.
- A Software Architecture Description.
- A revised risk list.
- A revised Project Schedule.
Throughout the Visualize Phase, everse uses its Client Extranet to present the solution to the client and apply feedback to future iterations. Both everse and the client validate all aspects of the phase before proceeding to solution design and development.