<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
<channel>
<title>Wirtschaftsinformatik 44(5) - Oktober 2002</title>
<link>http://dl.gi.de/handle/20.500.12116/11882</link>
<description/>
<pubDate>Tue, 21 Jul 2026 13:15:56 GMT</pubDate>
<dc:date>2026-07-21T13:15:56Z</dc:date>
<item>
<title>Web-Services als Basis für evolvierbare Softwaresysteme</title>
<link>http://dl.gi.de/handle/20.500.12116/12318</link>
<description>Web-Services als Basis für evolvierbare Softwaresysteme
Stiemerling, Oliver
Web-service-technologies are often regarded as the dominant way of software development in the future, especially for inter-company scenarios. While the current discussion in this area focuses mainly on the integration of software, this paper takes the next step and looks at the evolvability of the system resulting from the integration. A system’s adaptability in the face of changing requirements is usually the decisive success factor in industrial environments.This paper analyses experiences with a large, web-service-based application already in industrial use. As principal result we show that such a web-service-architecture indeed has the potential to support the evolvability of a complex software system. The clear separation of system components achieved by web-services — not only on a conceptual, but also on a technological and organizational level — is especially beneficial for large, long-term software projects that span company boundaries. The decision for a web-service-architecture requires additional efforts in the design, development and deployment of the software. With these additional efforts in mind, the concluding discussion offers some guidelines for web-service-projects, especially concerning the sensible (and economical) decomposition of the system into components connected by webservices.This contribution draws on experiences from a portal project for a large German company. The project employed around 50 persons including all sub- and partner-projects. For reasons of confidentiality the name of the company and project details are omitted, albeit without hurting the main points of the paper.
</description>
<pubDate>Tue, 01 Jan 2002 00:00:00 GMT</pubDate>
<guid isPermaLink="false">http://dl.gi.de/handle/20.500.12116/12318</guid>
<dc:date>2002-01-01T00:00:00Z</dc:date>
</item>
<item>
<title>Integration von Daten, Anwendungen und Prozessen am Beispiel des Telekommunikationsunternehmens EWE TEL</title>
<link>http://dl.gi.de/handle/20.500.12116/12317</link>
<description>Integration von Daten, Anwendungen und Prozessen am Beispiel des Telekommunikationsunternehmens EWE TEL
Bunjes, Bernd; Friebe, Jörg; Götze, Rainer; Harren, Arne
The necessary specialisation in information processing in the telecommunication sector led to a wide range of software systems in the relevant software market. This can be traced back by the fact that there is a lack of capable and integrated solutions. If a telecommunication company comes to the decision to use specialised software systems, it has to face the sophisticated challenge of systems integration. This can be done at least at the levels of data, applications and processes. Illustrated by examples from the heterogeneous system environment at the telecommunication company EWE TEL, concepts for system integration and gained experiences are presented in this article. The following aspects are discussed in detail: integration of data by means of middleware, integration of applications using application server technology, and integration of processes by employing workflow management systems.
</description>
<pubDate>Tue, 01 Jan 2002 00:00:00 GMT</pubDate>
<guid isPermaLink="false">http://dl.gi.de/handle/20.500.12116/12317</guid>
<dc:date>2002-01-01T00:00:00Z</dc:date>
</item>
<item>
<title>Kopplungsarchitekturen zur überbetrieblichen Integration von Anwendungssystemen und ihre Realisierung mit SAP R/3</title>
<link>http://dl.gi.de/handle/20.500.12116/12319</link>
<description>Kopplungsarchitekturen zur überbetrieblichen Integration von Anwendungssystemen und ihre Realisierung mit SAP R/3
Schissler, Martin; Mantel, Stephan; Ferstl, Otto K.; Sinz, Elmar J.
Business-to-business processes require an inter-company integration of the application systems supporting these business processes. Integration is based on inter-company couplings of application systems, which are specified in coupling architectures. The necessity of coupling of application systems arises from relationships between business tasks which are to be supported by these application systems. Starting with relevant relationships between business tasks, three classes of coupling architectures are identified and illustrated by concrete instances. It is investigated to which extent coupling mechanisms as provided by SAP R/3 are suitable for an implementation of these coupling architectures.
</description>
<pubDate>Tue, 01 Jan 2002 00:00:00 GMT</pubDate>
<guid isPermaLink="false">http://dl.gi.de/handle/20.500.12116/12319</guid>
<dc:date>2002-01-01T00:00:00Z</dc:date>
</item>
<item>
<title>Supply Chain Event Management</title>
<link>http://dl.gi.de/handle/20.500.12116/12313</link>
<description>Supply Chain Event Management
Nissen, Volker
</description>
<pubDate>Tue, 01 Jan 2002 00:00:00 GMT</pubDate>
<guid isPermaLink="false">http://dl.gi.de/handle/20.500.12116/12313</guid>
<dc:date>2002-01-01T00:00:00Z</dc:date>
</item>
</channel>
</rss>
