Unable to Create Customised SysML Block Definition Diagram Using v15

[wikitect]

This is a gotcha.

You can only produce custom SysML diagrams using view specifications.

On v 15 however there is only the SysML 1.5 heading in the new diagram dialog from which to create SysML diagrams. The SysML 1.5 heading doesn’t, however, list the custom technology SysML BDDs under the SysML1.5 > ‘BlockDefinition’ subheading - only Sparx’s own offerings (other SysML customisation such as Requirement Diagram, Activity Diagram do appear).

The net result is that it is impossible in v15 to produce a customised SysML BDD from a technology.

In v16 it is possible because there are additional technology headings and the BlockDefinition subheading does list the customised BDDs.

This bug has clearly been around for some time.

[Eve]

I'll give you the same answer here that you were given through the support email.

That's correct. That capability didn't exist in 15.2. The following is an extract from the release notes for 16.0 Build 1604.

New diagram dialog updated to better support view specifications:

• Profiles with view specifications extending diagrams from external technologies are now listed as their own page
• View specifications displayed for a diagram type are now filtered by perspective
• UML diagram types now only display UML views within this dialog

It was/is still possible to create the view specifications. They appear under the diagram type in the SysML category and you can select the view from the properties for the diagram. It's just that we added a feature to make it easier to find them in 16.

[wikitect]

Support ignored the bug identified.

It was/is still possible to create the view specifications. They appear under the diagram type in the SysML category and you can select the view from the properties for the diagram.

Not true. This is true for Requirement, Activity, UseCase and StateMachine - not Block Definition. I've not yet tried IBD, Parametric, Package or Sequence.

As I said

The SysML 1.5 heading doesn’t, however, list the custom technology SysML BDDs under the SysML1.5 > ‘BlockDefinition’ subheading - only Sparx’s own offerings (other SysML customisation such as Requirement Diagram, Activity Diagram do appear).

There is a bug. Selecting the SysML 1.5 heading only lists: the basic SysML technology and the UAF. It does not list any of the 21 custom BDDs I've defined using View Specifications - not something I'd miss. Luckily in v16 there is the additional technology heading where all of the SysML diagrams are listed. Not so for the SysML 1.5.

[wikitect]

Oh - and for good measure the Extension connector shows nothing in the Traceability pane when either of the pair of elements selected that are connected using this connector. As a result I always have to use an additional Dependency between  View Specification and SysML stereotype.

[wikitect]

Just tried an experiment wrt the other SysML diagram types.

As there's nothing listing the SysML Diagram names to use for extension I normally create a vanilla one and look at the properties to figure out the name.

• SysML Package - 'SysML1.4::Package'
• SysML Parametric - 'SysML1.4::Parametric
• SysML Sequence - 'SysML1.4::Sequence'

all appear correctly in both the technology and SysML1.5 headings.

But - SysML Internal Block Diagram - 'SysML1.4::Internal Block' only appears under the technology heading. It too, like the BDD, does not appear under the SysML1.5 heading.

Anyone therefore on v15 is unable to see / select / produce a customised SysML BDD and a SysML IBD.

On v16 the additional technology heading does list everything so there is a workaround. The bug is still present however.

[wikitect]

And support have confirmed that a customised UML Class diagram created using a View Specification also doesn't show in the New Diagram dialog.

SysML BDD, SysML IBD and UML Class diagram affected. How did this get through testing?

[qwerty]

Well, you are the test department (along with all the other users). Banana software will ripe at the customer site.

q.

[wikitect]

I'd much rather not be. The trouble is in building profiles semi-regularly I'm spending a lot of time in the fringes of stuff that most EA users hardly encounter. Perhaps I ought to be given a discount as I won't feel so inclined to spend when on a pension soon...

[Eve]

I've not yet tried IBD, Parametric, Package or Sequence.

Then why are you telling me my statement is incorrect?

On v 15 however there is only the SysML 1.5 heading in the new diagram dialog from which to create SysML diagrams. The SysML 1.5 heading doesn’t, however, list the custom technology SysML BDDs under the SysML1.5 > ‘BlockDefinition’ subheading - only Sparx’s own offerings (other SysML customisation such as Requirement Diagram, Activity Diagram do appear).

Selecting the SysML 1.5 heading only lists: the basic SysML technology and the UAF. It does not list any of the 21 custom BDDs I've defined using View Specifications

That sounds like your profile isn't specifying the extension to SysML Block Definition diagram correctly. In both of those statements you are saying that the feature is working.

[wikitect]

Quote from: wikitect on August 29, 2023, 04:31:02 pm

    I've not yet tried IBD, Parametric, Package or Sequence.

Then why are you telling me my statement is incorrect?

I can only base my statement on what I've verified by evidence i.e. the non-apperanace of customised BDDs under the SysML1.5 heading. I've since confirmed the same with the IBD.

You said

Quote

    It was/is still possible to create the view specifications. They appear under the diagram type in the SysML category and you can select the view from the properties for the diagram.

i.e. ingoring the problem identified - custom BDDs not appearing under the SysML1.5 heading. They don't as I stated in my original post hence if you then state that they do - this is the incorrect statement. Quoting my statement that I'd not yet tested other types of SysML diagram has no bearing on the one type (BDD) for which the point was made. Quoting that doesn't support any argument is odd.

Clearly it isn't working - it shows under the technology heading - so the profile is correct.

It doesn't, however, show under the older SysML.15 heading - same profile extending the same SysML stereotype which - when visible and used creates a SysML BDD.

And similarly with the IBD...