The subresult Responsibility Analysis specifies the expected functionality of the system with respect to the functional and non-functional user requirements. It describes the required services and use cases of the system in a declarative way by stating what is expected without prescribing how this is accomplished. Contained are parts like Service Specifications, Class Diagrams, and a Data Dictionary.

The subresult Risk Analysis identifies and assesses the benefits and risks associated with the development of the system under consideration. In the context of componentware, this requires a Market Study with information about existing business-oriented solutions, systems, and components.

Note that Analysis usually not only covers functional and non-functional requirements, but also technical requirements restricting the technical architecture of the system to be built. While the functional requirements must be fulfilled by the Business Design main result, the non-functional and technical requirements must be compliant with the Technical Design main result. Furthermore, the Implementation must pass the System Test Cases.