Within this process we define the high-level functional and supplemental requirements, and determine the scope and prioritize its elements. We use workshop technique to conduct these activities. The workshops used in this phase are high-level facilitated workshops where a lot of brainstorming occurs. Therefore, techniques that allow this kind of activity can be successfully used (for example, brown bag sessions).
In the Requirements Analysis process, the Business Requirements are captured and analyzed and the functional requirements are transformed and structured into a Business Use Case Model.
Use Case Models are used to document the requirements of the system in details, for the business as well as the project team. During the Inception phase, you should not describe every use case in details, this is neither necessary nor reasonable, as many use cases will evolve through the phases. The users should be involved in developing the Business Use Case Model, as they can provide the best input to give a more precise understanding of the requirements. It might be useful to use workshops to collect the missing pieces in the requirements that we need to form the Business Use Case Model. It all depends on the level of details and accuracy of the requirements captured in the Business Requirements process.
During the Design process, the system is shaped and formed to meet functional and supplemental requirements. At this stage the focus is on an architectural level. The architecturally significant use cases that have been analyzed in the Analysis process are taken further to design architectural significant classes, software components and their interfaces. We will also create an initial Logical Database Design, applying the rules and principles of relational system design.