In the development of software technology, necessary to the language used to model the software that will be made and the need for standardization so that people in different countries can understand the modeling software. As we know that it brings together many heads to tell an idea in order to understand the same thing is not easy, therefore, required a software modeling language that can be understood by many people.
Many people who have made a modeling language software development in accordance with the programming technology developed at that time, for example, who had time to develop and are used by many parties is the Data Flow Diagrams (DFD) for modeling software that uses pemrogramana procedural or structural, then also there State Transition Diagram (STD) that is used to model real-time systems.
In the development of object-oriented programming techniques, there appeared a standardized modeling language for software development that is built by using object oriented programming techniques, the Unified Modeling Language (UML). UML emerged for their visual modeling needs to specify, describe, construct, and documentation of the software system. UML is a visual language for modeling and communication about a system using diagrams and supporting texts.
As we know that many things in the world of information systems that can not be standardized, all depending on the needs, the environment and context. So also with the development of UML use depends on the level of abstraction use. So it is not necessarily a different view on the use of UML is a wrong, but should be examined where UML is used and what people want to visualize. By analogy, if the language that we use everyday, not necessarily the delivery of the language of poetry is the wrong thing. The information system is not an exact science, so if there are many differences and interpretations in the field of information systems is a very reasonable thing.
Many people who have made a modeling language software development in accordance with the programming technology developed at that time, for example, who had time to develop and are used by many parties is the Data Flow Diagrams (DFD) for modeling software that uses pemrogramana procedural or structural, then also there State Transition Diagram (STD) that is used to model real-time systems.
In the development of object-oriented programming techniques, there appeared a standardized modeling language for software development that is built by using object oriented programming techniques, the Unified Modeling Language (UML). UML emerged for their visual modeling needs to specify, describe, construct, and documentation of the software system. UML is a visual language for modeling and communication about a system using diagrams and supporting texts.
As we know that many things in the world of information systems that can not be standardized, all depending on the needs, the environment and context. So also with the development of UML use depends on the level of abstraction use. So it is not necessarily a different view on the use of UML is a wrong, but should be examined where UML is used and what people want to visualize. By analogy, if the language that we use everyday, not necessarily the delivery of the language of poetry is the wrong thing. The information system is not an exact science, so if there are many differences and interpretations in the field of information systems is a very reasonable thing.
A History of UML
Object-oriented programming language first developed known as Simula-67 developed in 1967. This programming language is less developed and developed further, but the appearance has greatly contributed to the developer of object-oriented programming language developers later.
Active development of object-oriented programming started to squirm when the development of Smalltalk programming language in the early 1980s, followed by the development of object-oriented programming language that is more like an object C, C ++, Eiffel, and CLOS. In actual, the use of object-oriented programming language at that time still limited, but it has attracted attention at the time. About five years after Smalltalk expanding, it also develops object-oriented development methods. The first method was introduced by Sally Shlaer and Stephen Mellor (Shlaer-Mellor, 1988) and Peter Coad and Edward Yourdon (Coad-Yourdon, 1991), followed by Grady Booch (Booch, 1991), James R. Rumbaugh, Michael R. Blaha William Lorensen, Frederick Eddy, William Premerlani (Rumbaugh-Blaha-Premerlani-Eddy-Lorensen, 1991), and many more. Famous book is also developing next is a bouquet of Ivar Jacobson (Jacobson, 1992), which explains the different approaches that focus on use cases and process development. About five years later came the book discusses the object-oriented methodology followed by other books. It also discusses the concepts, definitions, notation, terminology, and processes the object-oriented methodology.
Since the number of methodologies developed rapidly at the time, then came the idea to create a language that can be understood by all people. This unification efforts are taking on methodologies developed at that time. Then created a language which is a combination of several concepts such as the concept of Object Modeling Technique (OMT) from Rumbaugh and Booch (1991), the concept of the Classes, Responsibilities, Collaborators (CRC) of Rebecca Wirfs-Brock (1990), the concept of thought Ivar Jacobson, and several other concepts where James R. Rumbaigh, Grady Booch and Ivar Jacobson joined a company called Rational Software Corporation produces language called Unified Modeling language (UML). In 1996, the Object Management Group (OMG) proposed that the standardization of object-oriented modeling and in September 1997 UML accommodated by OMG so far UML has contributed sizable in object-oriented methodology.
Conversion Conversion Emoticon Emoticon