Requirements Engineering for e-Business Systems: Integrating Jackson Problem Diagrams with Goal Modeling and BPM

Authors:
Steven J. Bleistein;Karl Cox;June Verner
Affiliations:
University of New South Wales / National ICT Australia;University of New South Wales / National ICT Australia;National ICT Australia
Venue:
APSEC '04 Proceedings of the 11th Asia-Pacific Software Engineering Conference
Year:
2004

Citing 0
Cited 8

Strategic alignment in requirements analysis for organizational IT: an integrated approach

Proceedings of the 2005 ACM symposium on Applied computing
Validating strategic alignment of organizational IT requirements using goal modeling and problem diagrams

Journal of Systems and Software
A contingency view of organizational infrastructure requirements engineering

Proceedings of the 2006 ACM symposium on Applied computing
Communicating requirements for business: UML or problem frames?

Proceedings of the 3rd international workshop on Applications and advances of problem frames
Editorial: A roadmap of problem frames research

Information and Software Technology
Deriving requirements from process models via the problem frames approach

Information and Software Technology
An approach to identify commonalities in web application engineering for a web content management system

Proceedings of the 12th International Conference on Information Integration and Web-based Applications & Services
Investigating Goal-Oriented Requirements Engineering for Business Processes

Journal of Database Management

Quantified Score

Hi-index	0.00

Visualization

Abstract

Jackson problem diagrams, goal modeling, and business process modeling (BPM) are employed in a requirements engineering approach that captures both business strategy and process requirements for e-business systems. As a means of linking abstract, high-level business requirements to low-level system requirements, we leverage the paradigm of projection in both problem diagrams and goal models simultaneously. We use Jackson context diagram to describe the business model domain context while goal modeling is used to represent both requirements and to describe the objectives of business strategy. Role activity diagrams are used to describe business processes in detail where needed. The feasibility of our approach is shown by a proof-of-concept case study.