FRINK Linked Data Fragments server

Matches in SemOpenAlex for { <https://semopenalex.org/work/W2785172334> ?p ?o ?g. }

• W2785172334 endingPage "618" @default.
• W2785172334 startingPage "613" @default.
• W2785172334 abstract "The Unified Modeling Language (UML) was adopted by the Object Management Group (OMG) in 1997 as a language for object-oriented (OO) analysis and design. After several minor revisions, a major overhaul resulted in UML version 2.0 (OMG, 2003), and the language is still being refined. Although suitable for object-oriented code design, UML is less suitable for information analysis, since its graphical language provides only weak support for the kinds of business rules found in data-intensive applications, and its textual Object Constraint Language (OCL) is too technical for most business people to understand. Moreover, UML’s graphical language does not lend itself readily to verbalization and multiple instantiation for validating data models with domain experts. These problems can be remedied by using a fact-oriented approach for information analysis, where communication takes place in simple sentences, each sentence type can easily be populated with multiple instances, and attributes are avoided in the base model. At design time, a fact-oriented model can be used to derive a UML class model or a logical database model. Object Role Modeling (ORM), the main exemplar of the fact-oriented approach, originated in Europe in the mid-1970s (Falkenberg, 1976), and has been extensively revised and extended since, along with commercial tool support (e.g., Halpin, Evans, Hallock, & MacLean, 2003). Recently, a major upgrade to the methodology resulted in ORM 2, a second-generation ORM (Halpin 2005). Neumont ORM Architect (NORMA), an open source tool accessible online at http://sourceforge.net/projects/orm, is under development to provide deep support for ORM 2 (Curland & Halpin, 2007). This article provides a concise comparison of the data modeling features within UML and ORM. The next section provides background on both approaches. The following section summarizes the main structural differences between the two approaches, and outlines some benefits of ORM’s factoriented approach. A simple example is then used to highlight the need to supplement UML’s class modeling notation with additional constraints, especially those underpinning natural identification schemes. Future trends are then briefly outlined, and the conclusion motivates the use of both approaches in concert to provide a richer data modeling experience, and provides references for further reading." @default.
• W2785172334 created "2018-02-02" @default.
• W2785172334 creator A5014873848 @default.
• W2785172334 date "2011-05-24" @default.
• W2785172334 modified "2023-09-26" @default.
• W2785172334 title "A Comparison of Data Modeling in UML and ORM" @default.
• W2785172334 cites W125501231 @default.
• W2785172334 cites W136396747 @default.
• W2785172334 cites W1499802916 @default.
• W2785172334 cites W1555070774 @default.
• W2785172334 cites W1572253281 @default.
• W2785172334 cites W1998430220 @default.
• W2785172334 cites W2116120329 @default.
• W2785172334 cites W2171465923 @default.
• W2785172334 cites W2483595258 @default.
• W2785172334 doi "https://doi.org/10.4018/978-1-60566-026-4.ch100" @default.
• W2785172334 hasPublicationYear "2011" @default.
• W2785172334 type Work @default.
• W2785172334 sameAs 2785172334 @default.
• W2785172334 citedByCount "6" @default.
• W2785172334 crossrefType "book-chapter" @default.
• W2785172334 hasAuthorship W2785172334A5014873848 @default.
• W2785172334 hasConcept C115903868 @default.
• W2785172334 hasConcept C145644426 @default.
• W2785172334 hasConcept C199360897 @default.
• W2785172334 hasConcept C2777904410 @default.
• W2785172334 hasConcept C41008148 @default.
• W2785172334 hasConcept C41298492 @default.
• W2785172334 hasConcept C77088390 @default.
• W2785172334 hasConceptScore W2785172334C115903868 @default.
• W2785172334 hasConceptScore W2785172334C145644426 @default.
• W2785172334 hasConceptScore W2785172334C199360897 @default.
• W2785172334 hasConceptScore W2785172334C2777904410 @default.
• W2785172334 hasConceptScore W2785172334C41008148 @default.
• W2785172334 hasConceptScore W2785172334C41298492 @default.
• W2785172334 hasConceptScore W2785172334C77088390 @default.
• W2785172334 hasLocation W27851723341 @default.
• W2785172334 hasOpenAccess W2785172334 @default.
• W2785172334 hasPrimaryLocation W27851723341 @default.
• W2785172334 hasRelatedWork W125501231 @default.
• W2785172334 hasRelatedWork W1583973933 @default.
• W2785172334 hasRelatedWork W1666003788 @default.
• W2785172334 hasRelatedWork W167686354 @default.
• W2785172334 hasRelatedWork W172234034 @default.
• W2785172334 hasRelatedWork W2171465923 @default.
• W2785172334 hasRelatedWork W217510991 @default.
• W2785172334 hasRelatedWork W2292449444 @default.
• W2785172334 hasRelatedWork W2374237465 @default.
• W2785172334 hasRelatedWork W2374264231 @default.
• W2785172334 hasRelatedWork W2394049954 @default.
• W2785172334 hasRelatedWork W2407689631 @default.
• W2785172334 hasRelatedWork W2478326403 @default.
• W2785172334 hasRelatedWork W2484044703 @default.
• W2785172334 hasRelatedWork W2504421683 @default.
• W2785172334 hasRelatedWork W2505871501 @default.
• W2785172334 hasRelatedWork W2524795266 @default.
• W2785172334 hasRelatedWork W2529266300 @default.
• W2785172334 hasRelatedWork W2975463411 @default.
• W2785172334 hasRelatedWork W2187286502 @default.
• W2785172334 isParatext "false" @default.
• W2785172334 isRetracted "false" @default.
• W2785172334 magId "2785172334" @default.
• W2785172334 workType "book-chapter" @default.