%0 Journal Article %1 burgues_08_improving %A Burgu'es, Xavier %A Franch, Xavier %A Rib'o, Josep %D 2008 %J Software and Systems Modeling %K 2008 metamodelling uml %N 3 %P 361--379 %R http://dx.doi.org/10.1007/s10270-007-0062-z %T Improving the accuracy of UML metamodel extensions by introducing induced associations %U http://dx.doi.org/10.1007/s10270-007-0062-z %V 7 %X Abstract^A ^A In the process of extending the UML metamodel for a specific domain, the metamodel specifier introduces frequently some metaassociations at MOF level M2 with the aim that they induce some specific associations at MOF level M1. For instance, if a metamodel for software process modelling states that a ^a€oeRole"i¿½? is responsible for an ^a€oeArtifact"i¿½?, we can interpret that its specifier intended to model two aspects: (1) the implications of this metaassociation at level M1 (e.g., the specific instance of Role ^a€oeTestEngineer"i¿½? is responsible for the specific instance of Artifact ^a€oeTestPlans"i¿½?); and (2) the implications of this metaassociation at level M0 (e.g., ^a€oeJohn Doe"i¿½? is the responsible test engineer for elaborating the test plans for the package ^a€oeFoo"i¿½?). Unfortunately, the second aspect is often not enforced by the metamodel and, as a result, the models which are defined as its instances may not incorporate it. This problem, consequence of the so-called ^a€oeshallow instantiation"i¿½? in Atkinson and Khne (Procs. UML^a€™01, LNCS 2185, Springer, 2001), prevents these models from being accurate enough in the sense that they do not express all the information intended by the metamodel specifier and consequently do not distinguish metaassociations that induce associations at M1 from those that do not. In this article we introduce the concept of induced association that may come up when an extension of the UML metamodel is developed. The implications that this concept has both in the extended metamodel and in its instances are discussed. We also present a methodology to enforce that M1 models incorporate the associations induced by the metamodel which they are instances from. Next, as an example of application we present a quality metamodel for software artifacts which makes intensive use of induced associations. Finally, we introduce a software tool to assist the development of quality models as correct instantiations of the metamodel, assuring the proper application of the induced associations as required by the metamodel.

@article{burgues_08_improving, abstract = {Abstract^{A} ^{A} In the process of extending the UML metamodel for a specific domain, the metamodel specifier introduces frequently some metaassociations at MOF level M2 with the aim that they induce some specific associations at MOF level M1. For instance, if a metamodel for software process modelling states that a ^{a}€{oe}Role"{i}¿½? is responsible for an ^{a}€{oe}Artifact"{i}¿½?, we can interpret that its specifier intended to model two aspects: (1) the implications of this metaassociation at level M1 (e.g., the specific instance of Role ^{a}€{oe}TestEngineer"{i}¿½? is responsible for the specific instance of Artifact ^{a}€{oe}TestPlans"{i}¿½?); and (2) the implications of this metaassociation at level M0 (e.g., ^{a}€{oe}John Doe"{i}¿½? is the responsible test engineer for elaborating the test plans for the package ^{a}€{oe}Foo"{i}¿½?). Unfortunately, the second aspect is often not enforced by the metamodel and, as a result, the models which are defined as its instances may not incorporate it. This problem, consequence of the so-called ^{a}€{oe}shallow instantiation"{i}¿½? in Atkinson and Khne (Procs. UML^{a}€™01, LNCS 2185, Springer, 2001), prevents these models from being accurate enough in the sense that they do not express all the information intended by the metamodel specifier and consequently do not distinguish metaassociations that induce associations at M1 from those that do not. In this article we introduce the concept of induced association that may come up when an extension of the UML metamodel is developed. The implications that this concept has both in the extended metamodel and in its instances are discussed. We also present a methodology to enforce that M1 models incorporate the associations induced by the metamodel which they are instances from. Next, as an example of application we present a quality metamodel for software artifacts which makes intensive use of induced associations. Finally, we introduce a software tool to assist the development of quality models as correct instantiations of the metamodel, assuring the proper application of the induced associations as required by the metamodel.}, added-at = {2009-02-11T20:12:31.000+0100}, author = {Burgu'{e}s, Xavier and Franch, Xavier and Rib'{o}, Josep}, biburl = {https://www.bibsonomy.org/bibtex/201e008fd5bb62690f254167d14645a7e/leonardo}, citeulike-article-id = {1454098}, doi = {http://dx.doi.org/10.1007/s10270-007-0062-z}, interhash = {caf3868bb0e0d5237acad2caad5da642}, intrahash = {01e008fd5bb62690f254167d14645a7e}, journal = {Software and Systems Modeling}, keywords = {2008 metamodelling uml}, month = {July}, number = 3, pages = {361--379}, posted-at = {2007-08-01 01:31:33}, priority = {3}, timestamp = {2009-02-11T20:12:31.000+0100}, title = {Improving the accuracy of UML metamodel extensions by introducing induced associations}, url = {http://dx.doi.org/10.1007/s10270-007-0062-z}, volume = 7, year = 2008 }