This paper is giving an overview of the process of requirement analysis for software development. Here I have discussed about key parts in requirement analysing, gathering relevant materials, functional analysis and allocations, how to improve and make a quality process and also document development as well and many more which relates to requirement analysis process. The scope of this study is not a generalized approach but rather discuss through specific cases such as like Dutch flower case. It describes the main areas of requirement process in practice, and highlights. I hope that readers will find this paper useful in guiding them toward the knowledge and resources they needed.
References
[1]
System Engineering Fundamentals, Defense Acquisition University, Fort Belvoir, Virginia, 2001, 31-45.
[2]
Ian Somerville, Software Engineering 7, Pearson education Inc, 29-36, 94-100.
[3]
Sommerville, I. and Sawyer, P. (1997) Requirements Engineering: A Good Practice Guide. John Wiley & Sons, Chichester.
[4]
Bourque, P. and Richard, E. (1999) Guided to the Software Engineering Body of Language. IEEE Computer Society Press, CA, 1-15.
Nuseibeh, B. and Easterbrook, S. (2000) Requirement Engineering: A Road Map. ICSE’00 Proceedings of the Conference on the Future of Software Engineering, Limerick, 4-11 June 2000, 35-46. https://doi.org/10.1145/336512.336523
[7]
Naik, S. and Tripathy, P. (2008) Software Testing and Quality Assurance: Theory and Practice. Wiley-Spektrum. https://doi.org/10.1002/9780470382844
[8]
Chung, L., Nixon, B., Yu, E. and Mylopoulos, J. (2000) Non Functional Requirements in Software Engineering. Kluwer Academic Publishers, Boston.
https://doi.org/10.1007/978-1-4615-5269-7
[9]
Van Heck, E. and Ribbers. (1997) Experiences with Electronic Auctions in the Dutch Flower Industry. Electronic Markets, 29-34.
https://doi.org/10.1080/10196789700000046
[10]
Moore, J.W. (2006) The Road Map to Software Engineering: A Standards-Based Guide. 1st Ed., Wiley-IEEE Computer Society Press.
