Interestingly, the video also shows something that I didn't know until very recently. If you manage to import two projects that reference and nest the same third party unit, then Rhapsody will deal with the duplicate import situation by creating a linked unit. Generally, this problem will only occur if you move referenced units until other units (but it's interesting to know that there are still things to know!)
Understand the art of the possible. My mission is to make executable Model-based Systems Engineering (MBSE) easy with the Object Management Group's Systems Modeling Language™ (SysML®) and UML® to make simple modeling easy to deploy to the masses. This site provides practical experience of tuning IBM® Rational® Rhapsody® - a precision engineering UML/SysML tool. Rhapsody tips and ideas will be posted with links to videos. You can follow by email (if google app is allowed).
Friday, 13 April 2018
Rhapsody Tip #31 - Referencing units in other projects (Intermediate)
This Rational Rhapsody helper videos follows on from my video #30 on units and managing the project on the file system. In this video we look at referencing units from other Rational Rhapsody projects. Building families of projects that reference each other can often be better than having a single monolithic project. Separation of concern across projects means that projects can be managed separately, in different locations, and with separate versioning yet they can share common elements or interfaces. In this video I show how two projects can reference the same common unit in another project, including touching on the importance of considering absolute or relative references.
Interestingly, the video also shows something that I didn't know until very recently. If you manage to import two projects that reference and nest the same third party unit, then Rhapsody will deal with the duplicate import situation by creating a linked unit. Generally, this problem will only occur if you move referenced units until other units (but it's interesting to know that there are still things to know!)
Interestingly, the video also shows something that I didn't know until very recently. If you manage to import two projects that reference and nest the same third party unit, then Rhapsody will deal with the duplicate import situation by creating a linked unit. Generally, this problem will only occur if you move referenced units until other units (but it's interesting to know that there are still things to know!)
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment
Note: only a member of this blog may post a comment.