Goal-directed requirements acquisition
6IWSSD Selected Papers of the Sixth International Workshop on Software Specification and Design
The Unified Modeling Language reference manual
The Unified Modeling Language reference manual
Problem frames: analyzing and structuring software development problems
Problem frames: analyzing and structuring software development problems
A UML-Based Design Methodology for Real-Time and Embedded Sytems
Proceedings of the conference on Design, automation and test in Europe
Identifying Domain Context for the Intentional Modelling Technique MAP
DEXA '07 Proceedings of the 18th International Conference on Database and Expert Systems Applications
Aligning the Map Requirements Modelling with the B-method for Formal Software Development
APSEC '07 Proceedings of the 14th Asia-Pacific Software Engineering Conference
Three integration approaches for map and B-SCP requirements engineering techniques
Proceedings of the 2008 ACM symposium on Applied computing
Hi-index | 0.00 |
Requirements engineering describes how an IT implementation will support business functions. Most IT systems are operational in nature and typical requirements engineering techniques and methods are usually adequate in capturing and documenting the requirements for such systems. Jackson's problem frames is a technique that is suitable for straightforward IT systems descriptions. However, when an organization deploys an IT system that must deliver upon its competitive business strategy, then an appropriate technique or method needs to be used to capture that business strategy in order to connect it to business-critical IT requirements. Here we provide an overview of the use and adaptation of problem frames to connect requirements to business strategy. We found that a simplification of the problem frames notation was necessary and that to be really effective, we had to integrate problem fames with goal modelling and Map, a method that helps describe the evolution of IT over time.