Sequence with Component Ports and Interfaces

The Sequence with Component Ports and Interfaces pattern creates elements and a Sequence diagram that describes the interaction between two components through their Ports and Interfaces.

Figure 1. Shows a Sequence diagram and the interaction between two Components that have Ports and Interfaces defined.

Figure 2. Shows a Component diagram that describes the information (payload) that is being exchanged between two Components. The Components, Ports and Interfaces can be shown on a sequence diagram, but it is ultimately the Interfaces that exchanges the messages, the work being done by the Components or their parts.

Discussions
The purpose is to allow the interaction between the elements to be visualized. Designers and Implementations teams typically create the Sequence diagrams either as a design tool or for the purposes of documentation. The sequence of messages can often inform a design decision or bring clarity to a problem discovered in an operation system.

The pattern is typically used during the design or implementation phase but can also be used when an initiative has been completed and documentation is required. It can be used to:
·	Visualize a complex interaction between two or more components and the messages they exchange.
Sequence diagrams can also conveniently be created automatically from call stacks.

The following is a list of some things you may want to do when working with this pattern.
·	Change the name of the diagram to suit the initiative.
Change the name of the Components to suit the initiative.
Change the names of the Component's Operations which are visible on the diagram as Messages.
Create additional, Components and Messages that model the interactions applicable to the initiative.
·	Change the text on the Note elements to be applicable to the messages to suit the initiative.

The following is a list of some things you may want to do when working with this pattern.
·	Extend the diagram to include other elements that reflect the sequence that needs to be analyzed.
Use the Visual Execution Analyzer to automatically create Sequence and to build, debug, record, profile implemented systems.
·	Create additional Interaction Operators to model the sequence of message flows.
Enable the Show Sequence Numbering option to assist in the readability of the diagram.
·	Create automatically generated Documentation of the Sequence diagrams directly from the repository.

Useful Workspace Layouts Core | Core Modeling

Reference
The following help topics will assist you learn about how to work with this pattern.
Sequence Diagrams
Component
Operation
Message
Create Sequence Diagram of Call Stack

The following are some of the tools that will be helpful when working with this pattern.
Visual Execution Analyzer
The Visual Execution Analyzer is made up of an advanced and powerful suite of tools that allow you to build, debug, record, profile, simulate and otherwise construct and verify your software development while keeping the code tightly integrated with your model. Enterprise Architect has rich support for a wide range of popular compilers and platforms, in particular the Java, .Net and Microsoft Windows C++ environments. Software development becomes a highly streamlined visual experience, quite unlike working in traditional environments. For more details see the Visual Execution Analyzer  help topic.
Scenario Builder
The Scenario Builder is a productive and unique too l and editor that allows the analyst to work with the text of Use Cases and Scenarios directly inside the model. Many analysts will be familiar with creating long and voluminous Word Processor documents describing the details of Use Cases. With the Scenario Builder the descriptions and steps of Scenarios can be entered directly into the repository and linked to other elements. Alternate and Exception paths can be defined including branch and re-entry points. Sequence and other behavioral diagrams representing the steps in a scenario can be generated and automatically synchronized. For more details see the Scenario Builder help topic.
Element Discussions
The Element Discussion facility is a fully featured collaboration tool allowing modelers and model viewers and reviewers to communicate with each other directly inside the repository. Modelers using the full client or occasional viewers using WebEA can both post and reply to discussions and communicate and engage in chat. For more details see the Element Discussions help topic.
Pan and Zoom
The Pan and Zoom facility is one of the tools that can be used to navigate around a large diagram. Often the resolution of a diagram must be reduced to ensure it is wholly visible but by using the Pan and Zoom window you can leave the diagram at a readable resolution and pan around to areas of interest zooming in when necessary. For more details see the Pan and Zoom help topic.
Diagram Legends
The Diagram Legend facility is useful for manually or automatically changing the appearance of elements and connectors on a diagram. A legend can be added from the Common Toolbox and configured to codify the fill and line color and line thickness. This is a powerful way to add meaning and expression to a diagram and is particularly expressive when applied automatically based on element or connector properties. It can be used with a number of specialized diagrams such as roadmaps to create a powerful visualization.  For more details see the Diagram Legends help topic.
Document Generator
The Document Generator is a powerful facility in Enterprise Architect that allows a Database Engineer or other stakeholder to create high quality corporate or technical documentation directly from the model, suitable for internal or external audiences. For more details see the Documentation help topic or the more general topic on Model Publishing.

© 2000 - 2018  Sparx Systems Pty Ltd.  All rights Reserved.