UML: Architecture, Domain and Class Diagrams 2 of 2

In this pair of videos, I give an overview UML (the Unified Modeling Language).

Category:

Howto & Style

Tags:

• software
• engineering
• codingkriggs
• uml
• unified
• modeling
• language
• architecture
• domain
• class
• diagram
• model
• dependency
• arrow

[noizz]

Aha!

I knew I'd found an introduction to UML on youtube! Thanks, I really enjoyed this 10 minutes

kthx.

[codingkriggs]

Anytime :) If you need any more info on a software topic, let me know and I might make another video.

[janis2006]

this one i much better.. but still you should make a project for a program and show it in a tutorial

but i see a 3layer model.. shouldn't it be a 5layer model?

ui/

control layer/

busniss layer/

perspectie layer(connection to database)/

database layer

[codingkriggs]

Interesting. Just as there is no concensus with the MVC, there is no concensus on the layered model. Craig Larman has the following layers in his book "Applying UML and Patterns".

ui/ (presentation)

application/ (workflow)

domain/ (business logic and model)

businessinfrastructure/ (model utilities)

technicalservices/ (persistence, db, etc.)

foundation/ (math, threads, etc.)

I've only ever used 3 though. I'd love if you told me about the advantages of spliting each layer into two.

[iBradleyAllen]

Hi, great videos on UML. could you consider making a video on using Papyrus for Eclipse, making a simple project and explain the various main components. In a vid somewhere, a visual class was done, then converted to code; I was trying to duplicate this but wasnt able to.

In these vids you give an excellent intro to UML, that Ive now got to learn. I can follow OO and C# is my favorite but never had to do UML until now

thanks

[josyula547]

great atlast i know what the diamond is for!!

thnk u!!

[laksiv]

Thanks a lot! its a great intro to domain modelling

[ppppschmidt]

I also agree he didn't distinguish composition (dark diamond) from aggregation (clear diamond) correctly. One small point- might be good to use a UML tool in the tutorial and talk from it. As models get complicated, you can't run audit checks on slips of paper.

[ComradeAart]

Sorry to for me bitching about it, but your story about the composite aggregation is incorrect. I will illustrate this with your example.

The only thing the diamond tells you is that an instance of Slide cannot exist without an instance of SlideShow. SlideShow is indeed a collector, but it can still manipulate the instances of Slide. There are no restrictions like the one you are mentioning in the UML specification.

Note that the UML specification is very "open" and that you can add constraints.

[ComradeAart]

Sorry to for me bitching about it, but your story about the composite aggregation is incorrect. I will illustrate this with your example.

The only thing the diamond tells you is that an instance of Slide cannot exist without an instance of SlideShow. SlideShow is indeed a collector, but it can still manipulate the instances of Slide. There are no restrictions like the one you are mentioning in the UML specification.

Note that the UML specification is very "open" and that you can add constraints.

[costarricense2006]

Nice video fellow !

[Illyum]

Awesome! thanks! Trying to understand OO and UML better for the course I`m doing in school. Thanks!

[VeAleyna]

Hi I really enjoyed your effort.

I am curios about how a good design can be built and how very complex problems of real world can be abstracted in an easy manner. Could you please solve an arbitrary real world problem step by step?

I mean how do designers choose and place appropriate classes and the exact relations between them? What are the phases and so on?