What do you understand by term requirement? Can you differentiate between Requirement and need?

2 Ans. A Requirement is basically a need of the Client. The need or requirement will transform into a solution while taking various shapes and forms as progress in each stages of Software Development Life Cycle (SDLC).

Requirement 2 Ans. A Requirement is basically a need of the Client. The need or requirement will transform into a solution while taking various shapes and forms as progress in each stages of Software Development Life Cycle (SDLC).
Requirement serves as the foundation of system or system components. A requirement can be thought of something that is obligatory or demanded a property that is essential for the system to perform its functions.
Requirements can be described as a condition or capability a customer needs to solve a problem or achieve a target. For clarification purpose, a describer should always describe requirements. For example Business requirements, user requirements and functional requirements.
Types of Requirements: –
1. Business Requirements.
2. Stakeholder Requirements.
3. Solution Requirements.
• Functional Requirements
• Non-functional Requirements
4. Transition Requirements.

• Business Requirements: – These are the high-level statements of the goals, objectives or needs of the enterprise. The purpose of this requirement is to define the project and to get success criteria. This tells us why this project is needed, who will benefit from the given project, where it will be taking place and what standards are to be followed. Here we can also know what the business problem is, why the solution for this project is needed, what the scope of this project is and what are the rules and regulations to be followed in this project and what the key features are.
• Stakeholder Requirements: – These are the statements of the needs the particular stakeholder or class of stakeholder. It is often referred to as User requirement which tells us what to do with the system. User requirements are documented using texts, use case, scenarios and user stories. These are generally documented in user requirement document. These are generally signed by user community and employed in creating system requirement.
These are considered separate from system requirements because the users are unable to tell the entire requirements and the information they require. This whole responsibility falls on Business Analyst. Therefore, the BA carefully analyses and constructs requirements meeting the characteristics of the user.
• Solution Requirements: – These describe the characteristics of a solution that meets the business requirements and stakeholder requirements. These are what the developers use to build the system. Here, they use shall statements that describes what the system “shall do”.
• Functional Requirements: – This specifies something that the developer needs to build to deliver the solution.
• Non-Functional Requirements: – They capture conditions that do not directly relate to the behavior or functionality of the solution, but rather describe environmental conditions under which the solution must remain effective or qualities that the system must have They are also known as the quality or supplementary requirements. These can include requirements relating to capacity, speed, security, availability and the information architecture and presentation of the user interface.
• Transition Requirements: – These describe capabilities that the solution must have in order to facilitate transition from the current state of the enterprise to a desired future state. These requirements are elicit, analyzed, managed and communicated by performing tasks as for other requirements. The difference is not same in the methods defining them. But the inputs, nature of transiting requirements and in that they cease to be relevant once the existing solution is eleiminated.
Differentiating between need and requirements.
S.no. Need Requirement
1 These are the goals and objectives a business must achieve These are the things we need to do in order to achieve a need.
2 They can be divided into lower level, detailed requirement A need can have more than one requirement.
3 They are not specific. They are more specific and detailed.
4 It is vast and inclusive of requirement. They are limited in scope.

serves as the foundation of system or system components. A requirement can be thought of something that is obligatory or demanded a property that is essential for the system to perform its functions.

Requirements can be described as a condition or capability a customer needs to solve a problem or achieve a target. For clarification purpose, a describer should always describe requirements. For example Business requirements, user requirements and functional requirements.

Types of Requirements: –

1. Business Requirements.
2. Stakeholder Requirements.
3. Solution Requirements.

• Functional Requirements
• Non-functional Requirements

4. Transition Requirements.

• Business Requirements: – These are the high-level statements of the goals, objectives or needs of the enterprise. The purpose of this requirement is to define the project and to get success criteria. This tells us why this project is needed, who will benefit from the given project, where it will be taking place and what standards are to be followed. Here we can also know what the business problem is, why the solution for this project is needed, what the scope of this project is and what are the rules and regulations to be followed in this project and what the key features are.
• Stakeholder Requirements: – These are the statements of the needs the particular stakeholder or class of stakeholder. It is often referred to as User requirement which tells us what to do with the system. User requirements are documented using texts, use case, scenarios and user stories. These are generally documented in user requirement document. These are generally signed by user community and employed in creating system requirement.

These are considered separate from system requirements because the users are unable to tell the entire requirements and the information they require. This whole responsibility falls on Business Analyst. Therefore, the BA carefully analyses and constructs requirements meeting the characteristics of the user.

• Solution Requirements: – These describe the characteristics of a solution that meets the business requirements and stakeholder requirements. These are what the developers use to build the system. Here, they use shall statements that describes what the system “shall do”.
• Functional Requirements: – This specifies something that the developer needs to build to deliver the solution.
• Non-Functional Requirements: – They capture conditions that do not directly relate to the behavior or functionality of the solution, but rather describe environmental conditions under which the solution must remain effective or qualities that the system must have They are also known as the quality or supplementary requirements. These can include requirements relating to capacity, speed, security, availability and the information architecture and presentation of the user interface.
• Transition Requirements: – These describe capabilities that the solution must have in order to facilitate transition from the current state of the enterprise to a desired future state. These requirements are elicit, analyzed, managed and communicated by performing tasks as for other requirements. The difference is not same in the methods defining them. But the inputs, nature of transiting requirements and in that they cease to be relevant once the existing solution is eleiminated.

Differentiating between need and requirements.