ScienceDirect® Home Skip Main Navigation Links
You have guest access to ScienceDirect. Find out more.
 
Home
Browse
My Settings
Alerts
Help
 Quick Search
 Search tips (Opens new window)
    Clear all fields    
Information and Software Technology
Volume 48, Issue 9, September 2006, Pages 846-868
Special Issue Section: Distributed Software Development
 
Font Size: Decrease Font Size  Increase Font Size
 Abstract - selected
Article
Purchase PDF (1033 K)

 
 
 
Related Articles in ScienceDirect
View More Related Articles
 
View Record in Scopus
 
doi:10.1016/j.infsof.2005.12.001    How to Cite or Link Using DOI (Opens New Window)
Copyright © 2006 Elsevier B.V. All rights reserved.

B-SCP: A requirements analysis framework for validating strategic alignment of organizational IT based on strategy, context, and process

Steven J. Bleisteina, b, Corresponding Author Contact Information, E-mail The Corresponding Author, E-mail The Corresponding Author, Karl Coxa, b, E-mail The Corresponding Author, June Vernera, b, E-mail The Corresponding Author and Keith T. Phalpc, E-mail The Corresponding Author

aEmpirical Software Engineering Research Program, National ICT Australia, Sydney 1430, Australia bSchool of Computer Science and Engineering, University of New South Wales, Sydney 2052, Australia cEmpirical Software Engineering Research Group, Bournemouth University, Bournemouth, UK

Received 17 June 2005; 
revised 27 September 2005; 
accepted 1 December 2005. 
Available online 30 January 2006.

Purchase the full-text article



References and further reading may be available for this article. To view references and further reading you must purchase this article.

Abstract

Ensuring that organizational IT is in alignment with and provides support for an organization's business strategy is critical to business success. Despite this, business strategy and strategic alignment issues are all but ignored in the requirements engineering research literature. We present B-SCP, a requirements engineering framework for organizational IT that directly addresses an organization's business strategy and the alignment of IT requirements with that strategy. B-SCP integrates the three themes of strategy, context, and process using a requirements engineering notation for each theme. We demonstrate a means of cross-referencing and integrating the notations with each other, enabling explicit traceability between business processes and business strategy. In addition, we show a means of defining requirements problem scope as a Jackson problem diagram by applying a business modeling framework. Our approach is illustrated via application to an exemplar. The case example demonstrates the feasibility of B-SCP, and we present a comparison with other approaches.

Keywords: Requirements engineering; Strategic alignment; Business strategy; Business modeling; Goal modeling; Business process modeling; Jackson problem frames

Article Outline

1. Introduction
2. Overview of goal modeling, Jackson problem diagrams, and role activity diagrams
2.1. Organizational goal modeling notation
2.2. Overview of problem diagrams
2.3. Role activity diagrams (RADs)
3. The B-SCP framework for strategic alignment
4. Building a requirements model using the B-SCP framework
4.1. Strategy: the goal model
4.2. Context: Jackson context diagrams and integrating strategy
4.3. Refining strategy and context
4.4. Linking process models to goal models and context diagrams
4.5. B-SCP summary
5. Case example: Seven-Eleven Japan
5.1. SEJ case overview
5.2. SEJ strategy: business model goals and context
5.2.1. Domain DA and requirements set RA
5.2.2. Domain DB and requirements set RB
5.2.3. Domain DC and requirements set RC
5.2.4. Domain DD and requirements set RD
5.3. Validating strategic alignment
5.3.1. Validating requirements against strategy via contribution links
5.3.2. Cross-referencing the process model
5.3.2.1. Collecting consumer purchase and profile data, and the checkout process
5.3.2.2. Decision support and demand forecasting process
5.3.3. Summary of process models
6. Discussion and evaluation
6.1. Comparison with other approaches
6.1.1. i* Framework
6.1.2. Information Engineering
6.1.3. Business modeling with UML
6.1.4. e3-Value
6.2. A note on complexity and the relevance of RE research
7. Conclusion
References













Information and Software Technology
Volume 48, Issue 9, September 2006, Pages 846-868
Special Issue Section: Distributed Software Development
 
Home
Browse
My Settings
Alerts
Help
Elsevier.com (Opens new window)
About ScienceDirect  |  Contact Us  |  Information for Advertisers  |  Terms & Conditions  |  Privacy Policy
Copyright © 2008 Elsevier B.V. All rights reserved. ScienceDirect® is a registered trademark of Elsevier B.V.