<?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">MEMOCenterNG -A full-featured modeling environment for organization modeling and model-driven software development</title>
			</titleStmt>
			<publicationStmt>
				<publisher/>
				<availability status="unknown"><licence/></availability>
			</publicationStmt>
			<sourceDesc>
				<biblStruct>
					<analytic>
						<author>
							<persName><roleName>Prof</roleName><forename type="first">Jens</forename><surname>Gulden</surname></persName>
							<email>jens.gulden@uni-duisburg-essen.de</email>
							<affiliation key="aff0">
								<orgName type="institution">University Duisburg-Essen</orgName>
								<address>
									<addrLine>Universitaetsstr. 9</addrLine>
									<postCode>45141</postCode>
									<settlement>Essen</settlement>
									<country key="DE">Germany</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><roleName>Dr</roleName><forename type="first">Ulrich</forename><surname>Frank</surname></persName>
							<email>ulrich.frank@uni-duisburg-essen.de</email>
							<affiliation key="aff0">
								<orgName type="institution">University Duisburg-Essen</orgName>
								<address>
									<addrLine>Universitaetsstr. 9</addrLine>
									<postCode>45141</postCode>
									<settlement>Essen</settlement>
									<country key="DE">Germany</country>
								</address>
							</affiliation>
						</author>
						<title level="a" type="main">MEMOCenterNG -A full-featured modeling environment for organization modeling and model-driven software development</title>
					</analytic>
					<monogr>
						<imprint>
							<date/>
						</imprint>
					</monogr>
					<idno type="MD5">FE87FCEEFF2111DBD27A41C77D153C3C</idno>
				</biblStruct>
			</sourceDesc>
		</fileDesc>
		<encodingDesc>
			<appInfo>
				<application version="0.7.2" ident="GROBID" when="2023-03-24T21:53+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>
			<textClass>
				<keywords>
					<term>Modeling</term>
					<term>Model-driven software development</term>
					<term>Multi-perspective modeling</term>
					<term>Enterprise modeling</term>
				</keywords>
			</textClass>
			<abstract>
<div xmlns="http://www.tei-c.org/ns/1.0"><p>We present MEMOCenterNG 1 , an integrated, full-featured modeling environment containing 11 built-in modeling languages together with meta-modeling support for creating new languages and corresponding diagram editors. Tools for analysis, model transformation and code generation are included.</p></div>
			</abstract>
		</profileDesc>
	</teiHeader>
	<text xml:lang="en">
		<body>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="1">A comprehensive multi-language modeling tool</head><p>Large modeling projects typically use multiple modeling languages simultaneously to express a variety of aspects of a modeled system. This holds true in diverse types of modeling projects, especially in business process modeling, which unites conceptual business aspects with technical realizations. Model-driven software development benefits from multiple interrelated modeling perspectives to gain a coherent and as complete view as possible on the system to be developed.</p><p>To foster large modeling projects, an integrated modeling environment tool is desirable to reduce efforts in combining multiple model editors operating on shared model content. Semantic integrity is an indispensable requirement for multi-perspective modeling <ref type="bibr" target="#b5">[6]</ref>, that means, when different model editors reference the same concept (e.g., a person displayed both in an organization structure diagram and in a process diagram), the model editor components need to share common information about its unique identity. The need for semantic integrity requires model editors to work on top of a common set of meta-concepts <ref type="bibr" target="#b6">[7]</ref> which ensures semantically valid relations among model data.</p><p>With MEMOCenterNG, we present a comprehensive modeling environment which integrates an extensible set of modeling languages on the basis of a consolidated common meta-model API. The provided modeling languages are suitable to express knowledge about a system on three different levels of abstraction from multiple interdependent perspectives.</p><p>The available levels of abstraction provided by built-in modeling languages in MEMOCenterNG are:</p><p>1. A meta-modeling layer which allows for creating new modeling languages and corresponding diagram editors, and also internally defines other built-in modeling lnaguages. 2. A set of built-in modeling languages for modeling the organizational environment of involved actors, their goals, behaviour and involved resources. This organizational abstraction layer is provided by domain-specific modeling languages of the MEMO modeling method <ref type="bibr" target="#b5">[6]</ref>.</p><p>3. An implementation model layer which offers general purpose modeling languages to express a software system's inner perspective in terms of, e.g., classes, attributes and relationships.</p><p>Figure <ref type="figure" target="#fig_0">1</ref> gives an overview on the component architecture of MEMOCen-terNG, as it evolves from applying the MEMO Meta Modeling Language (MML) for language creation.  . These initially available languages can be enhanced by any number of specific modeling languages created with the MML. Supplemented by third-party tooling components, models can be analyzed, model-transformations can be carried out, and code-generation mechanisms are available to generatively create software in a model-driven development process. Altogether, MEMOCenterNG forms a comprehensive environment for modeling on multiple layers of abstraction from multiple perspectives, store and manage interrelated models in a common environment, and further process model data inside the same platform. In modeldriven software development projects, generated artefacts can furthermore be edited, compiled and packaged within the same tool. The platform is based on the Eclipse <ref type="bibr" target="#b3">[4]</ref> environment which can additionally be enhanced by a multitude of third-party supplementary components for software development.</p><p>By means of the included MEMO Meta Modeling Language (MML, <ref type="bibr" target="#b6">[7]</ref>), new modeling languages can efficiently be created, and appropriate diagram editors for using the languages are automatically created from MML meta-models.</p><p>Since all generated components run in the same environment as MEMO-CenterNG, models and generated software components may even reflectively refer to MEMOCenterNG's models. This allows models to be integrated into software components at runtime as part of a self-referential information system architecture <ref type="bibr" target="#b7">[8]</ref>.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="2">Organization modeling languages</head><p>To express the outer context of an incident to be modeled, organization modeling languages capture people's goals, their behavior, organizational structure and resources of the modeled context. Such types of models play an important role in enterprise modeling (EM, <ref type="bibr" target="#b5">[6]</ref>), to express types of business processes that are performed in an organization. Besides business contexts in a narrow sense, any organizational setting and projects with shared goals among groups of people can generically be expressed with the semantic modeling concepts provided by these modeling languages.</p><p>MEMOCenterNG comes pre-packaged with interrelated modeling languages of the MEMO OrgML <ref type="bibr" target="#b5">[6]</ref> that cover organization modeling. These are in the first place the Organization Diagram language for modeling organizational structure, and the Process Control Flow Language <ref type="bibr" target="#b5">[6]</ref>, which allow to express semantically rich process model descriptions of business processes and other methodical procedures in organizations. The Process Control Flow language is enhanced by the Process Decomposition Language which allows for specifying static decomposition relationships among process steps, i.e., express which process steps are made out of others. Finally, the Strategy Diagram and Activity Diagram languages for expressing strategy, goals and actions from a high-level strategic view are part of the environment.</p><p>To model physical and non-tangible resources in business contexts, the ResML [10] is included in the set of modeling languages, accompanied by the Allocation Diagram language which is responsible to express the mappings between process steps and resources.  The MEMO Meta Modeling Language (MML, <ref type="bibr" target="#b6">[7]</ref>) included in MEMOCen-terNG has especially been designed to efficiently enhance existing languages, and to automatically generate deployable diagram editors from meta-model descriptions of modeling languages. The MML puts special focus on interlinking multiple modeling languages. Concepts from other, previously existing MML models, can be referenced. Every concept is classified by a unique graphical symbol which indicates to which language it belongs.</p><p>Full-featured diagram editors can automatically be generated by a single mouse-click from MML models within the user-interface of MEMOCenterNG's MML editor. These generated diagram editors are fully downwards-compatible to the Eclipse Modeling Framework (EMF, <ref type="bibr" target="#b12">[13]</ref>) and Graphical Modeling Framework (GMF, <ref type="bibr" target="#b8">[9]</ref>) components, which allows for applying any additional EMF / GMF technology component to MML-specified model editors and corresponding model instances, and also use model-instances for analysis, transformation and codegeneration (see sect. 5). Figure <ref type="figure" target="#fig_3">3</ref> gives an example of an MML model edited in MEMOCenterNG. In order to take a traditional modeling view on a low abstraction level, MEMO-CenterNG contains three classical formal systems modeling languages, Entity Relationship Models (ERM, <ref type="bibr" target="#b1">[2]</ref>), Data Flow Diagrams (DFD, <ref type="bibr" target="#b2">[3]</ref>) and object oriented class diagrams from the Unified Modeling Language (UML, <ref type="bibr" target="#b0">[1]</ref>). Selected concepts of these languages can be referenced from elements in organization models to trace implementation details from a high real-world abstraction level down to technical details.</p><p>Each of the implementation-level modeling languages comes with pre-packaged analysis and code-generation functionality. The ERM model editor allows to generate a relational database schema from ERM models as a sequence of executable SQL data declaration statements, which subsequently may be executed from inside the Eclipse platform to deploy the initial database. The DFD editor comes with basic analysis capabilities, and from UML class diagrams, the source code for Java classes can be generated.</p><p>Together with the software development features of the underlying Eclipse  All components of MEMOCenterNG are based on the Eclipse Modeling Project <ref type="bibr" target="#b8">[9]</ref> components EMF and GMF, and make use of the Ecore language <ref type="bibr" target="#b4">[5]</ref> through the MML. As a consequence, any supplementary component that exists for the Eclipse Modeling Project can be applied in MEMOCenterNG, too. This allows for seamlessly integrating supporting technology such as Xtend / Xpand <ref type="bibr" target="#b4">[5]</ref>, and other specific code generation languages such as Velocity <ref type="bibr" target="#b11">[12]</ref>, or the QVT <ref type="bibr" target="#b10">[11]</ref> model transformation language. By default, the Eclipse components for Xtend / Xpand transformations are included in the MEMOCenterNG environment.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="6">Availability</head><p>A beta-version of MEMOCenterNG is available for download at http://www. wi-inf.uni-duisburg-essen.de/FGFrank/download/memo/. Please request password information from the authors.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="7">Conclusion and Outlook</head><p>We have presented a modeling tool that offers multiple modeling languages in an integrated environment, based on a meta-model supported language architecture and enriched by an easy-to-use meta-model editor for specific language enhancements. A common language architecture ensures the semantic integration of concepts across multiple languages. By incorporating meta modeling and the creation of new modeling languages into the feature spectrum of the modeling tool, a new degree of flexibility and adaptability to future requirements part of the application. This makes MEMOCenterNG a comprehensive, full-featured integrated modeling environment for multiple types of modeling projects, including modeldriven software development approaches. Currently, the tool is successfully used for teaching purposes and in medium-sized business projects carried out in cooperation with our research group.</p><p>In further research work, we intend to develop and integrate additional modeling languages, e.g., for designing indicator systems that are integrated with models of business processes and IT resources. We also plan to extend the framework with elaborate support for method engineering by integrating model editors with corresponding process editors.</p></div><figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_0"><head>Fig. 1 .</head><label>1</label><figDesc>Fig. 1. MEMOCenterNG component architecture</figDesc></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_1"><head>Figure 2</head><label>2</label><figDesc>Figure 2 shows an example Process Control Flow model edited in MEMO-CenterNG.</figDesc></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_2"><head>Fig. 2 .</head><label>2</label><figDesc>Fig. 2. Example MEMO Process Control Flow model</figDesc><graphic coords="4,152.06,160.75,311.25,238.06" type="bitmap" /></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_3"><head>Fig. 3 .</head><label>3</label><figDesc>Fig. 3. Example of an MML model edited in MEMOCenterNG</figDesc><graphic coords="5,152.06,152.44,311.25,226.24" type="bitmap" /></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_4"><head></head><label></label><figDesc><ref type="bibr" target="#b3">[4]</ref> platform, MEMOCenterNG forms a fully integrated model-driven software development environment. An example of integrating between an organization model and an implementation model is displayed in figure4.</figDesc></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_5"><head>Fig. 4 .</head><label>4</label><figDesc>Fig. 4. Integrating between an organization model and an implementation model</figDesc><graphic coords="6,152.06,161.75,311.24,228.23" type="bitmap" /></figure>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="1" xml:id="foot_0">MEMOCenterNG is named after the MEMO enterprise modeling method<ref type="bibr" target="#b5">[6]</ref>. "NG" stands for "Next Generation", MEMOCenterNG is the successor to an earlier MEMOCenter prototype application.</note>
		</body>
		<back>
			<div type="references">

				<listBibl>

<biblStruct xml:id="b0">
	<monogr>
		<title level="m" type="main">The Unified Modeling Language Reference Manual</title>
		<author>
			<persName><forename type="first">G</forename><surname>Booch</surname></persName>
		</author>
		<author>
			<persName><forename type="first">I</forename><surname>Jacobson</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>Rumbaugh</surname></persName>
		</author>
		<imprint>
			<date type="published" when="1999">1999</date>
			<publisher>Addison-Wesley</publisher>
			<pubPlace>Reading</pubPlace>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b1">
	<analytic>
		<title level="a" type="main">The Entity-Relationship Model -Toward a Unified View of Data</title>
		<author>
			<persName><forename type="first">P</forename><surname>Chen</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">ACM Transactions on Database Systems</title>
		<idno type="ISSN">0362-5915</idno>
		<imprint>
			<biblScope unit="volume">1</biblScope>
			<biblScope unit="page" from="9" to="36" />
			<date type="published" when="1976">/1/1976. 1976</date>
			<publisher>ACM-Press</publisher>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b2">
	<monogr>
		<title level="m" type="main">Structured Analysis and System Specification</title>
		<author>
			<persName><forename type="first">T</forename><surname>Demarco</surname></persName>
		</author>
		<imprint>
			<date type="published" when="1979">1979</date>
			<publisher>Prentice Hall</publisher>
			<pubPlace>Upper Saddle River</pubPlace>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b3">
	<monogr>
		<ptr target="http://www.eclipse.org/" />
		<title level="m">Eclipse Foundation: Eclipse Platform</title>
				<imprint>
			<date type="published" when="2010-04-25">2010-04-25</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b4">
	<monogr>
		<author>
			<persName><forename type="first">S</forename><surname>Efftinge</surname></persName>
		</author>
		<author>
			<persName><forename type="first">P</forename><surname>Friese</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Haase</surname></persName>
		</author>
		<author>
			<persName><surname>Others</surname></persName>
		</author>
		<ptr target="http://www.openarchitectureware.org/pub/documentation/4.3.1/html/contents/index.html" />
		<title level="m">openArchitectureWare User Guide</title>
				<imprint>
			<date type="published" when="2008">2008</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b5">
	<analytic>
		<title level="a" type="main">MEMO: A Tool Supported Methodology for Analyzing and (Re-)Designing Business Information Systems</title>
		<author>
			<persName><forename type="first">U</forename><surname>Frank</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Technology of Object-Oriented Languages and Systems</title>
				<editor>
			<persName><forename type="first">R</forename><surname>Ege</surname></persName>
		</editor>
		<editor>
			<persName><forename type="first">M</forename><surname>Singh</surname></persName>
		</editor>
		<editor>
			<persName><forename type="first">B</forename><surname>Meyer</surname></persName>
		</editor>
		<imprint>
			<date type="published" when="1994">1994</date>
			<biblScope unit="page" from="367" to="380" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b6">
	<monogr>
		<title level="m" type="main">The MEMO Meta Modeling Language (MML) and Language Architecture</title>
		<author>
			<persName><forename type="first">U</forename><surname>Frank</surname></persName>
		</author>
		<imprint>
			<date type="published" when="2008">2008</date>
		</imprint>
		<respStmt>
			<orgName>Institute for Computer Science and Business (ICB), University Duisburg-Essen</orgName>
		</respStmt>
	</monogr>
	<note type="report_type">ICB-Research Report No. 24</note>
</biblStruct>

<biblStruct xml:id="b7">
	<monogr>
		<title level="m" type="main">Beyond ERP Systems: An Outline of Self-Referential Enterprise Systems</title>
		<author>
			<persName><forename type="first">Ulrich</forename><surname>Frank</surname></persName>
		</author>
		<author>
			<persName><forename type="first">U</forename><surname>Strecker</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename></persName>
		</author>
		<imprint>
			<date type="published" when="2009">2009</date>
		</imprint>
		<respStmt>
			<orgName>Institute for Computer Science and Business (ICB), University Duisburg-Essen</orgName>
		</respStmt>
	</monogr>
	<note type="report_type">ICB-Research Report No. 31</note>
</biblStruct>

<biblStruct xml:id="b8">
	<monogr>
		<title level="m" type="main">Eclipse Modeling Project: A Domain-Specific Language (DSL) Toolkit</title>
		<author>
			<persName><forename type="first">R</forename><forename type="middle">C</forename><surname>Gronback</surname></persName>
		</author>
		<imprint>
			<date type="published" when="2009">2009</date>
			<publisher>Addison-Wesley Longman</publisher>
			<pubPlace>Amsterdam</pubPlace>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b9">
	<monogr>
		<author>
			<persName><forename type="first">J</forename><surname>Jung</surname></persName>
		</author>
		<title level="m">Entwurf einer Sprache für die Modellierung von Ressourcen im Kontext der Geschftsprozessmodellierung</title>
				<meeting><address><addrLine>Berlin</addrLine></address></meeting>
		<imprint>
			<publisher>Logos</publisher>
			<date type="published" when="2007">2007</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b10">
	<monogr>
		<ptr target="http://www.omg.org/spec/QVT/1.0" />
		<title level="m">Object Management Group: Meta Object Facility Query / View / Transformations</title>
				<imprint>
			<date type="published" when="2008">2008</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b11">
	<monogr>
		<ptr target="http://velocity.apache.org/(2010-04-25" />
		<title level="m">Apache Software Foundation: The Apache Velocity Project</title>
				<imprint/>
	</monogr>
</biblStruct>

<biblStruct xml:id="b12">
	<monogr>
		<author>
			<persName><forename type="first">D</forename><surname>Steinberg</surname></persName>
		</author>
		<author>
			<persName><forename type="first">F</forename><surname>Budinsky</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Paternostro</surname></persName>
		</author>
		<author>
			<persName><forename type="first">E</forename><surname>Merks</surname></persName>
		</author>
		<title level="m">EMF: Eclipse Modeling Framework</title>
				<meeting><address><addrLine>Amsterdam</addrLine></address></meeting>
		<imprint>
			<publisher>Addison-Wesley Longman</publisher>
			<date type="published" when="2009">2009</date>
		</imprint>
	</monogr>
	<note>2nd edition</note>
</biblStruct>

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