No problem.

I understand now. Thank you for your explanation.

Hello again dserodio,

JUDE completely understands Subsystems as the quoto you pasted at your first post.

There is a presentation option for Subsystem notation.
Quote:From "OMG Unified Modeling Language Specification March 2003 Version 1.5 formal/03-03-01 :
3-14-3, Subsystem-Presentation Options" http://www.omg.org/docs/formal/03-03-01.pdf

So technically by adding the <<subsystem>> stereotype to a package, it transforms into a Subsystem like you mentioned but there will be no "pitchfork" icon shown in the notation when you do it. It is because that JUDE does not support the notation feature to change "Package notation" into "Subsystem notation" with pitchfork when adding <<subsystem>> stereotype to it. And like the presentation option says "the pitchfork symbol can be replaced by the keyword <<subsystem>> placed in a large rectangle".

Thanks for the reply.

When I create a subsystem using the Subsystem icon, and go to the Property View, there is no stereotype.

When I create a package, and then add the <<subsystem>> stereotype, it's not shown with the Subsystem notation (the "pitchfork" icon inside the package "tab".

Does this mean that Jude understand Subsystems and Packages as "similar-looking", but completely different things?

Thank you for your post dserodio.

On JUDE, you can add the "subsystem" stereotype to a package and vice-versa.

Here are two methods to add the "subsystem" stereotype to a package.

Method 1 :
1. Right-Clicking on a Package to open Pop-Up Menu in the Diagram Editor then select [Add Stereotype].
2. There will be <<stereotype>> showing up on the top inside the package element, then Double-Clicking on it and you can directly type "subsystem" in.

Method 2 :
1. Select a Package in the Diagram Editor or Structure Tree View.
2. Go to the Property View (It is the left bottom panel). then select [Stereotype] tab.
3. Press [Add].
4. Scroll to the "Subsystem" to set it or type "subsystem" in directly.

You can do vice-versa with same step.

From the "UML Reference Manual", page 100:

Quote:

Shouldn't I be able to add the "subsystem" stereotype to a package to "transform it" into a Subsystem and vice-versa?