During analysis, with both use cases and software requirements, you start looking at a system to be implemented, and build both structural and behaviour models. The structural model evolves from that of the domain – it no longer represents concepts from the domain, but rather entities in a software solution. This is usually called the analysis model. Use cases and software requirements lead to the specification of what is expected from the system from the user perspective. The system operations show how this behaviour can be carried out by the entities chosen.
It is at this stage also that architectural decisions are taken in terms of the overall structure of the system.
Some artefacts involved in analysis are shown in Figure 11.