Requirement Engineering: ​ The broad spectrum of tasks and techniques that lead to an understanding of requirements is called ​ requirements engineering
Inception: ​ At project inception, you establish a basic understanding of the problem, the people who want a solution, the nature of the solution that is desired, and the effectiveness of preliminary communication and collaboration between the other stakeholders and the software team.
Elicitation : To help overcome problems understanding, volatility, scope, you must approach requirements gathering in an organized manner.
Elaboration ​ This task focuses on developing a refined requirements model that identifies various aspects of software function, behavior, and information..
Negotiation ​ Customers, users, and other stakeholders are asked to rank requirements and then discuss conflicts in priority. Using an iterative approach that prioritizes requirements, assesses their cost and risk, and addresses internal conflicts, requirements are eliminated, combined, and/or modified so that each party achieves some measure of satisfaction.
Specification: A specification can be a written document, a set of graphical models, a formal mathematical model, a collection of usage scenarios, a prototype, or any combination of these.

T​ he specificity of requirements determines n​ _1​ / n_{​ 2}
n​ ₁​ is the number of requirements for which all reviewers have identical interpretations
n​ ₂​ is number of requirements in a specification

→ A project is a success if it meets the objectives of time, cost, technical and business.
Essential components:
1.Software size estimation
2.Effort estimation
3.Time estimation
4.Cost estimation