The Why, What, Who, When and How of Software Requirements

2000 Words4 Pages

Title -:The_Why_What_Who_When_and_How_of_Software_Requirements

Article summary

This article discuss about a requirement elicitation process in the context of why, what, who, when and how. First, elaborating why should be there a requirement elicitation process, secondly what sort of requirements and types need to be defined at various levels, who are the stakeholders and how to get them involved in this process, When the requirement elicitation process should happen during the Software development life cycle and Finally how to analysis, specifying , validate requirements during requirement validation process by using various techniques .

Requirements are what the customers, users and suppliers wants from a system. This needs to be identified and determined based on the available information and agreed by customer and project stakeholders. Based on this what functional requirements must be implemented to support client business needs , what can these requirements do to effectively perform client’s business functions must be determined. Further what those non functional requirements can do to add any value to clients must be determined, since non functional requirements improve the overall user experience ,Moreover what are the limitations in implementing the requirements must be identified by the technical team based on technical limitations, less Return of Investment(ROI) due to changing trends etc.

Business requirements are typically stated in terms of the objectives of the customer or organization requesting the development of the software. User requirements look at the functionality of the software product from the perspectives of the various users of that product. They define what the software has to do in...

... middle of paper ...

...essed.

Moreover I found his approach of baseline business requirement first then take that as an input and finalize user requirements and then take that as an input again and finalize non functional requirements is somewhat impractical situation. As per “Software Requirements Memory Jogger” ,(Gottesdiener, 2005), these are parallel activities and it would be more effective if feedback from each of these areas is taken to determine and baseline the requirements rather than considering each as a dependency to complete the other process.

Moreover there were no requirement validation techniques mentioned in the article. Since verification of requirement is absolutely required , this aspect should have addressed further in this article.

Article citation

3000 Custer Road, Suite 270, PMB 101

Plano, TX 75075

lwestfall@westfallteam.com

www.westfallteam.com

Open Document