Fishbone Methodology: An Improved Goal-Oriented Framework for Requirements Engineering

 
 
 
  • Abstract
  • Keywords
  • References
  • PDF
  • Abstract


    Goals are a reasonable system intended for recognizing, arranging and mitigating software supplies. The word Goal is continuously used in Requirement Engineering (RE). Ended the historical ten years, the supplies manufacturing (RE) society consumes constantly extended hers acceptance then version of goal-oriented methods to equally useful and non-functional supplies (NFRs). Goal-Oriented obligation engineering (GORE) gives an imperceptible method aimed at elicitation, investigation, clarification & modification, pattern and modeling of requirements. Different methods of G.O.R.E are exists for these processes of requirement engineering based on confident underlying concepts and principles. Founded on our literature appraisal, we recognize that prevailing penalty area concerned with requirement elicitation procedure do not sustain to prioritize the supplies when the stakeholders view are frequently unclear and contain ambiguity. Therefore, we presented improved goal-oriented Approach called Fishbone Methodology for requirement engineering in this paper. The objective of this research article is to understand the needs of stakeholders and accordingly provide services to develop the increments of RE processes which results in building a prototype model of the software. We talk about goalmouths after the viewpoint of 2 themes: goal inspection and goal progression. Finally, our proposed method provides appropriate representation mechanisms to enhance stakeholder comprehension and facilitate communication between analysts and stakeholders.

     

     


  • Keywords


    Requirement Engineering, GORE, GBRAM, Goal Evaluation, Goal Analysis.

  • References


      [1] M. Bano, D. Zowghi, N. Ikram, "Systematic reviews in requirements engineering: A tertiary study", EmpiRE, pp. 9-16, 2014.

      [2] M. Daneva, D. Damian, A. Marchetto, O. Pastor, "Empirical researchmethodologies and studies in requirements engineering: How far did we come?", J Syst Software, vol. 95, pp. 1-9, 2014.

      [3] Zhu M X, Luo X-X, Chen X H, and Wu D D, “A Non-functional Requirements Tradeoff Model in Trustworthy Software” Information Science-Elsevier, Vol. 191, pp.61-75, 2012.

      [4] Thakurta R, “A Framework for Prioritization of Quality Requirements for Inclusion in a Software Project”, Software Quality Journal, Springer, 2012.

      [5] S. Ghanavati, D. Amyot, L. Peyton, "A systematic review of goal-oriented requirements management frameworks for business process compliance", RELAW, pp. 25-34, 2011.

      [6] Zickert F, “Evaluation of the Goal Oriented Requirements Engineering Methods KAOS”, American Conference on Information system”, pp.1-9, 2010.

      [7] Sadiq M, Shahid M, “Elicitation and Prioritization of Software Requirements”, International Journal of Recent Trends in Engineering, Vol. 2, No. 3, November, 2009.

      [8] P. Zave. Classification of Research Efforts in Requirements Engineering. ACM Computing Surveys, 29(4), 1997.

      [9] E. Yu, J. Mylopoulos. Why Goal-Oriented Requirements Engineering. Proc. 4th International Workshop on Requirements Engineering: Foundations of Software Quality, Pisa, Italy, June 1998.

      [10] G. Kotonya, I. Sommerville. Requirements Engineering: Processes and Techniques. Wiley, 1998.

      [11] Jennifer Horkoffand Fatma Başak Aydemir,”Goal-oriented requirements engineering: an extended systematic mapping study”, Requirement engineering, Springer, PP 1-28, 2017.

      [12] Alexei Lapouchnian ,”Goal-Oriented Requirements Engineering: An Overview of the Current Research”, text book printed 2005.

      [13] Shaistaparveen and Asif imam ,”analysis of different techniques of gore (goal oriented requirement engineering)”, International Journal of Advances in Electronics and Computer Science, ISSN: 2393-2835, Volume-3, Issue-8, Aug.-2016.

      [14] Ming-xun Zhu and Xin-Xing Luo,”A non-functional requirements tradeoff model in Trustworthy Software”, DOI: 10.1016/j.ins.2011.07.046, 2011.

      [15] https://pdfs.semanticscholar.org/cbd9/a5381256f02f1d49b035adc3de0b3ab557cf.pdf.

      [16] Anton A I”Goal based requirements analysis 2nd IEEE international conference on 'RE ICRE 1996 pp136-144.

      [17] Goal oriented Requirements Engineering-A Review”, Caine-2011, The International Conference on Computer Applications in Industry and engineering, Honolulu, Hawaii, United States.

      [18] Jonathan Lee ,Nien-Lin Xue , Kuo-Hsun Hsu , Yong-Yi Fangjang, Structuring Requirements Specifications through Goals Interactions, Proceedings of the 11th IEEE International Conference on Tools with Artificial Intelligence, p.61, November 08-10, 1999.

      [19] Kavakli, E. (1999) Goal-Driven Requirements Engineering: Modelling and Guidance, PhD Thesis, UMIST, 1999.

      [20] Ayala, C., Franch, X. “A process for Building Goal-Oriented COTS Taxonomies” LSIDepartment. Technical University of Catalunya. 2006. Report Number: LSI-06-7-R.

      [21] Jameelabano et.al “A Fishbone methodology using Goal oriented requirements engineering, “International Conference on Systematic, Cybernetics and Informatics, ICSCI-2008.


 

View

Download

Article ID: 23183
 
DOI: 10.14419/ijet.v7i4.19.23183




Copyright © 2012-2015 Science Publishing Corporation Inc. All rights reserved.