Title -:The_Why_What_Who_When_and_How_of_Software_Requirements_Article Summary This article discusses the requirements acquisition process in the context of the why, what, who, when, and how. Firstly, elaborate why there should be a requirements elicitation process, secondly what kind of requirements and typologies need to be defined at various levels, who are the stakeholders and how to involve them in this process, when the elicitation process Requirements elicitation should occur during the requirements elicitation process. Software development life cycle and finally how to analyze, specify and validate the requirements during the requirements validation process using various techniques. Requirements are what customers, users, and suppliers want from a system. This must be identified and determined based on available information and agreed between the client and project stakeholders. Based on this, what functional requirements need to be implemented to support the customer's business needs, it is necessary to determine what these requirements can do to effectively perform the customer's business functions. Additionally, you need to determine what these non-functional requirements can do to add value to your customers, as non-functional requirements improve the overall user experience. Also, what are the limitations in implementing the requirements need to be identified by the technical team based on the technical limitations, minus Return on Investment (ROI) due to changing trends, etc. Business requirements are generally stated in terms of the objectives of the client or organization requesting software development. User requirements examine the functionality of the software product from the perspective of the various users of that product. They define what the software should do in... middle of the paper......essed. Also I found his approach based on the basic business requirements first, so taking them as input and finalizing the user requirements and then taking them input again and finalizing the non-functional requirements is a somewhat impractical situation. According to “Software Requirements Memory Jogger,” (Gottesdiener, 2005), these are parallel activities and it would be more effective if feedback from each of these areas were taken into account to determine and define the requirements rather than considering each as a dependency to complete the other process. There were also no requirements validation techniques mentioned in the article. Since requirements verification is absolutely necessary, this aspect should be addressed further in this article. Article Citation 3000 Custer Road, Suite 270, PMB 101 Plano, TX [email protected]