Abstract: A code-proving system is adapted to analyze implementation code for compliance with a at least a specified model. The implementation code can be code that is used to provide control or semi-automated control of a complex electromechanical system, such as an automobile. The specified model may be written to comply with a meta-model such as the software architecture specification known as Automotive Open System Architecture (AUTOSAR).

Abstract: A code-proving system is adapted to analyze implementation code for compliance with a at least a specified model. The implementation code can be code that is used to provide control or semi-automated control of a complex electromechanical system, such as an automobile. The specified model may be written to comply with a meta-model such as the software architecture specification known as Automotive Open System Architecture (AUTOSAR).

Abstract: Methods, mediums and systems are provided to enable a user to build and edit a UML model for a system containing one or more physical component, which includes the across variable and/or the through variable of the components. A UML model may include classifiers, such as classes, interfaces, datatypes, signals, components, nodes, use cases and subsystems, that describes the structural and behavioral features of the system. A UML model may include at least one of the classifiers that is described using the across variables and/or the through variables of the system. For example, the interface of a component in a UML model may be described using the across variables and/or the through variables of the component.

Abstract: Methods, mediums and systems are provided to enable a user to program the behaviors of a Unified Modeling Language (UML) model in a graphical programming or modeling environment, such as block diagram programming environment. The UML model is exported into a text-based format, which is subsequently imported into the graphical programming or modeling environment. The graphical programming or modeling environment represents the UML model using functional blocks so that the user can program the behaviors of the UML model. The graphical programming or modeling environment also enables the user to simulate or execute the UML model to determine the behaviors of the UML model.

Abstract: Methods, mediums and systems are provided to enable a user to program the behaviors of a Unified Modeling Language (UML) model in a graphical programming or modeling environment, such as block diagram programming environment. The UML model is exported into a text-based format, which is subsequently imported into the graphical programming or modeling environment. The graphical programming or modeling environment represents the UML model using functional blocks so that the user can program the behaviors of the UML model.

Abstract: Methods, mediums and systems are provided to enable a user to program the behaviors of a Unified Modeling Language (UML) model in a graphical programming or modeling environment, such as block diagram programming environment. The UML model is exported into a text-based format, which is subsequently imported into the graphical programming or modeling environment. The graphical programming or modeling environment represents the UML model using functional blocks so that the user can program the behaviors of the UML model.

Abstract: In system design simulators, probes are software objects that collect data from simulated system components. A probe synchronization method and device are used to collect simulation data from the components during a period of interest. For example, a given event that occurs during the simulation may signal the beginning of the period, and another event may signal the end of the period. An acquisition window having a starting point and an ending point coinciding with the occurrence of the events may be used by a probe master to cause one or more probes to collect data during this period of interest. A unique Identifier or Tag of this period of interest is generated by the Probe Master and sent to all the slave probes. This Tag is dumped in the simulation database. It allows post-processing correlations between high-level simulation events and low-level model reactions.

Abstract: In system design simulators, probes are software objects that collect data from simulated system components. A probe synchronization method and device are used to collect simulation data from the components during a period of interest. For example, a given event that occurs during the simulation may signal the beginning of the period, and another event may signal the end of the period. An acquisition window having a starting point and an ending point coinciding with the occurrence of the events may be used by a probe master to cause one or more probes to collect data during this period of interest. A unique Identifier or Tag of this period of interest is generated by the Probe Master and sent to all the slave probes. This Tag is dumped in the simulation database. It allows post-processing correlations between high-level simulation events and low-level model reactions.