Book a Demo

Author Topic: ArchiMate - Data views: "objects" and  f  (Read 14029 times)

Paolo F Cantoni

  • EA Guru
  • *****
  • Posts: 8626
  • Karma: +259/-129
  • Inconsistently correct systems DON'T EXIST!
    • View Profile
ArchiMate - Data views: "objects" and  f
« on: February 22, 2013, 04:50:27 pm »
As is probably known, ArchiMate appears to be a bit "light-on" for Data stuff...

However, one thing that IS bothering me is that it is suspiciously quiet on the ability to add structural features (attributes) to Business Objects, Data Objects and Artifacts.

I couldn't see anything in the ArchiMate spec that prohibited this, and I can certainly add them with EA - but EA resolutely refuses to allow me to make them visible! (see:  hiMate non-icon style rendering).

Can any ArchiMate gurus comment?

TIA,
Paolo
« Last Edit: February 22, 2013, 04:55:37 pm by PaoloFCantoni »
Inconsistently correct systems DON'T EXIST!
... Therefore, aim for consistency; in the expectation of achieving correctness....
-Semantica-
Helsinki Principle Rules!

rsipin

  • EA Novice
  • *
  • Posts: 9
  • Karma: +0/-0
    • View Profile
Re: ArchiMate - Data views: "objects" and  f
« Reply #1 on: February 26, 2013, 03:09:35 am »
This is a big one for us as well. We're using Archimate as our standard framework, but it gets difficult to make diagrams which convey everything that we need them to. We cannot turn on the various diagram compartment settings when dealing with Archimate elements in a diagram and I don't understand why this framework should behave different than any others.

Sunshine

  • EA Practitioner
  • ***
  • Posts: 1353
  • Karma: +121/-10
  • Its the results that count
    • View Profile
Re: ArchiMate - Data views: "objects" and  f
« Reply #2 on: February 26, 2013, 06:48:31 am »
I use Archimate and found the same problem. I work around it by thinking of Archimate being equivalent to the conceptual data model. I transform the Archimate Data Objects to plain old UML Classes which is my logical data model and add attributes to those elements. I then transform to a physical model to create database schema's.
Happy to help
:)