Isabelle Mirbel

Situational method engineering: combining assembly-based and roadmap-driven approaches

Because the engineering situation of each information system development (ISD) project is different, engineering methods need to be adapted, transformed or enhanced to satisfy the specific project situation. Contributions, in the field of situational method engineering (SME), aim at providing techniques and tools allowing to construct project-specific methods instead of looking for universally applicable ones. In addition to the engineering method tailoring, necessary to fit the project situation, a customization of the engineering method for each engineer participating in the project is also required. Such a configuration allows a better understanding of the method by focusing on guidelines related to the project engineer’s daily tasks. It also increases his/her involvement in the ISD method realization. To achieve this twofold objective (ISD method tailoring and customization), we propose a framework for SME combining an assembly-based approach for project-specific method construction and a roadmap-driven approach for engineer-specific method configuration. The first step of our process provides support to build a new method that is most suitable for the current ISD project situation, whereas the second step aims at choosing the most adapted path (roadmap) to satisfy the requirements of a particular project engineer within the project-specific method. The two core elements of our SME framework are the method chunks repository and the reuse frame. The former concerns reusable method components definition and storage whereas the latter deals with the characterization of the project situation and the project engineer’s profile. In this paper we start first by presenting our SME framework and its core elements: the method chunk repository and the reuse frame. Then we show how to take advantage of them through our two-step process combining assembly-based method construction and roadmap-driven method configuration.

Using patterns to design rules in workflows

In order to design workflows in changing and dynamic environments, a flexible, correct, and rapid realization of models of the activity flow is required. In particular, techniques are needed to design workflows capable of adapting themselves effectively when exceptional situations occur during process execution. The authors present an approach to flexible workflow design based on rules and patterns developed in the framework of the WIDE project. Rules allow a high degree of flexibility during workflow design by modeling exceptional aspects of the workflow separately from the main activity flow. Patterns model frequently occurring exceptional situations in a generalized way by providing the designer with skeletons of rules and suggestions about their instantiation, together with indications on relationships with other rules, with the activity flow, and with related information. Pattern based design relies on a pattern catalog containing patterns to be reused and on a formal basis for specializing and instantiating available patterns.

An environment for designing exceptions in workflows

Abstract When designing a workflow schema, the workflow designer must often explicitly deal with exceptional situations, such as abnormal process termination or suspension of task execution. This paper shows how the designer can be supported by tools allowing him to capture exceptional behavior within a workflow schema, by reusing an available set of pre-configured exceptions skeletons. Exceptions are expressed by means of triggers, to be executed on the top of an active database environment. In particular, the paper deals with the handling of typical workflow exceptional situations which are modeled as generic exception skeletons to be included in a new workflow schema by simply specializing or instantiating them. Such skeletons, called patterns , are stored in a catalog; the paper describes the catalog structure and its management tools constituting an integrated environment for pattern-based exception design and reuse.

WIDE workflow development methodology

The development of workflows (WFs) for complex organizations to be interfaced with existing information systems requires a specific methodological approach to guarantee benefits and effectiveness of the final results. In fact, the WF should be well integrated in the organization both from the technical and the organizational point of view. While the characteristics of the Workflow Management System (WFMS) platform adopted in the implementation are relevant to establish the boundary between the workflow system and other related applications, it is also important that the analysis and design phases are developed independently of those characteristics.The WF development methodology proposed in this paper starts with an analysis phase based on UML, adopted for business process descriptions and business goals. The design phase proposes a pattern-based approach to workflow schemas design, based on the WIDE WF model. This model allows a flexible representation of the exceptions which may occur during WF execution. It also considers the interaction of the WF with external applications and information systems. Finally, the paper briefly discusses the mapping to commercial and prototype WFMSs.

Engineering Methods in the Service-Oriented Context

This book constitutes the refereed proceedings of the 4th IFIP WG 8.1 Working Conference on Method Engineering, ME 2011, held in Paris, France, in April 2011. The 13 revised full papers and 6 short papers presented together with the abstracts of two keynote talks were carefully reviewed and selected from 30 submissions. The papers are organized in topical sections on situated method engineering, method engineering foundations, customized methods, tools for method engineering, new trends to build methods, and method engineering services.

Semantic integration of conceptual schemas

Abstract Our goal is to work out an integration process which makes it possible to give a global design schema obtained from several schemas, each of them describing the same reality viewed in different ways, in order to obtain the fullest view. Problems and conflicts arise during the schema integration. They are due to the several ways of representing the semantic knowledge and of structuring knowledge (using the same design model). When the detection and solution of structural problems are model dependent, the detection and solution of semantic problems are not model dependent. To represent the semantic of the words which are used in a schema, we have defined a model of a thesaurus drawn from the domain dealing with the meaning of words: linguistics. In this paper, we will show the interest in using this fuzzy thesaurus when design schema are being integrated.

Adapting Analysis and Design to Software Context: The JECKO Approach

New object-oriented technologies have been developed in order to manage complexity inherent in new information system development. But developments are very different one from the others, and a given technique, notation or mechanism is used differently depening Softtware under consideration. Flexibility is required from the methodology with regards to the Software context.We propose JECKO, a flexible approach to analysis and design rohere fiexibility is handled through a fragmentation mechanism. In order to adapt the analysis and design activities, fragments are selected with regards to Software context. The chosen fragments constitute the route map built for the Software specificity.

Checking the temporal integrity of interactive multimedia documents

Abstract. When authoring multimedia scenarios, and in particular scenarios with user interaction, where the sequence and time of occurrence of interactions is not predefined, it is difficult to guarantee the consistency of the resulting scenarios. As a consequence, the execution of the scenario may result in unexpected behavior or inconsistent use of media. The present paper proposes a methodology for checking the temporal integrity of interactive multimedia document (IMD) scenarios at authoring time at various levels. The IMD flow is mainly defined by the events occurring during the IMD session. Integrity checking consists of a set of discrete steps, during which we transform the scenario into temporal constraint networks representing the constraints linking the different possible events in the scenario. Temporal constraint verification techniques are applied to verify the integrity of the scenario, deriving a minimal network, showing possible temporal relationships between events given a set of constraints.

WIRES: A Methodology for Developing Workflow Applications

Workflow management systems are becoming a relevant support for a large class of business applications, and many workflow models as well as commercial products are currently available. While the large availability of tools facilitates the development and the fulfilment of customer requirements, workflow application development still requires methodological guidelines that drive the developers in the complex task of rapidly producing effective applications. In fact, it is necessary to identify and model the business processes, to design the interfaces towards existing cooperating systems, and to manage implementation aspects in an integrated way. This paper presents the WIRES methodology for developing workflow applications under a uniform modelling paradigm – UML modelling tools with some extensions – that covers all the life cycle of these applications: from conceptual analysis to implementation. High-level analysis is performed under different perspectives, including abusiness and an organisational perspective. Distribution, interoperability and cooperation with external information systems are considered in this early stage. A set of “workflowability” criteria is provided in order to identify which candidate processes are suited to be implemented as workflows. Non-functional requirements receive particular emphasis in that they are among the most important criteria for deciding whether workflow technology can be actually useful for implementing the business process at hand. The design phase tackles aspects of concurrency and cooperation, distributed transactions and exception handling. Reuse of component workflows, available in a repository as workflow fragments, is a distinguishing feature of the method. Implementation aspects are presented in terms of rules that guide in the selection of a commercial workflow management system suitable for supporting the designed processes, coupled with guidelines for mapping the designed workflows onto the model offered by the selected system.

Unifying and Extending user Story Models

Within Agile methods, User Stories (US) are mostly used as primary requirements artifacts and units of functionality of the project. The idea is to express requirements on a low abstraction basis using natural language. Most of them are exclusively centered on the final user as only stakeholder. Over the years, some templates (in the form of concepts relating the WHO, WHAT and WHY dimensions into a phrase) have been proposed by agile methods practitioners or academics to guide requirements gathering. Using these templates can be problematic. Indeed, none of them define any semantic related to a particular syntax precisely or formally leading to various possible interpretations of the concepts. Consequently, these templates are used in an ad–hoc manner, each modeler having idiosyncratic preferences. This can nevertheless lead to an underuse of representation mechanisms, misunderstanding of a concept use and poor communication between stakeholders. This paper studies templates found in literature in order to reach unification in the concepts’ syntax, an agreement in their semantics as well as methodological elements increasing inherent scalability of US-based projects.