Is There a Difference Between the Theoretical and Practical Complexity of UML?

Author(s):  
Keng Siau ◽  
John Erickson ◽  
Lih Yunn Lee

An on-going and major problem faced by information systems developers and business users alike is reaching a clear and consensual understanding of the system by both groups. This can be difficult because the businesses are (typically) process driven, while the systems are (increasingly) object-oriented. Enter modeling. Modeling is one way of presenting complex information in a way that enhances or eases understanding. But, even models can be extremely complex, and the underlying tools and modeling languages are not any less complex. This chapter investigates the possibility that modeling languages can be simplified by considering that not all of the “words” in the language are used all of the time. If theoretical (maximum) represents all the words in a modeling language, then this chapter suggests that there might exist a more use-based (we name it practical complexity) subset that represents an easier to learn and use subcomponent of the language.

Author(s):  
Liliana Favre ◽  
Liliana Martinez ◽  
Claudia Pereira

The Unified Modeling Language (UML) has emerged as a modeling language for specifying, visualizing, constructing, and documenting software-intensive systems. It unifies proven software modeling languages that incorporate the object-oriented community’s consensus on core modeling concepts. It also includes additional expressiveness to handle problems that previous visual languages did not fully address (Rumbaugh, Jacobson & Booch, 1999).


Author(s):  
Peter Rittgen

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).


2006 ◽  
Vol 153 (1) ◽  
pp. 55-75 ◽  
Author(s):  
Mario Ornaghi ◽  
Marco Benini ◽  
Mauro Ferrari ◽  
Camillo Fiorentini ◽  
Alberto Momigliano

Author(s):  
Peter Rittgen

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).


Author(s):  
G.S. Romanenko ◽  
A.N. Tolchkov ◽  
A.A. Chumichkin

The article considers the task of modeling advanced information systems. The work is based on research on the development of a methodological apparatus for substantiating requirements for military-grade information systems. Currently the requirements for advanced information systems are formed in a natural language, the expressive properties of which are not enough for a concise and unambiguous description of them. The developed methodological approach is based on the construction of a complex of models of system with the integrated use of methodologies of functional and object-oriented modeling of the information system and related management processes, as well as the developed notation of user interface modeling. The use of a unified modeling language provides unambiguous interpretation of models by all participants in the process of developing an information system – from the customer to the developer.


10.28945/2600 ◽  
2003 ◽  
Author(s):  
Richard Alan Hodgett

It is claimed that the Unified Modeling Language (UML) is emerging as the accepted standard graphical language for specifying, constructing, visualizing and documenting the object oriented information systems development process. As such it has gained a place in many information systems programs. An investigation of Australian organizations indicates that the use of object oriented development methodologies and UML is gradually increasing in Australia but is still to see general acceptance. This raises the question of the priority that should be accorded to the inclusion of UML in competition with other topics and issues in information systems education programs.


e-NARODROID ◽  
2015 ◽  
Vol 1 (2) ◽  
Author(s):  
Immah Inayati

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.


Proceedings ◽  
2020 ◽  
Vol 47 (1) ◽  
pp. 55
Author(s):  
Shan Zhang

By applying the concept of natural science to the study of music, on the one hand, we can understand the structure of music macroscopically, on the other, we can reflect on the history of music to a certain extent. Throughout the history of western music, from the classical period to the 20th century, music seems to have gone from order to disorder, but it is still orderly if analyzed carefully. Using the concept of complex information systems can give a good answer in the essence.


Sign in / Sign up

Export Citation Format

Share Document