Event 5: Practical experiences with Enterprise Architecture tools

Dear,

We are proud to present our fifth Architecture café which will be about Practical Experiences with Enterprise Architecture Tools.

Date: 2009, June 23d from 18h to 21h
(with networking event after the presentation)

Place: AE – Interleuvenlaan 27b – Heverlee
(Several GPS systems tend to show you the wrong way so do check the plan here.)

Agenda

  • 18h: Interactive session by Ingrid Evers and Marc Vander Bracht “Requirements for Enterprise Architecture Tools”
  • 19h: Demonstration of three widely used tools – with pros and cons per tool. Demo by neutral users (not vendors)
  • 20h30: Networking with food & beverage by AE

Tools

  • MEGA: by Steven Laurent/Geert Lathouwers
  • ARIS: by Philip Van Langenhove
  • Enterprise Architect: by Joris Van denstorme

In March 2010, there is an event where several tool vendors will present their solution.

The result of this Architecture Café is available for subscribers.

  • Contact us if you are a tool vendor and you don’t want to miss this event.
  • Should you have any specific questions regarding tool requirements or experiences, do send them to us.

Best regards,

The Belgian Chapter of a|EA

2 thoughts on “Event 5: Practical experiences with Enterprise Architecture tools

  1. Pingback: BAEA
  2. The response to the workshop was enormous. Here is a quick summary of the main requirements for Enterprise Architecture tools (members will be able to download a full overview at the protected section):

    • traceability: being able to drill-down, do an impact analysis, have business models connected to IT models and integrated versioning is key
    • repository: this is what ultimately makes the difference with drawing tools. Having an integrated CMS is a must
    • support for different perspectives: if it is truly enterprise architecture, multiple views are needed: business and IT, managers as well as developers, architects and product owners need to find what they are looking for
    • completeness: the tool needs to be able to document a wide range of models and related information, from strategy maps, business processes to UMl models and component design models. This includes the capability to develop your own models, and to attach text and other related info to it.
    • open tool: it should be easy to extract info out of the tool, so being able to develop custom reports in different formats (word, powerpoint, visio, web) is key. Also it should comply to standards and frameworks and be able to export and import easily to other tools.
    • non-functional requirements: the main non-functional requirement is usability, because non-specialists need to work with it.

Leave a Reply

Your email address will not be published. Required fields are marked *