Teduh Dirgahayu

Learn More
An approach to system specification defined by the Model-Driven Architecture (MDA) separates the specification of system functionality from the specification of the implementation of that functionality on a specific platform. To this end, the MDA proposes a framework for transforming a model into another model of the same system. The framework can also be(More)
This paper presents an approach for developing transformations from business process models to implementations that facilitates reuse. A transformation is developed as a composition of three smaller tasks: pattern recognition, pattern realization and activity transformation. The approach allows one to reuse the definition and implementation of pattern(More)
In this paper we present an approach for designing interaction behaviour in service-oriented enterprise application integration. The approach enables business analysts to actively participate in the design of an integration solution. In this way, we expect that the solution meets its integration goal and business requirements. The approach consists of four(More)
The success of software development projects to a large extent depends on the quality of the models that are produced in the development process, which in turn depends on the conceptual and practical support that is available for modelling, design and analysis. This paper focuses on model-driven support for service-oriented software development. In(More)
To tackle the complexity of inter-organizational business collaborations, the design of such collaborations may require explicit modelling at multiple abstraction levels. At a high abstraction level, the collaboration is specified as a single abstract interaction; and at a lower abstraction level, the collaboration is specified as a composition of(More)
The increasing number of location-based service (LBS) applications raises the need for location services that return location information at a high abstraction level, i.e. they return area names instead of geo-location coordinates. Area names are application-specific because the same geo-location coordinates may be interpreted into different area names by(More)
Cobit 4.1 defines a number of IT processes; each of which consists of several activities. A process is controlled by several control objectives. All processes share the same maturity attributes. Cobit 4.1 however does not define any assessment method to determine the maturity of IT processes. This paper reviews current assessment methods and identifies(More)