The requirement is a basically need of the Client or Stakeholder. It needs to solve a problem or achieve an objective to the client. For giving better solution to them, we need to categorize the requirements. Based on the categorization, we can fulfill the expectations of their requirement. Here, the requirements arranging by class or group which is suitable to the need of the customer or client.
Consider customer search for a Car. The Car is a requirement for the Customer. There are different types of cars available in the market found it in different ways. He/she select the particular one as per their convenient or based on their need.
The car has attributes (Properties) and behavior. The behavior consists of the operation how it carries out. Attributes and operations taken together can be called as features.
Customer select the car (requirement) based on the categorization criteria’s:
Identity: Regd Number
State: Attributes – Attribute values
Colour – Blue
Passenger capacity – 4 or 5
Fuel – Diesel
Wheels – 4
Behaviour – Operations
Start, Stop and Move
Identity is the brand name or that identifies the car uniquely
Eg: Toyota or Number plate of the car.
Steps to follow to categorize the Requirements:
1. Gathering or Capturing the requirement
2. Look for Key words:
I. Sort the Requirement
II. Prioritize the requirement
III. Validate the requirements
3. Clarify with Stakeholders or Client
4. Put the requirement into particular set or Group
1. Gathering or Capturing the requirement:
The first step is to gathering the requirement from the client by using elicitation techniques such as Brain Storming, Reverse engineering, interviews, Workshop, Focus Group, Observation and Questionnaires.
2. Look for Key words:
Review the elicitation notes and look for keywords that define the client exact requirement. Here are the things we can categorize as follows:
I. Sort the Requirements:
Sort the requirements by removing duplicate requirements and grouping into similar functionality or into modules.
II. Prioritize the requirement:
Prioritize the requirement by using MoSCoW technique. This MoSCoW method can help Software Development to reach a common understanding with stakeholders on the importance they place on the delivery of each requirement.
MoSCoW stands for must, should, could and would:
M – Must have this requirement to meet the business needs of the client
S – Should have this requirement if possible, but project success does not rely or effect on it
C – Could have this requirement if it does not affect anything else in the requirement
W – Would like to have this requirement later, but it would not be delivered this time
III. Validate the requirements:
Validate the requirements by using FURPS technique. FURPS is an acronym representing a model for classifying software quality attributes (functional and non-functional requirements)
3. Clarify with Client or Stakeholders:
What we noted the requirement by performing different actions then once we needs to show to the client and confirm the same. This validation can help to prevent defects or misunderstandings.
4. Put the requirement into particular set or Group:
Document the requirements appropriately by what we gathered and functionality followed in the process. And put the requirement into particular set or Group