Edit Connection Settings

The Edit Connection Settings command, accessed on the right-click context menu for a related project listed in Project Explorer, enables the user to adjust the settings which govern the connection with a related project. This includes the settings required to resolve the project as well as the settings for how to traverse the boundary between the projects.

 

 

The settings for a related project include:

 

• Project Name - this read-only field is the descriptive name for the project. Though GENESYS enforces project name uniqueness within a repository, this is simply to avoid user confusion. The real identifier is the project ID. The project name for a related project is cached when successfully connecting to that project so that the team has a convenient reference for the project.
• Project ID - the unique identifier for a project. In order to successfully resolve and connect to a related project, a project with the specified ID must exist within the repository. If the mapping has been broken, the project ID can be changed here.
• Relationship Traversal - governs whether the related project is treated as a white box (allowing seamless traversal) or black box (stopping just beyond the project boundary).
• • Follow through related project - when this is selected, the related project is completely open (within the bounds of access control). This allows diagrams, reports, and simulations to traverse the boundary as if it doesn't even exist, effectively creating a meta-project.
  • Stop with connected entities - when this is selected, the attributes of the related entities are accessible but not their relationships. This provides connectivity without exposing the related project's details.
  • Hide connected entities - when this is selected, related entities are not visible. This is useful when your project is a reference architecture or a reuse module. This allows you to analyze your subset independent of any connections.

 

NOTE:

The relationship traversal behavior is set independently from each project. This means that one project can seamlessly traverse the other from one direction while from the other direction the behavior is black box.

 

NOTE:

What permissions are required to edit connection settings? To edit connection settings for a related project, you must have project administrator permission for the current project.

 

NOTE:

Although hiding connected entities is useful when generating specifications, simulating a reuse module, or performing detailed analysis of the isolated module, the best practice is to limit operations within this mode. Working with connected entities hidden prevents you from understanding the impact of your changes on related entities. Instead, set your project to Stop with connected entities so that you can see your connectivity and operate with greater insight.