Sparx Systems Forum
Enterprise Architect => Suggestions and Requests => Topic started by: karlwg on March 05, 2011, 01:26:21 am
-
Hi,
I noticed, that elements can stay within the Project Browser even if they were deleted from all diagrams.
Is there a way to find (and then delete) such orphaned requirements?
Kind regards
Karl
-
Ctrl-F
Find Orphans
select all
Ctrl-Del
q.
-
Thank you very much, this is, what I was looking for!
-
And just for info, a simple deletion on a diagram, i.e. pressing the delete key when an element is selected will never delete the element from the model/project browser. You have to use control-delete to achieve that.
-
Was predefined search "Find Orphans" removed in EA13?
-
I guess you need to search for it. Didn't you know the Easter bunny has its main residence on planet Sparx?
Honestly, I don't know the answer :-\
Diagram Searches/the first on the list
q.
-
Diagram Searches/the first on the list
Thanks a lot!
Looks like documentation is not up-2-date ;)
-
And just for info, a simple deletion on a diagram, i.e. pressing the delete key when an element is selected will never delete the element from the model/project browser. You have to use control-delete to achieve that.
Umm, that is not actually true.
There are things, that when deleted on a diagram, disappear into the great bit bucket in the sky, please be very careful giving advice like this.
For example if you delete an attribute from a class it is gone (but not a column from a table, or an attribute from a model document)
-
It is also not a good idea to delete everything on the Find Orphans report without knowing exactly why it is an orphan. As several of you have pointed out many times, diagrams are just a human-support mechanism to help you visualize an aspect of your model, and you could - if you felt so inclined - develop part or all of your model without using diagrams at all.
@hfrmobile - what documentation are you referring to? As far as I can see, the release 13 Help is up to date; where did you find the not-updated material?
-
Isn't an orphan an element that has zero relationships rather than an element that isn't on a diagram?
Also, Skiwi, point taken, my comment was slightly ambiguous, but the main thrust of what I said related to elements and that still holds true I believe... "pressing the delete key when an element is selected will never delete the element from the model/project browser. You have to use control-delete to achieve that."
-
For those who want to see the "real ophans", I wrote an SQL query a while ago that return the elements that are really not used anywhere.
See Searching for REAL orphans in Enterprise Architect (http://bellekens.com/2015/10/16/searching-for-real-orphans-in-enterprise-architect/)
Geert
-
Graham, I think it depends. An orphan is someone/something without relations. I guess one can argue that an element not showing on a diagram is also "unrelated". However, there should be lists for both orphan types (maybe Geert's script does address this).
q.
-
Graham, I think it depends. An orphan is someone/something without relations. I guess one can argue that an element not showing on a diagram is also "unrelated". However, there should be lists for both orphan types (maybe Geert's script does address this).
q.
Don't agree. It the wrong use of the word "orphan". The existence of an item on a diagram and or the browser is a matter of choice, even if inadvertent. That's not to say there shouldn't be a means of finding them -as they represent anomalies within the model.
In addition, I believe EA treats items which have no package (for example, the package has been deleted, but the package reference remains) as "orphans". I don't think that's correct, they are just logical inconsistencies - which are rectified by the Project Integrity Checker.
Paolo