Enterprise Architect version 13.5

download
purchase

enzh-CNcsnlfrdehiiditkoplptruskessv

My Profile

Social Media Channels

facebook google plus twitter youtube linkedin

DT_Sam

DT_Sam

Sam Nice

Dunstan Thomas Consulting
Monday, 30 October 2017 06:00

HTML Report 2, Electric Boogaloo

HTML Report 2, Electric Boogaloo

As a sequel to my previous article on how to edit the CSS generated by Enterprise Architect to personalise your generated HTML report I was prompted by Guillaume to create this follow up as he gave me an idea on how to make these changes prior to generation. As we have already identified the changes that we need to make in the previous article we can actually create our own customised version of the CSS EA would use and specify that this is then used as we create our HTML report.


So how do we do this?

Keeping in mind the list of changes that we need to make:

  1. Change the attributes for .IndexHeader so that the logo fits within the header of the report.
  2. Change the attributes for .IndexBody to cater for the changes that we have made to the header.
  3. Change the attributes for #contentIFrame so that the content section of the report fills the correct amount of the screen.
  4. Change the attributes of #tocIFrame so the table of content is displayed correctly.

With these changes in mind we are ready to get to work on defining our template. To do this you will need to fire up EA. At the bottom of your project browser you will see a tab labelled Resources, click this…

HTML Report 2, Electric Boogaloo

Having clicked this your view will change to…

HTML Report 2, Electric Boogaloo

You will then need to click into the section for Document Generation…

HTML Report 2, Electric Boogaloo

Next, right click Web Style Templates and choose Create HTML Template. This will bring up the following dialog…

HTML Report 2, Electric Boogaloo

Enter a name for your new template and a new window will open…

HTML Report 2, Electric Boogaloo

You can select any of the options listed in the left hand pane for editing by simply clicking on them. As the changes we are looking to make are relatively simple the only option that we need to concern ourselves with is CSS – Main. Click this option and you will see the following…

HTML Report 2, Electric Boogaloo

You will then see the CSS display itself in the right hand pane, navigate to the areas of interest by pressing ctrl+f and entering the headings outlined earlier. Clicking on the find next button will take you to these areas in the CSS and you can make the necessary changes. Once you have made the changes click save and then click close. With these actions complete you are now ready to generate a new HTML report that will automatically use your custom CSS.

As before right click on your project in the project browser and choose HTML Report…

HTML Report 2, Electric Boogaloo

Clicking this will display the familiar dialog…

HTML Report 2, Electric Boogaloo

Under the Style option you will now be able to have a drop down menu that will list the names of any custom templates that you have created. For this example, I have changed the style to be the CUSTOM template created earlier in this article, this means that when we generate our report EA will now use our predefined custom CSS rather than the standard set. We also need to specify our logo as before, then click Generate.

The result is that our HTML report has been generated with no changes to be made and that we can re-use our template every time that we need to create this kind of report…

HTML Report 2, Electric Boogaloo

Editing an HTML report generated from Enterprise Architect using CSS

Introduction

This article will walk you through the process of making a couple of simple tweaks to your HTML Report generated from Sparx Systems Enterprise Architect.


So what's the challenge here?

If you have ever needed to create a quick and simple report to walk a colleague or stakeholder through certain aspects of your model, then by far the quickest and easiest route is to generate an HTML Report from EA.

This will create an HTML version of your project locally that can be navigated & drilled down into (but not updated etc). When creating this report, you have the option to include your own logo as a way of adding a little bit of an extra visual engagement to your publication.

The challenge that you can, and will likely, run into is that there is a set size for the logo that EA does not tell you about and you will not see the effect of until you view the report and see that your logo is cut off by content.


How do I fix this?

To start you will need to generate an HTML report from your model. If you are not sure of how to do this simply right click the root node of your model in EA and choose “HTML Report” from the menu…

Editing an HTML report generated from Enterprise Architect using CSS

When you click this option you will be presented with the following dialog…

Editing an HTML report generated from Enterprise Architect using CSS

In this dialog check all the options that you want to include in your report and specify your output destination folder and your logo image. When ready, click “Generate” and you will have a progress bar pop up momentarily while EA generates your report.

When this process has finished you can either click “View” or navigate to your Output folder & open the file “Index.htm” (there will be other files & folders generated as well but for now this all you will need).

When opened you will see something like this….

Editing an HTML report generated from Enterprise Architect using CSS

As you can see, the logo is too big for the report and there is no way to address this issue inside of EA.

So what do we do?


The Solution!

The first thing we do is to open up the HTML report using Chrome. This itself posed its own challenge initially as out of the box Chrome does not really support file based URLs, but there is a work around for this (thanks to Phil Chudley for showing me this).

Firstly, find your shortcut for Chrome, right click it and choose “Properties”. When the Properties window appears locate the section labelled “Target” and add the following to the end of the information there:

--allow-file-access-from-files

Make sure that you include a space between …chrome.exe” and the string shown above for this to work.

Editing an HTML report generated from Enterprise Architect using CSS

We now need to make some changes to the HTML report.

Earlier I mentioned that there are several files generated at your output destination when you create this HTML report. One of those folders is titled CSS and contains two files, you will need to open the “ea.css”, personally I use Notepad for this but there are a host of tools you could use.

With your CSS file open and with Chrome displaying your report it’s time to start editing.

Hover your cursor over your logo, right click and choose the “Inspect” tool…

Editing an HTML report generated from Enterprise Architect using CSS

This will open up a new Chrome window displaying the developer tools…

Editing an HTML report generated from Enterprise Architect using CSS

The sections that we will need to pay attention to are:

  • IndexHeader; this will be apparent immediately if you choose to inspect the logo
  • IndexBody; you will see this below IndexHeader but you will also need to expand this section clicking the triangular icon to the left of it to expose the other areas we need:
    • tocIFrame; this is the section of the page containing the model tree in your report
    • contentIFrame; this is the main section of your report that displays your information

.IndexHeader

Editing an HTML report generated from Enterprise Architect using CSS

This is the CSS controlling the display of this section of the report. The important factor here is the height property. As you can see, it is by default only 60 pixels tall and in our example the logo is larger than this.

To adjust this click into the area where it displays “60px”. You can overwrite this with your desired figure or you can adjust it your logo by using the up arrow to increase the height one pixel at a time. In our example I changed mine to 91px.

With your ea.css file open you will need to find .IndexHeader in there and adjust the height to your new value. Save but don’t close your ea.css file.

You will, for now, still see something similar to this…

Editing an HTML report generated from Enterprise Architect using CSS

What we now need to do is make the body of our report work with the changes that we have made to the header.

To do this we need to make some changes to the section of the CSS for .IndexBody

.IndexBody

Using the developer tools window you now need to pay attention to the CSS for this section…



The change we need to make here is to the position attribute from position: absolute; to position: inherit;

You will see that this changes the position of the body of the report allowing the header section to be fully displayed along with our logo...

Editing an HTML report generated from Enterprise Architect using CSS

Make sure to adjust this section in your ea.css file & save.

You will notice that this has created a new issue in that the frame housing our table of contents has now shrunk. You can still expand and use this section as you normally would however it quickly results in excessive scrolling. This is something that we don’t want and so we will need to make a couple more changes to fix this.

#contentIFrame

This is the frame that displays our content & in the developer tools it will look like this…

Editing an HTML report generated from Enterprise Architect using CSS

In the developer tools this section will appear grey and so cannot be edited there. Instead you will need to locate this section in the ea.css file and make the change there without previewing it.

The change that you will need to make is to the attribute height: 100%; to instead be height: -webkit-fill-available; as shown above. Then save your ea.css file. This will set the size for the main display frame.

Next we need to look at the frame for the table of contents.

#tocIFrame

To make our Iframe look correct we will need to make the same change as we have just made to the content frame…

Editing an HTML report generated from Enterprise Architect using CSS

Again the change that you will need to make is to the attribute height: 100%; to instead be height: -webkit-fill-available; as shown above.

Then save your ea.css file.

You have now completed the changes necessary to have your HTML report display properly and with your own logo. From now on you will see something akin to this upon opening…

Editing an HTML report generated from Enterprise Architect using CSS

Everything is now exactly where you would expect it to be and in a useable fashion.

There is something to bear in mind should you choose to use this method. If after following this method, you need to make changes to your model & regenerate the HTML report to the same output destination then your changes to the CSS will be overwritten as well.

To get around this, before you regenerate your HTML report simply rename the ea.css file to something else e.g. ea – NEW.css and then regenerate the report.

What you find now is that in the CSS folder in your output destination there will now be another file called ea.css and this is the one that the report will default to. Simply delete this file and rename the ea – NEW.css file back to ea.css having done this your updated report will open & use your modified CSS still.

Obviously there is a lot more styling you could apply by using the CSS, this is just a simple fix for a particularly common bugbear with the HTML Report.

You can find more content like this on our YouTube channel, Facebook and Twitter.

Enterprise Architect User Group

London 2017; 18th - 19th May

EA User Group - London 2017The London

2017 meeting of the Enterprise Architect User Group sees a shakeup to the agenda in the form of an additional day being added to the roster. In additional to the traditional presentation day of User Stories, How to's etc the extra day added to the event is taking the form of a training day.

The training day adds to the event a selection of six, three hour training sessions on a variety of subjects from BPMN to TOGAF and Model Curation.


Location

Code Node, 10 South Place, London, EC2M 7BT

Get Directions

EA User Group - London 2017

 

 

 

 

 

 

 

 

 


Agenda; Thursday 18th May

EA User Group - London 2017

You can find information on these training sessions over at the EA User Group website.


Agenda; Friday 19th May

EA User Group - London 2017

You can find a synopsis for each of these presentations over on the EA User Group website.


How to buy your tickets...

Tickets for the event are available directly from the EA User Group website and are priced as follows:

  • Full two day event ticket; £550.00 +Vat
  • Friday only ticket; £75.00 +Vat

EA User Group - London 2017

Wednesday, 11 January 2017 09:51

London User Group; Call for Speakers

 
 

If you are a user of Sparx Systems’ Enterprise Architect, we’re inviting you to share your user stories with the EA community at the next User Group event in central London on May 19th 2017.

 

We are interested in just about everything you do with Enterprise Architect, from the organisation of your model to enhancements you have made using MDG or the automation API, or even just a project with which you are especially happy. That said, we are not just after the sunshine stories and would be interested in hearing about any experiences learned the hard way.

Presentations of an obvious or purely commercial nature will not be accepted. View our speakers style guide for tips.
 JOIN US AT Code Node, London
This year's London event is returning to the fantastic Skills Matter venue, Code Node. But this time around we're adding a twist to the proceedings. London 2017 will see an additional day added to the event roster which will be on the 18th May before the usual day of presentations and networking on the 19th. This extra day of content will be a training day with no less than six half day training sessions running! Full details on the training day will be published on the EA User Group website, along with ticketing information very soon.
 
 
Friday, 02 December 2016 12:03

How to use the Relationship Matrix

Dunstan Thomas ConsultingAbove all else one of the most recurring questions Dunstan Thomas Consulting has encountered from clients over the years is "How do we use the Relationship Matrix?"

With that in mind we've got a short clip on how you can start effectively putting the Relationship Matrix into use for yourself...

https://www.youtube.com/watch?v=miiWN5PBuk0&t=30s

 

Sam Nice
Online Training, Marketing & Product Specialist
Dunstan Thomas Consulting
@DTUML 

 

Friday, 02 December 2016 11:58

What's new with ArchiMate 3.0 & EA v.13?

ArchiMate 3.0

by Phil Chudley, Principal Consultant at Dunstan Thomas Consulting

  The Open Group released the official specification of ArchiMate 3.0 in June 2016, and this new specification is supported in Enterprise Architect version 13. This article summarises the new features and changes within ArchiMate 3.0 and provides an example of how to migrate an existing ArchiMate 2.0 model to ArchiMate 3.0 model using Enterprise Architect v.13.

Summary of Changes

The following is a summary of the changes made within ArchiMate 3.0:

  • Motivation Extension;
    • New element for modelling Outcomes.
    • New set of Strategy Elements, Resource, Capability, Course of Action.
  • Business Layer;
    • Representation of the Contract element modified so as to be different from the Business Object Element.
    • Location element removed (although Enterprise Architect has re-located this element to the Technology Layer – Physical Extension).
  • Application Layer;
    • Two new elements added, Application Process and Application Event
  • Technology layer;
    • Elements called Infrastructure in ArchiMate 2.0 are now called Technology in ArchiMate 3.0.
    • Four new elements added, Technology Process, Technology Interaction, Technology Event and Technology Collaboration.
    • New set of Physical Elements, Equipment, Facility, Distribution Network and Material. These elements are known as the Physical Extension.
  • Implementation and Migration Extension;
    • One new element added, Implementation Event.
  • Relationships;
    • Representation of Assignment modified to have a directional arrow.
    • Bi-directional Access relationship added.
    • Plus (positive) and Minus (negative) symbols added to Influence Relationship.
    • New relationship, Serving.

Detail of Changes

The following tables provided an example of the changes for each of the sections listed in the Summary of Changes above.

Motivation Extension

 Element Definition  Notation 
 Outcome An end result that has been achieved. motivation extension - outcome - ArchiMate 3.0
Resource An asset owned or controlled by an individual or organisation.  motivation extension - resource - ArchiMate 3.0
Capability  An ability that an active structure element, such as an organisation, person, or system possesses. motivation extension - capability - ArchiMate 3.0
Course of Action  An approach or plan for configuring some capabilities and resources of the enterprise, undertaken to achieve a goal. motivation extension - course of action - ArchiMate 3.0

Business Layer

 Element Definition  Notation 
 Contract A formal or informal specification of an agreement between a provided and consumer that specifies the rights and obligations associated with a product. business layer - contract - ArchiMate 3.0

Application Layer

 Element Definition  Notation 
Application Process A sequence of application behaviours that achieves a specific outcome. application layer - application process - ArchiMate 3.0
Application Event An application behaviour element that denotes a state change. application layer - application event - ArchiMate 3.0

Technology Layer

 Element Definition  Notation 
Technology Collaboration An aggregate of two or more nodes that work together to perform collective technology behaviour. technology layer - technology collaboration - ArchiMate 3.0
Technology Process A sequence of technology behaviours that achieves a specific outcome. technology layer - technology process - ArchiMate 3.0
Technology Event A technology behaviour element that denotes a state of change. technology layer - technology event - ArchiMate 3.0
Technology Interaction A unit of collective technology behaviour performed by (a collaboration of) two or more nodes. technology layer - technology interaction - ArchiMate 3.0
Equipment One or more physical machines, tools, or instruments that can create, use, store, move, or transform materials. technology layer - equipment - ArchiMate 3.0
Facility A physical structure or environment.  technology layer - facility - ArchiMate 3.0
Distribution Network A physical network used to transport materials or energy. technology layer - distribution network - ArchiMate 3.0
Material Tangible physical matter or physical elements. technology layer - material - ArchiMate 3.0

Implementation & Migration Extension

 Element Definition  Notation 
 Implementation Event A behaviour element that denotes a change of state related to an implementation or migration. implementation and migration extension - implementation event - ArchiMate 3.0

Relationships

 Element Definition  Notation 
Assignment Expresses the allocation of responsibility, performance of behaviour, or execution. relationships - assignment - ArchiMate 3.0
Serving Models that an element provides its functionality to another element. relationships - serving - ArchiMate 3.0
Access Models the ability of behaviour and active structure elements to observe or act upon passive structure elements. relationships - access - ArchiMate 3.0
Influence Models that an element affects the implementation or achievement of some motivation element. relationships - influence - ArchiMate 3.0

Implications to existing ArchiMate models

If an organisation has modelled their Enterprise Architecture using Enterprise Architect and ArchiMate 2, and are now using Version 13 of Enterprise Architect, they have two courses of action:

  1. Continue to model using ArchiMate 2.0. In this case no action is required either for Enterprise Architect or the model repository. An organisation would continue to model using ArchiMate 2.0 if they do not wish to make use of any of the new features in ArchiMate 3.0.
  2. Migrate their existing ArchiMate 2.0 model to ArchiMate 3.0, and then continue to model using ArchiMate 3.0. An organisation would continue to model using ArchiMate 2.0 if they wish to make use of any of the new features in ArchiMate 3.0.

My own personal opinion is that an organisation should consider moving to Enterprise Architect version 13 (mainly due its new feature of “Time Aware Modelling”) and ArchiMate 3.0. One of the main reasons, is due to inherent ambiguity (due to the lack of direction indication) in the assigns relationship in ArchiMate 2.0, which has been eliminated in ArchiMate 3.0 by making the assigns relationship directional.

Migrating an ArchiMate 2.0 model to ArchiMate 3.0

Enterprise Architect version 13 provides a migration script for this purpose. The following steps are used to perform the migration:

  1. Take a backup copy of the existing model repository.
  2. Using the Configure | Manage Technology ribbon, ensure that both ArchiMate 2.0 and ArchiMate 3.0 MDG technologies are enabled.
  3. Using the Code | Scripting ribbon, make the scripting window visible:
    Migrating ArchiMate 2.0 models to ArchiMate 3.0
  4. Select the topmost package (or view) that contains the model to migrate:
    Migrating ArchiMate 2.0 models to ArchiMate 3.0
  5. Select the script Migrate ArchiMate 2 to ArchiMate 3 in the scripting window.
  6. Right-click and select Run Script from the menu.
  7. The progress of the migration, together with any errors / warnings will be displayed in the system output window.
  8. Review the diagrams (you may have to tidy some of the relationships).
  9. Turn off the MDG ArchiMate 2.0 using the Configure | Manage Technology ribbon.
NOTE: It appears that composition relationships are NOT HIDDEN, when using nested structures in ArchiMate 3.0. I suspect this is an Enterprise Architect version 13 issue. This is likely to be fixed and should not deter migration, as these relationships can always be hidden using the Visible Relations function in Enterprise Architect. (Layout | Manage ribbon and select Show and Hide Relationships… from the menu). composition relationships - ArchiMate 3.0

Phil Chudley
Principal Consultant
Dunstan Thomas Consulting
@SparxEAGuru

You'll find lots of useful Enterprise Architect videos on our YouTube Channel.

Wednesday, 24 August 2016 11:21

New EA workshops from Dunstan Thomas

NEW: Sparx Systems Enterprise Architect Workshops from Dunstan Thomas Consulting

logoHex_cl

As an alternative to our traditional classroom style training Dunstan Thomas Consulting now offer a series of Sparx Systems Enterprise Architect workshops.

These workshops provide all the fundamental practical skills that are necessary in order for you to use Enterprise Architect efficiently and effectively. The emphasis is on the practical rather than the theoretical and we will work with you so that exercises can be tailored to meet your specific modelling requirements.

 


Available Workshops

Sparx Systems Authorised Training Partner - ArcGIS Geodatabase Modelling in EAOur current offering of Sparx Systems Enterprise Architect Workshops include:


All details are available on our website or call our sales team on +44 (0) 23 9282 2254.

Re-Using Elements

In this latest instalment in the series Phil Chudley will be looking at how to re-use Elements from your repository in Enterprise Architect.

https://www.youtube.com/watch?v=_DIs2ROV8fM 

As always all of our videos are available right now via our YouTube channel ... and don't forget to subscribe!

Managing Connectors

In this latest instalment in the series Phil Chudley will be looking at managing your connectors in Enterprise Architect.

https://www.youtube.com/watch?v=UhTsvUDrgDU

As always all of our videos are available right now via our YouTube channel ... and don't forget to subscribe!

Thursday, 14 April 2016 13:21

EA User Group; London - Agenda Confirmed

The EA User Group returns to London this May

On the 17th May the annual London meeting of the Enterprise Architect User Group will be happening at Skillsmatter's Code Node venue.

The final agenda has been confirmed today and we've got a great day lined up...

Agenda

Tickets

Tickets are available from the EA User Group website at the price of £65.00 +Vat per person.

Page 1 of 5