<?xml version="1.0" encoding="UTF-8"?>
<TEI xml:space="preserve" xmlns="http://www.tei-c.org/ns/1.0" 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
xsi:schemaLocation="http://www.tei-c.org/ns/1.0 https://raw.githubusercontent.com/kermitt2/grobid/master/grobid-home/schemas/xsd/Grobid.xsd"
 xmlns:xlink="http://www.w3.org/1999/xlink">
	<teiHeader xml:lang="en">
		<fileDesc>
			<titleStmt>
				<title level="a" type="main">Advantages of a Full Integration between Agents and Workflows</title>
			</titleStmt>
			<publicationStmt>
				<publisher/>
				<availability status="unknown"><licence/></availability>
			</publicationStmt>
			<sourceDesc>
				<biblStruct>
					<analytic>
						<author>
							<persName><forename type="first">Thomas</forename><surname>Wagner</surname></persName>
							<affiliation key="aff0">
								<orgName type="department" key="dep1">MIN Faculty</orgName>
								<orgName type="department" key="dep2">Department of Informatics http://www</orgName>
								<orgName type="institution" key="instit1">University of Hamburg</orgName>
								<orgName type="institution" key="instit2">informatik.uni-hamburg.de/TGI</orgName>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Lawrence</forename><surname>Cabac</surname></persName>
							<affiliation key="aff0">
								<orgName type="department" key="dep1">MIN Faculty</orgName>
								<orgName type="department" key="dep2">Department of Informatics http://www</orgName>
								<orgName type="institution" key="instit1">University of Hamburg</orgName>
								<orgName type="institution" key="instit2">informatik.uni-hamburg.de/TGI</orgName>
							</affiliation>
						</author>
						<title level="a" type="main">Advantages of a Full Integration between Agents and Workflows</title>
					</analytic>
					<monogr>
						<imprint>
							<date/>
						</imprint>
					</monogr>
					<idno type="MD5">ABBEFC3DEC14EB24053BCF2483127040</idno>
				</biblStruct>
			</sourceDesc>
		</fileDesc>
		<encodingDesc>
			<appInfo>
				<application version="0.7.2" ident="GROBID" when="2023-03-23T23:37+0000">
					<desc>GROBID - A machine learning software for extracting information from scholarly documents</desc>
					<ref target="https://github.com/kermitt2/grobid"/>
				</application>
			</appInfo>
		</encodingDesc>
		<profileDesc>
			<abstract>
<div xmlns="http://www.tei-c.org/ns/1.0"><p>This poster describes the notion of a full integration of agents and workflows. It differentiates the term from the more common partial integrations already well documented and researched. Finally, the advantages of a full integration are discussed.</p></div>
			</abstract>
		</profileDesc>
	</teiHeader>
	<text xml:lang="en">
		<body>
<div xmlns="http://www.tei-c.org/ns/1.0"><p>Multi-agent systems feature a very structure-centric perspective on a software system. Agents are the main modelling abstraction, and other aspects are always seen in relation to them. Workflow systems on the other hand feature a very behaviour-centric perspective. The main abstraction here are the workflows/processes, which incorporate the data/information about other aspects. An integration of the two concepts agent and workflow can offer many advantages. These advantages represent the first outcomes in our current research on modelling systems and are the main result presented in this poster.</p><p>It is possible to differentiate between two kinds of integrations: partial and full. In a partial integration one of the concepts is used to enhance the other one. This includes agent-based workflow management systems (WFMS) and workflow-based agent management systems. Partial integrations feature only one of the two concepts main abstraction. This main abstraction may be enhanced and enriched in a number of ways, but still remains, at its core, either an agent or a workflow. This limits the potential benefits in a partial integration.</p><p>A full integration between agents and workflows aims to address that limit. In contrast to partial integrations it features both agents and workflows incorporated into one main modelling unit. This unit can serve as agent, workflow, or a hybrid between the two and can dynamically change its role during runtime. We call these hybrids that provide all the functionality agents and workflows would usually provide, including communication and user interaction facilities, entities. Using entities enables a system modeller to dynamically switch and mix structural and behavioural aspects of a system. This allows for a new integrated perspective on the system during development.</p><p>There are numerous examples of partial integrations. Agent-based WFMS are, for example, presented in <ref type="bibr" target="#b0">[1,</ref><ref type="bibr" target="#b1">2]</ref>. A workflow-based agent management system is discussed in <ref type="bibr" target="#b2">[3]</ref>. All of these make use of both concepts to provide an enhanced modelling experience. They still only offer extended classical workflow or agent functionality and do not feature the possibilities of a full integration. To the best of our knowledge there are no examples of full integrations.</p><p>A full integration between agents and workflows exhibits a number of advantages to the system modeller. These assume an efficient and comprehensive implementation of a full integration system (see last paragraphs for outlook).</p><p>Abstraction The abstraction of the individual concepts into one unified entity enables a freedom to work with dynamic and hybrid constructs. Entities can operate as agents, workflows, or something in between. They can dynamically adapt to the requirements before, acting as an agent at one point and processing like a workflow at another. Entities naturally and directly incorporate any and all mechanisms, facilities, and properties of agents and workflows. Consequently, providing these characteristics in dynamic ways becomes far easier.</p><p>Flexibility Allowing a modeller to use agents and workflows on the same abstraction level, allows to model a system along the two dimensions structure and behaviour. Classically, only one of these dimensions was in the foreground, while modelling aspects of the other was heavily biased by the original dimension. This two-dimensional modelling enables a modeller to utilise the dynamic interaction between agents and workflows on a conceptual level.</p><p>Simplicity A full integration offers the combined capabilities of agents and workflows. It does so by providing simple-to-use and predefined constructs (entities) which allow a modeller to make full use of the strengths of agents and workflows. The entities in themselves can be used similarly to agents and workflows, but possess a larger spectrum of capabilities.</p><p>Expressiveness A full integration cannot necessarily express more then the classical paradigms. However, in the classical paradigms complex helper constructs might be necessary to implement more complicated structures available directly in a full integration. This means that a full integration is capable of expressing more constructs in a natural and simple way.</p><p>Enrichment The enrichment aspect, the main advantage of partial integration, is also applicable in a full integration. In fact, it is even more emphasised, since an entity can be improved from both its agent and workflow side.</p><p>Concerning future work the provision of a comprehensive implementation of a full integration is the main focus. Currently, the work is centred on establishing a working prototype as proof-of-concept. In conclusion, a full integration offers many beneficial advantages in comparison to classical systems. When extensively and efficiently implemented, it is a powerful tool for a system modeller to use.</p></div>			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" xml:id="foot_0">ModBE'13 -Modeling and Business Environments</note>
		</body>
		<back>
			<div type="references">

				<listBibl>

<biblStruct xml:id="b0">
	<analytic>
		<title level="a" type="main">BeesyBees -efficient and reliable execution of service-based workflow applications for BeesyCluster using distributed agents</title>
		<author>
			<persName><forename type="first">P</forename><surname>Czarnul</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Matuszek</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Wójcik</surname></persName>
		</author>
		<author>
			<persName><forename type="first">K</forename><surname>Zalewski</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Proceedings of IMCSIT 2010</title>
				<meeting>IMCSIT 2010</meeting>
		<imprint>
			<date type="published" when="2010-10">oct. 2010</date>
			<biblScope unit="page" from="173" to="180" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b1">
	<analytic>
		<title level="a" type="main">Collaborative Workflow Management in Holonic Multi-Agent Systems</title>
		<author>
			<persName><forename type="first">F</forename><surname>Hsieh</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Agent and Multi-Agent Systems: Technologies and Applications</title>
				<editor>
			<persName><forename type="first">J</forename><forename type="middle">O</forename><surname>Shea</surname></persName>
		</editor>
		<meeting><address><addrLine>Berlin Heidelberg</addrLine></address></meeting>
		<imprint>
			<publisher>Springer</publisher>
			<date type="published" when="2011">2011</date>
			<biblScope unit="volume">6682</biblScope>
			<biblScope unit="page" from="383" to="393" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b2">
	<analytic>
		<title level="a" type="main">Workflow based approach for designing and executing mobile agents</title>
		<author>
			<persName><forename type="first">A</forename><surname>Mislevics</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>Grundspenkis</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Digital Information Processing and Communications (ICDIPC), 2012 Second International Conference on</title>
				<imprint>
			<date type="published" when="2012-07">july 2012</date>
			<biblScope unit="page" from="96" to="101" />
		</imprint>
	</monogr>
</biblStruct>

				</listBibl>
			</div>
		</back>
	</text>
</TEI>
