Requirements engineering: a roadmap
Proceedings of the Conference on The Future of Software Engineering
Problem frames: analyzing and structuring software development problems
Problem frames: analyzing and structuring software development problems
Eliciting gaps in requirements change
Requirements Engineering
Journal of Systems and Software
A contingency view of organizational infrastructure requirements engineering
Proceedings of the 2006 ACM symposium on Applied computing
Towards evolution of strategic IT requirements
Proceedings of the 2007 ACM symposium on Applied computing
Identifying Domain Context for the Intentional Modelling Technique MAP
DEXA '07 Proceedings of the 18th International Conference on Database and Expert Systems Applications
Modelling variability in requirements with maps
ADVIS'04 Proceedings of the Third international conference on Advances in Information Systems
Integrating B-SCP and MAP to manage the evolution of strategic IT requirements
Information and Software Technology
Problem frames and business strategy modelling
Proceedings of the 3rd international workshop on Applications and advances of problem frames
A framework for software requirements engineering
SEPADS'09 Proceedings of the 8th WSEAS International Conference on Software engineering, parallel and distributed systems
Hi-index | 0.00 |
Integration of requirements engineering techniques has been common and proven beneficial. Map is a strategy-driven modelling technique that elicits requirements in terms of intentions and strategies. B-SCP is an approach to address alignment between requirements and business strategy. To address the problem of strategic requirements evolution in B-SCP, we have previously proposed the possibility of integrating Map with B-SCP. In this paper, we present three integration approaches for Map and B-SCP and evaluate their usefulness for two case studies: Seven Eleven Japan (SEJ) and CommSec Australia. SEJ presents an enterprise problem domain, while CommSec Australia presents a simple application domain. We find that each integration approach has advantages and disadvantages. We also conclude that the usefulness of each integration approach varies depending on the complexity of application domain and the nature of modelled requirements.