I am a graphic artist and speaking from this perspective I can safely say that it is more than possible to completely alter backgrounds, change the shape of an individual’s hair, as well as the dimensions, angles and even the positions of one’s limbs using the correct digital tools. In fact, many professional retouching agencies have portfolios clearly demonstrating this.
However, since none of us know for sure if that the image on the left was in need the original image that was altered to become the work on the right, we can neither agree nor disagree with what Daily Mail is claiming. I just wanted to make the point that it is very possible to do the things the Daily Mail is talking about, so one cannot claim this is all a lie as much as one cannot claim this is the truth.

Nice write-up Maguffyn, i must add.

Why do my comments get discarded everytime?

You make an excellent point: the divide between the ‘enterprise’ architecture (Archimate) and the ’system’ design (UML) is not clear.

I have worked in a company that attempted to enforce this separation through the use of separate tools to model business activity and system details. You can guess how sucessful this approach was (Hint: It wasn’t)

So now, like you, I have a rule of thumb that I (internally) apply to determine if I will create the diagram in Archimate or UML. Unfortunately, this rule of thumb is like much of my data modelling- I do something one way or the other because it ‘feels right’ rather than having any hard and fast rule that I have decomposed a Process Model to the 3rd Level or I have broken the systems down to components, so now it should be a UML model.

And yes, I do find myself occasionally recreating objects in both Archimate and UML, but until we get a single tool that will support both seamlessly that is just the price we have to pay.

Ian

I’ve been using Archimate as modeling language for some time now, and I have found the same limitations and applicability as you.

There is, however, something else I had to make a somewhat arbitrary decision on: the cutover point between Archimate and UML.
This becomes most obvious when modeling all the way from the business view towards technical views. UML is clearly geared towards technical semantics but not so rich on business modeling, and vice versa for Archimate.
My current practice is to do business structure and behaviour all in Archimate, doing high level information entities in Archimate too, and information systems at a conceptual service level. From there, I recreate the IS services as UML compoments and do UML from there.

This is more pragmatic common sense than rule-of-thumb however. What’s your view?

Interesting comments, instead of chasing one team of female soccer players. You should chase both teams …..and the fans too…that should increase your odds..

Great Blog

_______________________________
Don’t pay for your electricity any longer…
Instead, the power company will pay YOU!