<?xml version="1.0" encoding="UTF-8"?><feed xmlns="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
<title>BISE 62(3) - June 2020</title>
<link href="http://dl.gi.de/handle/20.500.12116/33250" rel="alternate"/>
<subtitle/>
<id>http://dl.gi.de/handle/20.500.12116/33250</id>
<updated>2026-07-22T22:11:19Z</updated>
<dc:date>2026-07-22T22:11:19Z</dc:date>
<entry>
<title>Virtual Assistance in Any Context</title>
<link href="http://dl.gi.de/handle/20.500.12116/33257" rel="alternate"/>
<author>
<name>Janssen, Antje</name>
</author>
<author>
<name>Passlick, Jens</name>
</author>
<author>
<name>Rodríguez Cardona, Davinia</name>
</author>
<author>
<name>Breitner, Michael H.</name>
</author>
<id>http://dl.gi.de/handle/20.500.12116/33257</id>
<updated>2020-06-25T07:54:28Z</updated>
<published>2020-01-01T00:00:00Z</published>
<summary type="text">Virtual Assistance in Any Context
Janssen, Antje; Passlick, Jens; Rodríguez Cardona, Davinia; Breitner, Michael H.
Several domain-specific assistants in the form of chatbots have conquered many commercial and private areas. However, there is still a limited level of systematic knowledge of the distinctive characteristics of design elements for chatbots to facilitate development, adoption, implementation, and further research. To close this gap, the paper outlines a taxonomy of design elements for chatbots with 17 dimensions organized into the perspectives intelligence, interaction and context. The conceptually grounded design elements of the taxonomy are used to analyze 103 chatbots from 23 different application domains. Through a clustering-based approach, five chatbot archetypes that currently exist for domain-specific chatbots are identified. The developed taxonomy provides a structure to differentiate and categorize domain-specific chatbots according to archetypal qualities that guide practitioners when taking design decisions. Moreover, the taxonomy serves academics as a foundation for conducting further research on chatbot design while integrating scientific and practical knowledge.
</summary>
<dc:date>2020-01-01T00:00:00Z</dc:date>
</entry>
<entry>
<title>The Role of IS in the Conflicting Interests Regarding GDPR</title>
<link href="http://dl.gi.de/handle/20.500.12116/33256" rel="alternate"/>
<author>
<name>Jakobi, Timo</name>
</author>
<author>
<name>Grafenstein, Maximilian</name>
</author>
<author>
<name>Legner, Christine</name>
</author>
<author>
<name>Labadie, Clément</name>
</author>
<author>
<name>Mertens, Peter</name>
</author>
<author>
<name>Öksüz, Ayten</name>
</author>
<author>
<name>Stevens, Gunnar</name>
</author>
<id>http://dl.gi.de/handle/20.500.12116/33256</id>
<updated>2020-06-25T07:54:28Z</updated>
<published>2020-01-01T00:00:00Z</published>
<summary type="text">The Role of IS in the Conflicting Interests Regarding GDPR
Jakobi, Timo; Grafenstein, Maximilian; Legner, Christine; Labadie, Clément; Mertens, Peter; Öksüz, Ayten; Stevens, Gunnar
</summary>
<dc:date>2020-01-01T00:00:00Z</dc:date>
</entry>
<entry>
<title>Interview with Omer Biran and Michael Halfmann on 'Conversational Agents at SAP'</title>
<link href="http://dl.gi.de/handle/20.500.12116/33252" rel="alternate"/>
<author>
<name>Pfeiffer, Jella</name>
</author>
<id>http://dl.gi.de/handle/20.500.12116/33252</id>
<updated>2020-06-25T07:54:28Z</updated>
<published>2020-01-01T00:00:00Z</published>
<summary type="text">Interview with Omer Biran and Michael Halfmann on 'Conversational Agents at SAP'
Pfeiffer, Jella
</summary>
<dc:date>2020-01-01T00:00:00Z</dc:date>
</entry>
<entry>
<title>User Assistance for Intelligent Systems</title>
<link href="http://dl.gi.de/handle/20.500.12116/33251" rel="alternate"/>
<author>
<name>Morana, Stefan</name>
</author>
<author>
<name>Pfeiffer, Jella</name>
</author>
<author>
<name>Adam, Marc T. P.</name>
</author>
<id>http://dl.gi.de/handle/20.500.12116/33251</id>
<updated>2020-06-25T07:54:28Z</updated>
<published>2020-01-01T00:00:00Z</published>
<summary type="text">User Assistance for Intelligent Systems
Morana, Stefan; Pfeiffer, Jella; Adam, Marc T. P.
</summary>
<dc:date>2020-01-01T00:00:00Z</dc:date>
</entry>
</feed>
