Software Engineering PS (WS2000/2001)
© Copyright 2000, Schwaiger Roland
Elaboration PhaseReferenzen: 10
The purpose of the elaboration phase is to analyze the problem domain, establish a sound architectural foundation, develop the project plan and eliminate the highest risk elements of the project. Architectural decisions have to be made with an understanding of the whole system: its scope, major functionality and nonfunctional requirements s.a. performance requirements.
In the elaboration phase, an executable architecture prototype is built in one or more iterations, depending on the scope, size, risk and novelty of the project. This effort should at least address the critical use cases identified in the inception phase, which typically expose the major techical risks of the project. While an evolutionary prototype of a production-quality component is always the goal, this does not exclude the development of one or more exploratory, throw-away prototypes to mitigate specific risks s.a. design/requirements trade-offs, component feasibility study, or demonstrations to investors, and end-users.
The outcome of the elaboration phase is:
At the end of the elaboration phase is the second important project milestone, the Lifecycle Architecture Milestone. At this point, you examine the detailed system objectives and scope, the choice of architecture, and the resolution of the major risks. The main evaluation criteria for the elaboration phase involves the answers to these questions.
last modified Friday, 28-Sep-2001 09:38:48 CEST email@example.com