There are many different techniques and notations for extracting architecturally interesting information from the source code of existing software systems. This process is known as reverse engineering. One current problem with reverse engineering techniques is that models of software systems cannot easily be transferred from one notation and storage format to another. We refer to this as the problem of bridging <em>technical spaces</em>. <br /><br /> In this work, we approach the issue of bridging between the SWAG technical space and the UML technical space. The SWAG technical space, named after the Software Architecture Group at the University of Waterloo, consists of fact extractors, fact manipulators, schemas, and a fact storage language - the Tuple-Attribute language (TA). The UML technical space consists of the UML metamodel, the XML Metadata Interchange (XMI) format for encoding UML models, and various UML modeling tools. We have designed and implemented a plugin for MagicDraw UML, which will import, export, and merge between XMI-encoded UML models and TA-encoded Function-Level Schema models. <br /><br /> We document evidence of what is referred to as a <em>Bridge Domain</em> - a technical space which exists between two encodable spaces. The metamodels of the two notation languages that we have focused on are very rich and flexible, but neither technical space is capable of fully expressing an accurate architectural model of any given software system; however, each technical space is capable of maintaining certain semantic information relevant to that technical space through multiple merge operations.

There are many different techniques and notations for extracting architecturally interesting information from the source code of existing software systems. This process is known as reverse engineering. One current problem with reverse engineering techniques is that models of software systems cannot easily be transferred from one notation and storage format to another. We refer to this as the problem of bridging <em>technical spaces</em>. <br /><br /> In this work, we approach the issue of bridging between the SWAG technical space and the UML technical space. The SWAG technical space, named after the Software Architecture Group at the University of Waterloo, consists of fact extractors, fact manipulators, schemas, and a fact storage language - the Tuple-Attribute language (TA). The UML technical space consists of the UML metamodel, the XML Metadata Interchange (XMI) format for encoding UML models, and various UML modeling tools. We have designed and implemented a plugin for MagicDraw UML, which will import, export, and merge between XMI-encoded UML models and TA-encoded Function-Level Schema models. <br /><br /> We document evidence of what is referred to as a <em>Bridge Domain</em> - a technical space which exists between two encodable spaces. The metamodels of the two notation languages that we have focused on are very rich and flexible, but neither technical space is capable of fully expressing an accurate architectural model of any given software system; however, each technical space is capable of maintaining certain semantic information relevant to that technical space through multiple merge operations.

<p>In order to automate development of integration adapters in industrial<br />settings, a model-driven approach to adapter specification is devised. In this<br />approach, a domain-specific modeling language is created to allow<br />specification of mappings between integrated technical spaces. Also<br />proposed is the mapping automation engine that comprises reuse and<br />alignment algorithms. Based on mapping specifications, executable adapters<br />are automatically generated and executed. Results of approach evaluations<br />indicate that it is possible to use a model-driven approach to successfully<br />integrate technical spaces and increase the automation by reusing domainspecific<br />mappings from previously created adapters.</p> / <p>За потребе повећања степена аутоматизације развоја адаптера за<br />интеграцију у индустријском окружењу, осмишљен је моделом вођен<br />приступ развоју адаптера. У оквиру овог приступа развијен је наменски<br />језик за спецификацију пресликавања између техничких простора који су<br />предмет интеграције. Приступ обухвата и алгоритме за поравнање и<br />поновно искориштење претходно креираних пресликавања са циљем<br />аутоматизације процеса спецификације. На основу креираних<br />пресликавања, могуће je аутоматски генерисати извршиви код адаптера.<br />У испитивањима приступа, показано је да је могуће успешно применити<br />моделом вођен приступ у интеграцији техничких простора као и да је<br />могуће успешно повећати степен аутоматизације поновним<br />искоришћењем претходно креираних пресликавања.</p> / <p>Za potrebe povećanja stepena automatizacije razvoja adaptera za<br />integraciju u industrijskom okruženju, osmišljen je modelom vođen<br />pristup razvoju adaptera. U okviru ovog pristupa razvijen je namenski<br />jezik za specifikaciju preslikavanja između tehničkih prostora koji su<br />predmet integracije. Pristup obuhvata i algoritme za poravnanje i<br />ponovno iskorištenje prethodno kreiranih preslikavanja sa ciljem<br />automatizacije procesa specifikacije. Na osnovu kreiranih<br />preslikavanja, moguće je automatski generisati izvršivi kod adaptera.<br />U ispitivanjima pristupa, pokazano je da je moguće uspešno primeniti<br />modelom vođen pristup u integraciji tehničkih prostora kao i da je<br />moguće uspešno povećati stepen automatizacije ponovnim<br />iskorišćenjem prethodno kreiranih preslikavanja.</p>