Multi-user Team Support

Together delivers support for true multi-user development. You can use these features to...

Protect your company's software assets
Help team members work together
Unobtrusively impose team-wide or enterprise-wide standards

Multi-user Version Control System

Together delivers seamless integration with your version control system without requiring you to artificially and manually split up your model into submodels, and subsequently split those submodel into files for your version control system. Together frees you from spending your time in the care and feeding of a proprietary internal repository like those found in other modeling products.

Together provides built-in integrations for leading multi-user version control systems, including those that support the SCC standard for Windows systems. Get started even faster with CVS, a leading multi-user version control system... already pre-confgured and ready to go.

Set Version Control options, enable version control for the project, and you can interact with version control right from the speedmenu system.

Interacting with the configured VCS

Once you have configured your version control options and associated your project with a version control project, it's a snap to interact with you VCS from Together. Version control commands appear on right-click menus for source elements (such as Classes) both in diagrams (as shown below) and on their nodes in the Model tab of the Explorer.

Hierarchical Configuration Options

Using the Advanced mode* of the Default Options dialog you can set configuration options at three levels- globally for your installation, project-specific, and diagram-local. The settings of all levels are merged together. If an option is set in multiple levels, the more local setting overrides the more global one. For example, diagram level overrides project level, which in turn overrides default level. However, options marked Final at a global level (by a project administrator on a shared installation, for example) cannot be overridden at a more local level. This is how you can enforce code formatting or blueprint options installation-wide on a server-based installation.

The number of levels is extensible by modifying the underlying properties file.

Set options at any of three default levels. Mark as Final any that you don't want overridden at another level.