Information model as an asset

By Johan Wreto CEO of Ferrologic Enterprise Design

In this seminar a holistic approach to information modeling is presented using Enterprise Architect. Information models are often stable and can be used for many purposes such as managing information security classification, definitions of the business meaning, mapping legacy data, seeding models using transformation and cloning to support agile development just to name a few.

Session Recording


Information model as an asset (EAPX)

Questions and Answers

You can have different strategies here. One is just to seed the code to include the documentation which will help and kickstart. You can go all the way and reverse/syncronize the code with the model which I believe is the way EA is developed. I can see some in between also. When working with agile teams we should not stop them, but we can harvest and get information back to the models making them better.
Yes, use ArchiMate BO:s make them composite and detail them in a UML diagram with attributes.
No, harvesting can't be done automatic. We will get a lot of implementation details in the information and it should not be there. Harvesting is the delicious work an information architect does to sort out things that add value to the information model.
I trust LEAN and they always start of manually and learn how to do things before they automate and create tools. This is also my approach so first I would follow the traceability to see which elements have cloned the information model element. Then I would go thru what changes were made and if I'm not to lazy I would find it in the project browser, drag the attribute of interest onto my information element (copy) and then make sure the documentation suits my standard.

Speaker Bio


Johan Wreto

CEO of Ferrologic Enterprise Design