Data Landscape Diagram

[Knightrider]

Hi All

I am new to Sparx EA and am looking at using the tool to implement a Data Landscape Diagram. The diagram will document each application in the enterprise and also document the type of information flowing between the applications. I am using the Ultimate version 12.1.1228.

Firstly a question:
Can I embed diagrams within each object/class. For example, I click on an application box in my Data Landscape Diagram and it pops up another diagram which shows the application in a more detailed diagram showing the activities being performed on the data. If so how is this done?

Secondly need some advice:
Is the best way of doing a Data Landscape diagram by having an application class which has all the attributes I want to capture for any application. The Data Landscape Diagram would then have an object application representing each application and have the attributes filled by me when instantiated. I could then also have a Data Class for each type of data I have. The information flow between any two applications could have all the applicable Data classes attached to show what type of information is flowing between any two applications.

Any guidance form the community will be greatly appreciated.

[qwerty]

Regarding your first question: yes. You can make and element composite. From the context menu choose New Child Diagram/*Composite*. There you can either create a new one to be placed inside the element or you can choose an existing one. The elements then will show a lying 8 to indicate that you can dbl-click them and a new diagram will open.

The second question is far too broad to give a meaningful answer. But using composite elements like above is a good start.

q.

[Geert Bellekens]

Firstly a question:
Can I embed diagrams within each object/class. For example, I click on an application box in my Data Landscape Diagram and it pops up another diagram which shows the application in a more detailed diagram showing the activities being performed on the data. If so how is this done?

Right click on the element on the diagram and choose New Child Diagram|Select Composite diagram to link this element to an existing diagram.
Doubleclicking on this element will now open the selected diagram.

Geert

[Glassboy]

Is the best way of doing a Data Landscape diagram by having an application class which has all the attributes I want to capture for any application. The Data Landscape Diagram would then have an object application representing each application and have the attributes filled by me when instantiated. I could then also have a Data Class for each type of data I have. The information flow between any two applications could have all the applicable Data classes attached to show what type of information is flowing between any two applications.

I use a component diagram.  Each system is a component (which may have sub-components).  I create an InformationItem that represents the information concepts flowing at a macro level (say Customer or Correspondence Preferences), which I then convey on Information Flows between the components.  If I know what the connect is between the systems I join them with an Assembly.

You can then document the logical data model for each application, and the data that is being replicated between systems using class diagrams.  I wouldn't convey the data class on the information flow as this would make keeping the diagram up to date very very fiddly.

[Knightrider]

Thanks all very much for you valuable comments.

What do others feel about Glassboy's cool idea about using Component Diagrams for showing how about 100 applications interact with each other in terms of the data flows and documenting application details.

[Paolo F Cantoni]

Thanks all very much for you valuable comments.

What do others feel about Glassboy's cool idea about using Component Diagrams for showing how about 100 applications interact with each other in terms of the data flows and documenting application details.

If you put large numbers of objects with lots of interrelationships on a single diagram then chose the Circle view, you get what I call a "Death Star" diagram.

The first time I did this, and showed it to "Support", they went white faced and said "S**T! Look how complicated it is!".  I showed the same diagram to "Marketing" and they said: "Cool! Look how complicated it is!"

It all seems to be a matter of perspective...  (and perhaps understanding)

HTH,
Paolo

[Sunshine]

What do others feel about Glassboy's cool idea about using Component Diagrams for showing how about 100 applications interact with each other in terms of the data flows and documenting application details.

Case of great minds think alike. I do this using Archimate Application Components and Information flows. I call this an Application Information Flow Diagram cos it shows the information flow between applications.
 

[Glassboy]

If you put large numbers of objects with lots of interrelationships on a single diagram then chose the Circle view, you get what I call a "Death Star" diagram.

It's not frightening if you can actually print it. :-)

[Paolo F Cantoni]

If you put large numbers of objects with lots of interrelationships on a single diagram then chose the Circle view, you get what I call a "Death Star" diagram.

It's not frightening if you can actually print it. :-)

I had access to an A1 plotter so it looked AWESOME!

[Knightrider]

The context is really making sure all our data and its flow is documented in one place so its easier to apply governance and improve the quality. By having a single diagram, the idea is to be able to easily home in on the flow of a particular type of data and see where its mastered and which applications down stream are its touch points.

[Glassboy]

The context is really making sure all our data and its flow is documented in one place so its easier to apply governance and improve the quality. By having a single diagram, the idea is to be able to easily home in on the flow of a particular type of data and see where its mastered and which applications down stream are its touch points.

I can't do that on any paper size that I can print, but what I can do is show slices of it, starting with the core systems.

What I'm struggling with now is whether I restrict each Information flow to only one Information Item so I can slice through and show how a concept moves across domains.  Which is helpful for bludgeoning people into seeing their "bounded context" is a big ball of mud.

[Eve]

If you put large numbers of objects with lots of interrelationships on a single diagram then chose the Circle view, you get what I call a "Death Star" diagram.

The first time I did this, and showed it to "Support", they went white faced and said "S**T! Look how complicated it is!".  I showed the same diagram to "Marketing" and they said: "Cool! Look how complicated it is!"

It all seems to be a matter of perspective...  (and perhaps understanding)

I see a new variant of the glass is half empty/full. Personally, I'd be likely to describe it as useless/unreadable/pointless. In terms of a diagram being there to convey information (to a human) the only purpose I can see in a model for such a diagram is "This is why I'm showing you many diagrams to show an overview and details of small sections."

Having said that, I do have a diagram around that is 100 classes, fully connected with dependencies in a circle. It does produce a beautiful Moiré-like effect, but it was only ever for testing purposes.

[Glassboy]

I see a new variant of the glass is half empty/full. Personally, I'd be likely to describe it as useless/unreadable/pointless. In terms of a diagram being there to convey information (to a human) the only purpose I can see in a model for such a diagram is "This is why I'm showing you many diagrams to show an overview and details of small sections."

Often what I do is more akin to forensic technical archaeology and the facts I need to display on my crime scene diagram can number in the 10s to the 1000s and the audience is people who use only PowerPoint and Outlook (and both badly).