Information Modeling in UML and ORM

2005 ◽  
pp. 1471-1475 ◽  
Author(s):  
Terry Halpin
Keyword(s):  
Unified Modeling Language ◽  
Object Oriented ◽  
Information Modeling ◽  
Code Design ◽  
Domain Experts ◽  
Weak Support ◽  
Unified Modeling ◽  
Data Intensive ◽  
Management Group ◽  
Data Intensive Applications

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 it provides only weak support for the kinds of business rules found in data-intensive applications. Moreover, UML’s graphical language does not lend itself readily to verbalization and multiple instantiation for validating data models with domain experts.

Information Analysis in UML and ORM

2002 ◽  
pp. 307-323 ◽  
Author(s):  
Terry Halpin
Keyword(s):  
Unified Modeling Language ◽  
Data Modeling ◽  
Object Oriented ◽  
Information Analysis ◽  
Domain Experts ◽  
Unified Modeling ◽  
Data Intensive ◽  
Class Diagrams ◽  
Conceptual Data ◽  
Data Intensive Applications

Since its adoption by the Object Management Group as a language for object-oriented analysis and design, the Unified Modeling Language (UML) has become widely used for designing object-oriented code. However, UML has had only minimal adoption among practitioners for the purposes of information analysis and database design. One main reason for this is that the class diagrams used in UML for data modeling provide only weak, and awkward, support for the kinds of business rules found in data-intensive applications. Moreover, UML’s graphical language does not lend itself readily to verbalization and multiple instantiation for validating data models with domain experts. These defects can be remedied by using a fact-oriented approach for information analysis, from which UML class diagrams may be derived. Object-Role Modeling (ORM) is currently the most popular fact-oriented modeling approach. This chapter examines the relative strengths and weaknesses of UML and ORM for conceptual data modeling, and indicates how models in one notation can be translated into the other.

Use Cases in the UML

2011 ◽  
pp. 3909-3913
Author(s):  
Brian Dobing ◽  
Jeffrey Parsons
Keyword(s):  
Software Development ◽  
Unified Modeling Language ◽  
Object Oriented ◽  
Use Cases ◽  
Use Case ◽  
Unified Modeling ◽  
Systems Analysis And Design ◽  
Text Document ◽  
Management Group ◽  
Uml 2.0

The unified modeling language (UML) emerged in the mid-1990s through the combination of previously competing object-oriented systems analysis and design methods, including Booch (1994), Jacobson, Christerson, Jonsson, and Overgaard (1992), Rumbaugh, Blaha, Premerlani, Eddy, and Lorensen (1991) and others. Control over its formal evolution was placed in the hands of the object management group (www.omg.org), which recently oversaw a major revision to UML 2.0 (OMG, 2005). The UML has rapidly emerged as a standard language and notation for object-oriented modeling in systems development, while the accompanying unified software development process (Jacobson, Booch, & Rumbaugh, 1999) has been developed to provide methodological support for applying the UML in software development. Use cases play an important role in the unified process, which is frequently described as “use case driven” (e.g., Booch et al., 1999, p. 33). The term “use case” was introduced by Jacobson (1987) to refer to a text document that outlines “a complete course of events in the system, seen from a user’s perspective” (Jacobson et al., 1992, p. 157). The concept resembles others being introduced around the same time. Rumbaugh et al. (1991), Wirfs-Brock, Wilkerson, and Wiener (1990), and Rubin and Goldberg (1992) use the terms “scenario” or “script” in a similar way. While use cases were initially proposed for use in object-oriented analysis and are now part of the UML, they are not inherently object-oriented and can be used with other methodologies.

Constraints on Conceptual Join Paths

2011 ◽  
pp. 258-277 ◽  
Author(s):  
Terry Halpin
Keyword(s):  
Unified Modeling Language ◽  
Conceptual Modeling ◽  
Information Modeling ◽  
Modeling Language ◽  
Weak Support ◽  
Unified Modeling ◽  
Systems Model ◽  
Entity Relationship ◽  
Object Role Modeling ◽  
Object Oriented Systems

To ensure that a software system accurately reflects the business domain that it models, the system needs to enforce the business rules (constraints and derivation rules) that apply to that domain. From a conceptual modeling perspective, many application domains involve constraints over one or more conceptual schema paths that include one or more conceptual joins (where the same conceptual object plays roles in two relationships). Popular information modeling approaches typically provide only weak support for such conceptual join constraints. This chapter contrasts how these join constraints are catered for in object-role modeling (ORM), the Unified Modeling Language (UML), the Object-oriented Systems Model (OSM), and some popular versions of entity-relationship (ER) modeling. Three main problems for rich support for join constraints are identified: disambiguation of schema paths, disambiguation of join types, and mapping of join constraints to implementation code. To address these problems, some notational, metamodel, and mapping extensions are proposed.

Fuzzy Information Modeling with the UML

2011 ◽  
pp. 153-176 ◽  
Author(s):  
Zongmin Ma
Keyword(s):  
Knowledge Engineering ◽  
Unified Modeling Language ◽  
Data Modeling ◽  
Data Models ◽  
Information Modeling ◽  
Fuzzy Information ◽  
Unified Modeling ◽  
Management Group ◽  
Conceptual Data ◽  
Design Databases

Computer applications in nontraditional areas have put requirements on conceptual data modeling. Some conceptual data models, being the tool of design databases, were proposed. However, information in real-world applications is often vague or ambiguous. Currently, less research has been done in modeling imprecision and uncertainty in conceptual data models. The UML (Unified Modeling Language) is a set of object-oriented modeling notations and is a standard of the Object Data Management Group (ODMG). It can be applied in many areas of software engineering and knowledge engineering. Increasingly, the UML is being applied to data modeling. In this chapter, different levels of fuzziness are introduced into the class of the UML and the corresponding graphical representations are given. The class diagrams of the UML can hereby model fuzzy information.

Modeling Information Systems in UML

2011 ◽  
pp. 2651-2656
Author(s):  
Peter Rittgen
Keyword(s):  
Unified Modeling Language ◽  
Object Oriented ◽  
Modeling Language ◽  
Modeling Languages ◽  
Unified Modeling ◽  
Management Group ◽  
Industry Standard ◽  
Single Method ◽  
Object Oriented Methods ◽  
The Individual

The first approaches to object-oriented modeling appeared already in the second half of the 1970s, but not much happened for more than a decade so there were still barely more than a handful of modeling languages at the end of the 1980s. It was the early 1990s that witnessed an ever-growing market in competing object-oriented methods so that potential users found it increasingly difficult to identify any single method that suited their needs. This phenomenon came to be known as the “method wars.” Toward the end of 1994, two of the “big” players, Grady Booch and Jim Rumbaugh, decided to join forces by integrating their respective approaches, the Booch method and OMT (object modeling technique). In late 1995, Ivar Jacobson became a member of this team merging in his OOSE method (object-oriented software engineering). The efforts of the “three amigos” aimed at overcoming unnecessary differences between the individual approaches and also improving each of them by creating a common, standardized modeling language that could serve as an industry standard. The result was the release of the Unified Modeling Language (UML), version 0.9, in June 1996. The UML partners, an industry consortium, performed further work on UML. This led to the versions 1.0 and 1.1 being introduced in 1997. The latter was adopted by the OMG (Object Management Group) in the same year. The current version is 2.0 (OMG, 2005, 2006).

Modeling Information Systems in UML

2005 ◽  
pp. 2001-2006
Author(s):  
Peter Rittgen
Keyword(s):  
Unified Modeling Language ◽  
Object Oriented ◽  
Modeling Language ◽  
Modeling Languages ◽  
Unified Modeling ◽  
Management Group ◽  
Industry Standard ◽  
Single Method ◽  
Object Oriented Methods ◽  
The Individual

The first approaches to object-oriented modeling appeared by the second half of the 1970s, but not much happened for more than a decade, so there were still barely more than a handful of modeling languages at the end of the 1980s. It was the early 1990s that witnessed an ever-growing market in competing object-oriented methods so that potential users found it increasingly difficult to identify any single method that suited their needs. This phenomenon came to be known as the “method wars.” Towards the end of 1994 two of the “big” players, Grady Booch and Jim Rumbaugh, decided to join forces by integrating their respective approaches, the Booch method and OMT (Object Modeling Technique). In late 1995, Ivar Jacobson became a member of this team merging in his OOSE method (Object-Oriented Software Engineering). The efforts of the “three amigos” aimed at overcoming unnecessary differences between the individual approaches and also improving each of them by creating a common, standardized modeling language that could serve as an industry standard. The result was the release of the Unified Modeling Language (UML), version 0.9, in June 1996. The UML partners, an industry consortium, performed further work on UML. This led to the versions 1.0 and 1.1 being introduced in 1997. The latter was adopted by the OMG (Object Management Group) in the same year. The current version is 1.5 (OMG, 2003) but a major upgrade to 2.0 is in preparation (Björkander & Kobryn, 2003).

APLIKASI PEMESANAN MAKANAN BERBASIS WEB

e-NARODROID ◽  
2015 ◽  
Vol 1 (2) ◽  
Author(s):  
Immah Inayati
Keyword(s):  
Unified Modeling Language ◽  
Object Oriented ◽  
Modeling Language ◽  
Unified Modeling ◽  
Model View Controller ◽  
Model View

Perkembangan dunia teknologi berjalan sangat cepat. Selaras dengan hal itu, kebutuhan manusia hususnya dibidang bisnis juga semakin berkembang. salah satunya adalah R.M. Lesehan Berkah Ilaahi. Rumah makan ini merupakan rumah makan yang memiliki banyak pelanggan. Dengan semakin bertambahnya jumlah pelanggan, maka [penumpukan antrian banyak terjadi. Di samping itu rumah makan ini memiliki potensi untuk dapat terus mengembangkan bisnisnya. Untuk itu dibutuhkan sebuah sistem yang mampu memfasilitasi proses pemesanan melalui online serta mampu membantu pemilik bisnis dalam melakukan promosi dan penawaran, terlebih kepada pelanggan yang daya belinya tinggi. Jurnal ini memaparkan proses pembangunan sistem pemesanan berbasis web dengan menekankan pada tahap analisa, desain, dan implementasi. Analisis kondisi lapangan dilakukan dengan cara observasi lapangan, studi literatur sistem lama, wawancara dan kuesioner pelanggan. Hasil analisa akan digambarkan menggunakan notasi UML (Unified Modeling Language) untuk selanjutnya diimplementasikan dalam sebuah aplikasi e-CRM menggunakan bahasa pemrograman PHP serta basis data PostgreSQL. Metode pengembangan yang digunakan adalah Object oriented dengan memanfaatkan Yii Framework yang merupakan framework PHP berbasis Model View Controller (MVC). Selain itu digunakan pula bootstrap framework dari sisi desain aplikasi untuk memberikan fleksibilitas aplikasi ketika diakses dengan device yang resolusinya lebih kecil seperti telephon genggam. Kata kunci : Observasi, Wawancara, Kuesioner, UML (Unified Modeling Language), Yii Framework, Object oriented, Model View Controller (MVC), bootstrap framework.

UML Based Design Approach for Storage System of Nano-Satellite

2014 ◽  
Vol 599-601 ◽  
pp. 530-533
Author(s):  
Hong Hao Wang ◽  
Hui Quan Wang ◽  
Zhong He Jin
Keyword(s):  
Storage System ◽  
Unified Modeling Language ◽  
Object Oriented ◽  
Modeling Language ◽  
Nand Flash ◽  
Unified Modeling ◽  
Object Oriented Design ◽  
High Level Modeling ◽  
High Level

Due to the complex timing sequence of NAND flash, a unified design process is urgently required to guarantee the reliability of storage system of nano-satellite. Unified Modeling Language (UML) is a widely used high level modeling language for object-oriented design. This paper adopts the UML as the design and modelling tool in the low level storage system design to elaborate the UML application in each phase of design in detail. The result shows taking UML as the modelling tool results in a clear and unambiguity design, which promotes the reliability and quality of software. At last, the feasibility of object-oriented implementation in C is presented.

scholarly journals Aplikasi Sistem Informasi Social Media Advertise Maintenance Menggunakan Pendekatan Object Oriented Methodology

2021 ◽  
Vol 7 (1) ◽  
pp. 19-31
Author(s):  
Sri Rahayu ◽  
Ryanthika Serliyanthi Setyaningrum ◽  
Yuni Kristina Dewi
Keyword(s):  
Social Media ◽  
Information System ◽  
Unified Modeling Language ◽  
Object Oriented ◽  
Negotiation Process ◽  
The Internet ◽  
Great Opportunity ◽  
Face To Face ◽  
Unified Modeling ◽  
The Right

Information systems built in the form of social media and the internet make us able to carry out various activities without having to meet face to face. Social media is currently the main attraction for people to communicate and find information quickly. This is a great opportunity for companies to reach and expand their market. With an information system built in the form of social media and the internet, all obstacles, both distance and high costs, can be suppressed and communication can be carried out effectively. So far, PT. Red Eye Utama conducts marketing through radio advertisements, newspapers / billboards, this is what causes problems, due to limited space and time, as well as high costs to carry out all these processes. The negotiation process between the company and the customer is one of the obstacles that affects the company's service to customers. Therefore, one solution to the problems in this system is to build a Social Media Advertise Maintenance Information System. By using PIECES method analysis for improvements based on performance indicators, indicator information, economic indicators, control indicators, efficiency indicators and service indicators. To design the new system, object-oriented modeling is used, namely UML (Unified Modeling Language) which is the right tool to use in describing the system design that will be made according to User needs.

Sign in / Sign up

Export Citation Format

Share Document