A Description of Unified Modeling Language
Unified Modeling Language Unified Modeling Language (UML) is an "object modeling and specification language used in software engineering ("Unified Modeling Language", 2005)." It was created to consolidate and standardize 50 different modeling languages that were used by many businesses. The project request to normalize the modeling languages was made by Object Management Group (OMG) and answered by James Rambaugh, Grady Booch, and Ivar Jacobson. In addition to Rambaugh, Booch, and Jacobson, a team called the UML Partners, which included Hewlett-Packard, IBM, Microsoft, Oracle Corporation, and other businesses submitted proposals that were either declined or integrated with the UML proposal. The Unified Modeling Language "is tailored specifically for object oriented systems development" (Siau & Cao, 2001). The new modeling language was successful and was adopted by OMG as their modeling language standard. The main purpose of Object Management Group 's request to standardize modeling languages is to create a common architecture that provide a platform where stakeholders and programmers are able to understand each other and be able to build an application that meets that project request criteria (Siau & Cao, 2001). In addition to this, UML includes modeling diagrams that present the static and dynamic view of a system (Siau & Cao, 2001). These modeling diagrams are separated into three categories: structure diagrams, behavior diagrams, and interaction diagrams. Structure diagrams include class, component, object, and deployment diagrams. A class diagram represents the "fundamental architecture of a system" ("Class Diagram", 2005). The diagram consists of boxes that contain information on the different classes in the system and how they relate to each other. An object diagram "depicts static "snapshots" of the elements within a system, showing objects ' structure, attributes, and relationships to another" ("Object Diagram", 2005). A deployment diagram shows the
References: Class Diagram. (2005). Wikipedia.com Retrieved January 9, 2006 from http://en.wikipedia.org/wiki/Class_diagram Component Diagram. (2005). Wikipedia.com Retrieved January 9, 2006 from http://en.wikipedia.org/wiki/Component_diagram Deployment Diagram. (2005). Wikipedia.com Retrieved January 9, 2006 from http://en.wikipedia.org/wiki/Deployment_diagram Maksimchuck, R. & Naiburg, E. (2001). Introduction to UML for database design. Retrieved January 9, 2006 from http://www.awprofessional.com/articles/article.asp?p=24028&seqNum=1&rl=1 Object Diagrams. (2005). Wikipedia.com Retrieved January 9, 2006 from http://en.wikipedia.org/wiki/Object_diagram Sequence Diagrams. (2005). Wikipedia.com Retrieved January 9, 2006 from http://en.wikipedia.org/wiki/Sequence_diagram Siau, K. & Cao, Q. (2001). Unified Modeling language (UML) – a complexity analysis. Retrieved January 9, 2006 from http://proquest.umi.com/pqdweb?did=126524621&Fmt=&clientId=2606&RQT=309&VName=PQD Unified Modeling Language. (2005). Wikipedia.com Retrieved January 9, 2006 from http://en.wikipedia.org/wiki/Unified_Modeling_Language Use Case Diagrams. (2005). Wikipedia.com Retrieved January 9, 2006 from http://en.wikipedia.org/wiki/Use_case#UML_Use_Case_diagram