Conflicts Identification among Stakeholders in Goal Oriented Requirements Engineering Process
Muhammad Suhaib, Sr. Full Stack Developer at T-Mark Inc., Tokyo, JP.
Manuscript received on September 16, 2019. | Revised Manuscript received on 24 September, 2019. | Manuscript published on October 10, 2019. | PP: 4926-4930 | Volume-8 Issue-12, October 2019. | Retrieval Number: L35571081219/2019©BEIESP | DOI: 10.35940/ijitee.L3557.1081219
Open Access | Ethics and Policies | Cite | Mendeley | Indexing and Abstracting
© The Authors. Blue Eyes Intelligence Engineering and Sciences Publication (BEIESP). This is an open access article under the CC-BY-NC-ND license (http://creativecommons.org/licenses/by-nc-nd/4.0/)
Abstract: Requirements Analysis are the most important part of Software Engineering for both System Application Development, and project requirements. Conflicts often arise during the requirements gathering and analysis phase. This research aims to identifying conflicts during requirements gathering phase in software development life cycle, Research, Development, and Technology converted the world into a global village. During requirements elicitation/gathering phase it’s very difficult to understand the main objective of stakeholders, after completion of requirements elicitation task final results are used for Software Requirements Specification (SRS), SRS is the highly important outcome of the requirements analysis phase. this is the foundation between the developers and stakeholders or customers, proposed methodology will be helpful to identify those conflicts in very easy manner during the initial phase of the project.
Keywords: Goal Oriented Requirements Analysis, Conflicts Identification Model, Requirements Analysis, Requirements Engineering.
Scope of the Article: Requirements Engineering