Journal ArticleDOI
Scope analysis: identifying the impact of changes in business process models
Reads0
Chats0
TLDR
The article presents a taxonomy of modifications that can be made to a process model and characterizes different modification types in terms of possible scopes of the changes made.Abstract:
Organizations often change their business processes in reaction to changes in the environment or as a result of improvement efforts. These changes lead to adjustments in the Business Process Support (BPS) system. The impact of a change in a business process may extend beyond the specific point that has been changed, affecting preconditions required for other activities, outputs to be created, or requiring new inputs. This article introduces a concept of a scope of a change, whose identification facilitates focused efforts when adjusting the BPS system to changes in business processes. The article presents a taxonomy of modifications that can be made to a process model and characterizes different modification types in terms of possible scopes of the changes made. Copyright © 2005 John Wiley & Sons, Ltd.read more
Citations
More filters
Journal ArticleDOI
Contextualisation of business processes
TL;DR: This paper discusses why context matters and how context can be conceptualised, classified and integrated with existing approaches to business process modelling and proposes a framework and a meta model for classifying relevant context.
Journal ArticleDOI
VIVACE: A Framework for the Systematic Evaluation of Variability Support in Process-Aware Information Systems
TL;DR: This paper will provide a framework for assessing and comparing process variability approaches and the support they provide for the dierent phases of the business process life.
Journal ArticleDOI
Goal-Driven Multi-Process Analysis.
Pnina Soffer,Yair Wand +1 more
TL;DR: Extant process modeling techniques address different aspects of processes, such as activity sequencing, resource allocation, and organizational responsibilities, but do not deal with important aspects of process design such as process goals.
Proceedings ArticleDOI
Process SEER: A Tool for Semantic Effect Annotation of Business Process Models
TL;DR: The conceptual underpinnings, design, implementation and evaluation of the ProcessSEER tool is described that supports several strategies for obtaining semantic effect descriptions of BPMN process models, without imposing an overly onerous burden of using formal specification on the analyst.
Journal ArticleDOI
Security Requirements Engineering for Evolving Software Systems: A Survey
TL;DR: It is suggested that a cross fertilization of the areas of software evolution and security engineering would address the problem of maintaining compliance to security requirements of software systems as they evolve.
References
More filters
Journal ArticleDOI
Toward reference models for requirements traceability
TL;DR: Four kinds of traceability link types are identified and critical issues that must be resolved for implementing each type and potential solutions are discussed, and implications for the design of next-generation traceability methods and tools are discussed and illustrated.
Book
Software Change Impact Analysis
TL;DR: This book identifies key impact analysis definitions and themes and illustrates the important themes to give a solid understanding for tackling impact analysis problems and shows how results from both areas can more effectively support impact analysis in software engineering repositories.
Journal ArticleDOI
An ontological model of an information system
Yair Wand,Ron Weber +1 more
TL;DR: An ontological model of an information system that provides precise definitions of fundamental concepts like system, subsystem, and coupling is proposed and is used to analyze some static and dynamic properties of anInformation system and to examine the question of what constitutes a good decomposition of an Information system.
Journal ArticleDOI
Rules and Tools for Software Evolution Planning and Management
Meir M. Lehman,Juan F. Ramil +1 more
TL;DR: This paper develops and presents some fifty rules for application in software system process planning and management and indicates tools available or that could usefully be developed to support their application.