Packages and Namespaces - Packages and Their Contents - Specific Elements from other Packages
7 important questions on Packages and Namespaces - Packages and Their Contents - Specific Elements from other Packages
What would happen if a name collision appears?
If there were already a C in A10, but you still needed the B10::C, you can add an alias to the import.
The import tag would then look like “«import» D”. Then in A10 a user of B10::C would just refer to the alias D.
What does the dashed elements on the left indicates?
Use of the Package and Element import bring the target as a ... Item?
As a publicly visible item, they are further visible to anyone who imports the importing Package.
- Higher grades + faster learning
- Never study anything twice
- 100% sure, 100% understanding
Many modelers make extensive diagrams showing the dependencies and other relationships between the Packages to guide them into placing Elements in their correct Package.
This is good practise. It can reveal?
For example, if PA depends on PB while PB depends on PA, coordination will be very difficult
How could a decision be made on where to put something and how would the development order of the Packages be determined?
What are Package Merge?
Why are Merges not longer in use?
They are not used by UML 2.5, but they are still defined in the UML specification in case there are other OMG specifications that might depend on them. Merging will probably be removed from future versions of UML
The question on the page originate from the summary of the following study material:
- A unique study and practice tool
- Never study anything twice again
- Get the grades you hope for
- 100% sure, 100% understanding