Unified Modeling Language Seminar

8/2/2019 Unified Modeling Language Seminar

1/21


2/21

What is uml

Its a language by which technical architects can communicate

with developers.

Its a language by which one can express design of a software

architecture.

Its a blue print of source code.

It has nine diagrams which can be used in design document toexpress design of software architecture.

Unified modeling language, a standard language for designing

and documenting a system in an object-oriented manner.


3/21

UML History


4/21


5/21

Model

Models provide various perspectives, when put togetherwill provide an overall view of the system.

Creating a model for a given level of abstraction decideswhich elements are to be included and which are to be

excluded.

He notation often takes the form of graphical symbolsand connections.

Models in software helps us to visualize,specify,constructand document the artifacts of a software intensivesystem.


6/21

Parts of UML

The UML is composed of three different parts:

Model elements- the model elements represent basicobject-oriented concepts such as classes,object andrelationships.

Diagrams-portray different combinations of modelelements.

The UML provides nine types of diagrams use

case,class,object,statechart,sequence,collaboration,activity,component, anddeployment.

Views-provide the highest level of abstraction for

analyzing the system.


7/21

Five main views in UML


8/21

Use case Diagrams

The use case diagram represents an outsideview of the system.

Creating a use-case model involves the

following steps: Defining the system

Identifying the actors and the use cases

Describing the use cases

Defining the relationship between the use

cases.


9/21


10/21

notations

Notations of use case

Notation for Actor

Relation:

Include-an include relationship shows behavior that iscommon to one or more use cases(mandatory)

Extend-an extend relationship shows optional

behavior(optional) System boundary: rectangle separates the clinic

system from the external actors.


11/21

Class Diagrams

Shows the existence of classes and their relationshipsin the structural view of system.

Classes and their structure and behavior

Relationships

Association Aggregation

Composition

Dependency

Generalization/specialization (inheritancerelationship)

Multiplicity and navigation indicators

Role names


12/21

Class Diagram - notation


13/21

Sequence diagram

Shows the interaction of objects with

respect to time

Sequence diagrams have two axes

Horizontal axis represents the objects

involved in a sequence.

Vertical axis represents the passage of time


14/21

Sequence Diagram


15/21

Activity diagram

Is essentially a fancy flowchart.

Activity diagrams and state chart diagrams are

related.

On the flow of activities involved in a single

process.

Shows the how those activities depend on oneanother


16/21

Activity Diagram


17/21


18/21

State Chart Diagram

A state chart(transition) diagram is used to show

The life history of a given

class,usecase,operation

The events that cause a transition from one

state to another

The actions state that result from a state change

state transition diagrams are created for

objects with significant dynamic behavior.


19/21

Advantages

We have a specific standard

Strong communication

UML is best for highly advanced

applications


20/21

criticism

Standards bloat

Problems in learning and adopting

Linguistic incoherence


21/21

conclusion

Unified Modeling Language Seminar

Documents