I was starting to panic, Last semester I had linear algebra, you saved me. This semester I have a software engineering module with use cases and sequence diagrams, you saved me. You have the most useful channel on youtube, Thank you for helping me get furter into my degree.
Oh no, another fight is brewing in my comments. It is so nice to be the only guy on RU-vid that doesn't sell anything. If anyone ever catches me trying to sell something feel free to hunt me down. I'm sure you guys are smart enough to find me :)
Amodh Naik . There are simpler examples at www.zenuml.com . You can even interact there. Use a desktop computer to get the best experience. Mobile also works though.
Right now I'm working on a tutorial that will show the whole process of using UML to build excellent OO designs. You'll get it. It will just take a few extra examples. The goal is to make the programming process easy by working out all of the hard stuff in UML
Respected Derek I took some of your lectures your work is really good I appreciate and all lectures are great! But this specific lecture is very difficult to understand, You should've started with simple diagram. Thanks!
Thank you :) Sorry if the example didn't help. I cover sequence diagrams once again in this tutorial ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-fJW65Wo7IHI.html
It is best to see all of the UML tools and pick which ever works best for you. I cover all of them. It is a tool you get good with over time. Once you get very used to it and OO design you'll create everything in UML and the coding will be very easy. More is in the works right now :) Look for my tutorial called Object Oriented Design
Thank you for excellent lessons, I have exam next tomorrow there were some confusion but luckily I found this and two previous videos. Pure and simple. Many thanks for your effort.
Thank you! Had a lecture on this today and only got half of it. I have checked out your tutorials on use case diagrams too and they have been very helpful as well. Keep up the good work!
Nếu tất cả chúng ta sẽ lắng nghe những người khôn ngoan của cuộc sống trong quá khứ sẽ là tốt hơn cho tất cả chúng ta.Một giáo viên chỉ là tốt như các sinh viên của mình
If this tutorial is too complicated for you, then start watch the Object Oriented Design Tutorial. There Derek explains the sequence diagram by building it step-by-step. Just as a hint. =) Of course, without any knowledge of sequence diagrams, you can hardly understand this video. But thanks again Derek, for making my exam preparations much easier and more interesting. Greetings from Switzerland!
Derek Thanks for this tutorial.I like it.Please do not be discourage about any bad comments please keep going.It is not easy to teach but i think you are doing great.
Your videos are great and awesome, To be honest I get much more out of your video than the lectures at my university. I won't name it but it's top 10 here in Australia. I would make my way to class if my lecturer sounds like you xD
Awesome!! There is so much valuable information with precise content and clear explanation. Thanks so much for making this videos available for everyone.
Ah, good to have confirmation from someone who knows so very much about this business. Keep up the amazing video series and I'll not only continue to lead everyone else to your superior tutorials, but I'll also keep posting with this and other wacky avatars ^.^
Things I understood from this video: - sending a signal message through a filled arrow will wait for a response - sending a signal message through a normal arrow will not wait - this messages can be also nested Sequence fragments: - are boxes that surround interactions - they got fragment operators in the top-left corner - optional - will run only if it fulfills a condition - negative - will not be used - reference - will reference to a sequence diagram and call it - a reference sequence diagram is like a method that we can call whenever we want. But instead of "method" it is called "reference". - loop is just a loop that will run as long as a condition is fulfilled - loop (5) - will loop 5 times - loop (x, y) - will loop from x to y - par (parallel) - the interactions from it can run in the same time - alt (alternative) - if - else statements where "if" is called "alt" - assert - if the interactions from this fragment will not fulfill the conditions we will throw an error. Similar to Java's try-catch blocks, or throws. - break - will break from a loop if a certain condition is fulfilled - critical - I didn't quite get this. - I think it is like a reverse loop (don't do this until that happens) Time Constraints: - the arrows are diagonal - we will specify a waiting time for signals while calling or replying - sending signal line will be a normal line - respond signal line will be a dash line Lost Message: -----------> *black hole* Found Message: *black hole* --------------> I found this lesson very hard for a beginner like me. But writing these down totally helped with the grasping process.
That is the normal way. Understand though that even though there are many UML rules they aren't often followed in the real world. From watching this tutorial it would seem that all UML diagrams are done using software. In the real world I almost never do this stuff using software. By myself I use pencil and paper and in a team I always used a whiteboard
Thank you :) Ill see if I can dig it up. I'll post it on the uml tutorial page when I find it. I should have it up today. I'm using the current version of UmLet
amazing presentation....your voice makes me inter a flow state .....mr.derek can you please do a javaEE video or series of videos ? that would be extremely helpful
Hi Derek, I believe a theory: If some one is make tutorial about something that he really is not using for a long time / for a living, he is misleading. Since you are talking about a really a wide range of computer Languages / cookings. I thought you sucks. But you don't! I've checked out this tutorial some years before. But didn't thought this useful / understandable. Till now, after I have tried myself declaring my guts using my "own UML" I figured out how powerfull UML is, how useful this tutorial is! Man, you'd have to be a more grown up developer before you really can understand the beauty & power of UML, and then you can understand what Derek said here is not really that bullshit. :)
Excellent videos! Ive learnt more in 12 minutes than I did all semester! Do you know of any other good resources for learning UML? Most of the textbooks I've read don't have enough examples / case studies. Ideally I'd like one where a case study is presented, I'm given the opportunity to attempt a solution, and then possible solutions are provided.
TyrannosaurusBatman Thank you :) I'm happy I could help explain a very important topic. Nothing really stands out book wise. I learn much of this stuff and object oriented design on the job.
Derek your lessons are very good, I think it would be better if while you are speaking you would be building at the same time, I have to be honest but once you showed a blueprint like this right off the bat I got scared. Difficult for those who are just beginners. But thanks anyway, good job.
Derek Banas I actually really liked the blueprint style of the video, it cut out the time wasted in building the diagram and left more time for explanation. thank you so much for spending your valuable time to make these tutorials.
Metin Erman Only a little % of developers is so smart and intelligent that they can programm out of their head. The problem is that 95% think they belong to that minority.
Amazing instructional video, thanks for taking the time to do this. I have a question, if I may. The diagrammatic blocks, linked vertically by the lifeline, that send and receive messages are different sizes. Some are little squares that only send one message and others are vertically much longer. What determines the size of those please? Thanks.
Thank you very much :) I basically draw everything based off of what the experts say is the right way. I do my best in these tutorials to present the buy the book way of drawing sequence diagrams. i hope that makes sense.
Great video, it's more intermediate to advanced level, I think it's too much code involve with it, cause UML is for business people as well, and they don't understand the class, attribute and etc, I think it's a good practice to write descriptive more than codes also you forgot to mention the sequence's steps numbers.
Thank you :) I always use sequence diagrams on most every project. This tutorial is probably the only one in this series that deviates a bit to my personal style. This is normally what the programmers I'm working with use. I wouldn't show this to business people. They prefer pretty pictures :D
Hello Derek, Nice videos( but i wish the speed was bit less for beginners). I recently subscribed to your channel..Awesome videos on your channel. I love the editing too.could you teach me how you edit these videos ..
Loved your work.. Helped alot.. But have a question 1) At 8:30 par stands for parallel execution so if there is a line in between the two interactions first checkfunds execute before savefunds isnt that a irony for defining parallel execution? Thanks in advance
After I finish UML 2.0 and Refactoring. It looks like Android, Games, C, etc. has won for now. I need to figure out how I will structure the tutorial. By the time refactoring is done, I'll have everything ready to go
Thank you so much for these videos. Love the short, quick, get-to-the-point videos. Question on UML2 Class Diagrams (Part3). In the diagram between Dog and Animal classes, you show in one place Dog pointing to Animal and in another Animal pointing to Dog. Which is it? Does it matter? Can it be either way? Thanks again.
Dear Coach, chỉ cần đi để cho thấy đúng như thế nào Socrates là khi ông nói: Càng biết Càng biết Đó Ông biết vậy là ít hơn. Chia sẻ hào phóng của bạn là một nhắc nhở hàng ngày rằng trường học của cuộc sống là luôn luôn mở cửa cho giáo viên như bạn.
Derek, are these sequence diagrams made previous to programming? I mean, it looks pretty dificult to build a functionality in detail without having the code before. I'd imagine it more as a way of documenting the code but not building it. Maybe it's just because I'm not used to it.
Cesar Augusto Zapata Baldassarri Yes they were. It is something you have to practice. Start with a use case description and then move on to the sequence diagram. As you bounce between those 2 diagrams and the class diagrams changes will come up. Keep at it. I think it is the #1 most important skill a programmer can develop.
Derek Banas Nice. I'll definitely work on that skill. Thanks for your quick feedback. Btw, Thank you so much for creating all these videos for us. I always go to your website first when I need to quickly learn something... no jibber jabber.
I might have missed it but what do the boxes along the life lines mean? So in which cases exactly do you draw them there and in which cases does a life line alone suffice?
Two concepts you didn't cover sufficiently I thought: Activation regions (including nested activation regions) and return messages. Also I thought it would have been good to split the content into things that people will use all the time and concepts that get used in specialised circumstances.
OMG another great tutorial :-) Could you please post the link of the UMLet file source? Or just tell me which version you use 'cause I can't find your UML élément in mine ;-) Thanks in advance
Mr. Banas - I was looking for the application. One I found is v10.2? Looked for the v12.x and thats where I failed. Thanks for the link to the diagrams.
Hello Derek, When you say participant("theCustomer:Customer") invokes method "atmCardInserted(card:ATMCard)", Are you saying that, this method is part of "class CardReader"?
Hello sir, I have a question :) In STARUML Sequence diagram there is a CALL message and SEND message. Is there any differences between those two? Last question sir.. Is every message in sequence diagram need to be implemented (coded) into the application? Thanks :D
hi Derek! parallel from the name we understand that the actions accrue parallely together, not end one to start another . So I did not under stand what did you mean. Could you explain please or give a reference ?
How are you? Do you have an video that actually shows HOW to create a Sequence Diagram from the Use Case -- basically step by step? I feel this video only shows you the parts not the rationale behind why you designed it this way. I feel I need to see a Use Case referenced to the Sequence Diagram to really understand what is going on and why you chose to design it the way you did.
Thanks for the response. I'll take look. I hope you see my other response. I really need help. I want to practice designing the system I "designed" in school to actually get some practical application.
beeram santosh Sorry, but I don't understand the question. I approach building a system by writing out a use case description and then I make the sequence diagram from that. I show how I do it in the first 2 videos in my object oriented design tutorial. I hope it helps :)
Are the messages in the participants neccesarily static methods (if not preceded by a )? For example, in order for Customer to call something in CardReader, it must have a CardReader object living inside it, correct? Can you post the corresponding code to this example?
+Wuzzysbrand06 They represent the lifetime that the object is alive. Where you see breaks in the box, it's just showing that the object is still alive in memory, but that the message is being passed somewhere else. The further down the life line, the further along you are in the sequence. Does that make any more sense or no?
+Dan Fletcher So basically when there's a break in the box, it means the object is still there in memory but it's not being used at the moment (no methods are called on it and no parameters are being changed)?
Yeah, kind of. It's more just so that when you have other lines passing through it - which aren't messages for that object - it doesn't look messy. If Derek didn't have so many notes on this diagram, you'd see less breaks in the boxes.