Reusing metamodels and notation with Diagram Definition
It is increasingly common for language specifications to describe visual forms (concrete syntax) separately from underlying concepts (abstract syntax). This is typically to enable interchange of visual information between graphical modeling tools, such as positions of nodes and routings of lines. Of...
Gespeichert in:
| Veröffentlicht in: | Software and systems modeling 2018-10, Vol.17 (4), p.1079-1103 |
|---|---|
| Hauptverfasser: | , |
| Format: | Artikel |
| Sprache: | eng |
| Schlagworte: | |
| Online-Zugang: | Volltext |
| Tags: |
Tag hinzufügen
Keine Tags, Fügen Sie den ersten Tag hinzu!
|
| container_end_page | 1103 |
|---|---|
| container_issue | 4 |
| container_start_page | 1079 |
| container_title | Software and systems modeling |
| container_volume | 17 |
| creator | Bock, Conrad Elaasar, Maged |
| description | It is increasingly common for language specifications to describe visual forms (concrete syntax) separately from underlying concepts (abstract syntax). This is typically to enable interchange of visual information between graphical modeling tools, such as positions of nodes and routings of lines. Often overlooked is that separation of visual forms and abstract concepts enables languages to define multiple visual forms for the same underlying concepts and for the same visual form to be used for similar underlying concepts in different languages (many-to-many relationships between concrete and abstract syntax). Visual forms can be adapted to communities using different notations for the same concepts and can be used to integrate communities using the same notation for similar concepts. Models of concrete syntax have been available for some time, but are rarely used to capture these many-to-many relationships with abstract syntax. This paper shows how to model these relationships using concrete graphical syntax expressed in the Diagram Definition standard, examining cases drawn from the Unified Modeling Language and the Business Process Model and Notation. This gives definers of graphical languages a way to specify visual forms for multiple communities. |
| doi_str_mv | 10.1007/s10270-016-0537-x |
| format | Article |
| fullrecord | <record><control><sourceid>proquest_cross</sourceid><recordid>TN_cdi_proquest_journals_2100178375</recordid><sourceformat>XML</sourceformat><sourcesystem>PC</sourcesystem><sourcerecordid>2100178375</sourcerecordid><originalsourceid>FETCH-LOGICAL-c355t-a36c66353c4c2ea879e5979e999773c0072ba5a31b6eab8f0ab9138a43343c603</originalsourceid><addsrcrecordid>eNp1kE1LAzEQhoMoWGp_gLcFz9FkZ5NsjtKqFQqC6DnMptka6WZrssX6701Z0ZOXmWF43_l4CLnk7Jozpm4SZ6VilHFJmQBFDydkwiXXlIOqTn9rKc_JLCXfMFaVWldSToh6dvvkw6bo3IBdv3bbVGBYF6EfcPB9KD798FYsPG4idsXCtT74Y_-CnLW4TW72k6fk9f7uZb6kq6eHx_ntiloQYqAI0koJAmxlS4e10k7oHLTWSoHNx5cNCgTeSIdN3TJsNIcaK4AKrGQwJVfj3F3sP_YuDea938eQV5oy_85VDUpkFR9VNvYpRdeaXfQdxi_DmTkiMiMikxGZIyJzyJ5y9KSsDRsX_yb_b_oGh05oHw</addsrcrecordid><sourcetype>Aggregation Database</sourcetype><iscdi>true</iscdi><recordtype>article</recordtype><pqid>2100178375</pqid></control><display><type>article</type><title>Reusing metamodels and notation with Diagram Definition</title><source>SpringerNature Journals</source><creator>Bock, Conrad ; Elaasar, Maged</creator><creatorcontrib>Bock, Conrad ; Elaasar, Maged</creatorcontrib><description>It is increasingly common for language specifications to describe visual forms (concrete syntax) separately from underlying concepts (abstract syntax). This is typically to enable interchange of visual information between graphical modeling tools, such as positions of nodes and routings of lines. Often overlooked is that separation of visual forms and abstract concepts enables languages to define multiple visual forms for the same underlying concepts and for the same visual form to be used for similar underlying concepts in different languages (many-to-many relationships between concrete and abstract syntax). Visual forms can be adapted to communities using different notations for the same concepts and can be used to integrate communities using the same notation for similar concepts. Models of concrete syntax have been available for some time, but are rarely used to capture these many-to-many relationships with abstract syntax. This paper shows how to model these relationships using concrete graphical syntax expressed in the Diagram Definition standard, examining cases drawn from the Unified Modeling Language and the Business Process Model and Notation. This gives definers of graphical languages a way to specify visual forms for multiple communities.</description><identifier>ISSN: 1619-1366</identifier><identifier>EISSN: 1619-1374</identifier><identifier>DOI: 10.1007/s10270-016-0537-x</identifier><language>eng</language><publisher>Berlin/Heidelberg: Springer Berlin Heidelberg</publisher><subject>Business process engineering ; Communities ; Compilers ; Computer Science ; Information Systems Applications (incl.Internet) ; Interpreters ; IT in Business ; Languages ; Metamodels ; Modelling ; Programming Languages ; Programming Techniques ; Regular Paper ; Software Engineering ; Software Engineering/Programming and Operating Systems ; Syntax</subject><ispartof>Software and systems modeling, 2018-10, Vol.17 (4), p.1079-1103</ispartof><rights>Springer-Verlag Berlin Heidelberg (outside the USA) 2016 2016</rights><rights>Software & Systems Modeling is a copyright of Springer, (2016). All Rights Reserved.</rights><lds50>peer_reviewed</lds50><woscitedreferencessubscribed>false</woscitedreferencessubscribed><citedby>FETCH-LOGICAL-c355t-a36c66353c4c2ea879e5979e999773c0072ba5a31b6eab8f0ab9138a43343c603</citedby><cites>FETCH-LOGICAL-c355t-a36c66353c4c2ea879e5979e999773c0072ba5a31b6eab8f0ab9138a43343c603</cites></display><links><openurl>$$Topenurl_article</openurl><openurlfulltext>$$Topenurlfull_article</openurlfulltext><thumbnail>$$Tsyndetics_thumb_exl</thumbnail><linktopdf>$$Uhttps://link.springer.com/content/pdf/10.1007/s10270-016-0537-x$$EPDF$$P50$$Gspringer$$H</linktopdf><linktohtml>$$Uhttps://link.springer.com/10.1007/s10270-016-0537-x$$EHTML$$P50$$Gspringer$$H</linktohtml><link.rule.ids>314,780,784,27924,27925,41488,42557,51319</link.rule.ids></links><search><creatorcontrib>Bock, Conrad</creatorcontrib><creatorcontrib>Elaasar, Maged</creatorcontrib><title>Reusing metamodels and notation with Diagram Definition</title><title>Software and systems modeling</title><addtitle>Softw Syst Model</addtitle><description>It is increasingly common for language specifications to describe visual forms (concrete syntax) separately from underlying concepts (abstract syntax). This is typically to enable interchange of visual information between graphical modeling tools, such as positions of nodes and routings of lines. Often overlooked is that separation of visual forms and abstract concepts enables languages to define multiple visual forms for the same underlying concepts and for the same visual form to be used for similar underlying concepts in different languages (many-to-many relationships between concrete and abstract syntax). Visual forms can be adapted to communities using different notations for the same concepts and can be used to integrate communities using the same notation for similar concepts. Models of concrete syntax have been available for some time, but are rarely used to capture these many-to-many relationships with abstract syntax. This paper shows how to model these relationships using concrete graphical syntax expressed in the Diagram Definition standard, examining cases drawn from the Unified Modeling Language and the Business Process Model and Notation. This gives definers of graphical languages a way to specify visual forms for multiple communities.</description><subject>Business process engineering</subject><subject>Communities</subject><subject>Compilers</subject><subject>Computer Science</subject><subject>Information Systems Applications (incl.Internet)</subject><subject>Interpreters</subject><subject>IT in Business</subject><subject>Languages</subject><subject>Metamodels</subject><subject>Modelling</subject><subject>Programming Languages</subject><subject>Programming Techniques</subject><subject>Regular Paper</subject><subject>Software Engineering</subject><subject>Software Engineering/Programming and Operating Systems</subject><subject>Syntax</subject><issn>1619-1366</issn><issn>1619-1374</issn><fulltext>true</fulltext><rsrctype>article</rsrctype><creationdate>2018</creationdate><recordtype>article</recordtype><sourceid>ABUWG</sourceid><sourceid>AFKRA</sourceid><sourceid>AZQEC</sourceid><sourceid>BENPR</sourceid><sourceid>CCPQU</sourceid><sourceid>DWQXO</sourceid><sourceid>GNUQQ</sourceid><recordid>eNp1kE1LAzEQhoMoWGp_gLcFz9FkZ5NsjtKqFQqC6DnMptka6WZrssX6701Z0ZOXmWF43_l4CLnk7Jozpm4SZ6VilHFJmQBFDydkwiXXlIOqTn9rKc_JLCXfMFaVWldSToh6dvvkw6bo3IBdv3bbVGBYF6EfcPB9KD798FYsPG4idsXCtT74Y_-CnLW4TW72k6fk9f7uZb6kq6eHx_ntiloQYqAI0koJAmxlS4e10k7oHLTWSoHNx5cNCgTeSIdN3TJsNIcaK4AKrGQwJVfj3F3sP_YuDea938eQV5oy_85VDUpkFR9VNvYpRdeaXfQdxi_DmTkiMiMikxGZIyJzyJ5y9KSsDRsX_yb_b_oGh05oHw</recordid><startdate>20181001</startdate><enddate>20181001</enddate><creator>Bock, Conrad</creator><creator>Elaasar, Maged</creator><general>Springer Berlin Heidelberg</general><general>Springer Nature B.V</general><scope>AAYXX</scope><scope>CITATION</scope><scope>3V.</scope><scope>7SC</scope><scope>7XB</scope><scope>8AL</scope><scope>8AO</scope><scope>8FD</scope><scope>8FE</scope><scope>8FG</scope><scope>8FK</scope><scope>ABUWG</scope><scope>AFKRA</scope><scope>ARAPS</scope><scope>AZQEC</scope><scope>BENPR</scope><scope>BGLVJ</scope><scope>CCPQU</scope><scope>DWQXO</scope><scope>GNUQQ</scope><scope>HCIFZ</scope><scope>JQ2</scope><scope>K7-</scope><scope>L7M</scope><scope>L~C</scope><scope>L~D</scope><scope>M0N</scope><scope>P5Z</scope><scope>P62</scope><scope>PQEST</scope><scope>PQQKQ</scope><scope>PQUKI</scope><scope>PRINS</scope><scope>Q9U</scope></search><sort><creationdate>20181001</creationdate><title>Reusing metamodels and notation with Diagram Definition</title><author>Bock, Conrad ; Elaasar, Maged</author></sort><facets><frbrtype>5</frbrtype><frbrgroupid>cdi_FETCH-LOGICAL-c355t-a36c66353c4c2ea879e5979e999773c0072ba5a31b6eab8f0ab9138a43343c603</frbrgroupid><rsrctype>articles</rsrctype><prefilter>articles</prefilter><language>eng</language><creationdate>2018</creationdate><topic>Business process engineering</topic><topic>Communities</topic><topic>Compilers</topic><topic>Computer Science</topic><topic>Information Systems Applications (incl.Internet)</topic><topic>Interpreters</topic><topic>IT in Business</topic><topic>Languages</topic><topic>Metamodels</topic><topic>Modelling</topic><topic>Programming Languages</topic><topic>Programming Techniques</topic><topic>Regular Paper</topic><topic>Software Engineering</topic><topic>Software Engineering/Programming and Operating Systems</topic><topic>Syntax</topic><toplevel>peer_reviewed</toplevel><toplevel>online_resources</toplevel><creatorcontrib>Bock, Conrad</creatorcontrib><creatorcontrib>Elaasar, Maged</creatorcontrib><collection>CrossRef</collection><collection>ProQuest Central (Corporate)</collection><collection>Computer and Information Systems Abstracts</collection><collection>ProQuest Central (purchase pre-March 2016)</collection><collection>Computing Database (Alumni Edition)</collection><collection>ProQuest Pharma Collection</collection><collection>Technology Research Database</collection><collection>ProQuest SciTech Collection</collection><collection>ProQuest Technology Collection</collection><collection>ProQuest Central (Alumni) (purchase pre-March 2016)</collection><collection>ProQuest Central (Alumni Edition)</collection><collection>ProQuest Central UK/Ireland</collection><collection>Advanced Technologies & Aerospace Collection</collection><collection>ProQuest Central Essentials</collection><collection>ProQuest Central</collection><collection>Technology Collection</collection><collection>ProQuest One Community College</collection><collection>ProQuest Central Korea</collection><collection>ProQuest Central Student</collection><collection>SciTech Premium Collection</collection><collection>ProQuest Computer Science Collection</collection><collection>Computer Science Database</collection><collection>Advanced Technologies Database with Aerospace</collection><collection>Computer and Information Systems Abstracts Academic</collection><collection>Computer and Information Systems Abstracts Professional</collection><collection>Computing Database</collection><collection>Advanced Technologies & Aerospace Database</collection><collection>ProQuest Advanced Technologies & Aerospace Collection</collection><collection>ProQuest One Academic Eastern Edition (DO NOT USE)</collection><collection>ProQuest One Academic</collection><collection>ProQuest One Academic UKI Edition</collection><collection>ProQuest Central China</collection><collection>ProQuest Central Basic</collection><jtitle>Software and systems modeling</jtitle></facets><delivery><delcategory>Remote Search Resource</delcategory><fulltext>fulltext</fulltext></delivery><addata><au>Bock, Conrad</au><au>Elaasar, Maged</au><format>journal</format><genre>article</genre><ristype>JOUR</ristype><atitle>Reusing metamodels and notation with Diagram Definition</atitle><jtitle>Software and systems modeling</jtitle><stitle>Softw Syst Model</stitle><date>2018-10-01</date><risdate>2018</risdate><volume>17</volume><issue>4</issue><spage>1079</spage><epage>1103</epage><pages>1079-1103</pages><issn>1619-1366</issn><eissn>1619-1374</eissn><abstract>It is increasingly common for language specifications to describe visual forms (concrete syntax) separately from underlying concepts (abstract syntax). This is typically to enable interchange of visual information between graphical modeling tools, such as positions of nodes and routings of lines. Often overlooked is that separation of visual forms and abstract concepts enables languages to define multiple visual forms for the same underlying concepts and for the same visual form to be used for similar underlying concepts in different languages (many-to-many relationships between concrete and abstract syntax). Visual forms can be adapted to communities using different notations for the same concepts and can be used to integrate communities using the same notation for similar concepts. Models of concrete syntax have been available for some time, but are rarely used to capture these many-to-many relationships with abstract syntax. This paper shows how to model these relationships using concrete graphical syntax expressed in the Diagram Definition standard, examining cases drawn from the Unified Modeling Language and the Business Process Model and Notation. This gives definers of graphical languages a way to specify visual forms for multiple communities.</abstract><cop>Berlin/Heidelberg</cop><pub>Springer Berlin Heidelberg</pub><doi>10.1007/s10270-016-0537-x</doi><tpages>25</tpages></addata></record> |
| fulltext | fulltext |
| identifier | ISSN: 1619-1366 |
| ispartof | Software and systems modeling, 2018-10, Vol.17 (4), p.1079-1103 |
| issn | 1619-1366 1619-1374 |
| language | eng |
| recordid | cdi_proquest_journals_2100178375 |
| source | SpringerNature Journals |
| subjects | Business process engineering Communities Compilers Computer Science Information Systems Applications (incl.Internet) Interpreters IT in Business Languages Metamodels Modelling Programming Languages Programming Techniques Regular Paper Software Engineering Software Engineering/Programming and Operating Systems Syntax |
| title | Reusing metamodels and notation with Diagram Definition |
| url | https://sfx.bib-bvb.de/sfx_tum?ctx_ver=Z39.88-2004&ctx_enc=info:ofi/enc:UTF-8&ctx_tim=2025-01-01T19%3A09%3A58IST&url_ver=Z39.88-2004&url_ctx_fmt=infofi/fmt:kev:mtx:ctx&rfr_id=info:sid/primo.exlibrisgroup.com:primo3-Article-proquest_cross&rft_val_fmt=info:ofi/fmt:kev:mtx:journal&rft.genre=article&rft.atitle=Reusing%20metamodels%20and%20notation%20with%20Diagram%20Definition&rft.jtitle=Software%20and%20systems%20modeling&rft.au=Bock,%20Conrad&rft.date=2018-10-01&rft.volume=17&rft.issue=4&rft.spage=1079&rft.epage=1103&rft.pages=1079-1103&rft.issn=1619-1366&rft.eissn=1619-1374&rft_id=info:doi/10.1007/s10270-016-0537-x&rft_dat=%3Cproquest_cross%3E2100178375%3C/proquest_cross%3E%3Curl%3E%3C/url%3E&disable_directlink=true&sfx.directlink=off&sfx.report_link=0&rft_id=info:oai/&rft_pqid=2100178375&rft_id=info:pmid/&rfr_iscdi=true |