System Model Development

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.

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.

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.

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.

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 ensures the product is consistent with the model.

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.

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.