The MDG Integration for Microsoft Office allows teams to seamlessly leverage the information authored in Microsoft Word & Excel documents within Enterprise Architect.
Upgrade your existing static documents into rich traceable models. Automatically map document sections and tables to corresponding element properties and tagged values in Enterprise Architect. Utilize your model directly within a PowerPoint presentation to ensure that your presentation remains up-to-date with your latest model changes.
In this webinar you will learn how to:
Don't miss this opportunity to learn more about Enterprise Architect
|Word Document 1:||system-requirements-simple-table.docx|
|Word Document 2:||requirements-with-connectors.docx|
Enterprise Architect 12 (Build 1212 and above).
Enterprise Architect 12, build 1215.
MDG stands for Model Driven Generation.
No. The MDG Integration for Microsoft Office is not free. Please refer to the page below for pricing information:
Yes. Enterprise Architect 12 (Build 1212 or higher)
No. Enterprise Architect 12 (Build 1212 or higher)
For the Corporate Edition, The MDG Integration for Microsoft Office add-in must be purchased from Sparx Systems website.
Enterprise Architect 12 (Build 1212 or higher). Please use the link below to purchase the latest version of Enterprise Architect:
You need to install the "MDG Integration for Microsoft Office" using the link below:
The MDG Integration for Microsoft Office add-In can be downloaded from this page:
The page includes system requirements and installation instructions.
If the "MDG Integration for Microsoft Office" was installed on your machine then the add-in will be shown under Extensions | Microsoft Office.
The current release just supports single layer of parent-child association, however, for supporting multi-layer parent-child relationships, you can map multiple columns as connectors and each valid entry in the columns will be converted into connectors.
SysML requirements can be imported by mapping the data in Excel or Word to Requirements, setting the stereotype as ‘SysML1.3::requirement'. You can also map id and text tagged values (to the ID and Description in the Excel or Word document)
Yes. Custom tagged values can be imported. Refer to the‘Tagged Values' section in the Help.
All office products from Microsoft Office 2007 and above are currently supported.
Using Excel exporter, you can export elements and element details including tagged values and diagram only objects.
Yes. For 32 bit Office applications, install the MDG Integration for Microsoft Office installer from:
would enable Enterprise Architect Ribbon in the Office applications.
Office Integration supports Office 2007 and above. You can define profiles from Enterprise Architects' ‘Extensions' menu or from within the Word or Excel documents' ‘Enterprise Architect' ribbon.
This is not possible at the moment, however this could be lodged as a feature request.
The MDG Integration for office is available from the product page or registered download section. See the links below:
The MDG Integration for Microsoft Office will only be visible if you have the MDG Add-In installed.The first step is to download the extension from the Sparx Systems website:
Once the product is installed, the Microsoft Office option will appear under the Extensions Menu.
For office 64 bit, an additional installer to enable Ribbons for 64 bit Office setup is under development.
You can enable synchronization while importing from Word and Excel documents and re-import documents to update the contents in the Enterprise Architect model.
If the import is done with ‘Synchronization' enabled, the MDG Integration for Microsoft Office will update the changes , and create any new connectors if required ( however if any connector information is removed, it will not be deleted)
Converting documents to PDF is still possible, however the synchronization data may not be relevant as a PDF.
Yes, as long as the Word document is saved and available for the importer to read, it can import the document.
Enterprise Architect provides a comprehensive inbuilt documentation capability.
Working with MS Word, by inserting sections of model into document can be achieved by referring to the following link.The following webinar outlines document generation features in Enterprise Architect:
Yes, you have to map the headers as the respective Enterprise Architect Element and its associated metadata as its properties (either delimited values or inline tables). Refer to the BRD Document example from sample documents.
Visio integration allows users to import Visio diagrams into Enterprise Architect. Key diagrams such as BPMN and UML are converted to respective stereotypes in Enterprise Architect. The functionality is the same as the Visio Importer that was available previously, with some minor enhancements to improve mapping of stereotypes and properties.
SharePoint integration may be considered in a future release. However we cannot advise an indicative timeframe now.
The MDG Integration for Microsoft Office add-in has not been tested on a Mac
Yes, support for stereotypes during connector import is under development and will be available in upcoming builds.
Not supported at the moment, but a feature request or suggestion would be helpful.