MCA-3rd YEAR

NRI-IT

P age |1

UML Notes
On

UNIFIED MODELING LANGUAGE

MCA III year I semester
Topic: Basic concepts of UML

By

SK.BILAL AHMED 10KN1F0002 MCA NRI Institute of Technology

Pothavarappadu

SK.BILAL AHMED

shaikbilalahmed786@gmail.com

MCA-3rd YEAR

NRI-IT

P age |2

The Unified Modeling Language

CONTENT Basic concept of unified modeling language (UML) Overview Introduction to UML Why do we model? What is the Importance of UML Conceptual Model of UML References

SK.BILAL AHMED

shaikbilalahmed786@gmail.com

MCA-3rd YEAR

NRI-IT

P age |3

Basic concept of unified modeling language(UML) Overview:

The heart of object-oriented problem solving is the construction of a model. The model abstracts the essential details of the underlying problem from its usually complicated real world. Several modeling tools are wrapped under the heading of the UML, which stands for Unified Modeling Language. Unified Modeling Language, UML for short, is the international standard notation for Object-Oriented Analysis and Design (OOAD). It is a standardized specialization language that can be used for Object Modeling. It has been defined by the Object Management Group (OMG) and has already become the de-facto standard for designing Object-Oriented Software Applications.

In the field of software engineering, the UML is a standardized specification language for object modeling. UML is a general-purpose modeling language that includes a graphical notation used to create an abstract model of a system, referred to as a UML Model.

Introduction to UML:
According to the OMG specification, "The Unified Modeling Language (UML) is a graphical language for visualizing, specifying, constructing, and documenting the artifacts of a software-intensive system. Example of artifacts : requirements , architecture , design , Source code , test cases Visualizing A picture is worth a thousand words; a graphical notation articulates and unambiguously communicates the overall view of the system (problem-domain).

SK.BILAL AHMED

shaikbilalahmed786@gmail.com

MCA-3rd YEAR

NRI-IT

P age |4

Visualizing

Specifying

Constructing

Specifying UML provides the means to model precisely, unambiguously and completely, the system in question Constructing models built with UML have a design dimension to it; these are language independent and can be implemented in any programming language. Documenting every software project involves a lot of documentation - from the inception phase to the deliverables.

SK.BILAL AHMED

shaikbilalahmed786@gmail.com

MCA-3rd YEAR

NRI-IT

P age |5

Why do we model
A model is a simplification of reality. We build models so that we can better understand the system we are developing Benefits: Models help us to visualize a system as it is or as we want it to be. Models permit us to specify the structure or behavior of a system. Models give us a template that guides us in constructing a system. Models document the decisions we have made. Provide structure for problem solving Experiment to explore multiple solutions Furnish abstractions to manage complexity Reduce time-to-market for business problem solutions Decrease development costs Manage the risk of mistakes Why is UML important? From the point of view of the construction trade. Architects design buildings. Builders use the designs to create buildings. The more complicated the building, the more critical the communication between architect and builder. Blueprints are the standard graphical language that both architects and builders must learn as part of their trade. Writing software is not unlike constructing a building. The more complicated the underlying system, the more critical the communication among everyone involved in creating and deploying the software. In the past decade, the UML has emerged as the software blueprint language for analysts, designers, and programmers alike. It is now part of the software trade. The UML gives everyone from business analyst to designer to programmer a common vocabulary to talk about software design. The UML is applicable to object-oriented problem solving. Anyone interested in learning UML must be familiar with the underlying tenet of object-oriented problem solving -- it all begins with the construction of a model. A model is an abstraction of the underlying problem. The domain is the actual world from which the problem comes. Models consist of objects that interact by sending each other messages. Think of an object as "alive." Objects have things they know (attributes) and things they can do (behaviors or operations). The values of an object's attributes determine its state. Classes are the "blueprints" for objects. A class wraps attributes (data) and behaviors (methods or functions) into a single distinct entity. Objects are instances of classes.

SK.BILAL AHMED

shaikbilalahmed786@gmail.com

MCA-3rd YEAR

NRI-IT

P age |6

UML Modeling:
However, most of the software projects developed around the globe do not follow any specific modeling technique to avoid the perceived risk and complexity in Object Oriented modeling of large systems. The semantics defined in the language are based on the software systems; they do not have complete support for systems of other domains

Moreover, the UML is still incomplete in its support for components. "While modeling software is useful, it will notsolve all design issues . Smart people and a good methodology are a must. But if used correctly, UML and the modeling process can help improve quality, completeness, and scalability and reduce production time in many software projects.

SK.BILAL AHMED

shaikbilalahmed786@gmail.com

MCA-3rd YEAR

NRI-IT

P age |7

Conceptual Model of UML

Building Blocks

Rules

Common Mechanisms

Things

Relationships Diagrams

1. Class Diagram. 1) Association 2. Object Diagram. 2) Dependency 3. Use Case Diagram. 3) Generalization 4. Sequence Diagram. *Stereotypes 4) Realization 5. Collaboration Diagram. *Tagged Values 6. State Chart Diagram. 1) Names *Constraints 7. Activity Diagram. 2) Scope 9. Deployment Diagram. 3) Visibility 4) Integrity 5) Execution

1) Specifications 2) Adornments 3) Common Divisions 4) Extensibility Mechanisms

Structural Things Behavioral Things

Grouping Things Annotational Things *Packages *notes

*Classes *Interfaces *Collaborations *Use Case *Component *Node

*Interaction *State machines *States

SK.BILAL AHMED

shaikbilalahmed786@gmail.com

MCA-3rd YEAR

NRI-IT

P age |8

Structural Things in UML- 7 Kinds (Classifiers)

Nouns. Conceptual or physical elements.
Active Class Class
(processes/threads)

Component
(replaceable part, realizes interfaces)

Interface
(collection of externally Visible ops)

Node
(computational resource at run-time, processing power w. memory)

Student std_id grade changeLevel( ) setGrade( ) getGrade( )

Event Mgr thread time Start suspend( ) stop( )

Course.cpp
IGrade
<<interface>> IGrade setGrade() getGrade()

UnivWebServer

Register for Courses

Use Case
(a system service -sequence of Interactions w. actor)

Manage Course Registration

Collaboration
(chain of responsibility shared by a web of interacting objects, structural and behavioral)
7

Structural Things
Structural things are the nouns of UML models. These are the mostly static parts of a model, representing elements that are either conceptual or physical. In all, there are seven kinds of structural things. It Includes: Classes Interfaces Collaborations Use Case Component Node

SK.BILAL AHMED

shaikbilalahmed786@gmail.com

MCA-3rd YEAR

NRI-IT

P age |9

The Structural things define the static part of the model. They represent physical and conceptual elements. Following are the brief descriptions of the structural things.

SK.BILAL AHMED

shaikbilalahmed786@gmail.com

MCA-3rd YEAR

NRI-IT

P a g e | 10

References: Grady Booch, et al: The Unified Modeling Language User Guide, Addison-Wesley
James Rumbaugh, et al: The Unified Modeling Language Reference Manual, Addison-Wesley The UML Center UML Information, UML Events, Articles and Publications, Industry Links, UML Tools

UML and Software engineering

SK.BILAL AHMED

shaikbilalahmed786@gmail.com