Requirement analysis also called requirements engineering, is a process of determining user expectations for a new or a modified product. These features, called Requirement, must be quantifiable, relevant, and detailed. In software engineering, such requirements are often called functional specifications.
Requirement analysis involves frequent communication with system users to determine specific features expectations, resolution of conflict or ambiguity in requirement as demanded by the various users or group of users, avoidance of feature creep, and documentation of all aspects of the project’s development process from start to finish.
What is Requirement?
A Requirement is a statement of what the system must do or what characteristics it needs to have. During the analysis phase, requirements are written from the perspective of the business person and they focus on what the system does. They focus on business user needs so they usually are called Business requirements (sometimes, user requirements).
Later in the design phase, and they describe how the system will be implemented. Requirements in the design phase are written from the developer’s perspective, and they usually are called System Requirement.
Types of Requirement
Different types of Requirement are as follows:
- System Requirement
- Functional Requirement
- Non Functional Requirement
- Domain Requirement
- User Requirement