Principles of software engineering management
Principles of software engineering management
Software engineering (5th ed.)
Software engineering (5th ed.)
Classification of research efforts in requirements engineering
ACM Computing Surveys (CSUR)
Software Engineering: A Practitioner's Approach
Software Engineering: A Practitioner's Approach
Identifying Quality-Requirement Conflicts
IEEE Software
A field study of requirements engineering practices in information systems development
RE '95 Proceedings of the Second IEEE International Symposium on Requirements Engineering
Process-oriented complete requirement engineering cycle for generic projects
Proceedings of the International Conference and Workshop on Emerging Trends in Technology
Hi-index | 0.00 |
Varied frameworks of Requirement Engineering have been proposed by numerous research works majority of them focusing on the process as a whole. Few have managed to look beyond the basic framework, identifying complexities that lie within each activity of this crucial framework. One such complexity often faced by requirement engineers involves resolution of conflicts between the elicited set of requirements which are related to one another. This research provides with a conflict resolution strategy to overcome this complexity. OBJECTIVE-The objective of this research is to present a systematic approach towards resolving software requirement spanning from requirement elicitation to requirement analysis activity of the requirement engineering process. PROPOSED MODEL-Proposed in this study is a requirement "Conflict Resolution Strategy" (CRS) which employs requirement filter and an analysis strategy for resolving conflicts arising during software development. METHODOLOGY- This model is based on both empirical results that we carried out and our extensive research on requirement conflict resolutions and the area of Requirement Engineering. Our model is based on filtering the elicited requirement set into three sets of requirements according to their nature of implementation and then analyzing them by applying CRS methodology. CONCLUSION-Initial validation of the model indicates that the model is effective in identifying and resolving software conflicts that arise during a requirement engineering process.