UML Component Diagrams A.Y 2018/2019

Transcription

1 UML Component Diagrams A.Y 2018/2019

2 Component diagrams Component diagrams are integral to building your software system. Drawn out with UML diagramming software, they help your team understand the structure of existing systems and then build new ones.

3 What is a UML component diagram? The purpose of a component diagram is to show the relationship between different components in a system. The term component refers to a module of classes that represent independent systems or subsystems with the ability to interface with the rest of the system.

4 The role of component diagrams There exists a whole development approach that revolves around components: component-based development (CBD). In this approach, component diagrams allow the planner to identify the different components so the whole system does what it's supposed to do. More commonly, in an OO programming approach, the component diagram allows a senior developer to group classes together based on common purpose so that the developer and others can look at a software development project at a high level.

5 Benefits of component diagrams Though component diagrams may seem complex at first glance, they are invaluable when it comes to building your system. Component diagrams can help your team: - Imagine the system s physical structure. - Pay attention to the system s components and how they relate. - Emphasize the service behavior as it relates to the interface.

6 How to use component diagrams A component diagram in UML gives a bird s-eye view of your software system. Understanding the exact service behavior that each piece of your software provides will make you a better developer. Component diagrams can describe software systems that are implemented in any programming language or style.

7 What component diagrams are UML is a set of conventions for object-oriented diagrams that has a wide variety of applications. In component diagrams, the Unified Modeling Language dictates that components and packages are wired together with lines representing assembly connectors and delegation connectors.

8 Notation A component provides and consumes behavior through interfaces, as well as through other components. Think of components as a type of class. Shows input or materials that a component either receives or provides.

9 Required interfaces: A straight line from the component box with an attached half circle (also represented as a dashed arrow with an open arrow). These symbols represent the interfaces where a component requires information in order to perform its proper function. Provided and required interfaces Provided interfaces: A straight line from the component box with an attached circle. These symbols represent the interfaces where a component produces information used by the required interface of another component.

10 Example

11 UML Sequence Diagrams

12 Sequence diagrams Sequence diagrams are a popular dynamic modeling solution in UML because they specifically focus on lifelines, or the processes and objects that live simultaneously, and the messages exchanged between them to perform a function before the lifeline ends.

13 What is a sequence diagram in UML? A sequence diagram is a type of interaction diagram because it describes how and in what order a group of objects works together. These diagrams are used by software developers and business professionals to understand requirements for a new system or to document an existing process. Sequence diagrams are sometimes known as event diagrams or event scenarios.

14 Benefits of sequence diagrams Sequence diagrams can be useful references for businesses and other organizations. Try drawing a sequence diagram to: - Represent the details of a UML use case. - Model the logic of a sophisticated procedure, function, or operation. - See how objects and components interact with each other to complete a process. - Plan and understand the detailed functionality of an existing or future scenario.

15 Use cases for sequence diagrams Usage scenario: A usage scenario is a diagram of how your system could potentially be used. It's a great way to make sure that you have worked through the logic of every usage scenario for the system. Method logic: Just as you might use a UML sequence diagram to explore the logic of a use case, you can use it to explore the logic of any function, procedure, or complex process. Service logic: If you consider a service to be a high-level method used by different clients, a sequence diagram is an ideal way to map that out.

16 Notation Lifeline: Represents the passage of time as it extends downward. This dashed vertical line shows the sequential events that occur to an object during the charted process. Lifelines may begin with a labeled rectangle shape or an actor symbol. Actor: Shows entities that interact with or are external to the system. Activation box: Represents the time needed for an object to complete a task. The longer the task will take, the longer the activation box becomes.

17 Message symbols Synchronous message: This symbol is used when a sender must wait for a response to a message before it continues. The diagram should show both the call and the reply. Asynchronous message: Asynchronous messages don't require a response before the sender continues. Only the call should be included in the diagram. Return message: Represented by a dashed line with a lined arrowhead.

18 Example

19 Exercise 1 Draw a component diagram that models an application that provides a user interface for visualizing gene interactions in rare diseases. Gene interactions should be identified by mining correlations among genes when a specific disease is observed.

20 Exercise 2 Draw a sequence diagram that models the events of an application that provides a user interface for visualizing gene interactions in rare diseases. Gene interactions should be identified by mining correlations among genes when a specific disease is observed.

21 Questions