What’s New In GENESYS 2025

UPDATES IN VERSION – GENESYS 2025

MODEL ORGANIZATION WITH CONTAINMENT FOR GREATER INTEROPERABILITY

At the heart of GENESYS 2025 is the introduction of containment, a transformative approach to model organization. Containment allows users to structure engineering data in a way that aligns more naturally with user intent and industry best practices.

Key Benefits:

• Intuitive Navigation: Easier to explore and manage complex system models.
• Standards Alignment: Supports widely adopted data exchange standards.
• Enhanced Interoperability: Seamless collaboration across MBSE tools and teams.

To access the Containment View, click on the Containment tab at the top of Project Explorer.

The containment view organizes models according to Relationships, Views, Attributes, and Parameters. Entities are placed in the view based on the Owns/Owned By relationships. This organization provides a more logical structure that aligns with many methodologies.

Additional capabilities supporting the Containment View include:

• Jump to Entity in Containment View – From the context menu on an entity (right-click), you can select this option and navigate directly to the selected entity in the Containment View.
• Uncontained Entities – Provides a list of all entities that do not currently exist in the Containment View (i.e., lack the Owns/Owned By relationship).

FULL CONTROL PERMISSION OPTION ON NEW PROJECTS

Users can now automatically give the Administrators group full control permissions on new projects at the time of creation. This option is checked by default and helps streamline administrative processes for enterprise customers.

UNIFIED ARCHITECTURE FRAMEWORK (UAF) SUPPORT WITH BUILT-IN GUIDANCE

GENESYS 2025 incorporates robust support for the Unified Architecture Framework^® (UAF^®), a standard developed by the Object Management Group^® (OMG^®) to support mission engineering and enterprise architecture.

The new UAF features include built-in modeling guidance that assists users in correctly applying the UAF methodology. Additionally, there are normative diagram samples that help accelerate learning and adoption. These new features streamline the user experience, particularly for new UAF users.

These enhancements lower the barrier to entry for organizations adopting UAF, enabling teams to build effective, standards-compliant architectures from day one.

SCHEMA UPDATES

Summary of changes to the default schemas:

• Requirement class: The “Composite” enumeration of the Type attribute in the has been removed and replaced with a separate Boolean attribute called “Is Composite?” This allows the user to declare a requirement as composite while still assigning it to a general type.
• The formerly optional “Standards Compliance Schema” has now been formerly incorporated into the GENESYS 2025 Base Schema and Capability Schema. This includes a new class and several new relationships that allow the user to better trace to standards if needed.
• Removal of the Service Specification
• Minor changes to the Review class to better support integration with Sidekick.
• General UAF relationship updates and error corrections to better align with the UAF 1.2 Specification.

The following changes were applied to the GENESYS 2025 Base Schema and Capability Schema:

1. Requirement class changes:
   1. The “Composite” enumeration has been removed from the Type
   2. New attribute called Is Composite with enumeration literals of “Nil, No, Yes” has been added.
      1. Note: the schema migrator will set the Is Composite attribute to “Yes” for requirements that currently have the Type attribute set to “Composite” and then set the Type attribute to “Nil.”
   3. Service Specification class has been removed from the GENESYS 2025 Base Schema.
      1. Note: the schema migrator will transform any Service Specification entity to a Requirement entity with the term “[Service Specification] appended to the name of the entity. If the Service Specification class is still desired, the user can add it back to the GENESYS 2025 schema before migrating the project.
   4. Review class changes:
      1. Attributes publishedDate and startDate have been removed
      2. Attribute order changed to:
         1. Name
         2. Number

• Description

1. reviewID
2. mode
3. createBy

• leadUser
• purpose

1. guidance
2. plannedClosingDate
3. actualClosingDate

• sidekickReviewLink

4. Standard Compliance Schema Extension inclusion in the GENESYS 2025 Base Schema and Capability Schema. For more information, please see the “Standard Compliance Schema Extension User Guide” located in the “Extensions” folder in the install directory of GENESYS.
   1. Added new relationship pairs:
      1. Compliance with / satisfied by – Compliance with identifies the industry or process standard which the entity satisfies
         1. Standard “satisfied by” Program Activity, Requirement, RequirementGroup
         2. ProgamActivity, Requirement, RequirementGroup “compliance with” Standard
      2. Clarified by / clarifies – Clarified by designates lower-level standards for this entity.
         1. Standard “clarified by” Standard
         2. Standard “clarifies” Standard
      3. Added new Class:
         1. Standard
            1. Attributes:
               1. Section Number
               2. Standard Applicability
               3. Standard Rationale
            2. Relationships
               1. Augmented by with target class ExternalFile, Text
               2. Categorized by with target class Category
               3. Clarified by with target class Standard
               4. Clarifies with target class Standard
               5. Documented by with target class Document
               6. Packaged by with target class Package
               7. Satisfied by with target class ProgramActivity, Requirement, RequirementGroup
            3. UAF Schema Updates:
               1. New Relationships:
                  1. Competence “provides competence” to Actual Organization, Actual Organization “utilizes” Competence.
                  2. Capability “maps from” Operational Activity, Operational Activity “maps to” Capability.

REST API ENHANCEMENTS

New endpoints have been added to the GENESYS 2025 REST API expanding access to GENESYS models.

The Packages endpoint provides a convenient mechanism for obtaining package hierarchies and packaged entities.

The ProjectFolders endpoint provides the ability to access and manipulate the project folder hierarchy and contained projects.

The Views endpoint provides access to model view data and includes the ability to generate images for all GENESYS diagram types and HTML content for Matrix and Table views.

GENESYS 2025 RESOLVED ISSUES

The table below contains a list of issues that were resolved in GENESYS 2025. They are grouped by area and provide a description of the main observed behavior or symptom resolved in this release.

PREVIOUS VERSION HISTORY