A Goal Oriented Requirement Engineering Research Structure

Shaik Subhani¹ , K.P. Suryateja²

Section:Research Paper, Product Type: Journal-Paper
Vol.5 , Issue.10 , pp.39-44, Oct-2019

Online published on Oct 31, 2019

Copyright © Shaik Subhani, K.P. Suryateja . This is an open access article distributed under the Creative Commons Attribution License, which permits unrestricted use, distribution, and reproduction in any medium, provided the original work is properly cited.
 

View this paper at   Google Scholar | DPI Digital Library

XML View     PDF Download

How to Cite this Paper

Abstract :
Requirements engineering is a sub regulation of software engineering and critical phase in the overall software engineering life cycle. A number of improvements have been made to process the requirements engineering process. Most of them attempted to bond these requirements to goals. In this paper, we present major research works done in Goal-Oriented Requirement Engineering. It offers an incremental approach for elicitation, analysis, elaboration & refinement, specification and modeling of requirements. The assets of GORE claimed in the literature are presented. Several goal-oriented methods have been proposed and a comparative study is made, which handle as a pilot for readers to choose a suitable goal-oriented technique to accomplish the requirements engineering needs

Key-Words / Index Term :
Requirements, GORE, Elicitation, Software Product, Goals, Refinement

References :
[1] A. van Lamsweerde, "Requirements Engineering in the Year 00: A Research Perspective", Keynote Paper for ICSE’2000 - 22nd International Conference on Software Engineering, Limerick, ACM Press, 2000.
[2] Axel van Lamsweerde, “Goal-Oriented Requirements Engineering: A Roundtrip from Research to Practice‖”, 12th IEEE International Requirements Engineering Conference (RE’04), Kyoto, Japan, 2004.
[3] Alexei Lapouchnian “Goal-Oriented Requirement Engineering: An Overview of the Current Research‖, University of Toronto, 2005.
[4] Kavakli, E.,”Goal-Oriented Requirements Engineering: A Unifying Framework: Requirements Engineering”, Vol. 6 No. 4. pp. 237-251, 2002.
[5] I. Sommerville, “Software Engineering” 7th Edition, Addison-Wesley, 2004.
[6] Bashar Nuseibeh & Steve Easterbrook "Requirements Engineering: A Roadmap", 2000.
[7] Klaus Pohl "The Three Dimensions of Requirements Engineering"2003.
[8] K. Yue, “What Does It Mean to Say that a Specification is Complete?”, Proc. IWSSD-4, Fourth International Workshop on Software Specification and Design, Monterey, 1987.
[9] Robinson, W.N., “Integrating Multiple Specifications Using Domain Goals”, Proc. IWSSD-5 - 5th Intl. Workshop on Software Specification and Design, IEEE, , 219-225, 1989.
[10] P. Zave,”Classification of Research Efforts in Requirements Engineering”, ACM Computing Surveys, 29(4), 1997.
[11] Subhani Shaik et al.,”A Comparative Study Based on Optimization Techniques for Software Cost Estimation”, International Journal of Innovative Research in Computer and Communication Engineering, Vol. 4, Issue 10, 2016.
[12] Megha Jain , Abhikrati Shukla , Swati Gupta,” A Comparative Study of Financial Performance of Maruti Suzuki India Ltd & Tata Motors Ltd”, International Journal of Scientific Research in Multidisciplinary Studies, Vol.5, Issue.9, pp.75-85, 2019.