Subtitles of the Movie

It's time to wrap up what we covered in this course through out the course we have gone over the basic of UML. We looked at different kinds of notation and different kinds of diagrams to give a good basic overview of how UML works, how to read a diagram, how to create your own. The different kinds of diagrams that we looked at included use case diagrams, such as this one here. You should be able to read this without any difficulty, we have a view of the system from the perspective of some actor outside the system and the different goals that actor might have interacting with the system. We looked at class diagrams, where we defined classes and their static relationships. Class diagrams help you define the different kinds of objects in the system and how those associate with each other. From there we moved on to object diagrams which shows the system structure at a specific particular point in time, with objects, instances of classes and various kinds of relationships, static relationships among them. We also looked at package diagrams. Package diagrams given us a higher level view of the system because we bundle a number of similar elements into a package and take things up a level. We also looked at state diagrams to get a dynamic view of the systems behavior, the different states in which the system can exist and the different transitions between those states. The triggers and the guards and what happens to move from one state to another. We looked at activity diagrams which is as you recall are very helpful for modeling workflow, various kinds of processes, procedural logic and so on. Activity diagrams as you may recall are made up of individual actions, they also have decision points forks and joins and so on to show the flow of various actions that together make up an activity. We looked at two kinds of interaction diagrams, sequence diagrams as you see here that show the communication among participants and some interaction, adding also the dimension of time earlier at the top of the diagram, later as you moved down the diagram. So this shows communication. Similarly communication diagrams emphasize communication, these are another kind of interaction diagram that emphasis objects that communicate and links that enable those objects to communicate. We also looked at component diagrams, components are encapsulated replaceable, reusable, chunks of code the sort of building blocks of your system that communicate with each other through interfaces, so we have components here, we have required interfaces and we have provided interfaces. A provided interface is implemented by the component a required interface is needed by the component in order to do it's functionality. And finally we looked at deployment diagrams to give us a sense of the physical layout of the system, the different nodes that can host software, the software artifacts and the communication paths among nodes. All of these kinds of diagrams together can give a good overview of your system, no single diagram can do that alone, but the different types can show different aspects of the system and together those different diagrams are what will create the model of your system.