MS Office Integration and SysML Requirements Editor in Enterprise Architect 16

Enterprise Architect 16, Build 1605 was used throughout the webinar.

A number of enhancements around Custom Documents in version 16 provided the ability to select and apply a template on initial document creation and then drag and drop content from the Browser where it is needed.

For more information on Enterprise Architect 16 or to download a copy of a free 30 day trial, please refer to the official product landing page: Enterprise Architect 16 landing page

This extension to Enterprise Architect enriches your documents and spreadsheets with tools for UML®, SysML, BPMN™, SysML and many other modeling notations.

Please take a look at the Sparx Systems website for more information: Model Integration for Microsoft® Office

You can use Document Fragments to report on specific sections, the fragments will allow you to setup filters based on type, stereotype, tagged values and much more.

For more information, please refer to the Enterprise Architect User Guide topic : Template Fragments

Yes. MDG Office integration is supported in Enterprise Architect 15. Some of the new features related to Custom Documentation that were showcased in the webinar are only available in Enterprise Architect 16.

The MDG Office Integration is included as part of the Enterprise Architect Ultimate edition, or can be bought as a separate add-in for all other editions.

The RESTful API based Pro Cloud Server allows integration with various other source systems, and the data from external systems can be updated in the EA Repository, as well as Items from the Enterprise Architect repository sent to other systems too (based on configuration).

Yes, that is correct. The importer will look for existing items in the model to create a connector.

The connector will not be created and the log will indicate connector creation failed. This is not like XML import where it keeps a reference to connected items and restores them when the item is made available. This is a simple Name / Alias based lookup.

Yes. MDG Office Integration is supported in the 64 bit version of Enterprise Architect 16. The Office Integration plug-in is available to support all combinations (64 bit windows - 32 bit office, 32 bit Enterprise Architect / 64 bit Windows, 64 bit Office, 64 bit Enterprise Architect). There are specific installers for each of these options.

For more information, please refer to the Enterprise Architect User Guide topic: Migrating from 32 bit to 64 bit

The first iteration of the SysML Requirements Editor is primarily to model requirements, however you can submit this as a feature request and we'll be able to consider support in future updates.

Currently it supports SysML requirements and default attributes only. Based on feedback and comments we can support extended types in the future.

If you need the spreadsheet and profile, please email support@prolaborate.com and we will be able to share the template.

The MDG Office Integration can be used to import Jira issues. Staff have used the Excel importer to import external data sources.

Yes. You can import into specific packages, you can check the MDG Office help file and accompanying examples to see how.

Yes. The webinar demonstration showed how this can be achieved. You can do so by specifying the stereotype in the connector configuration.

Yes. This is possible, the SysML Requirements editor does this specifically for SysML requirements.

The connectors are created by looking for a Name matching or Alias Mapping (if you are using an Alias to Store IDs this can be useful).

If you are synchronising the contents in the model , the Prolaborate dashboard will be automatically updated based on the refreshed data.