EA Model Health Check

An EA model health check usually takes the form of a two-day engagement that will allow us to gather an understanding of the current state of your modelling activities and your intended future use of the tool.

Health Check; Day 1

Enterprise Architect Health CheckYour model health check will have the DT team join you for a fact-finding workshop to gather the following information:

  • What version(s) of Enterprise Architect is in use
  • The number of users currently active with Enterprise Architect
  • What model repositories have been created, their content and structure
  • The current use of Enterprise Architect
  • Type, Location and access method for these repositories
  • Modelling notation(s) in use
  • The customisations (if any) to Enterprise Architect (scripts, extensions and meta-model definitions (MDGs) that have been developed and are in use
  • Method (if any) in use for versioning or baselining
  • Reports (if any) that are produced by Enterprise Architect from the model repository(ies)
  • Use (if any) of common modelling elements located in a model library
  • Conduct an in-depth analysis of how traceability is used including but not limited to EA Relationship Matrix profiles

With this information gathered, the DT team will then try to gather an understanding of where you want to be with EA in the future:

  • The future use of Enterprise Architect
  • The number of users that will be using Enterprise Architect
  • The role of these users, that is, will users be:
    • Modellers
    • Project Managers
    • Reviewers
  • Number of and location of future model repositories
  • Integrations required with other tools (for example JIRA)
  • Meta-models that may be required
  • Automation scripts and / or extensions that may be required
Health Check; Day 2

Based on the information gathered from your team during the workshop the Dunstan Thomas will then prepare a roadmap report containing the following:

  • The current use of Enterprise Architect within your organisation
  • A critique of the structure and content of the current model repository(ies) and recommendations for improvement
  • The desired future use of Enterprise Architect
  • Roadmap of how to proceed from the current use of Enterprise Architect to the future use of Enterprise Architect
Scroll to Top