No abstract

Abstract-In this paper, we present a UML metamodel-based approach for creating and executing workflow models. The workflow modeling language is introduced through its abstract syntax, and an evaluation shows how this language supports known workflow patterns. Some patterns can be expressed easier compared to established languages like EPCs or BPMN. Organizational and data aspects in workflow models can be described on the basis of the presented metamodel. The workflow models can be instantiated and executed with a tool realizing parts of the UML action semantics. At an early stage of design, our workflow models can be evaluated by testing scenarios with the used tool in combination with the developed workflow plugin. Employing the tool, dynamic aspects of the workflow process models together with data and organizational aspects can be evaluated. During execution of the workflow scenarios, the workflow models can be adaptively changed, and data can be captured and evaluated by formulating process mining queries with UML's OCL (Object Constraint Language).

Abstract. This paper argues for a transfer of knowledge and experience gained in task-based design to Software Engineering. A transformation of task models into activity diagrams as part of UML is proposed. By using familiar notations, software engineers might be encouraged to accept task modelling and to pay more attention to users and their tasks. Generally, different presentations of a model can help to increase its acceptance by various stakeholders. The presented approach allows both the visualization of task models as activity diagrams as well as task modelling with activity diagrams. Corresponding tool support is presented which includes the animation of task models. The tool itself was developed in a model-based way.

Abstract. This paper discusses the relationship between tests and proofs with focus on a tool for UML and OCL models. Tests are thought of as UML object diagrams and theorems or properties which are to be checked are represented as OCL constraints, i.e., class invariants or operation pre-and postconditions. The paper shows for the UML and OCL tool USE (UML-based Specification Environment) how to trace and debug the validity of an expected theorem (an OCL constraint) within a given test case (a state model in the form of a UML object diagram).

No abstract