Book a Demo

Author Topic: New Diagram to navigate model  (Read 2714 times)

TonyD

  • EA Novice
  • *
  • Posts: 10
  • Karma: +0/-0
  • I love YaBB 1G - SP1!
    • View Profile
New Diagram to navigate model
« on: August 19, 2013, 12:43:26 pm »
Hi
I have several views that I would like to combine in a single diagram so that developers can easily navigate the model.  I plan on providing them the html output.  I am having issues determining the best way to provide cut-down views of the system relevant to the current item of work.  

For example, the EA Example project contains Orders.  If we were implementing the Orders functionality and screens, I would like to provide my developers with easy access to views containing the Orders related Use Cases, Class Model, Web Modelling View (used to show Navigation), and likely some form of View for Test Cases.

I have the equivalent of Orders packages within each of the above Views, with Orders related Diagrams.  What is the best way to provide a single page to access all of the above mentioned Orders Views?

Regards,
Tony

Helmut Ortmann

  • EA User
  • **
  • Posts: 970
  • Karma: +42/-1
    • View Profile
Re: New Diagram to navigate model
« Reply #1 on: August 19, 2013, 03:43:10 pm »
Hi Tony,

I would use a class diagram and drag the wanted diagrams to see on that diagram as hyperlink.

The SPARX Example model (help, open example models) shows a lot of examples.

Helmut
Coaching, Training, Workshop (Addins: hoTools, Search&Replace, LineStyle)

Ian Mitchell

  • EA User
  • **
  • Posts: 507
  • Karma: +22/-4
  • The eaDocX and Model Expert guy
    • View Profile
Re: New Diagram to navigate model
« Reply #2 on: August 19, 2013, 06:23:08 pm »
The choice of exactly which EA Diagram type to use is largely irrelevant: that just controls which toolbox appears. Just pick a diagram type, drop the relevant 'Order' stuff onto it, and EA will connect-up those elements which already have connections.
The EAExample models are great for looking at individual model styles: Process, Class, UI, Use Case etc, but they have almost no 'vertical' links. So you can't rely on them to tell you how to, for example, link a BPMN process event to a Data Warehouse 'Fact', or a Class to a UI Screen.
These are the bits you are going to have to invent for yourself, but the good news is that almost regardless of how you decide to do it, EA will be able to support you!
Ian Mitchell, Designer, eaDocX


www.eaDocX.com
www.theartfulmodeller.com