This window lets you rename each element before it is created. Simply drag and drop this pattern onto the current diagram to create a new test step with expected and test results, as defined in this UML pattern. Your UML pattern is now available to use on your Enterprise Architect project it should be displayed within the list of UML Patterns. To import and have this pattern available from an EA project, open the Resources view (use the Project menu > Resources if this view is not displayed on your EA client), and right click onto UML patterns, choose "Import UML pattern", and browse to the UML pattern's XML file. The aim of an enterprise architecture diagram is to determine how an organization can effectively achieve its current and future objectives. It is used to analyze and document an organization and its business functions, along with the applications and systems on which they are implemented. Enable the "Merge" option if you need in some cases to merge a given activity (or another node) from your pattern with an existing activity from the target diagram (active diagram). An Enterprise Architecture (EA) diagram is used to display the structure and operations of an organization. Once our pattern is defined in a standard diagram, such as the UML activity diagram above, we can save it into an Enterprise Architect UML pattern : open the Diagram menu > Advanced > Save UML Pattern, and save into a new XML file (e.g. We can abstract these elements to be represented as re-usable steps, shown here : : pre-conditions / initial context, expected result, test result (OK/KO). In the following example, a test case has been represented by modelling each step to follow as a node within a UML activity diagram, e.g. Similarly to the use of design patterns (GoF), the aim is to define a set of elements that can be applied for modelling purposes. an activity description or a child composite diagram and its sub-elements, mustn't be re-used, hence they need to be deleted.Įnterprise Architect makes it possible to re-use a set of elements, their associations, any notes, and their layout on the diagram by creating UML patterns. We also need to ensure that any specific element or information, e.g. Then the newly created diagram needs to be displayed again so the paste as new command can be executed (Ctrl+Maj/Shift+V). Hence the diagram that contains those elements has got to be opened first, followed by a selection on the elements of interest, copied to the clipboard (Ctrl+C). Once the new diagram is created, the elements that need to be duplicated aren't available from this blank diagram. a pattern of modelling elements available from one or several diagrams within our model, we need to apply them several times onto a new diagram. Given a context where we have our set of elements i.e. The "copy and paste" feature on a selection of elements, including their associations and layout works ok, but there could be a more suitable way to go about this. As an Enterprise Architect user, you may have had the need to apply several times more or less the same set of elements on a given diagram, leading to numerous uses of copy and paste as new.