Model-Based Systems Engineering

Solutions for Model Creation
Menu

MBSE for Electrical / Electronic Design

Digital Engineering requires a model-based design process that begins in Systems Engineering.  Zuken acquired Vitech Corporation, a leader in Systems Engineering practices and model-based systems engineering (MBSE) solutions, with the intent of implementing an E/E model-based design process.  The model-driven system provides a single source of truth for the product development process.

MBSE panel 2

Collaborative Model Creation

GENESYS delivers connectivity through a collaborative framework that supports today’s geographically dispersed engineering teams.

Build better models and deliver better products:

  • Integrated requirements management
  • Fully executable behavior models
  • Architecture development tools
  • Validation and Verification

DOORS® Integration

Many companies currently use DOORS for requirements capture and management.  GENESYS supports the use of DOORS with a bi-directional interface.  The DOORS Connector supports transferring in information in an ongoing system design and development effort.

digital engineering model - MBSE

SysML Views - MBSE

Leverage SysML Views

GENESYS comes ready to deliver SysML representations out of the box. If you need to leverage the power of SysML but want the flexibility of an integrated approach, GENESYS brings these elements together so you don’t have to compromise.

Access the Model with Excel

The model data can be exposed to design teams through the use of an Excel Connector.  The contents for the Excel spreadsheet is user configurable and based on the relationships within the model. The Connector is bi-directional so requirements can be added and verifications requirement status can be updated.  The Excel Connector is a important tool in making the model accessible and relevant through the product life cycle.

Model data through Excel Connector - MBSE

Model Creation Highlights

Model Based Design

The process is based on a model built upon relationships. The model replaces document based design. The model is typically created by the Systems Engineering team who converts system purpose into structure, behavior and requirements.  The model is considered the single source of truth.

Unified Design Model

Relationships can be built textually or graphically. The model is stored so that views are generated from the model. Change the model and all the views will automatically incorporate the change.  View synchronization is automatic.

Leverage SysML Views

GENESYS comes ready to deliver SysML representations out of the box. If you need to leverage the power of SysML but want the flexibility of an integrated approach, GENESYS brings these elements together so you don’t have to compromise.

Product Structure

The architecture for the electrical and electronic subsystem is defined in the model and provides the design team with an implementation structure.

Product Requirements

The product must meet specific performance, safety, and design requirements. The requirements are contained in the model and associated to design elements.

Design Envelope

When the design transitions from System Engineering to the implementation team, a design envelope must be clearly defined. The design team then knows what are the acceptable parameters in terms of cost, weight, size, power, etc.

Design Verification Gates

The model must remain relevant through the product development process. This is accomplished through verification gates which are comprised of a set of verification requirements. The design can not proceed to the next development phase until the gate requirements are satisfied.  This insures the product is consistent with the model.

Model Verification Status

As the design moves through each verification gate, the model must be updated to reflect the verification requirement status. This allows Systems Engineering to monitor the design progress in terms of meeting verification requirements. As the design progresses through the implementation process, Systems Engineering has a window into its model consistency.

Model Verification

Create verification events comprised of a series of verification requirements that can, in turn, contain multiple requirements. Verification events create approval gates in the design process.

Excel Connector

The Excel Connector provides read/write access to the design information in the model such as requirements, structure, verification requirements, etc. For instance, requirements can be added to a design element through the Excel Connector.

Integration with DOORS

GENESYS provides a bidirectional connection to DOORS, a common requirement capture system. The bidirectional link allows for easy movement of requirements between GENESYS and DOORS.

Got a Question? - Contact Zuken today

For more information on how Zuken can help your design process, contact Zuken today.
Contact us today