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
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.
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.
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.
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?
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.
well it save's me a lot of time and it's easy to use.. when you make your own connection to the db it take's lot of time. if you forgot to secure it.. like unicode protection ppl can hack your db..
i have also read that microsoft will come with there own version of it..
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
iBradleyAllen 9 months ago
great atlast i know what the diamond is for!!
thnk u!!
josyula547 10 months ago
Thanks a lot! its a great intro to domain modelling
laksiv 1 year ago
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.
ppppschmidt 3 years ago
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 3 years ago
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 3 years ago
Nice video fellow !
costarricense2006 4 years ago
Awesome! thanks! Trying to understand OO and UML better for the course I`m doing in school. Thanks!
Illyum 4 years ago
Aha!
I knew I'd found an introduction to UML on youtube! Thanks, I really enjoyed this 10 minutes
kthx.
noizz 4 years ago
Anytime :) If you need any more info on a software topic, let me know and I might make another video.
codingkriggs 4 years ago
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?
VeAleyna 4 years ago
thnx
waalteer 4 years ago
i was once test to create an endless loop, that the class own each other, it ends with meanless result :)
voyager838 4 years ago
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
janis2006 4 years ago
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.
codingkriggs 4 years ago
presistence example ibatis
well it save's me a lot of time and it's easy to use.. when you make your own connection to the db it take's lot of time. if you forgot to secure it.. like unicode protection ppl can hack your db..
i have also read that microsoft will come with there own version of it..
don't know if it will be in vs2007
janis2006 4 years ago