Scribd
Upload
59 views8 pages

Week 5 UMLSlides

The document provides an overview introduction to the Unified Modeling Language (UML). It discusses that UML is an open standard modeling language used to visually communicate aspects of a system through sketches, blueprints, or as a programming language. It can be used for forward or reverse engineering of systems, from initial sketches to detailed models close to final code implementation. The document also formally defines what a model, classifier, behavior, and event are in the context of UML modeling.

Uploaded by

savvy_as_98-1
Copyright
© © All Rights Reserved
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
59 views8 pages

Week 5 UMLSlides

The document provides an overview introduction to the Unified Modeling Language (UML). It discusses that UML is an open standard modeling language used to visually communicate aspects of a system through sketches, blueprints, or as a programming language. It can be used for forward or reverse engineering of systems, from initial sketches to detailed models close to final code implementation. The document also formally defines what a model, classifier, behavior, and event are in the context of UML modeling.

Uploaded by

savvy_as_98-1
Copyright
© © All Rights Reserved
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/ 8

2/6/16

MODELING
INTRO / OVERVIEW OF UML

FORMALITIES

Initially we cover the formal concepts


Then we will give some examples
For the class we are NOT going to be formal
We will not follow the spec
You do NOT need to worry about understanding the details of UML

2/6/16

UML
Unified Modeling Language
Why model
What about programming language
What about just using text / narrative
Open Standard
OMG Open Management Group

HOW IS IT USED

Sketch
Blueprint
Programming Language

2/6/16

SKETCH
Selectivity

Help communicate some aspects of a system

Forward Sketching
Reverse Sketching
This is what we want
This is what we have

BLUEPRINT
Completeness
The blueprint should be complete and sufficient for someone downstream to build or select the system
The blueprint should be understandable by non-developers, but at the same time be backed up by the
detail that the developers will need to perform the build
All of your design point should tie back to the requirement that caused you to add that point

2/6/16

BLUEPRINT

There is a concept of Forward and Reverse blueprints


Reverse blue prints would be used to document the details of an existing system

PROGRAMMING LANGUAGE
CASE Computer Aided Software Engineering
Autogeneration of programming code
For example

Read data from file per modeled input format

Sort data by second field descending

Write data to file per modeled output format

Good, Bad, and sometimes Really Really UGLY

2/6/16

PROGRAMMING LANGUAGE

The more detailed a model becomes, the closer it is to the final progamming code
The designer may turn the model over to the programmers who then take the model to the next level
At some point the model becomes code

maybe not automated, but a really detailed model takes a lot of guesswork out of the coding

Resuability in modeling also introduces consistency => easier maintenance

MODEL - FORMAL DESCRIPTION


A model is always a model of something. The thing being modeled can
generically be considered a system within some domain of discourse. The
model then makes some statements of interest about that system, abstracting
from all the details of the system that could possibly be described, from a
certain point of view and for a certain purpose. For an existing system, the
model may represent an analysis of the properties and behavior of the
system. For a planned system, the model may represent a specification of
how the system is to be constructed and behave.

From the UML Language Specifiction 2.5 The Open Group

2/6/16

MODELS

A UML model consists of three major categories of model elements, each of


which may be used to make statements about different kinds of individual
things within the system being modeled (termed simply individuals).

From the UML Language Specifiction 2.5 The Open Group

MODELS

Classifiers.
A classifier describes a set of objects. An object is an individual with a state
and relationships to other objects. The state of an object identifies the values
for that object of properties of the classifier of the object.

From the UML Language Specifiction 2.5 The Open Group

2/6/16

MODELS

Behaviors.
A behavior describes a set of possible executions. An execution is a
performance of a set of actions (potentially over some period of time) that
may generate and respond to occurrences of events, including accessing and
changing the state of objects.

From the UML Language Specifiction 2.5 The Open Group

MODELS

Events.
An event describes a set of possible occurrences.
An occurrence is something that happens that has some consequence with
regard to the system.

From the UML Language Specifiction 2.5 The Open Group

2/6/16

DIAGRAMS

Some examples

You might also like