8.2. Introduction To The Unified Modeling Language: UML Standard Diagrams
UML (Unified Modeling Language) is a standardized modeling language that can be used to model both software and non-software systems. It provides graphical representations to help understand, design, and document systems. UML uses different types of diagrams to represent different aspects (structural and behavioral) of a system. The main types of structural diagrams are class, object, component, and deployment diagrams. The main types of behavioral diagrams are use case, sequence, collaboration, state chart, and activity diagrams. UML aims to be a general purpose modeling language that is easy for all modelers to use.
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0 ratings0% found this document useful (0 votes)
131 views
8.2. Introduction To The Unified Modeling Language: UML Standard Diagrams
UML (Unified Modeling Language) is a standardized modeling language that can be used to model both software and non-software systems. It provides graphical representations to help understand, design, and document systems. UML uses different types of diagrams to represent different aspects (structural and behavioral) of a system. The main types of structural diagrams are class, object, component, and deployment diagrams. The main types of behavioral diagrams are use case, sequence, collaboration, state chart, and activity diagrams. UML aims to be a general purpose modeling language that is easy for all modelers to use.
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 2
8.2.
Introduction to the Unified Modeling Language
Unified Modeling Language (UML) makes it possible to describe systems with pictures and words. It can be used to model a variety of systems-business systems ,software systems or any other system. It is a graphical modeling language that is used to express designs. UML is a standardized language to specify the components and artifacts of a software system. It describes a notation and not a process. It does not put forth a single process or method of design, but rather is a standardized tool that can be used in a design process. A picture is worth a thousand words, this concept absolutely fits while discussing about UML in this module. There are a number of goals for developing UML but the most important goal is to define some general purpose modeling language ,which all modelers can use and also it needs to be made simple to understand and easy to use. UML diagrams are not only made for developers but also for common people, business users and anybody interested to understand the a software or non software. It is clear that UML is not a development methodology rather than it accompanies with processes to make a successful system. UML breaks the complex system into small pieces that can be understood easily. Complex system can be understood by different developers who are working on different platforms. Handing over the system or application to new team becomes easier. UML model is not a platform or system specific. UML unifies all different developers under one roof. UML Modeling provides following benefits: We can use UML with all processes throughout the development life cycle and across different implementation technologies. Software will behave as we expect it to (fewer surprises). We will have lower development costs. Working with new developers will be easier. The right decisions are made to prevent poorly written code. Overall cost would be very less. We can develop memory and processor efficient systems. Efficient communication with programmers and outside contractors. Less system maintenance cost. UML Standard Diagrams We prepare UML diagrams to understand a system in simple and better way. A single diagram is not enough to cover the different aspects of the system. UML defines various kinds of diagrams to cover all the aspects of a system. We can also create our own set of diagrams to meet our requirements. UML diagrams are generally made in an incremental and iterative way.There are two broad categories of UML diagrams and then are again divided into sub-categories: Structural Diagrams Behavioral Diagrams 1. Structural Diagrams The structural diagram represents the static aspect of the system. These static parts are represented by classes, interfaces, objects, components and nodes. The four structural diagrams are, 1.Class diagram 2.Object diagram 3.Component diagram 4.Deployment diagram 2. Behavioral Diagrams Any system can have two aspects, static and dynamic. A model is considered as complete when both the system and dynamic aspects are covered fully. Behavioral diagram basically represents the dynamic aspect of a system. Dynamic aspect can be further described as the changing or moving parts of a system.UML has the following five types of behavioral diagrams: 1.Use case diagram 2.Sequence diagram 3.Collaboration diagram 4.State chart diagram 5.Activity diagram
For further reading you may refer the websites below.
Download (Ebook) Data Modeling Made Simple with Embarcadero ER/Studio Data Architect: Adapting to Agile Data Modeling in a Big Data World by Steve Hoberman ISBN 9781634620925, 1634620925 ebook All Chapters PDF
Co-Evolution of Metamodels and Model Transformations: An operator-based, stepwise approach for the impact resolution of metamodel evolution on model transformations.