<rdf:RDF xmlns:community="http://www.bibsonomy.org/ontologies/2008/05/community#" xmlns:foaf="http://xmlns.com/foaf/0.1/" xmlns:owl="http://www.w3.org/2002/07/owl#" xmlns:admin="http://webns.net/mvcb/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:cc="http://web.resource.org/cc/" xmlns:xsd="http://www.w3.org/2001/XMLSchema#" xmlns:swrc="http://swrc.ontoware.org/ontology#" xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#" xmlns="http://purl.org/rss/1.0/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xml:base="http://www.bibsonomy.org/tag/uml"><owl:Ontology rdf:about=""><rdfs:comment>BibSonomy publications for /tag/uml</rdfs:comment><owl:imports rdf:resource="http://swrc.ontoware.org/ontology/portal"/></owl:Ontology><rdf:Description rdf:about="http://www.bibsonomy.org/bibtex/2da2b659a6e6608a2578c2ac337fda9a3/maxirichter"><owl:sameAs rdf:resource="http://www.bibsonomy.org/uri/bibtex/2da2b659a6e6608a2578c2ac337fda9a3/maxirichter"/><rdf:type rdf:resource="http://swrc.ontoware.org/ontology#Misc"/><owl:sameAs rdf:resource="http://www.freiesmagazin.de/mobil/freiesMagazin-2012-02-bilder.html"/><swrc:date>Mon Feb 06 11:24:35 CET 2012</swrc:date><swrc:title>freiesMagazin Februar 2012</swrc:title><swrc:year>2012</swrc:year><swrc:keywords>freiesmagazin python uml </swrc:keywords><swrc:author><rdf:Seq><rdf:_1><swrc:Person swrc:name=" freiesMagazin"/></rdf:_1></rdf:Seq></swrc:author></rdf:Description><rdf:Description rdf:about="http://www.bibsonomy.org/bibtex/2be8dada251ca411274f5dabf752c7236/maxirichter"><owl:sameAs rdf:resource="http://www.bibsonomy.org/uri/bibtex/2be8dada251ca411274f5dabf752c7236/maxirichter"/><rdf:type rdf:resource="http://swrc.ontoware.org/ontology#Misc"/><owl:sameAs rdf:resource="http://arxiv.org/ftp/arxiv/papers/1201/1201.2031.pdf"/><swrc:date>Wed Jan 11 14:21:43 CET 2012</swrc:date><swrc:note>cite arxiv:1201.2031Comment: 16 pages,14 figures</swrc:note><swrc:title>General Methodology for developing UML models from UI</swrc:title><swrc:year>2012</swrc:year><swrc:keywords>modelling ui_modelling uml </swrc:keywords><swrc:abstract>  In recent past every discipline and every industry have their own methods of
developing products. It may be software development, mechanics, construction,
psychology and so on. These demarcations work fine as long as the requirements
are within one discipline. However, if the project extends over several
disciplines, interfaces have to be created and coordinated between the methods
of these disciplines. Performance is an important quality aspect of Web
Services because of their distributed nature. Predicting the performance of web
services during early stages of software development is significant. In
Industry, Prototype of these applications is developed during analysis phase of
Software Development Life Cycle (SDLC). However, Performance models are
generated from UML models. Methodologies for predicting the performance from
UML models is available. Hence, In this paper, a methodology for developing Use
Case model and Activity model from User Interface is presented. The methodology
is illustrated with a case study on Amazon.com.
</swrc:abstract><swrc:author><rdf:Seq><rdf:_1><swrc:Person swrc:name="Ch Ram Mohan Reddy"/></rdf:_1><rdf:_2><swrc:Person swrc:name="D. Evangelin Geetha"/></rdf:_2><rdf:_3><swrc:Person swrc:name="K. G. Srinivasa"/></rdf:_3><rdf:_4><swrc:Person swrc:name="T. V. Suresh Kumar"/></rdf:_4><rdf:_5><swrc:Person swrc:name="K. Rajani Kanth"/></rdf:_5></rdf:Seq></swrc:author></rdf:Description><rdf:Description rdf:about="http://www.bibsonomy.org/bibtex/23863acf8ff3140326d136473c0269470/porta"><owl:sameAs rdf:resource="http://www.bibsonomy.org/uri/bibtex/23863acf8ff3140326d136473c0269470/porta"/><rdf:type rdf:resource="http://swrc.ontoware.org/ontology#InProceedings"/><owl:sameAs rdf:resource="http://portal.acm.org/citation.cfm?id=1782434.1782447"/><swrc:date>Tue Dec 27 21:14:40 CET 2011</swrc:date><swrc:address>Berlin/Heidelberg</swrc:address><swrc:booktitle>Proceedings of the 6th international conference on Task models and diagrams for user interface design</swrc:booktitle><swrc:pages>98--111</swrc:pages><swrc:publisher><swrc:Organization swrc:name="Springer-Verlag"/></swrc:publisher><swrc:series>TAMODIA&#039;07</swrc:series><swrc:title>From task to dialog model in the {UML}</swrc:title><swrc:year>2007</swrc:year><swrc:keywords>task dialog model UML </swrc:keywords><swrc:abstract>Many model-based approaches for user interface design start from a task model, for which the {ConcurTaskTrees} notation is frequently used. Despite this popularity and the importance that has been given to a close relation with {UML}, no relation has been established with {UML} state machines, which have been shown to be useful for the description of the behavior of user interfaces. This paper proposes a semantic mapping of tasks and all temporal relations of the {ConcurTaskTrees} to {UML} state machines which forms the basis for a compact dialog modeling notation using {UML} state machines. The proposed approach uses a {UML} profile to reduce the visual complexity of the state machine.</swrc:abstract><swrc:hasExtraField><swrc:Field swrc:value="2011-12-27 09:14:40" swrc:key="timestamp"/></swrc:hasExtraField><swrc:hasExtraField><swrc:Field swrc:value="porta" swrc:key="username"/></swrc:hasExtraField><swrc:hasExtraField><swrc:Field swrc:value="3863acf8ff3140326d136473c0269470" swrc:key="intrahash"/></swrc:hasExtraField><swrc:hasExtraField><swrc:Field swrc:value="Toulouse, France" swrc:key="location"/></swrc:hasExtraField><swrc:hasExtraField><swrc:Field swrc:value=":VandenBergh2007From.pdf:PDF" swrc:key="file"/></swrc:hasExtraField><swrc:hasExtraField><swrc:Field swrc:value="d1cf40009e9cc14d24d30a37e369034b" swrc:key="interhash"/></swrc:hasExtraField><swrc:hasExtraField><swrc:Field swrc:value="public" swrc:key="groups"/></swrc:hasExtraField><swrc:author><rdf:Seq><rdf:_1><swrc:Person swrc:name="Jan Van den Bergh"/></rdf:_1><rdf:_2><swrc:Person swrc:name="Karin Coninx"/></rdf:_2></rdf:Seq></swrc:author></rdf:Description><rdf:Description rdf:about="http://www.bibsonomy.org/bibtex/232a2ab2806fbd0d9e9b5f3266891fbe6/porta"><owl:sameAs rdf:resource="http://www.bibsonomy.org/uri/bibtex/232a2ab2806fbd0d9e9b5f3266891fbe6/porta"/><rdf:type rdf:resource="http://swrc.ontoware.org/ontology#Book"/><owl:sameAs rdf:resource="/brokenurl#www.springer.com/978-3-8274-1555-4"/><swrc:date>Tue Dec 27 21:13:48 CET 2011</swrc:date><swrc:address>Heidelberg</swrc:address><swrc:publisher><swrc:Organization swrc:name="Spektrum Akademischer Verlag"/></swrc:publisher><swrc:title>Generative {Software-Entwicklung} mit der Model Driven Architecture</swrc:title><swrc:year>2006</swrc:year><swrc:keywords>book code design development generation software tool uml </swrc:keywords><swrc:abstract>Um den Anspr{\&#034;{u}}chen auf dem sich rasch ver{\&#034;{a}}ndernden Markt gerecht zu werden, muss die Softwareindustrie Produkte entwickeln, die trotz der zunehmenden Komplexit{\&#034;{a}}t flexibel, sicher und wieder verwendbar sind und verschiedensten technischen Anforderungen gen{\&#034;{u}}gen. So entsteht Software schon lange nicht mehr durch reines Programmieren, sondern in zunehmendem Ma{\\ss}e durch Generieren. Mit der Model Driven Architecture (MDA) stellt die Object Management Group (OMG) einen Standard vor, der die vielf{\&#034;{a}}ltigen bew{\&#034;{a}}hrten Ans{\&#034;{a}}tze zusammenfasst und von dem man sich einen deutlichen Innovationsschub f{\&#034;{u}}r die generative Softwareentwicklung erhofft. Das Buch wendet sich mit seiner grunds{\&#034;{a}}tzlichen und praxisorientierten Einf{\&#034;{u}}hrung in die MDA-basierte Softwareentwicklung an Studierende der Informatik und an Programmierer und Softwareentwickler aus der Industrie, die die MDA verstehen und sie direkt in die Praxis umsetzen m{\&#034;{o}}chten. Neben einer Beschreibung der Vorgehensweise und der Ziele enth{\&#034;{a}}lt es grundlegende Standards, wie z.B. die UML 2.0, bevor an einem konkreten Fallbeispiel Schritt f{\&#034;{u}}r Schritt die Vorgehensweise vom Modell zum generierten Code mit frei verf{\&#034;{u}}gbaren Werkzeugen erkl{\&#034;{a}}rt und eine {\&#034;{U}}bersicht {\&#034;{u}}ber die aktuelle Produktlandschaft gegeben wird.</swrc:abstract><swrc:hasExtraField><swrc:Field swrc:value="2011-12-27 09:13:48" swrc:key="timestamp"/></swrc:hasExtraField><swrc:hasExtraField><swrc:Field swrc:value="porta" swrc:key="username"/></swrc:hasExtraField><swrc:hasExtraField><swrc:Field swrc:value="32a2ab2806fbd0d9e9b5f3266891fbe6" swrc:key="intrahash"/></swrc:hasExtraField><swrc:hasExtraField><swrc:Field swrc:value="b9ebf2194c2a1bd935701a9a7000bbe3" swrc:key="interhash"/></swrc:hasExtraField><swrc:hasExtraField><swrc:Field swrc:value="public" swrc:key="groups"/></swrc:hasExtraField><swrc:author><rdf:Seq><rdf:_1><swrc:Person swrc:name="Klaus Zeppenfeld"/></rdf:_1><rdf:_2><swrc:Person swrc:name="Regine Wolters"/></rdf:_2></rdf:Seq></swrc:author></rdf:Description><rdf:Description rdf:about="http://www.bibsonomy.org/bibtex/2a84272e7b008794efc605a5a0895cba1/pbrada"><owl:sameAs rdf:resource="http://www.bibsonomy.org/uri/bibtex/2a84272e7b008794efc605a5a0895cba1/pbrada"/><rdf:type rdf:resource="http://swrc.ontoware.org/ontology#Article"/><swrc:date>Fri Dec 16 09:35:00 CET 2011</swrc:date><swrc:journal>{IEEE} Software</swrc:journal><swrc:month>April</swrc:month><swrc:number>2</swrc:number><swrc:pages>40-- 46</swrc:pages><swrc:title>In practice: {UML} software architecture and design description</swrc:title><swrc:volume>23</swrc:volume><swrc:year>2006</swrc:year><swrc:keywords>survey UML modeling </swrc:keywords><swrc:abstract>The Unified Modeling Language has attracted many organizations and practitioners. {UML} is now the de facto modeling language for software development. Several features account for its popularity: it&#039;s a standardized notation, rich in expressivity; {UML} 2.0 provides 13 diagram types that enable modeling several different views and abstraction levels. Furthermore, {UML} supports domain-specific extensions using stereotypes and tagged values. Finally, several case tools integrate {UML} modeling with other tasks such as generating code and reverse-engineering models from code. Our study focused on {UML} use and model quality in actual projects rather than on its adequacy as a notation or language.</swrc:abstract><swrc:hasExtraField><swrc:Field swrc:value="2011.10.24" swrc:key="timestamp"/></swrc:hasExtraField><swrc:hasExtraField><swrc:Field swrc:value="pbrada" swrc:key="username"/></swrc:hasExtraField><swrc:hasExtraField><swrc:Field swrc:value="0740-7459" swrc:key="issn"/></swrc:hasExtraField><swrc:hasExtraField><swrc:Field swrc:value="In practice" swrc:key="shorttitle"/></swrc:hasExtraField><swrc:hasExtraField><swrc:Field swrc:value="10.1109/MS.2006.50" swrc:key="doi"/></swrc:hasExtraField><swrc:hasExtraField><swrc:Field swrc:value="public" swrc:key="groups"/></swrc:hasExtraField><swrc:hasExtraField><swrc:Field swrc:value="study is &#034;focused on UML use and model quality in actual projects rather than on its adequacy as a notation or language&#034;  most often used models in terms of 4+1 views - use case 80% - logical 80% - component 50% - scenario 50% - deployment 18%  strict adherence to uml standard - very loose 20% - loose 45% - strict 35%  when to stop modeling - complete model 52% (but completeness cannot be measured; more often used on large projects) - review pass 34% - deadline 33% (!) - effort spent 18%  problems iwth uml descriptions, inherent in multi-diagram notations: - scattered info -- design info scattered over multiple views - complete and thorough models knowingly for only a subset of views, focusing on most important needed - inconsistent models -- due to multi-team model development and limited consistency check support in tools other problems (common errors: no class method for sequence diagram message, objects with anonymous class) - diagram quality (extent, layout, style, conventions) =&gt; &#034;how easy the model is to understand and how it gets interpreted&#034; - informal use of notation =&gt; ambiguity  opportunities for improvement - defect checking and feedback - architectural metrics on uml models" swrc:key="review"/></swrc:hasExtraField><swrc:author><rdf:Seq><rdf:_1><swrc:Person swrc:name="C. {F.J} Lange"/></rdf:_1><rdf:_2><swrc:Person swrc:name="M. {R.V} Chaudron"/></rdf:_2><rdf:_3><swrc:Person swrc:name="J. Muskens"/></rdf:_3></rdf:Seq></swrc:author></rdf:Description><rdf:Description rdf:about="http://www.bibsonomy.org/bibtex/233624b1029864f9e98fcb9b360aa9f37/pbrada"><owl:sameAs rdf:resource="http://www.bibsonomy.org/uri/bibtex/233624b1029864f9e98fcb9b360aa9f37/pbrada"/><rdf:type rdf:resource="http://swrc.ontoware.org/ontology#Article"/><owl:sameAs rdf:resource="http://doi.acm.org/10.1145/504087.504088"/><swrc:date>Fri Dec 16 09:34:23 CET 2011</swrc:date><swrc:journal>{ACM} Trans. Softw. Eng. Methodol.</swrc:journal><swrc:month>January</swrc:month><swrc:number>1</swrc:number><swrc:pages>2–57</swrc:pages><swrc:title>Modeling software architectures in the Unified Modeling Language</swrc:title><swrc:volume>11</swrc:volume><swrc:year>2002</swrc:year><swrc:keywords>modeling UML OCL architecture </swrc:keywords><swrc:hasExtraField><swrc:Field swrc:value="2011.10.24" swrc:key="timestamp"/></swrc:hasExtraField><swrc:hasExtraField><swrc:Field swrc:value="pbrada" swrc:key="username"/></swrc:hasExtraField><swrc:hasExtraField><swrc:Field swrc:value="{1049-331X}" swrc:key="issn"/></swrc:hasExtraField><swrc:hasExtraField><swrc:Field swrc:value="10.1145/504087.504088" swrc:key="doi"/></swrc:hasExtraField><swrc:hasExtraField><swrc:Field swrc:value="public" swrc:key="groups"/></swrc:hasExtraField><swrc:hasExtraField><swrc:Field swrc:value="reqts on what UML should support wrt architectures (p5): - structural concerns - stylistic issues (patterns) - behavioural aspects (&#034;While this may appear to be an unfair requirement ... our study has shown UML to be surprisingly flexible [in representing semantics]&#034;) - interaction paradigms (connectors) - constraints (arising from structure, arch styles, etc)  strategies how to achieve: - use plain uml - constrain uml = more precise (sw arch related) semantics of existing uml model elements - augment uml = add modeling capabilities at meta-model level; ruled out because it leads to non-standardizable extensions  evaluation - plain uml: workable but &#034;architectural entities with very different responsibilities, connectors and components must be modeled in UML using the same mechanism&#034;, arch style rules are only implicitly embedded or not present at all in the model =&gt; additional documentatino is needed - constrained uml (using OCL and stereotypes): equivalent to uml profiles but &#034;in constraining UML to represent Rapide, we were confronted by a number of semantic ambiguities and limitations of UML&#034; + Fig 13 p30 shows that readability suffers  conclusions - uml classes cannot specify outgoing communication (required features) - behavioural specs can be modeled in uml to a large degree - &#034;software architect may find that the support for [arch relevant] perspectives provided by UML only partially satisfies his/her needs&#034; because arch needs precise constrained rules whereas uml is less formal and rigorous - uml has added value of good domain modeling support (which arch modeling and components lack) - &#034;the abstractions UML provides may not match an architect’s mental model of the system&#034; -- &#034;we believe this to be a a key issue and one that argues against considering a notation like UML to be a “mainstream” ADL&#034; - no direct modeling of arch rules in uml, needs profiles  - uml can usefully augment adl code generation (which omits impl details)  my notes: - no talk about component diagram - this was the time of UML1 - but most points still valid (uml component model does not have connectors, does not distinguish contract levels, not expected ot be linked with semantics like statecharts or sequence diagrams)" swrc:key="review"/></swrc:hasExtraField><swrc:author><rdf:Seq><rdf:_1><swrc:Person swrc:name="Nenad Medvidovic"/></rdf:_1><rdf:_2><swrc:Person swrc:name="David S. Rosenblum"/></rdf:_2><rdf:_3><swrc:Person swrc:name="David F. Redmiles"/></rdf:_3><rdf:_4><swrc:Person swrc:name="Jason E. Robbins"/></rdf:_4></rdf:Seq></swrc:author></rdf:Description><rdf:Description rdf:about="http://www.bibsonomy.org/bibtex/2394f5be8ea3ecc6d6aa26486676de96d/pbrada"><owl:sameAs rdf:resource="http://www.bibsonomy.org/uri/bibtex/2394f5be8ea3ecc6d6aa26486676de96d/pbrada"/><rdf:type rdf:resource="http://swrc.ontoware.org/ontology#InProceedings"/><swrc:date>Fri Dec 16 09:34:21 CET 2011</swrc:date><swrc:booktitle>Proceedings of the 9th Working Conference on Reverse Engineering ({WCRE} 2002)</swrc:booktitle><swrc:month>November</swrc:month><swrc:publisher><swrc:Organization swrc:name="IEEE Computer Society"/></swrc:publisher><swrc:title>A Study on the Current State of the Art in Tool-Supported  UML-Based Static Reverse Engineering</swrc:title><swrc:year>2002</swrc:year><swrc:keywords>uml reverse-engineering tool comparison </swrc:keywords><swrc:hasExtraField><swrc:Field swrc:value="2011.10.24" swrc:key="timestamp"/></swrc:hasExtraField><swrc:hasExtraField><swrc:Field swrc:value="pbrada" swrc:key="username"/></swrc:hasExtraField><swrc:hasExtraField><swrc:Field swrc:value="0-7695-1799-4" swrc:key="isbn"/></swrc:hasExtraField><swrc:hasExtraField><swrc:Field swrc:value="public" swrc:key="groups"/></swrc:hasExtraField><swrc:hasExtraField><swrc:Field swrc:value="analyze reveng capabilities of two leading commercial tools and two research prototypes, authors note that obtaining more abstract representations and recognition of advanced (semantically rich) model features -- which are important for the analys -- was rare at the time of writing." swrc:key="review"/></swrc:hasExtraField><swrc:author><rdf:Seq><rdf:_1><swrc:Person swrc:name="Ralf Kollman"/></rdf:_1><rdf:_2><swrc:Person swrc:name="Petri Selonen"/></rdf:_2><rdf:_3><swrc:Person swrc:name="Eleni Stroulia"/></rdf:_3><rdf:_4><swrc:Person swrc:name="Tarja Syst{\&#034;a}"/></rdf:_4><rdf:_5><swrc:Person swrc:name="Albert Z{\&#034;u}ndorf"/></rdf:_5></rdf:Seq></swrc:author><swrc:editor><rdf:Seq><rdf:_1><swrc:Person swrc:name="Arie van Deursen"/></rdf:_1><rdf:_2><swrc:Person swrc:name="Elizabeth Burd"/></rdf:_2></rdf:Seq></swrc:editor></rdf:Description><rdf:Description rdf:about="http://www.bibsonomy.org/bibtex/2079554e4d7eb94edd81c9e50aeb2f068/pbrada"><owl:sameAs rdf:resource="http://www.bibsonomy.org/uri/bibtex/2079554e4d7eb94edd81c9e50aeb2f068/pbrada"/><rdf:type rdf:resource="http://swrc.ontoware.org/ontology#InProceedings"/><swrc:date>Fri Dec 16 09:34:05 CET 2011</swrc:date><swrc:address>Toronto, Canada</swrc:address><swrc:booktitle>1st ICSE Workshop on Describing Software Architecture with UML</swrc:booktitle><swrc:pages>79-82</swrc:pages><swrc:title> {UML Component Diagrams and Software Architecture -- Experiences from the Wren Project}</swrc:title><swrc:year>2001</swrc:year><swrc:keywords>components notation uml </swrc:keywords><swrc:hasExtraField><swrc:Field swrc:value="pbrada" swrc:key="username"/></swrc:hasExtraField><swrc:hasExtraField><swrc:Field swrc:value="public" swrc:key="groups"/></swrc:hasExtraField><swrc:author><rdf:Seq><rdf:_1><swrc:Person swrc:name="Chris L\&#034;{u}er"/></rdf:_1><rdf:_2><swrc:Person swrc:name="David S. Rosenblum"/></rdf:_2></rdf:Seq></swrc:author></rdf:Description><rdf:Description rdf:about="http://www.bibsonomy.org/bibtex/260df453892d020f004ef5b86674ac933/drmatusek"><owl:sameAs rdf:resource="http://www.bibsonomy.org/uri/bibtex/260df453892d020f004ef5b86674ac933/drmatusek"/><rdf:type rdf:resource="http://swrc.ontoware.org/ontology#Article"/><owl:sameAs rdf:resource="http://www.sciencedirect.com/science/article/pii/S0010465511002700"/><swrc:date>Sun Dec 04 15:36:18 CET 2011</swrc:date><swrc:journal>Computer Physics Communications</swrc:journal><swrc:month>February</swrc:month><swrc:number>2</swrc:number><swrc:pages>213 - 230</swrc:pages><swrc:title>Visual modeling for scientific software architecture design. A practical approach</swrc:title><swrc:volume>183</swrc:volume><swrc:year>2012</swrc:year><swrc:keywords>UML approach driven model software </swrc:keywords><swrc:abstract>This paper presents the problem of Molecular Beam Epitaxy and Reflection High-Energy Electron Diffraction with the help of a unified, modern MDA approach. Model-Driven Architecture MDA constitutes a modern and unusually efficient method of improving the process of generating software. It was created at the beginning of the twenty-first century by the Object Management Group as an element of Model-Driven Development, a highly promoted trend in software engineering. In MDA a viewpoint on a system is a technique for abstraction using a selected set of architectural concepts and structuring rules, in order to focus on particular concerns within a system. In MDA, system design begins with defining the problem domain. Next, at a highly abstract level independent of the system and programming platform Platform-Independent Model PIM is constructed as well as a general system specification. This specification is created with the help of Unified Modeling Language. The real implementation of the system is performed through the transformation of PIM to Platform-Specific Model PSM. The essence of Model-Driven Architecture is the replacement of the twentieth century approach to programming, calling that &#034;everything is an object&#034;, to the modern &#034;everything is a model.&#034;</swrc:abstract><swrc:hasExtraField><swrc:Field swrc:value="0010-4655" swrc:key="issn"/></swrc:hasExtraField><swrc:hasExtraField><swrc:Field swrc:value="10.1016/j.cpc.2011.07.021" swrc:key="doi"/></swrc:hasExtraField><swrc:author><rdf:Seq><rdf:_1><swrc:Person swrc:name=" Andrzej"/></rdf:_1><rdf:_2><swrc:Person swrc:name=" Daniluk"/></rdf:_2></rdf:Seq></swrc:author></rdf:Description><rdf:Description rdf:about="http://www.bibsonomy.org/bibtex/2ca3fc4524815c5c489d3056f3140df41/livany"><owl:sameAs rdf:resource="http://www.bibsonomy.org/uri/bibtex/2ca3fc4524815c5c489d3056f3140df41/livany"/><rdf:type rdf:resource="http://swrc.ontoware.org/ontology#Book"/><swrc:date>Mon Nov 28 21:34:58 CET 2011</swrc:date><swrc:address>M{\&#034;u}nchen [u.a.]</swrc:address><swrc:publisher><swrc:Organization swrc:name="Addison-Wesley"/></swrc:publisher><swrc:title>UML konzentriert</swrc:title><swrc:year>2004</swrc:year><swrc:keywords>UML </swrc:keywords><swrc:hasExtraField><swrc:Field swrc:value="3-8273-2126-3" swrc:key="isbn"/></swrc:hasExtraField><swrc:author><rdf:Seq><rdf:_1><swrc:Person swrc:name="Martin Fowler"/></rdf:_1></rdf:Seq></swrc:author></rdf:Description><rdf:Description rdf:about="http://www.bibsonomy.org/bibtex/25e29e519088a5eba214165a26b5bf765/livany"><owl:sameAs rdf:resource="http://www.bibsonomy.org/uri/bibtex/25e29e519088a5eba214165a26b5bf765/livany"/><rdf:type rdf:resource="http://swrc.ontoware.org/ontology#Book"/><swrc:date>Mon Nov 28 20:47:50 CET 2011</swrc:date><swrc:address>Heidelberg</swrc:address><swrc:publisher><swrc:Organization swrc:name="dpunkt.verlag"/></swrc:publisher><swrc:title>UML@Work, Objektorientierte Modellierung mit UML 2</swrc:title><swrc:year>2005</swrc:year><swrc:keywords>uml </swrc:keywords><swrc:hasExtraField><swrc:Field swrc:value="3-89864-261-5" swrc:key="isbn"/></swrc:hasExtraField><swrc:hasExtraField><swrc:Field swrc:value="400" swrc:key="numpages"/></swrc:hasExtraField><swrc:author><rdf:Seq><rdf:_1><swrc:Person swrc:name="Martin Hitz"/></rdf:_1><rdf:_2><swrc:Person swrc:name="Gerti Kappel"/></rdf:_2><rdf:_3><swrc:Person swrc:name="Elisabeth Kapsammer"/></rdf:_3><rdf:_4><swrc:Person swrc:name="Werner Retschitzegger"/></rdf:_4></rdf:Seq></swrc:author></rdf:Description><rdf:Description rdf:about="http://www.bibsonomy.org/bibtex/210d74cd50e1ceb33342b1c533d92ca1e/voj"><owl:sameAs rdf:resource="http://www.bibsonomy.org/uri/bibtex/210d74cd50e1ceb33342b1c533d92ca1e/voj"/><rdf:type rdf:resource="http://swrc.ontoware.org/ontology#Article"/><swrc:date>Sun Nov 20 23:04:47 CET 2011</swrc:date><swrc:journal>IEEE Software</swrc:journal><swrc:month>7</swrc:month><swrc:number>4</swrc:number><swrc:pages>19-21</swrc:pages><swrc:title>Are Domain-Specific Models Easier to Maintain Than UML Models?</swrc:title><swrc:volume>26</swrc:volume><swrc:year>2009</swrc:year><swrc:keywords>dsl modeling uml </swrc:keywords><swrc:hasExtraField><swrc:Field swrc:value="10.1109/MS.2009.87" swrc:key="doi"/></swrc:hasExtraField><swrc:author><rdf:Seq><rdf:_1><swrc:Person swrc:name="Lan Cao"/></rdf:_1><rdf:_2><swrc:Person swrc:name="Balasubramaniam Ramesh"/></rdf:_2><rdf:_3><swrc:Person swrc:name="Matti Rossi"/></rdf:_3></rdf:Seq></swrc:author></rdf:Description><rdf:Description rdf:about="http://www.bibsonomy.org/bibtex/2ee31394bff5ac3576d40fa007f636f22/voj"><owl:sameAs rdf:resource="http://www.bibsonomy.org/uri/bibtex/2ee31394bff5ac3576d40fa007f636f22/voj"/><rdf:type rdf:resource="http://swrc.ontoware.org/ontology#InProceedings"/><swrc:date>Sun Nov 20 18:02:51 CET 2011</swrc:date><swrc:booktitle>Proceedings of the Workshop on Philosophical Foundations of Information	Systems Engineering</swrc:booktitle><swrc:pages>547--557</swrc:pages><swrc:title>A Semiotic Approach to UML Models</swrc:title><swrc:volume>13</swrc:volume><swrc:year>2005</swrc:year><swrc:keywords>modeling semiotic uml </swrc:keywords><swrc:author><rdf:Seq><rdf:_1><swrc:Person swrc:name="G. Génova"/></rdf:_1><rdf:_2><swrc:Person swrc:name="M.C. Valiente"/></rdf:_2><rdf:_3><swrc:Person swrc:name="J. Nubiola"/></rdf:_3></rdf:Seq></swrc:author></rdf:Description><rdf:Description rdf:about="http://www.bibsonomy.org/bibtex/2b969b37620060e92bf124f2040ee2841/voj"><owl:sameAs rdf:resource="http://www.bibsonomy.org/uri/bibtex/2b969b37620060e92bf124f2040ee2841/voj"/><rdf:type rdf:resource="http://swrc.ontoware.org/ontology#InProceedings"/><swrc:date>Sun Nov 20 17:30:14 CET 2011</swrc:date><swrc:booktitle>Fifth Workshop on System Analysis and Modelling</swrc:booktitle><swrc:title>On UML&#039;s Composite Structure Diagram</swrc:title><swrc:year>2006</swrc:year><swrc:keywords>uml </swrc:keywords><swrc:abstract>The composite structure diagram and related notions have been introduced into UML2.0 to supplement already existing artifacts such as classes. However the usage of these constructs by engineers and/or modellers is not always in the spirit of inventors of these constructs. A number of additional interpretations develop which are not always consistent with the intended usage of the structure nor with the language itself. Understanding these additional usages assists in understanding areas of ambiguity, extension, inconsistency and the future development of the language.</swrc:abstract><swrc:author><rdf:Seq><rdf:_1><swrc:Person swrc:name="Ian Oliver"/></rdf:_1><rdf:_2><swrc:Person swrc:name="Vesa Luukala"/></rdf:_2></rdf:Seq></swrc:author></rdf:Description><rdf:Description rdf:about="http://www.bibsonomy.org/bibtex/25e29e519088a5eba214165a26b5bf765/khilgenberg"><owl:sameAs rdf:resource="http://www.bibsonomy.org/uri/bibtex/25e29e519088a5eba214165a26b5bf765/khilgenberg"/><rdf:type rdf:resource="http://swrc.ontoware.org/ontology#Book"/><swrc:date>Sat Oct 29 18:21:58 CEST 2011</swrc:date><swrc:address>Heidelberg</swrc:address><swrc:publisher><swrc:Organization swrc:name="dpunkt.verlag"/></swrc:publisher><swrc:title>UML@Work, Objektorientierte Modellierung mit UML 2</swrc:title><swrc:year>2005</swrc:year><swrc:keywords>UML design imported kde projekt sdcframework software ss11 </swrc:keywords><swrc:hasExtraField><swrc:Field swrc:value="3-89864-261-5" swrc:key="isbn"/></swrc:hasExtraField><swrc:hasExtraField><swrc:Field swrc:value="400" swrc:key="numpages"/></swrc:hasExtraField><swrc:author><rdf:Seq><rdf:_1><swrc:Person swrc:name="Martin Hitz"/></rdf:_1><rdf:_2><swrc:Person swrc:name="Gerti Kappel"/></rdf:_2><rdf:_3><swrc:Person swrc:name="Elisabeth Kapsammer"/></rdf:_3><rdf:_4><swrc:Person swrc:name="Werner Retschitzegger"/></rdf:_4></rdf:Seq></swrc:author></rdf:Description><rdf:Description rdf:about="http://www.bibsonomy.org/bibtex/2f1c437a7b76ba20293a4ab39d3b826ff/voj"><owl:sameAs rdf:resource="http://www.bibsonomy.org/uri/bibtex/2f1c437a7b76ba20293a4ab39d3b826ff/voj"/><rdf:type rdf:resource="http://swrc.ontoware.org/ontology#Article"/><swrc:date>Mon Oct 24 13:07:03 CEST 2011</swrc:date><swrc:journal>ACM Queue</swrc:journal><swrc:month>3</swrc:month><swrc:number>1</swrc:number><swrc:pages>72-80</swrc:pages><swrc:title>Death by UML Fever</swrc:title><swrc:volume>2</swrc:volume><swrc:year>2004</swrc:year><swrc:keywords>UML </swrc:keywords><swrc:hasExtraField><swrc:Field swrc:value="10.1145/984458.984495" swrc:key="doi"/></swrc:hasExtraField><swrc:author><rdf:Seq><rdf:_1><swrc:Person swrc:name="Alex E Bell"/></rdf:_1></rdf:Seq></swrc:author></rdf:Description><rdf:Description rdf:about="http://www.bibsonomy.org/bibtex/2473c8d7cd391798c0961eeeabd7afc02/voj"><owl:sameAs rdf:resource="http://www.bibsonomy.org/uri/bibtex/2473c8d7cd391798c0961eeeabd7afc02/voj"/><rdf:type rdf:resource="http://swrc.ontoware.org/ontology#TechnicalReport"/><owl:sameAs rdf:resource="http://www.omg.org/spec/UML/2.4.1/"/><swrc:date>Mon Oct 24 12:29:14 CEST 2011</swrc:date><swrc:month>8</swrc:month><swrc:title>Documents Associated With UML Version 2.4.1</swrc:title><swrc:year>2011</swrc:year><swrc:keywords>UML specification </swrc:keywords><swrc:editor><rdf:Seq><rdf:_1><swrc:Person swrc:name=" OMG"/></rdf:_1></rdf:Seq></swrc:editor></rdf:Description><rdf:Description rdf:about="http://www.bibsonomy.org/bibtex/282262b87dba8b4c16d169c7f407def7d/jil"><owl:sameAs rdf:resource="http://www.bibsonomy.org/uri/bibtex/282262b87dba8b4c16d169c7f407def7d/jil"/><rdf:type rdf:resource="http://swrc.ontoware.org/ontology#Book"/><swrc:date>Thu Oct 20 05:17:48 CEST 2011</swrc:date><swrc:address>Berlin</swrc:address><swrc:edition>2.</swrc:edition><swrc:publisher><swrc:Organization swrc:name="Springer"/></swrc:publisher><swrc:title>Model Driven Engineering and Ontology Development</swrc:title><swrc:year>2009</swrc:year><swrc:keywords>book driven mda model ontology owl uml </swrc:keywords><swrc:abstract>Defining a formal domain ontology is generally considered a useful, not to say necessary step in almost every software project. This is because software deals with ideas rather than with self-evident physical artefacts. However, this development step is hardly ever done, as ontologies rely on well-defined and semantically powerful AI concepts such as description logics or rule-based systems, and most software engineers are largely unfamiliar with these.  Gasevic and his co-authors try to fill this gap by detailing how to use model-driven engineering for ontology development on the Semantic Web. Part I of their book describes existing technologies, tools, and standards like XML, RDF, OWL, MDA, and UML. Part II presents the first detailed description of OMG&#039;s new ODM (Ontology Definition Metamodel) initiative, a specification which is expected to be in the form of an OMG language like UML. Finally, Part III is dedicated to applications and practical aspects of developing ontologies using MDA-based languages.  For this second edition, the descriptions of the related standards (like MOF, ODM, OCL, and OWL) have been revised and updated; new chapters introducing the basic principles of model-driven engineering, recent research results on metamodeling Semantic Web rule languages, an introduction to the Atlas Transformation Language (ATL) and its tool support, and, last but not least, many new examples have been added.</swrc:abstract><swrc:hasExtraField><swrc:Field swrc:value="Springer Product page:http\://www.springer.com/978-3-642-00281-6:URL;Amazon Search inside:http\://www.amazon.de/gp/reader/3642002811/:URL;Google Books:http\://books.google.de/books?isbn=978-3-642-00281-6:URL" swrc:key="file"/></swrc:hasExtraField><swrc:hasExtraField><swrc:Field swrc:value="978-3-642-00281-6" swrc:key="isbn"/></swrc:hasExtraField><swrc:hasExtraField><swrc:Field swrc:value="10.1007/978-3-642-00282-3" swrc:key="doi"/></swrc:hasExtraField><swrc:author><rdf:Seq><rdf:_1><swrc:Person swrc:name="Dragan Ga{\v{s}}evic"/></rdf:_1><rdf:_2><swrc:Person swrc:name="Dragan Djuric"/></rdf:_2><rdf:_3><swrc:Person swrc:name="Vladan Deved{\v{z}}ic"/></rdf:_3></rdf:Seq></swrc:author></rdf:Description><rdf:Description rdf:about="http://www.bibsonomy.org/bibtex/287cd8646a253f1deac06ab65bbdade94/iyas_hilal"><owl:sameAs rdf:resource="http://www.bibsonomy.org/uri/bibtex/287cd8646a253f1deac06ab65bbdade94/iyas_hilal"/><rdf:type rdf:resource="http://swrc.ontoware.org/ontology#InProceedings"/><owl:sameAs rdf:resource="http://fparreiras/papers/UMLasOntologyModellingLanguage.pdf"/><swrc:date>Wed Oct 19 20:45:02 CEST 2011</swrc:date><swrc:booktitle>Intelligent Information Integration</swrc:booktitle><swrc:crossref>DBLP:conf/ijcai/1999iii</swrc:crossref><swrc:series>CEUR Workshop Proceedings</swrc:series><swrc:title>UML as an Ontology Modelling Language.</swrc:title><swrc:volume>23</swrc:volume><swrc:year>1999</swrc:year><swrc:keywords>mde ontology ontologyengineering uml </swrc:keywords><swrc:hasExtraField><swrc:Field swrc:value="http://SunSITE.Informatik.RWTH-Aachen.DE/Publications/CEUR-WS/Vol-23/cranefield-ijcai99-iii.pdf" swrc:key="ee"/></swrc:hasExtraField><swrc:hasExtraField><swrc:Field swrc:value="DBLP, http://dblp.uni-trier.de" swrc:key="bibsource"/></swrc:hasExtraField><swrc:author><rdf:Seq><rdf:_1><swrc:Person swrc:name="Stephen Cranefield"/></rdf:_1><rdf:_2><swrc:Person swrc:name="Martin K. Purvis"/></rdf:_2></rdf:Seq></swrc:author></rdf:Description><rdf:Description rdf:about="http://www.bibsonomy.org/bibtex/282262b87dba8b4c16d169c7f407def7d/iyas_hilal"><owl:sameAs rdf:resource="http://www.bibsonomy.org/uri/bibtex/282262b87dba8b4c16d169c7f407def7d/iyas_hilal"/><rdf:type rdf:resource="http://swrc.ontoware.org/ontology#Book"/><swrc:date>Wed Oct 19 20:10:03 CEST 2011</swrc:date><swrc:address>Berlin</swrc:address><swrc:edition>2.</swrc:edition><swrc:publisher><swrc:Organization swrc:name="Springer"/></swrc:publisher><swrc:title>Model Driven Engineering and Ontology Development</swrc:title><swrc:year>2009</swrc:year><swrc:keywords>mda mde modeldrivenengineering ontology uml </swrc:keywords><swrc:abstract>Defining a formal domain ontology is generally considered a useful, not to say necessary step in almost every software project. This is because software deals with ideas rather than with self-evident physical artefacts. However, this development step is hardly ever done, as ontologies rely on well-defined and semantically powerful AI concepts such as description logics or rule-based systems, and most software engineers are largely unfamiliar with these.  Gasevic and his co-authors try to fill this gap by detailing how to use model-driven engineering for ontology development on the Semantic Web. Part I of their book describes existing technologies, tools, and standards like XML, RDF, OWL, MDA, and UML. Part II presents the first detailed description of OMG&#039;s new ODM (Ontology Definition Metamodel) initiative, a specification which is expected to be in the form of an OMG language like UML. Finally, Part III is dedicated to applications and practical aspects of developing ontologies using MDA-based languages.  For this second edition, the descriptions of the related standards (like MOF, ODM, OCL, and OWL) have been revised and updated; new chapters introducing the basic principles of model-driven engineering, recent research results on metamodeling Semantic Web rule languages, an introduction to the Atlas Transformation Language (ATL) and its tool support, and, last but not least, many new examples have been added.</swrc:abstract><swrc:hasExtraField><swrc:Field swrc:value="Springer Product page:http\://www.springer.com/978-3-642-00281-6:URL;Amazon Search inside:http\://www.amazon.de/gp/reader/3642002811/:URL;Google Books:http\://books.google.de/books?isbn=978-3-642-00281-6:URL" swrc:key="file"/></swrc:hasExtraField><swrc:hasExtraField><swrc:Field swrc:value="978-3-642-00281-6" swrc:key="isbn"/></swrc:hasExtraField><swrc:hasExtraField><swrc:Field swrc:value="10.1007/978-3-642-00282-3" swrc:key="doi"/></swrc:hasExtraField><swrc:author><rdf:Seq><rdf:_1><swrc:Person swrc:name="Dragan Ga{\v{s}}evic"/></rdf:_1><rdf:_2><swrc:Person swrc:name="Dragan Djuric"/></rdf:_2><rdf:_3><swrc:Person swrc:name="Vladan Deved{\v{z}}ic"/></rdf:_3></rdf:Seq></swrc:author></rdf:Description><foaf:Group rdf:about="http://www.bibsonomy.org/tag/uml"><foaf:name>uml</foaf:name><description>Community for tag(s) uml</description></foaf:Group></rdf:RDF>
