<?xml version="1.0" encoding="UTF-8"?><rdf:RDF xmlns="http://purl.org/rss/1.0/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel rdf:about="http://dl.gi.de/handle/20.500.12116/24820">
<title>P075 - EMISA 2005 - Enterprise Modelling and Information Systems Architectures</title>
<link>http://dl.gi.de/handle/20.500.12116/24820</link>
<description/>
<items>
<rdf:Seq>
<rdf:li rdf:resource="http://dl.gi.de/handle/20.500.12116/24839"/>
<rdf:li rdf:resource="http://dl.gi.de/handle/20.500.12116/24838"/>
<rdf:li rdf:resource="http://dl.gi.de/handle/20.500.12116/24836"/>
<rdf:li rdf:resource="http://dl.gi.de/handle/20.500.12116/24837"/>
</rdf:Seq>
</items>
<dc:date>2026-07-21T13:21:44Z</dc:date>
</channel>
<item rdf:about="http://dl.gi.de/handle/20.500.12116/24839">
<title>Unbundling and deploying CRM applications as e-services</title>
<link>http://dl.gi.de/handle/20.500.12116/24839</link>
<description>Unbundling and deploying CRM applications as e-services
Falcone Sampaio, Pedro R.; Yong, He
Desel, Jörg; Frank, Ulrich
The development of Customer Relationship Management (CRM) capabilities by incrementally sourcing and combining "best of breed" services from different providers is a key lever for reducing implementation risks and costs linked to CRM projects. Central to a "best of breed" and incremental CRM implementation strategy is the unbundling of CRM functionality into a portfolio of services that can be sourced from application service providers and/or developed internally within the client organization. This paper addresses issues and methodological steps relating to unbundling CRM applications into self contained e-Services and developing the service blueprint to deliver the e-Service. In particular a study is conducted illustrating the unbundling of customer segmentation functionality towards modeling, packaging and delivering the business process functionality as an on-demand e-Service.
</description>
<dc:date>2005-01-01T00:00:00Z</dc:date>
</item>
<item rdf:about="http://dl.gi.de/handle/20.500.12116/24838">
<title>A framework for comparing conceptual models</title>
<link>http://dl.gi.de/handle/20.500.12116/24838</link>
<description>A framework for comparing conceptual models
Pfeiffer, Daniel; Gehlert, Andreas
Desel, Jörg; Frank, Ulrich
Conceptual models are a widely used mean for documenting software systems as well as describing organisational structures. The trend towards integrated and flexible information systems has encouraged research about the comparison of conceptual models. Current approaches on the identification of similarities between conceptual models often adopt an automation perspective only. In this paper we will unfold severe arguments that a fully automatic model comparison process is not feasible. Furthermore, we will show that only a semiautomatic process can perform the comparison of conceptual models at the semantic level. On this theoretical basis, we will develop a framework which identifies all necessary and sufficient components for comparing conceptual models. We will show that this framework includes all the requirements that a semi-automatic model comparison process must meet.
</description>
<dc:date>2005-01-01T00:00:00Z</dc:date>
</item>
<item rdf:about="http://dl.gi.de/handle/20.500.12116/24836">
<title>A model-driven approach for the rapid development of E-negotiation systems</title>
<link>http://dl.gi.de/handle/20.500.12116/24836</link>
<description>A model-driven approach for the rapid development of E-negotiation systems
Benyoucef, Morad; Rinderle, Stefanie
Desel, Jörg; Frank, Ulrich
Most of today's e-marketplaces support a single negotiation protocol. The protocol is usually built into the e-marketplace infrastructure, therefore if a new one is introduced then a time consuming and complex process of implementing it takes place. Moreover, participants in the e-marketplace need to adapt their interfaces to the new protocol, especially if they make use of automated means such as software agents to interact with the e-marketplace. This paper reports on a model-driven approach and a framework for rapid and user-friendly development of configurable e-marketplaces and automated e-negotiation systems. A designer on the e-marketplace specifies negotiation protocols using Statecharts and feeds them to a mapping system that transforms them into web service orchestrations. Participants use automated negotiation systems to interact with the e-marketplace. An automated negotiation entity capable of interacting with the e- marketplace is generated based on the negotiation protocol implemented on the e- marketplace. The automated negotiation entity is provided with negotiation strategies and tactics specified in a declarative format. We propose a mapping algorithm to transform Statechart models of negotiation protocols into web service orchestrations.
</description>
<dc:date>2005-01-01T00:00:00Z</dc:date>
</item>
<item rdf:about="http://dl.gi.de/handle/20.500.12116/24837">
<title>Visualizing join point selections using interaction-based vs. state-based notations exemplified with help of business rules</title>
<link>http://dl.gi.de/handle/20.500.12116/24837</link>
<description>Visualizing join point selections using interaction-based vs. state-based notations exemplified with help of business rules
Stein, Dominik; Hanenberg, Stefan; Unland, Rainer
Desel, Jörg; Frank, Ulrich
In Aspect-Oriented Software Development, the selection of join points is an essential part. Join point selections identify the points in a program (i.e. in its code, or during its execution) at which aspectual adaptations need to take place. In order to communicate such selections independent of the underlying aspectoriented programming language, it is desirable to visualize join point selections in an appropriate way. In this paper we focus on the appropriateness of interaction diagram-based and state diagram-based visualizations of join point queries, exemplified with help of two business rule examples. As a result, we discover that even if join point queries are based on interactions in the base application, state diagram-based representations are needed to appropriately capture the selection semantic of that query.
</description>
<dc:date>2005-01-01T00:00:00Z</dc:date>
</item>
</rdf:RDF>
