Bug 145181 - Cannot define a system boundary for an use case
Summary: Cannot define a system boundary for an use case
Status: RESOLVED UNMAINTAINED
Alias: None
Product: umbrello
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR wishlist
Target Milestone: ---
Assignee: Umbrello Development Group
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-05-08 12:18 UTC by Sumit Madan
Modified: 2021-12-21 09:23 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Sumit Madan 2007-05-08 12:18:04 UTC
Version:           1.5.6 (using KDE 3.5.6, Debian Package 4:3.5.6.r1.dfsg.1-4 (lenny/sid))
Compiler:          Target: i486-linux-gnu
OS:                Linux (i686) release 2.6.18-4-686

Hello,

there should be a way to define a system boundary and a name for this system boundary. At the moment, i am using the box as a system boundary, but cannot define a name for it.

What a system boundary is see here: http://www.parlezuml.com/tutorials/usecases/usecases_intro.pdf (Fig. 1.5 UML Use Case diagram)

Thank you
Sumit.
Comment 1 Antoine Dopffer 2007-05-27 00:40:21 UTC
Hi Sumit.
 What about writing a label just near the box ?
It's not perfect but would it satisfy you ?

Thank you.
Comment 2 Sumit Madan 2007-05-28 12:14:40 UTC
Hello Antoine,

already using a box and a label component as a system boundary.

Right, its not perfect but its working :)

Regards, Sumit
Comment 3 Oliver Kellogg 2007-06-05 21:33:17 UTC
Can we close this?
Comment 4 Sumit Madan 2007-06-05 21:43:29 UTC
Is it not possible to implement a system boundary component?

When you think that there is no need to implement such a component, then 
you can close the bug.

Thank you,
Sumit
Comment 5 Ralf Habacker 2019-12-26 00:54:56 UTC
https://sparxsystems.com/enterprise_architect_user_guide/14.0/model_domains/systemboundary.html mentions a definition of a system boundary.
Comment 6 Robert Hairgrove 2020-08-11 14:22:42 UTC
If nobody else wants to work on this, I will make an effort.

There should be exactly one system per use case diagram, however there could be several diagrams using the same system? And there can be several different systems with use cases split up among the different systems?

Should this be a configurable option in the use case diagram properties (i.e. show or hide the system boundary)? 

How do we change the GUI of Umbrello? I am only familiar with editing Qt .ui files in Qt Designer. And the text for the option would need to be translatible.

Also, what would be the preferred way of serializing this in the XMI file? I assume there is a little leeway in format since use cases are actually not in the object model per se.
Comment 7 Robert Hairgrove 2020-08-13 06:47:15 UTC
Here are my ideas for implementing this feature:

1. There should be a checkbox under the "General" property page for a use case diagram with text "Show system boundary". In the XMI file, use case diagrams already have the Boolean attribute "showpackage" which seems to be unused -- this could be utilized to store the value of the option. Otherwise, an additional attribute could be defined: "showsystem".

2. If there is an eclosing folder, the name of the folder will be used as the system name. Otherwise, either the name of the current XMI file, or simply the word "System" will be used.

3. In the case that an actor is positioned inside the bounding box of use cases which would be used to draw the rectangle, an error message (warning) is shown when the properties dialog is closed advising the user to move the actor widgets outside of the rectangle. No boundary is shown. After moving an actor, if it is possible to show the use case, and the option is checked, the box is automatically drawn. Alternatively, the bounding rectangle could be shown as a gray or red dotted or dashed line to show the user where it would be drawn.

4. Code which controls dragging or resizing the actor and use case (presumably in the mouseMove event of the diagram or scene?) should prevent the widgets from crossing the system boundary if it is already being shown.

Before attempting a solution, it would be nice to have some feedback or additional ideas here. I think that after thirteen (!) years, this could definitely be implemented with relatively little effort.
Comment 8 Robert Hairgrove 2020-08-13 06:52:37 UTC
"... if it is possible to show the use case..."

should be:

"... if it is possible to show the system boundary..."
Comment 9 Robert Hairgrove 2020-08-13 12:44:26 UTC
(In reply to Robert Hairgrove from comment #7)
> 1. There should be a checkbox under the "General" property page for a use
> case diagram with text "Show system boundary".

I see that there is already a checkbox which is only used for sequence and collaboration diagrams. But it would have to show a different text. It would be simple to replace the string "Autoincrement Sequence" with something different, but how much of a problem would it be to get it translated?