Book a Demo

Author Topic: Sparx EA and TOGAF  (Read 2706 times)

EPI

  • EA Novice
  • *
  • Posts: 1
  • Karma: +0/-0
    • View Profile
Sparx EA and TOGAF
« on: March 11, 2010, 04:36:13 am »
We are starting to standardize on the TOGAF architecture content metamodel.   So far we are finding pretty good coverage of the TOGAF metamodel in Sparx EA TOGAF add-in.  The effort has led to a couple of early questions...

In general:
We would like to use TOGAF to structure our Enterprise Architecture metamodel.     Is it possible of us to copy the TOGAF profile provided by Sparx then, tailor (as TOGAF suggests) for our specific requirements.   We would like to force and control the data in our meta model, but need to customize the generic Sparx provided TOGAF content (tag values, sterotypes etc.).
[Reference number for this enquiry is 10034946]

Specific example...
Some of the TOGAF toolbox items have different sterotypes but are associated the same graphic.  E.g. Logical Application Components and Logical Data Components are different toolbox items and are unique stereotypes but use the same uml graphic (component).      As a workaround we are displaying the stereotypes on the diagrams, but this clutters the diagrams making them less readable.
?:   Is there a way we can associate different graphics to the toobox items in the TOGAF Namespace?
Response from Sparx support: No workarounds, sorry. I have logged this as a feature request and if it's approved it'll be added to a future release of EA.
Anyone else using SparxEA for a TOGAF-centric model drive architecture used primarily for IT architecture planning and governance?

Thanks in advance!

EPI

Thelonius

  • EA User
  • **
  • Posts: 274
  • Karma: +6/-0
  • I think. Therefore I get paid.
    • View Profile
Re: Sparx EA and TOGAF
« Reply #1 on: March 29, 2010, 03:37:19 pm »
Hi EPI

A (late) answer to your first query: yes - there are several people here in Australia using the Sparx TOGAF add-in for Enterprise Architecture.

I believe there are others out there doing the same, but difficult to know how many and where.

A different graphic would be useful - but I've been using the stereotype and have gotten used to seeing it on my diagrams.

Good luck, though.

Thelonius