Access the full text.
Sign up today, get DeepDyve free for 14 days.
(2003)
Unified Modeling Language (UML), specification version 1
G. Sindre, A. Opdahl (2001)
Templates for Misuse Case Description
Elayne Coakes, Dianne Willis, C. Sanger, D. Diaper, R. Lloyd-Jones (2000)
The New Sociotech: Graffiti on the Long Wall
(2002)
Using norm analysis to derive use cases from business processes
G. Vickers (1987)
Policymaking, communication, and social learning
(1987)
Policymaking, Communication, and Social Learning, Transaction Books
E. Yu, J. Mylopoulos (1996)
Using goals, rules, and methods to support reasoning in business process reengineering1994 Proceedings of the Twenty-Seventh Hawaii International Conference on System Sciences, 4
(1990)
Soft System Methodology in Action
(2002)
Using norm analysis to derive use cases from business processes Modelling the regulative role
G. Weinberg (1975)
An Introduction to General Systems Thinking
R. Dorf, M. Raitanen (1997)
The Balanced Scorecard: Translating Strategy Into ActionProceedings of the IEEE, 85
I. Alexander (2002)
On Abstraction in ScenariosRequirements Engineering, 6
(2001)
Draft Specification of the Goal-oriented Requirement Language
Kecheng Liu (2002)
Coordination and Communication Using Signs
V. Glushkov (1966)
Introduction to Cybernetics.
P. Kueng, P. Kawalek (1997)
Goal-based business process models: creation and evaluationBus. Process. Manag. J., 3
I. Alexander (2002)
Modelling the Interplay of Conflicting Goals with Use and Misuse Cases
K. Boulding, G. Vickers (1971)
Value Systems and Social Process.Political Science Quarterly, 86
(2002)
2002d), “On abstraction in scenarios
A. Lamsweerde (2001)
Goal-oriented requirements engineering: a guided tourProceedings Fifth IEEE International Symposium on Requirements Engineering
(2002)
Towards automatic traceability in industrial practice
Gil Regev (2003)
A Systemic Paradigm for Early IT System Requirements Based on Regulation Principles: The Lightswitch Approach
E. Mumford (1995)
Reengineering the Corporation: A Manifesto for Business RevolutionEuropean Journal of Information Systems, 4
(1992)
Object-oriented Software Engineering: A Use Case Driven Approach, Addison-Wesley
A. MacLean, R. Young, T. Moran (1989)
Design rationale: the argument behind the artifact
A. Antón (1997)
Goal identification and refinement in the specification of software-based information systems
(1998)
Strategy Safary – The Complete Guide through the Wilds of Strategic Management, Prentice-Hall, London
J. Conklin, A. Selvin, S. Shum, M. Sierhuis (2001)
Facilitated hypertext for collective sensemaking: 15 years on from gIBISProceedings of the 12th ACM conference on Hypertext and Hypermedia
A. Lamsweerde, Emmanuel Letier (2000)
Handling Obstacles in Goal-Oriented Requirements EngineeringIEEE Trans. Software Eng., 26
I. Jacobson, Magnus Christerson, P. Jonsson, Gunnar Övergaard (1993)
Object-oriented software engineering - a use case driven approach
(1971)
World Dynamics, 2nd ed., Wright-Allen
M. Ben-Menachem (2001)
Writing effective use casesACM SIGSOFT Softw. Eng. Notes, 26
(2002)
Coordination and Communication Using Signs: Studies in Organizational Semiotics, Kluwer, Dordrecht
A. Dardenne, A. Lamsweerde, S. Fickas (1993)
Goal-Directed Requirements AcquisitionSci. Comput. Program., 20
Gil Regev, A. Wegmann (2002)
Regulation Based Linking of Strategic Goals and Business Processes
(2001)
Writing Effective Use
J. Forrester, J. Warfield (1973)
World dynamics
(2003)
Scenario Plus
S. Robertson, J. Robertson (1999)
Mastering the Requirements Process
G. Weinberg, Daniela Weinberg (1988)
General principles of systems design
BPMJ
(1975)
An Introduction to General Systems
(2002)
Draft Specification of the Use Case Map Notation
(1999)
Mastering the Requirements Process, Addison-Wesley, Reading MA
I. Alexander (2002)
Initial industrial experience of misuse cases in trade-off analysisProceedings IEEE Joint International Conference on Requirements Engineering
G. Sindre, A. Opdahl (2000)
Eliciting security requirements with misuse casesRequirements Engineering, 10
(2002)
2002b), “Towards automatic traceability in industrial practice
(1968)
Value Systems and Social Process, Tavistock Publications, London
(2003)
The forty recommendations
Purpose – The purpose of this paper is to provide a framework for understanding value‐added and abuse prevention activities in business processes. Design/methodology/approach – The paper considers business processes as a regulation mechanism that an organization uses to survive and flourish in its environment. It proposes a theoretical framework based on the concept of homeostasis, the maintenance of identity in a changing world. In this framework the paper classifies business processes into three levels (strategic, operational, regulative) and analyse the relationships between these three levels. Based on this framework, the paper extends the “Use and Misuse Cases” technique to support modelling of value‐added and abuse prevention activities. Findings – The main finding is the importance of considering business processes as regulation mechanisms. Traditionally, business processes are analysed through the goals they are designed to achieve. This paper analyses what the organization aims at maintaining. This makes it possible to explicitly model the potential abuses (threats) to business processes and their associated corrective measures (regulative processes). Practical implications – Use of this framework enables process designers to explicitly model abuse prevention activities, even though they are traditionally considered as not participating in customer value creation. This should lead to better‐fitting business processes. Originality/value – The framework is useful because it provides a theoretical justification for the value creation and abuse prevention activities that can be found in business processes. The three levels that we use to analyse business processes (strategic, operational and regulative) constitute an innovation in business process modelling where only two levels (strategic and operational) have been considered thus far. Few, if any, business process theoretical frameworks provide this kind of rationale for abuse prevention activities.
Business Process Management Journal – Emerald Publishing
Published: Dec 1, 2005
Keywords: Organizational processes; Modelling; Systems theory
Read and print from thousands of top scholarly journals.
Already have an account? Log in
Bookmark this article. You can see your Bookmarks on your DeepDyve Library.
To save an article, log in first, or sign up for a DeepDyve account if you don’t already have one.
Copy and paste the desired citation format or use the link below to download a file formatted for EndNote
Access the full text.
Sign up today, get DeepDyve free for 14 days.
All DeepDyve websites use cookies to improve your online experience. They were placed on your computer when you launched this website. You can change your cookie settings through your browser.