Daniel Sinnig

Learn More
In this paper, we are exploring the roles of patterns in model-based design. In particular, we discuss the fundamental concepts underlying a generic notation for task patterns. Different views of patterns are suggested using UML and Concurrent Task Tree notations. A first classification of patterns according to models is also suggested.
Model-based approaches describe the process of creating UI models and transforming them in order to build a concrete UI. This allows developers to specify interactive systems on a more abstract and conceptual level instead of dealing with technical details of the low level implementation. However, specifying the various models is a complex and time(More)
A significant portion of our modern economy is dependent on the reliability and usability of enterprise applications (EAs) of which business transactions and concurrency management are central concepts. The correct orchestration of subordinate system transactions forming a business transaction, as well as proper concurrency conflict resolution strategies(More)
A precise model of the behavioral dynamics is a necessary precondition for the development of collaborative environments. In this paper we present a specification framework for collaborative environments. In particular we highlight the interplay of task specifications and domain models. The framework consists of two components: A formal specification(More)
Transformation by patterns ABSTRACT This paper proposes a model-based approach for developing interactive applications. In particular a tool for deriving the navigational structure of the UI from task, object, user and device models is introduced. The editor is based on the XIML technology and allows simulations considering temporal relations between task(More)
Use cases are the notation of choice for functional requirements documentation, whereas task models are used as a starting point for user interface design. In this paper, we motivate the need for an integrated development methodology in order to narrow the conceptual gap between software engineering and user interface design. This methodology rests upon a(More)