<?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">On Evaluating Multi-Level Modeling</title>
			</titleStmt>
			<publicationStmt>
				<publisher/>
				<availability status="unknown"><licence/></availability>
			</publicationStmt>
			<sourceDesc>
				<biblStruct>
					<analytic>
						<author>
							<persName><forename type="first">Colin</forename><surname>Atkinson</surname></persName>
							<affiliation key="aff0">
								<orgName type="institution">University of Mannheim Mannheim</orgName>
								<address>
									<country key="DE">Germany</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Thomas</forename><surname>Kühne</surname></persName>
							<affiliation key="aff1">
								<orgName type="institution">Victoria University of Wellington</orgName>
								<address>
									<settlement>Wellington</settlement>
									<country key="NZ">New Zealand</country>
								</address>
							</affiliation>
						</author>
						<title level="a" type="main">On Evaluating Multi-Level Modeling</title>
					</analytic>
					<monogr>
						<imprint>
							<date/>
						</imprint>
					</monogr>
					<idno type="MD5">6124274A7DA28248EBD5233AF51BEC3C</idno>
				</biblStruct>
			</sourceDesc>
		</fileDesc>
		<encodingDesc>
			<appInfo>
				<application version="0.7.2" ident="GROBID" when="2023-03-24T01:16+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>Multi-Level Modeling is receiving increasing levels of interest and its active research community is continuing to make progress. However, to advance the discipline effectively it is necessary to increase industry adoption and achieve better community cohesion. We believe that the key to addressing both these challenges is to promote the creation of more comparisons in the multi-level modeling field based on meaningful objective evaluations. In this position paper, we provide our view on what constitutes meaningful evaluations and discuss some of the issues involved in obtaining them, while presenting a broad overview of existing multi-level modeling evaluations. In particular, we emphasize the importance of understanding and managing the difference between internal and external qualities.</p></div>
			</abstract>
		</profileDesc>
	</teiHeader>
	<text xml:lang="en">
		<body>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>I. INTRODUCTION</head><p>Although Multi-level Modeling (MLM) has seen steady development over recent years, industry adoption is still virtually non-existent (a rare application of MLM in an industry setting is described in <ref type="bibr" target="#b7">[8]</ref>). One explanation for the low adoption rate is the current unavailability of industrial-strength approaches and tools. However, even if better tool support were available, wider adoption would still be hindered by the lack of compelling evidence that switching from Two-Level Modeling (TLM) to MLM brings benefits in industrial contexts. Creating convincing comparisons would reduce this barrier and could even expedite MLM research through industrial funding.</p><p>Another obstacle to the discipline's future growth is the lack of research cohesion that may eventually make it impossible for community members to build on each other's results. Without a sense of direction -i.e., a common understanding of the way forward -the discipline runs the risk of research diversification to a point where it loses its core focus and subsequently critical mass. We therefore believe that objective comparisons between competing approaches are not only desirable to provide a compass for future development but may eventually become necessary for the discipline's survival.</p><p>Since convincing comparative evaluations are the key to addressing both of the aforementioned challenges, in this position paper we discuss some of the issues involved in performing such evaluations in the context of MLM. We first establish the basic parameters of meaningful, scientifically sound evaluations and then discuss a variety of concrete approaches, pointing to existing work where applicable.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>II. MEANINGFUL EVALUATIONS</head><p>The effectiveness of MLM evaluations in promoting industry adoption and research cohesion depends on the extent to which they measure something of relevance. Naturally, relevance itself depends on the stakeholders and their respective goals. However, in general, a meaningful evaluation provides results that have some kind of real-world relevance. In contrast, a meaningless evaluation -e.g., measuring the number of vowels in a language's keywords -has no such real-world relevance. A comparison based on such an evaluation would not yield any meaningful insights into which language should be preferred for achieving any reasonable real-world impact. Meaningful evaluations, on the other hand, should be designed to deliver some insights that provide the basis for pragmatic guidance. In order for an evaluation to be meaningful in our sense, it must address the following aspects: A 1 : Measurability Any targeted properties must be objectively observable. Ideally, measurements should yield numeric results that are directly proportional to the property being measured, as it is then not only possible to decide which approach is better but also by how much. It is never possible to judge an approach or tool to be, e.g., "good" or "productive", without breaking down how the quality concerned manifests itself in terms of measurable properties. A 2 : Conclusiveness Measurements should yield consistent results. Repeated performances of the evaluation need not yield exactly the same outcome, but they should deliver reliable values within a given margin of error. This also excludes results with low confidence (e.g., because they lack statistical significance). A 3 : Impartiality The choice of the properties to be measured must not favor particularities of one solution that have no proven relationship to the ultimate goal. For example, a set of postulated requirements must be formulated in such a manner that they reference the problem-domain and the ultimate benefits to the targeted user rather than solution details. A 4 : Trueness When using proxies (e.g. substitutes for realworld artifacts or practitioners) care must be taken to ensure that no circumstantial bias is introduced. Trueness, therefore comprises at least: A 4.1 : Context Relevance Model proxies (i.e., samples used in lieu of real-world models) and the assumed operations on them should be demonstrated to be representative. Otherwise, a skewed selection could introduce undesired bias.</p><p>A 4.2 : Demographic Relevance Substitute users should be demonstrated to be representative of real users. In general, it is not possible to transfer results between different bodies of users (e.g., from students to practitioners in the field).</p><p>A 5 : Pragmatic Relevance Targeted properties must have a bearing on the actual needs of the intended users. This criterion is the very foundation of a meaningful evaluation. The previous aspects essentially characterize sound evaluations, whereas pragmatic relevance requires that there is an intent to measure something of pragmatic value.</p><p>It is obviously challenging to "tick" all the above "boxes" in practice, but we feel it is useful to have a checklist that helps to document where an evaluation may be lacking.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>III. INTERNAL VERSUS EXTERNAL QUALITIES</head><p>Some of the aforementioned aspects are more difficult to address than others. In order to understand why, it is important to be aware of whether an evaluation is intended to evaluate an internal quality or an external quality. We use these terms with their usual meaning in software engineering <ref type="bibr" target="#b16">[17]</ref>.</p><p>In our context, internal qualities pertain to the directly measurable properties of a model, e.g., number of model elements, number of constraints, average inheritance depth, etc. External qualities, on the other hand, pertain to the experience users have when working with a model, e.g., creating it, understanding it, maintaining it, etc.</p><p>Ultimately, only the external qualities have a direct bearing on meaningful evaluations. However, due to the cost and challenges involved in assessing external qualities directly in a meaningful way, one often attempts to approximate the assessment of external qualities by assessing internal qualities instead, based on the idea that there is a correlation between internal and external qualities. It is standard practice to assume that optimizing certain internal qualities (e.g., reducing complexity) is the key to achieving certain desirable external qualities (e.g., increased maintainability). However, such an indirect evaluation of external properties is only trustworthy if the assumed underlying correlation has been demonstrated, or at least has been made plausible by compelling arguments.</p><p>Interestingly, A 1 &amp;A 2 are most easily addressed by focusing on the internal qualities of an approach. Such qualities, e.g., the complexity of the models created by an approach, can typically be reliably assessed. In contrast, assessing external qualities often implies some compromise in A 1 &amp;A 2 because sample populations may be small or certain assumptions may not generalize.</p><p>Aspects A 3 &amp; A 5 , on the other hand, are best addressed by focusing on the external qualities of an approach. External qualities directly reflect the utility of the approach to its users and hence avoid solution bias (A 3 ) plus intrinsically imply pragmatic relevance (A 5 ). The increased cost involved in directly assessing external qualities relates to ensuring conclusiveness (A 2 ) and trueness (A 4 ). This cost is considerable and therefore represents a major hurdle for this kind of evaluation.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>IV. ASSESSING INTERNAL QUALITIES</head><p>Complexity is one of the most commonly measured internal qualities since it is assumed to have a correlation with important external qualities such as maintainability, robustness, and trustworthiness etc. In fact, the main value proposition for MLM is its ability to reduce accidental complexity <ref type="bibr" target="#b2">[3]</ref>, i.e., the difference in complexity between an ideal model and a concrete model involving solution-induced overhead, e.g. workarounds.</p><p>A number of evaluations of multi-level modeling have been based on approximating the complexity of a model by measuring its size, that is, the number of its elements. For example, Gerbig performed a comparison based on model size in his Ph.D. thesis using a sample model from the enterprise architecture domain <ref type="bibr" target="#b6">[7]</ref>. The MLM version of the model has 50 modeling elements while the TLM version, using standard workaround patterns such as the Type-Object pattern <ref type="bibr" target="#b9">[10]</ref>, has 95 modeling elements, amounting to an increase of 90%. Rossini et al. performed a similar evaluation which yielded a three-fold increase in the number of modeling elements in a two-level versus a multi-level model of their CloudML scenario <ref type="bibr" target="#b15">[16]</ref>.</p><p>The extent of the practical relevance of the above evaluations was shown by <ref type="bibr">de Lara et. al</ref>. by measuring the application frequency of TLM workaround techniques (cf. "Item Descriptor" pattern <ref type="bibr" target="#b5">[6]</ref>, "Type-Object" pattern <ref type="bibr" target="#b9">[10]</ref>, "Adaptive Object-Model" <ref type="bibr" target="#b17">[18]</ref>, etc.) in real-world models <ref type="bibr" target="#b11">[12]</ref>. Since these workaround techniques are responsible for increases of the size of two-level models relative to their multi-level counterparts, de Lara et al. hence demonstrated that the observations made in <ref type="bibr" target="#b6">[7]</ref>, <ref type="bibr" target="#b15">[16]</ref> apply to a wide range of modeling practice. As much as 35% of all models in some areas <ref type="bibr" target="#b11">[12]</ref>, could thus benefit from the potential size reductions.</p><p>Although the above results provide a convincing endorsement for the practical relevance of MLM, they do so only to the extent that the assumption that model size<ref type="foot" target="#foot_0">1</ref> approximates model complexity is reasonable. A larger model based on a simple underlying language could conceivably be preferable to a compact model based on a complex language.</p><p>Going beyond assessing model size, it appears useful to consider other classic metrics <ref type="bibr" target="#b4">[5]</ref>, <ref type="bibr" target="#b12">[13]</ref>, <ref type="bibr" target="#b14">[15]</ref> and quality attributes <ref type="bibr" target="#b3">[4]</ref>, <ref type="bibr" target="#b13">[14]</ref>. Indeed, in his MLM vs TLM comparison, Gerbig also considered such classic metrics <ref type="bibr" target="#b6">[7]</ref>. Overall, however, these proved to be less conclusive than model size comparisons, although he detected clear advantages for MLM with respect to coupling (average number of distinct connected classes) and overhead<ref type="foot" target="#foot_1">2</ref> ((well-formedness rules + additional operations)/ element count)) <ref type="bibr" target="#b6">[7]</ref>.</p><p>Given these less conclusive results (compared to model size analyses) it would be easy to be skeptical about the actual advantages offered by MLM. However, it is important to observe that these metrics were originally designed to target the type level only and thus entirely ignore the instance-level complexity caused by the application of TLM workarounds. This weakness of classic metrics for evaluating MLM is understandable given their motivation rooted in programming and/or modeling software. In these contexts, instances and </p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>TABLE I COGNITIVE CHALLENGES OF THE "5C"-APPROACH</head><p>their relationships are irrelevant to users. However, in many domain modeling applications instances directly represent the subject under study. In such contexts, the complexity of instance models is therefore very much a concern to users and should thus be considered in evaluations.</p><p>Instead of focusing on model properties (e.g., model complexity), one may also consider language properties (e.g., language expressiveness). For example, Atkinson et al. based their comparison of Melanee with MetaDepth on the differences between their respective language features <ref type="bibr" target="#b1">[2]</ref>. Grossmann et al.'s more comprehensive comparison of 21 MLM approaches <ref type="bibr" target="#b8">[9]</ref> also involved language feature comparisons. However, Grossmann et al. also considered the intended target audience and the purpose of approaches, and furthermore considered the extent to which an approach has seen industry usage. This latter consideration could be regarded as including an external quality, but without further information on how well the respective MLM approaches performed in industrial contexts it is only a good starting point for further investigations.</p><p>Ideally, feature-based comparisons should be accompanied by an analysis of the impact of the different features on users. While certain features may seem elegant, ultimately their value must be assessed by considering external qualities.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>V. ASSESSING EXTERNAL QUALITIES</head><p>In order to evaluate the ultimate purpose of any approach intended to deliver value to a user, it is necessary to determine properties based on external qualities which relate to user experience. As far as we are aware, only two MLM evaluations of this kind have been performed to date. Both of these investigate model changes and thus can be reasonably regarded as evaluating (aspects of) maintainability. In his Ph.D. thesis, Gerbig performed a comparative model change analysis by counting the number of primitive change operations needed to respond to certain requirements changes <ref type="bibr" target="#b6">[7]</ref>. It turned out that a homogeneous treatment of all classification levels and Melanee's emendation service <ref type="bibr" target="#b0">[1]</ref> reduce the effort needed to change the multi-level version of the model compared to the two-level, EMF-based version.</p><p>Kimura et al., also used a change-based approach to compare Melanee, MetaDepth and EMF, with a particular focus on extensibility <ref type="bibr" target="#b10">[11]</ref>. These kinds of analyses exhibit ideal measurability, reproducibility, impartiality, and pragmatic relevance. However, whether context relevance is adequately addressed depends on how representative the chosen models and editing operations are.</p><p>Another external quality which lends itself relatively straightforwardly to measurement is model robustness, i.e., the resilience of a model to user error. Here the goal would be to assess the likelihood of introducing errors when creating/maintaining models. In particular, in the context of MLM to TLM comparisons, one would expect a two-level model to suffer from more accidentally introduced errors than a corresponding multi-level model. TLM would only provide the same safeguards against the introduction of model inconsistencies if all the well-formedness constraints implied by MLM are transposed into the equivalent TLM models. One would still, however, expect a higher rate of well-formedness violations, since it is most likely easier to make mistakes in a lower level two-level model, compared to a higher-level multi-level model.</p><p>The final external quality we can cover here is productivity, i.e., the speed by which users can develop or make changes to models. The underlying hypothesis of what could be referred to as cognitive challenge-based evaluations is that modeler performance is a function of the adequacy of the language/tool used. The higher the adequacy of the language/tool, the better the modeler should perform when facing standard tasks.</p><p>To this end, we propose a "5C"-approach, comprising the cognitive challenges listed in Table <ref type="table">I</ref>.</p><p>Assessing the adequacy of an approach would be performed by measuring completion speeds for representative concrete tasks of the above five kinds. If languages/tools actually yield different levels of productivity, one should expect to see differences in the C 1 -C 5 completion measurements. Ideally, subjects should be chosen in such a way that results transfer to the intended user base in order to achieve demographic relevance. Full context relevance will be very hard to achieve with this approach as it is typically not feasible to work with realistically sized models in such experiments.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>VI. CONCLUSION</head><p>The goal of this position paper has been to provide a discussion of the issues involved when aiming to perform meaningful evaluations while providing a broad overview of the MLM evaluations that have been conducted to date. The number of already existing MLM evaluations is encouraging and each of them represents a very useful step towards growing MLM as a discipline. However, our discussion has shown that the evaluations performed until now are overwhelmingly focused on internal rather than external qualities. Hence their pragmatic relevance -in the absence of the demonstration of a strong correlation between the internal qualities they asses with the external qualities that matter to users -is limited.</p><p>It is natural that the first evaluations performed in an emerging field are focused on internal qualities, as these are usually much easier to asses than external ones. However, we believe that for a) the benefits of MLM to become convincing enough to generate serious interest from industry, and b) comparative evaluations to become useful enough to maintain the cohesion and momentum the research community requires, more user-oriented evaluations focusing on external qualities will be needed.</p><p>An important initiative in this regard is the "Bicycle Challenge" proposed by the MULTI 2017 workshop as a common sample scenario, allowing various MLM approaches to be compared based on an example with practical relevance. Ideally, more such benchmarks will be designed in the future along with agreed upon usage scenarios, e.g., involving subsequent extensions, detecting and removing defects, etc.</p><p>It will remain a challenge to distinguish models and usage scenarios that have context relevance from those that do not, but any attempts to move MLM evaluations towards directly assessing external qualities or to strengthen the confidence in hitherto only assumed correlations between internal and external qualities will represent significant steps forward.</p></div>			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="1" xml:id="foot_0">Apparently equivalent to the much debated "lines of code" metric for source code.</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="2" xml:id="foot_1">Referred to as "complexity" in<ref type="bibr" target="#b6">[7]</ref>.</note>
		</body>
		<back>
			<div type="references">

				<listBibl>

<biblStruct xml:id="b0">
	<analytic>
		<title level="a" type="main">On-the-fly emendation of multilevel models</title>
		<author>
			<persName><forename type="first">C</forename><surname>Atkinson</surname></persName>
		</author>
		<author>
			<persName><forename type="first">R</forename><surname>Gerbig</surname></persName>
		</author>
		<author>
			<persName><forename type="first">B</forename><surname>Kennel</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Proceedings of the 8th European Conference on Modelling Foundations and Applications</title>
				<meeting>the 8th European Conference on Modelling Foundations and Applications</meeting>
		<imprint>
			<publisher>Springer</publisher>
			<date type="published" when="2012">2012</date>
			<biblScope unit="page" from="194" to="209" />
		</imprint>
	</monogr>
	<note>ECMFA&apos;12</note>
</biblStruct>

<biblStruct xml:id="b1">
	<analytic>
		<title level="a" type="main">A feature-based comparison of melanee and metadepth</title>
		<author>
			<persName><forename type="first">C</forename><surname>Atkinson</surname></persName>
		</author>
		<author>
			<persName><forename type="first">R</forename><surname>Gerbig</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><forename type="middle">D</forename><surname>Lara</surname></persName>
		</author>
		<author>
			<persName><forename type="first">E</forename><surname>Guerra</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Proceedings of the 3rd Workshop on Multi-Level Modelling co-located with the 19th ACM/IEEE International Conference MODELS 2016</title>
		<title level="s">CEUR Workshop Proceedings</title>
		<meeting>the 3rd Workshop on Multi-Level Modelling co-located with the 19th ACM/IEEE International Conference MODELS 2016</meeting>
		<imprint>
			<biblScope unit="volume">1722</biblScope>
			<biblScope unit="page" from="25" to="34" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b2">
	<analytic>
		<title level="a" type="main">Reducing accidental complexity in domain models</title>
		<author>
			<persName><forename type="first">C</forename><surname>Atkinson</surname></persName>
		</author>
		<author>
			<persName><forename type="first">T</forename><surname>Kühne</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Software and Systems Modeling</title>
		<imprint>
			<biblScope unit="volume">7</biblScope>
			<biblScope unit="issue">3</biblScope>
			<biblScope unit="page" from="345" to="359" />
			<date type="published" when="2008">2008</date>
			<publisher>Springer Verlag</publisher>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b3">
	<analytic>
		<title level="a" type="main">A hierarchical model for object-oriented design quality assessment</title>
		<author>
			<persName><forename type="first">J</forename><surname>Bansiya</surname></persName>
		</author>
		<author>
			<persName><forename type="first">C</forename><forename type="middle">G</forename><surname>Davis</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">IEEE Trans. Softw. Eng</title>
		<imprint>
			<biblScope unit="volume">28</biblScope>
			<biblScope unit="issue">1</biblScope>
			<biblScope unit="page" from="4" to="17" />
			<date type="published" when="2002-01">Jan 2002</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b4">
	<analytic>
		<title level="a" type="main">A metrics suite for object oriented design</title>
		<author>
			<persName><forename type="first">S</forename><forename type="middle">R</forename><surname>Chidamber</surname></persName>
		</author>
		<author>
			<persName><forename type="first">C</forename><forename type="middle">F</forename><surname>Kemerer</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">IEEE Transactions on Software Engineering</title>
		<imprint>
			<biblScope unit="volume">20</biblScope>
			<biblScope unit="issue">6</biblScope>
			<biblScope unit="page" from="476" to="493" />
			<date type="published" when="1994">1994</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b5">
	<analytic>
		<title level="a" type="main">Object-oriented patterns</title>
		<author>
			<persName><forename type="first">P</forename><surname>Coad</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Communications of the ACM</title>
		<imprint>
			<biblScope unit="volume">35</biblScope>
			<biblScope unit="issue">9</biblScope>
			<biblScope unit="page" from="152" to="159" />
			<date type="published" when="1992-09">Sep 1992</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b6">
	<monogr>
		<author>
			<persName><forename type="first">R</forename><surname>Gerbig</surname></persName>
		</author>
		<title level="m">Deep, Seamless, Multi-format, Multi-notation Definition and Use of Domain-specific Languages</title>
				<imprint>
			<date type="published" when="2017">2017</date>
		</imprint>
		<respStmt>
			<orgName>University of Mannheim</orgName>
		</respStmt>
	</monogr>
	<note type="report_type">Ph.D. thesis</note>
</biblStruct>

<biblStruct xml:id="b7">
	<analytic>
		<title level="a" type="main">An integrated multi-level modeling approach for industrial-scale data interoperability</title>
		<author>
			<persName><forename type="first">M</forename><surname>Igamberdiev</surname></persName>
		</author>
		<author>
			<persName><forename type="first">G</forename><surname>Grossmann</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Selway</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Stumptner</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Software &amp; Systems Modeling</title>
		<imprint>
			<biblScope unit="page" from="1" to="26" />
			<date type="published" when="2016">2016</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b8">
	<analytic>
		<title level="a" type="main">A feature-based categorization of multi-level modeling approaches and tools</title>
		<author>
			<persName><forename type="first">M</forename><surname>Igamberdiev</surname></persName>
		</author>
		<author>
			<persName><forename type="first">G</forename><surname>Grossmann</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Stumptner</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Proceedings of the 3rd Workshop on Multi-Level Modelling co-located with the 19th ACM/IEEE International Conference MODELS 2016</title>
		<title level="s">CEUR Workshop Proceedings</title>
		<meeting>the 3rd Workshop on Multi-Level Modelling co-located with the 19th ACM/IEEE International Conference MODELS 2016</meeting>
		<imprint>
			<biblScope unit="volume">1722</biblScope>
			<biblScope unit="page" from="45" to="55" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b9">
	<analytic>
		<title level="a" type="main">Type object</title>
		<author>
			<persName><forename type="first">R</forename><surname>Johnson</surname></persName>
		</author>
		<author>
			<persName><forename type="first">B</forename><surname>Woolf</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Pattern Languages of Program Design 3</title>
				<editor>
			<persName><forename type="first">R</forename><forename type="middle">C</forename><surname>Martin</surname></persName>
		</editor>
		<editor>
			<persName><forename type="first">D</forename><surname>Riehle</surname></persName>
		</editor>
		<editor>
			<persName><forename type="first">F</forename><surname>Buschmann</surname></persName>
		</editor>
		<imprint>
			<publisher>Addison-Wesley</publisher>
			<date type="published" when="1997">1997</date>
			<biblScope unit="page" from="47" to="65" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b10">
	<analytic>
		<title level="a" type="main">An evaluation of multi-level modeling frameworks for extensible graphical editing tools</title>
		<author>
			<persName><forename type="first">K</forename><forename type="middle">S</forename><surname>Kosaku Kimura</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Proceedings of the 3rd Workshop on Multi-Level Modelling co-located with the 19th ACM/IEEE International Conference MODELS 2016</title>
		<title level="s">CEUR Workshop Proceedings</title>
		<meeting>the 3rd Workshop on Multi-Level Modelling co-located with the 19th ACM/IEEE International Conference MODELS 2016</meeting>
		<imprint>
			<biblScope unit="volume">1722</biblScope>
			<biblScope unit="page" from="35" to="44" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b11">
	<analytic>
		<title level="a" type="main">When and how to use multilevel modelling</title>
		<author>
			<persName><forename type="first">J</forename><forename type="middle">D</forename><surname>Lara</surname></persName>
		</author>
		<author>
			<persName><forename type="first">E</forename><surname>Guerra</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><forename type="middle">S</forename><surname>Cuadrado</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">ACM Transactions on Software Engineering and Methodology</title>
		<imprint>
			<biblScope unit="volume">24</biblScope>
			<biblScope unit="issue">2</biblScope>
			<biblScope unit="page">46</biblScope>
			<date type="published" when="2014">2014</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b12">
	<monogr>
		<title level="m" type="main">Object-oriented software metrics: a practical guide</title>
		<author>
			<persName><forename type="first">M</forename><surname>Lorenz</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>Kidd</surname></persName>
		</author>
		<imprint>
			<date type="published" when="1994">1994</date>
			<publisher>Prentice-Hall, Inc</publisher>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b13">
	<analytic>
		<title level="a" type="main">Applying oo metrics to assess uml meta-models</title>
		<author>
			<persName><forename type="first">H</forename><surname>Ma</surname></persName>
		</author>
		<author>
			<persName><forename type="first">W</forename><surname>Shao</surname></persName>
		</author>
		<author>
			<persName><forename type="first">L</forename><surname>Zhang</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Z</forename><surname>Ma</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Y</forename><surname>Jiang</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Proceedings of UML 2004</title>
				<editor>
			<persName><forename type="first">T</forename><surname>Baar</surname></persName>
		</editor>
		<editor>
			<persName><forename type="first">A</forename><surname>Strohmeier</surname></persName>
		</editor>
		<editor>
			<persName><forename type="first">A</forename><surname>Moreira</surname></persName>
		</editor>
		<editor>
			<persName><forename type="first">S</forename><forename type="middle">J</forename><surname>Mellor</surname></persName>
		</editor>
		<meeting>UML 2004<address><addrLine>Lisbon, Portugal</addrLine></address></meeting>
		<imprint>
			<publisher>Springer</publisher>
			<date type="published" when="2004">2004</date>
			<biblScope unit="page" from="12" to="26" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b14">
	<analytic>
		<title level="a" type="main">Product metrics for object-oriented systems</title>
		<author>
			<persName><forename type="first">S</forename><surname>Purao</surname></persName>
		</author>
		<author>
			<persName><forename type="first">V</forename><surname>Vaishnavi</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">ACM Comput. Surv</title>
		<imprint>
			<biblScope unit="volume">35</biblScope>
			<biblScope unit="issue">2</biblScope>
			<biblScope unit="page" from="191" to="221" />
			<date type="published" when="2003">2003</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b15">
	<analytic>
		<title level="a" type="main">A comparison of two-level and multi-level modelling for cloud-based applications</title>
		<author>
			<persName><forename type="first">A</forename><surname>Rossini</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>De Lara</surname></persName>
		</author>
		<author>
			<persName><forename type="first">E</forename><surname>Guerra</surname></persName>
		</author>
		<author>
			<persName><forename type="first">N</forename><surname>Nikolov</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Proceedings of ECMFA</title>
				<meeting>ECMFA</meeting>
		<imprint>
			<date type="published" when="2015">2015. 2015</date>
			<biblScope unit="volume">9153</biblScope>
			<biblScope unit="page" from="18" to="32" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b16">
	<monogr>
		<title level="m" type="main">Software Engineering</title>
		<author>
			<persName><forename type="first">I</forename><surname>Sommerville</surname></persName>
		</author>
		<imprint>
			<date type="published" when="2016">2016</date>
			<publisher>Pearson</publisher>
		</imprint>
	</monogr>
	<note>10 th edn.</note>
</biblStruct>

<biblStruct xml:id="b17">
	<analytic>
		<title level="a" type="main">The adaptive object-model architectural style</title>
		<author>
			<persName><forename type="first">J</forename><forename type="middle">W</forename><surname>Yoder</surname></persName>
		</author>
		<author>
			<persName><forename type="first">R</forename><forename type="middle">E</forename><surname>Johnson</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Proceedings of the 3rd IEEE/IFIP Conference on Software Architecture: System Design, Development and Maintenance</title>
				<meeting>the 3rd IEEE/IFIP Conference on Software Architecture: System Design, Development and Maintenance</meeting>
		<imprint>
			<publisher>Kluwer</publisher>
			<date type="published" when="2002">2002</date>
			<biblScope unit="page" from="3" to="27" />
		</imprint>
	</monogr>
</biblStruct>

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