Requirement engineering (RE) is the science and discipline concerned with analyzing and documentation requirements.
2. Requirement analysis:- The development and gathering of good quality requirements is the basic activity to develop quality software products. The requirement is then analyzed within the context of business requirements. After requirement elicitation, the requirements are analyzed to identify inconsistencies, defects, omissions, etc. Negotiation, agreement, communication, and prioritization, of the raw requirements, become important activities of requirement analysis.
3. Requirements documentation:- The end product of the first and second steps leads to the preparation of SRS becomes a foundation for the design of the software. A formal document is prepared after collecting requirements, which contains a complete description of the external behavior of the software system. The requirement is written so that they are meant not only to the customer but also to the designers in the development team.
4. Requirement review or requirement verification:- When the entire requirement is described and specified in the SRS, review or verification activities are carried out. It is the formula inspection of the requirement. The review and verification process is carried out to improve the quality of the SRS.
- Requirement engineering is a combination of two things first is understanding the requirement of customer and second is documenting the requirement.
- The requirement engineering and the requirement analysis both are the same things. So, we can say, that the requirement engineering is also called as requirement analysis.
- A requirement is a feature of the system or a description of somethings the system is capable of doing to full-fill the system's proper.
- The process to gather the software requirements from clients, analyze and document them is known as requirement engineering.
- Requirement engineering (RE) produces one large document written in natural language, containing a description of WHAT system will do without describing HOW it will do it. The large document which is developed by the developer is called SRS( Software Requirement Specification document ).
- Requirement engineering helps software engineers better understand the problem they are trying to solve.
- The requirement engineering ( RE ) process begins with inception, moves on to elicitation, negotiation, problem specification, and ends with a review or validation of the specification.
REQUIREMENT ENGINEERING CONSISTS OF THE FOLLOWING PROCESSES:-
- Requirement elicitation
- Requirements analysis
- Requirements documentation
- Requirement review
- Requirement management
1. Requirement elicitation:- This means to find out from the customer what the product objectives are, what is to be done, how the product fits into business needs, and how the product is used on a day to day basis. In simple words, it is to understand what a customer wants.
2. Requirement analysis:- The development and gathering of good quality requirements is the basic activity to develop quality software products. The requirement is then analyzed within the context of business requirements. After requirement elicitation, the requirements are analyzed to identify inconsistencies, defects, omissions, etc. Negotiation, agreement, communication, and prioritization, of the raw requirements, become important activities of requirement analysis.
3. Requirements documentation:- The end product of the first and second steps leads to the preparation of SRS becomes a foundation for the design of the software. A formal document is prepared after collecting requirements, which contains a complete description of the external behavior of the software system. The requirement is written so that they are meant not only to the customer but also to the designers in the development team.
4. Requirement review or requirement verification:- When the entire requirement is described and specified in the SRS, review or verification activities are carried out. It is the formula inspection of the requirement. The review and verification process is carried out to improve the quality of the SRS.
5. Requirement management:- Requirements management is the method of documenting, analyzing, tracing, prioritizing, and agreeing on needs so dominant amendment and act to relevant stakeholders. it's a never-ending method throughout a project.
Post a Comment
Post a Comment