Default Batman template: no project model displayed in general View

[yvanblanchard]

Hello,

I expected to get the display of diagrams (project models) of the existing Batman template, like this;

But I always have blank view in General View window:

Question:
Is it normal behavior (need to recreate diagrams by picking parts and items from tree) ? or is there something missing at my side ?

Since my own project models work (diagrams are well displayed when clicking on my project, when stopping and restarting the SysOn database), I expected same behavior for template example.

Thank you,
Yvan

[AxelRICHARD]

Hello,

No this is normal behavior.
You can use the "Add existing elements (recursive)" tool from the diagram background's palette to add all existing elements from your model to the diagram.

In the future, we probably update this template to propose a diagram with all elements already added to the diagram, but that is not a priority for the moment.

Regards,

[AxelRICHARD]

N.B : I'm converting this issue into a discussion. Feel free to open a bug if you find one.
Thank you!

[DarwinJS]

Not having diagram views automatically render is quite confusing compared to expectations created by existing tools.
I had to find and watch this video, just to figure out how to do this one activity on batman: https://www.youtube.com/watch?v=lUOH0S3T9Zo

Also having a very difficult time creating a basic use case diagram - can't find the person object/icon anywhere in the add item right click menu.

[AxelRICHARD]

Hello,

Thank you for your feedback.

The documentation of SysON is quite explicit about that: https://doc.mbse-syson.org/syson/v2025.4.0/user-manual/features/general-view.html.

Also having a very difficult time creating a basic use case diagram - can't find the person object/icon anywhere in the add item right click menu.

Are you talking about the Actor tool?
If so, yes this is not the easiest kind of Element to create. We do our best to provide an efficient tool, and will try to improve this.

Regards,

[DarwinJS]

Thanks @AxelRICHARD !

I mean the following feedback with the deepest desire to see your product succeed and I've seen the challenge with many developer led product motions.

It is super important to have Adoption Driven Development as a first class priority when building something in a domain where many well-solved alternatives exist - basically a "wheel problem".

A part of that is being sure that Out of Box Experiences meet the Defacto Reviewer Expectations created by the top alternatives.

In this case it feels like a Use Case diagram is going to be the first "blank slate" attempt to play with the product and that a desire to see how good visual modelling works in a free product would be another top of mind selection criteria (with defacto expectations created by current tools available)

If the above two "reviewer expectations" seems likely, then an Adoption Driven Development focus would encourage:

• Sample projects default to "no actions required to see visual representations"
• Use case diagrams and the Actor object are a primary sample
• Use case diagrams and the Actor object are very easy to find and use in case the first experience does not involve opening a sample.

While engineers of all types are tenacious - when I make things for them, I don't want to count on their tenacity - because it quickly fades in the face of many other options for the same job - for me and many others :)