Book a Demo

Author Topic: Converting from one notation or view to another  (Read 3117 times)

lucchase

  • EA Novice
  • *
  • Posts: 3
  • Karma: +0/-0
    • View Profile
Converting from one notation or view to another
« on: January 16, 2019, 08:53:11 pm »
Using one model-view to complement and cross-check another....

If I create a DFD, can I re-use the processes from that on a new BPMN model-view?

And can I see the data entities created on the DFD as available entities for an ER Diagram and/or on a BPMN view? 

And vice versa... if I instead start with an ER Diagram can I select from those entities when starting to build a DFD or BPMN model.

If yes, can I then check which have not been re-used in any complementary view?


Geert Bellekens

  • EA Guru
  • *****
  • Posts: 13523
  • Karma: +574/-33
  • Make EA work for YOU!
    • View Profile
    • Enterprise Architect Consultant and Value Added Reseller
Re: Converting from one notation or view to another
« Reply #1 on: January 16, 2019, 09:31:47 pm »
You'll have to be very careful with that.
Each notation has it's own stereotypes and properties, and you cannot simply mix them.
Things such as quicklinks, and exports to other formats will not work well with mixed notation models.

What we usually do is use the «trace» relation to indicate that the e.g. process from one notation (BPMN) is related to the process in another notation (DFD)

Geert

DFD, is that still used? I thought that was more something from the eighties, like mainframes and knight rider ;D

lucchase

  • EA Novice
  • *
  • Posts: 3
  • Karma: +0/-0
    • View Profile
Re: Converting from one notation or view to another
« Reply #2 on: January 16, 2019, 10:33:12 pm »
Geert,
thanks for your reply. Ignoring DFD for a second.....In the case of BPMN cross-checked with an Entity Model, from what you said am I correct that EA does not automatically recognise that a BPMN data-store is an entity on an Entity Relation model, but I can use «Trace» to achieve that?

Yes DFD use is has been around a while (late 1970s). It is a specialisation of graph theory and has been used almost as long as Objert Oriented software design (early 1960s). The great thing about DFDs over BPMN is it only uses exactly four symbols only, so (in my experience) much more useful for communicating with a business client who wants to actually understand the model before confirming it is a good model of their business design.

Geert Bellekens

  • EA Guru
  • *****
  • Posts: 13523
  • Karma: +574/-33
  • Make EA work for YOU!
    • View Profile
    • Enterprise Architect Consultant and Value Added Reseller
Re: Converting from one notation or view to another
« Reply #3 on: January 16, 2019, 10:55:55 pm »
Geert,
thanks for your reply. Ignoring DFD for a second.....In the case of BPMN cross-checked with an Entity Model, from what you said am I correct that EA does not automatically recognise that a BPMN data-store is an entity on an Entity Relation model, but I can use «Trace» to achieve that?
For EA a BPMN data object or data store and an entity in an Entity model are different things;
If you link them with a trace you will be able to find the relation between the two things and use that in for example searches, exports, scripts, document generation etc..

But there is nothing special to the «trace» relation. You'll have to do the interpretation yourself.

Geert

lucchase

  • EA Novice
  • *
  • Posts: 3
  • Karma: +0/-0
    • View Profile
Re: Converting from one notation or view to another
« Reply #4 on: January 16, 2019, 11:15:02 pm »
OK, thanks. Was hoping for a kind central data-dictionary where for example one view would 'know' that the entities had already been discovered in another view, and would offer them to be re-used in the current view. Then expose which had not been utilised in more than one view.