Specify the model requirement

Specifying the model requirement means to analyse, synthesise and refine the results got from the different elicitation techniques used to gather the requirement and design it according to requirement of the client.
It helps in creating the representation of those results which are gathered during the discussions during the specific elicitation techniques.
There are basically two understandings which need to be kept in mind
1. When the focus of the specifying and modelling activity is on understanding the need, the outputs are referred to as requirements
2. When the focus of the specifying and modelling activity is on a solution, the outputs are referred to as designs.
Here the model gives the descriptive and visual way to convey the information to the client in order to make the clear understanding.
Models also helps to confirm knowledge, identify the gap in the information that business analyst and to identify the duplicity of the information.
There are different formats methods out of which business analyst chooses:
1. Matrices: Business analyst uses matrix to gather the complex but uniform information, which can be broken into different elements. Matrices are also used for requirement traceability or for gap analysis and also matrices are used for requirement prioritising and recording attributes of requirement.
2. Diagram: To represent data visually, pictorially generally business analyst uses diagrams. There are some data which can not be represented in words there also business analyst uses diagram to make the clear understanding of data.
Diagrams can also be used to define boundaries for business domains, to categorize and create hierarchies of items, and to show components of objects such as data and their relationships.
To determine specific categories in one or more models also diagram is used
For Example: People and role models, models representing ‘why’ of a change, Activity flow, Capability, Data and information, Data flow Diagrams
Business analysts should use any combination of models best suited to meet stakeholder needs in a given context. Each modelling technique has strengths and weaknesses and provides unique insights into the business domain.
Next Step is to analyse the requirement: Complex requirements are broken down to simpler requirements so that it can be easily understood.
Requirements can be easily broken down for the following reasons:
• Changes that must in the organization be made so that the need is fulfilled.
• What must not change in the organization while the need is being fulfilled.
• Unnecessary parts or features of the solution.
• Constraints or assumptions that might affect parts of the solution.
After that Represent Requirements and Attributes , requirements should be detailed enough so that the characteristics of the requirements and the quality of the designs are fully understood.
The attributes of each requirement should be specified in such a way that they can be classified according to the Requirements Classification Schema. The Requirements Classification Schema splits requirements into business, stakeholder, solution and transition requirements.
The last step is to Implement the Appropriate Levels of Abstraction, the level of details in a requirement varies depending on the type of requirements and the target audience for those requirements.
The business analyst might need to produce different versions of the same requirements for different stakeholders.