Gil Regev

Bio: Gil Regev is an academic researcher from École Polytechnique Fédérale de Lausanne. The author has contributed to research in topics: Business process modeling & Artifact-centric business process model. The author has an hindex of 19, co-authored 86 publications receiving 1367 citations. Previous affiliations of Gil Regev include École Normale Supérieure & École Polytechnique.

Where do goals come from: the underlying principles of goal-oriented requirements engineering

Abstract: Goal is a widely used concept in requirements engineering methods. Several kinds of goals, such as achievement, maintenance and soft goals, have been defined in these methods. These methods also define heuristics for the identification of organizational goals that drive the requirements process. In this paper, we propose a set of principles that explain the nature of goal-oriented behavior. These principles are based on regulation mechanisms as defined in general systems thinking and cybernetics. We use these principles to analyze the existing definitions of these different kinds of goals and to propose more precise definitions. We establish the commonalities and differences between these kinds of goals, and propose extension for goal identification heuristics.

Taxonomy of Flexibility in Business Processes.

Abstract: Gil Regev, Pnina Soffer, Rainer Schmidt The aim of this working paper is to suggest a taxonomy of flexibility in business processes. The taxonomy should be generic. Hence, it relies on a minimal set of assumptions. We consider business processes as the dynamic aspect of an organization. Business processes can be addressed using the two layers of instance, and type. A process instance layer is an actual occurrence in the organization. The process type layer aggregates the instances as a template they all should fit. Business process flexibility Flexibility is the ability to yield to change without disappearing, i.e. without losing identity [ReWe05]. A business process is flexible if it is possible to change it without replacing it completely. Business process flexibility [Bide05], [Soff05], [Schm05] is the capability to implement changes in the business process type and instances by changing only those parts that need to be changed and keeping other parts stable.

Business and IT Alignment with SEAM for Enterprise Architecture

Abstract: To align an IT system with an organization's needs, it is necessary to understand the organization 's position within its environment as well as its internal configuration. In SEAM for enterprise architecture the organization is considered as a hierarchy of systems that span from business down to IT. The alignment process addresses the complete hierarchy. We illustrate the use of SEAM for enterprise architecture with an example in which a new hiring process and an IT system are developed. With this approach it is possible to train new engineers in the design of business and IT alignment. It is also possible to scope projects in a way that integrate both business and IT strategies. This enables the consideration of IT developments in an enterprise-wide context.

A Method and Tool for Business-IT Alignment in Enterprise Architecture

Abstract: Enterprise architects seek to align enterprise processes and structure with their supporting IT systems so that enterprises can flourish in their environment. The enterprise architecture (EA) discipline has emerged from business best practices. EA frameworks are therefore mostly informal. As a result there is a lack of EA tools that can help enterprise architects to check this alignment. Most notably, current EA tools do not help enterprise architects to formalize the alignment of the multiple levels that constitute an enterprise model. In this paper we propose an EA framework and an associated tool that provide alignment checking along the functional and organizational hierarchies. We illustrate this approach with the Sun Microsystems industrial example of the Pet Store.

Defining business process flexibility with the help of invariants

Abstract: Enterprise survival is about maintaining an identity that is separate from other enterprises. We define flexibility as the ability to change without losing identity. The identity of an enterprise can be analyzed as a set of norms and beliefs about these norms held by its stakeholders, such as customers, employees, suppliers, and investors. Business processes and their support systems maintain invariants that are the result of compromises between the often conflicting norms and beliefs of these stakeholders. We formalize these invariants as values in a state space. Identifying a minimum set of invariants provides a basis for defining flexible processes and support systems. We illustrate the use of this framework with production business process support (BPS) systems.

Soft Systems Methodology in Action

Abstract: (1991). Soft Systems Methodology in Action. European Journal of Information Systems: Vol. 1, No. 3, pp. 215-216.

Enabling Flexibility in Process-Aware Information Systems

Abstract: Traditionally, process-ware information systems (PAISs) have focused on the support of predictable and repetitive business processes. Even though respective processes are suited to be fully pre-specified in a process model, flexibility is required to support dynamic process adaptations in case of exceptions. Flexibility is also needed to accommodate the need for evolving business processes and to cope with business process variability. Furthermore, PAISs are increasingly used to support less structured processes which can often be characterized as knowledgeintensive. Processes of this category are neither fully predictable nor repetitive, and therefore cannot be fully pre-specified at build-time. The (partial) unpredictability of these processes also demands a certain amount of looseness. This chapter deals with the flexibility needs of both pre-specified and loosely-specified processes and elicitates requirements for flexible process support in a PAIS. In addition, the chapter discusses PAIS features needed to accommodate flexibility needs in practice like, for example, traceability, business compliance and user support.