Bug 188261 - deployment diagram (and model): a Node have to be able to contain Component
Summary: deployment diagram (and model): a Node have to be able to contain Component
Status: RESOLVED WORKSFORME
Alias: None
Product: umbrello
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: Umbrello Development Group
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-03-27 16:18 UTC by hevi
Modified: 2023-01-26 05:05 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
Screenshot of component inside node in deployment diagram (5.80 KB, image/png)
2022-12-27 06:37 UTC, Oliver Kellogg
Details

Note You need to log in before you can comment on or make changes to this bug.
Description hevi 2009-03-27 16:18:34 UTC
Version:           2.2.0 (using 4.2.00 (KDE 4.2.0), Kubuntu packages)
Compiler:          cc
OS:                Linux (x86_64) release 2.6.27-11-generic

deployment diagram (and model): 
a Node have to be able to contain Component.
and Component have to be able to contain Object as well as.

"Deployment diagrams show the configuration of run-time processing elements software components, processes, and objects that execute on them" [UML spec 1.4, 3.96.1]. One essential aspect of the configuration is composition of the deployment related modeling elements. This is required when designing and specifying the allocation architectures of the systems.

This is bug as this violates the UML specification (ie. don't make a cheap imitation of the Rational Rose (that has pathetic component and deployment diagrams), but go for UML specification).
Comment 1 Andrew Crouthamel 2018-11-02 04:24:43 UTC
Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!
Comment 2 Andrew Crouthamel 2018-11-16 02:42:26 UTC
Dear Bug Submitter,

This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version?

Thank you for helping us make KDE software even better for everyone!
Comment 3 Justin Zobel 2022-12-07 00:23:56 UTC
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Comment 4 Bug Janitor Service 2022-12-22 05:19:42 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 5 Oliver Kellogg 2022-12-27 06:37:06 UTC
Created attachment 154839 [details]
Screenshot of component inside node in deployment diagram

With current umbrello master I cannot reproduce the problem, see attached screenshot.
There may by an aesthetics issue with the node name appearing in the middle of the enlarged node (and the name cannot be moved to a better location) but IMHO that is a separate issue.
Comment 6 Bug Janitor Service 2023-01-11 05:18:05 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 7 Bug Janitor Service 2023-01-26 05:05:44 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!