Table of Contents
Analysis is the process of taking the “customer” requirements and re-casting them in the language of, and from the perspective of, a putative solution.
We are not actually trying the flesh out the detailed solution at this stage. That occurs in the Design Phase (see Chapter 5, Design).
Unlike the boundary between Requirements and Analysis Phases, the boundary between Analysis and Design Phases is inherently blurred. The key is that analysis should define the solution no further than is necessary to specify the requirements in the language of the solution. The artifacts in Analysis generally represent a high level of abstraction.
Once again the recursive, and iterative nature of our process means we will come back to the Analysis phase many times in the future.