![]() In the diagram below, each element in the diagram is a component stereotype. A stereotype is a name used to describe an artifact in a general manner. Notice that the component diagram defines a stereotype >. Interface symbols represent the services that the InstructionalVideoService provides. Take a look at the symbols section that follows the diagram below to learn the details of lollipop notation. The services provided by the associated components are represented as required interfaces using lollipop notation. The InstructionalVideoService consumes services provided by the Catalogue, MediaViewer, and UserLibrary components. Component exampleįigure 1 shows four components: InstructionalVideoService, Catalogue, MediaViewer, and UserLibrary. A component diagram is concerned with the various components that make up the system and the interfaces that those components expose and consume. ComponentĪs the name implies, a component diagram is a diagram that describes the various components that make up all or part of a software system. The following sections describe the details of each static diagram type. There are seven types of static diagrams: A dynamic diagram describes what a portion of the system is doing. A static diagram describes what a piece of the system is. Static diagrams describe the state of a system from a variety of perspectives. That application is a system that delivers an educational video to a user according to a selection made from a catalog of videos. In this article, I'll get into the details of static diagrams, and in another article, I describe dynamic diagrams.Įach example diagram for this article represents a particular aspect of a hypothetical application called the Instructional Video Service. My intro article answers essential questions like: What is UML? Why was UML created? Who created UML? and Why should you use UML? There are two basic types of UML diagrams: static and dynamic. Take a Linux infrastructure planning assessment.Technical debt: The IT leader's essential guide.An architect's guide to multicloud infrastructure.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |