Sharing Design Elements: Special Considerations

• By default, when you create a Use Case element on a Use Case diagram, the use case is stored within the diagram file. Therefore, when you right click on such an element, there is no Team menu. To commit or update a Use Case element, commit or update the Use Case diagram.
• Storing the design elements within the diagram itself may not always be what you want or need, so in Together you can control which design elements get stored in the diagram file, and which design elements reside in their own separate file within your project. These elements are known as First Class Citizens (FCC).
• In the Together modeling preferences dialog, you can choose several options for separating diagram elements. By default, Together stores diagram elements in a single file. To open the preferences dialog, from the menubar, select Window > Preferences. In the options list on the left, expand the Modeling node, and select the File Storage tab.

  Tip: You may wish to consider which design elements within your project should be First Class Citizens before the team starts each project. Otherwise you risk having design diagrams that contain a mixture, as the separation presets only affect elements created after the preset is changed.
• First Class Citizens have their own Team menu which you can use to interact with the VCS. You need to add and commit First Class Citizens individually or use Team > Synchronize with Repository... to get a list of outgoing changes (make sure the outgoing button is selected). Outgoing FCC elements are under the Together Model branch.
• It is recommended that while working with design diagrams that contain FCC design elements, you should keep the diagram file and the design element files synchronized by committing/updating all of them.
• Included in the structure of a project is the Together Model directory. (For more, see Sharing Projects.) Design elements that are First Class Citizens are created here at the level where the design diagram resides.