Model-Based Systems Engineering
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.
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
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 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
The architecture for the electrical and electronic subsystem is defined in the model and provides the design team with an implementation structure.
The product must meet specific performance, safety, and design requirements. The requirements are contained in the model and associated to design elements.
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.
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.
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.
As digital engineering changes the way we live and work, systems engineers are turning to model-based engineering software to help them navigate the complexity. GENESYS—an enormously powerful model-based systems engineering tool—addresses our 21st-century challenges with an underlying systems metamodel..
This webinar will discuss the relationship between systems engineering, digital engineering, and MBSE in creating the framework we need to deliver complex products.