The challenge of digital engineering is all about making the MBSE model relevant throughout the product lifecycle. Vitech makes it happen with the customer-driven enhancements in GENESYS 2020.
Click HERE for more complete information on all the new features.
Users now have the ability to tailor the GENESYS user interface by adding custom commands to the ribbon. A custom command can open a file, launch an application, or execute a GENESYS script.
When executing a script, the folder and entity selections in the user interface are available to the script, allowing simple or advanced operations against this information. Scripts can specify when the command is enabled in the ribbon based on the selections or any other logic desired. Scripts leverage the full power of the .NET framework and provide direct access to, and manipulation of, GENESYS data via the GENESYS API. Users have a powerful means of interacting with external applications and services, automating complex logic, or performing macro-style operations directly from the GENESYS ribbon. When combined with customer commands, scripts open a world of opportunity to personalize GENESYS to your specific needs.
Adding an external reference to your entity in order to supplement the textual description adds richness to the model and to the reports created from the model. We made this easier by allowing you to drag-drop files directly onto an entity. This will create a new entity in the ExternalFile class, set the attributes including file location, and then set the augments/augmented by relationship.
If instead you want to set an image for an entity, you can drag-drop an image file onto an entity, either in an entity list or on a diagram, which will set the image. Dropping an image onto an entity on a diagram will toggle on the Use Image option.
When navigating through the different views available in GENESYS, once you find an entity, there are times when you would like to know the database folder in which the entity is located. In the property sheet view, under the properties tab, the folder path is displayed as a hyperlink. If you click on the hyperlink, a new Project Explorer pane opens with the folder and entity selected.
As we work with customers, we find that there are some model assistant rules that work well in specific cases, but are not necessary for all projects. In GENESYS 2020, we have set some of the rules that frequently cause confusion to inactive by default. The changes will not affect existing user settings, and they can be tailored easily by visiting the Model Assistant in the Project Explorer tree view. These rules are:
We have also added the ability to keep root functions and states synchronized when auto-maintain connector names is enabled. This means that when you change a Component name, the connected Root Function and Root States that are using the default name will be renamed as well.
The decomposability of Interfaces and Links creates overlap between a low-level logical Interface and a high-level physical Link. Given this overlap, rather than requiring two separate classes, the connection between components can be represented with a single class – Link. At more abstract levels, the Link can be treated as a logical statement of connection. At more detailed levels, the Link can be treated as the physical realization of the connection.
Based upon experience, industry dialog, and internal reflection, we identified the following:
Given these observations, GENESYS 2020 versions of the baseline schemas include the following changes. Note, projects may continue to use prior versions of the schema with no changes to capability.
Given the nature of the schema changes made in the 2020 base and Capability Architecture Definition schemas, project migration is required to transform specific classes and specific attributes. To best support this migration, GENESYS 2020 provides a schema migration utility on the Project tab. Also included is a report which details what relationships will be removed during the migration and a script which will transform Interface entities to Link entities.
This utility is targeted at the standard Vitech schemas. If your project uses a customized schema, additional migration support may be required. If you have made schema extensions and would like to understand what special steps – if any – are required to support your extensions, please contact Vitech Customer Support with a copy of your extensions. We are happy to review these and advise you in your migration accordingly.
Note: You do not have to migrate your schema in order to make use of GENESYS 2020. You should assess your project needs, your project lifecycle, and the changes present in the 2020 schemas to determine if, and when, to migrate your schemas. Project teams nearing a major milestone or approaching conclusion should strongly consider remaining with their current schema. We recommend that others move to the 2020 schemas to take advantage of the latest improvements in the systems engineering metamodel.