Resolving Conflicts in Requirement Engineering Through Agile Software Development: A Comparative Case Study

Requirement engineering (RE) phase is the most important phase of software development life cycle (SDLC). To give the best possible product to the clients, the companies must identify and collect latest, complete, consistent, and clear requirements for the product. Poor requirements for any product will end up being the reiteration of the phases from the beginning, and it may results in an increase of cost and time. Every day clients are demanding something new, and if companies are not able to satisfy their requirements due to lack of requirement satisfaction of the clients, it may damage the reputation of the companies. In this paper, we have included some case studies regarding RE, conflicts in RE, and how to solve those conflicts which arise during the RE phase using Agile software development.

[1]  Ashish Sharma,et al.  A measure for modelling non-functional requirements using extended use case , 2016, 2016 3rd International Conference on Computing for Sustainable Global Development (INDIACom).

[2]  Omar El Beggar,et al.  CIM for data warehouse requirements using an UML profile , 2017, IET Softw..

[3]  Aspen Olmsted.  Secure software development through non-functional requirements modeling , 2016, 2016 International Conference on Information Society (i-Society).

[4]  Jörg Thomaschewski,et al.  Agile Requirements Engineering: A systematic literature review , 2017, Comput. Stand. Interfaces.

[5]  Adriano Bessa Albuquerque,et al.  Evaluation of an approach to define elicitation guides of non-functional requirements , 2017, IET Softw..

[6]  Kent Beck,et al.  Extreme Programming Explained: Embrace Change (2nd Edition) , 2004 .

[7]  Duaa Alkubaisy,et al.  A framework managing conflicts between security and privacy requirements , 2017, 2017 11th International Conference on Research Challenges in Information Science (RCIS).

[8]  P. D. D. Dominic,et al.  Investigating requirement engineering techniques in the context of small and medium software enterprises , 2016, 2016 3rd International Conference on Computer and Information Sciences (ICCOINS).

[9]  Atsushi Ohnishi,et al.  A Method for Verifying Non-Functional Requirements , 2017, KES.

[10]  Xi Zhang,et al.  Research on Agile Project Management with Scrum Method , 2009, 2009 IITA International Conference on Services Science, Management and Engineering.

[11]  Xiaoqing Frank Liu,et al.  Analysis of Conflicts among Non-Functional Requirements Using Integrated Analysis of Functional and Non-Functional Requirements , 2007, 31st Annual International Computer Software and Applications Conference (COMPSAC 2007).

[12]  Klaus-Dieter Thoben,et al.  Integrating Requirements Engineering for Different Domains in System Development – Lessons Learnt from Industrial SME Cases , 2017 .

[13]  Djamal Ziani,et al.  Software Requirements Conflict Identification: Review and Recommendations , 2016 .

[14]  Michel S. Soares,et al.  A Multi-Criteria Analysis of Techniques and Tools for Tracing Software Requirements , 2017 .

[15]  Rashmi Phalnikar.  Validation of Non-functional Requirements in Cloud Based Systems (Short Paper) , 2016, 2016 5th IEEE International Conference on Cloud Networking (Cloudnet).

[16]  Annie I. Antón,et al.  A legal cross-references taxonomy for identifying conflicting software requirements , 2011, 2011 IEEE 19th International Requirements Engineering Conference.

[17]  Barry W. Boehm,et al.  Conflicts and Synergies among Quality Requirements , 2017, 2017 IEEE International Conference on Software Quality, Reliability and Security Companion (QRS-C).