Send the link below via email or IMCopy
Present to your audienceStart remote presentation
- Invited audience members will follow you as you navigate and present
- People invited to a presentation do not need a Prezi account
- This link expires 10 minutes after you close the presentation
- A maximum of 30 users can follow your presentation
- Learn more about this feature in our knowledge base article
Do you really want to delete this prezi?
Neither you, nor the coeditors you shared it with will be able to recover it again.
Make your likes visible on Facebook?
You can change this under Settings & Account at any time.
A Simple Overview of UML
Transcript of A Simple Overview of UML
Some of you might have seen something like this:
What was that??
may be formed by reducing the information content of a concept or an observable phenomenon, typically to retain only information which is relevant for a particular purpose.
is anything used in any way to represent anything else.
We are interested in conceptual models, i.e., models that exist only in our mind.
Conceptual models are used to help us know and understand the subject matter they represent.
A no-pain perspective on the most famous modeling language of the galaxy
10,000 lines of code.
You want to understand what is it about.
There is no documentation.
The original developers escaped to other country.
Isn't more clear this one?:
We will cover:
Abstractions, Modeling and Representation
What is UML? What is
Benefits and Problems of Using UML
Some Concrete Examples
How to Incorporate UML in our day-to-day?
We Can Use
General-purpose Modeling Language
It is NOT:
A development method/process (think about OMT, Rational Unified Process, etc)
As simple as we choose
As complete as we wish
Helps to think more abstractly
* Overuse might reduce the focus on the real deliverables.
* You are the boss, not UML.
It's a Bird... It's a Plane... It's UML...,
no wait, it's just one more tool.
a diagram is a partial graphic representation of a system's model.
Represents static (no temporal) characteristics of your classes. What is represented is TRUE throughout all the life of the system.
Represents static (no temporal) characteristics of your objects in one particular instant (a temporal slice of a class diagram).
Differs from the class diagram in which here we represent concrete class INSTANCES, and hence the diagram shows a concrete moment in time.
Represents the DYNAMIC relationship within objects. Shows how a particular object interacts with others to fulfill some specific responsibility (think on a method).
How to add UML
to our life?
Papyrus UML (Eclipse)
... and thousand more
generalization and realization.
Association, Aggregation and Composition.
focus of control
Abstract Factory Pattern
Abuse the whiteboards!
Use during meetings to have more precise communication.
If some part of a system is complex enough and stable enough, some diagrams might help understand it better.