Aller au contenu principal

Glossary

This glossary defines key terms used in Sim4Sys-Designer documentation.

B​

Black Box
A view of a system or service where only the external interfaces (inputs and outputs) are visible, without revealing the internal structure or implementation details. Used at the Project Definition and Service levels.

C​

Code Generation
The automated process of generating C++ code from UML/SysML models. Sim4Sys-Designer can generate executable code that represents the behavior described in state machines and sequence diagrams.

F​

Flow
A communication mechanism between elements in a model. Flows carry data (parameters) between services, functions, or external actors. Flows are defined with types and directions (input/output).

Function
A part of the effective behavior of a service, representing a technical domain or capability. Functions are created at the System Analysis level and can interact through inter-function flows.

L​

Life Phase
A specific operational condition or context in which a service operates (e.g., "Standard Use", "Visualization"). Life phases help model different behaviors under different circumstances.

M​

Mapping
The process of connecting model elements (flows, types) to Virtual Bench visualization elements. Mappings are typically exported via XML files and imported into Virtual Bench.

Model
A structured representation of a system using UML/SysML notation. In Sim4Sys-Designer, a model contains projects, services, functions, and their relationships.

P​

Primitive Type
A basic data type representing atomic values (integer, decimal, or text). Primitive types are used to type parameters in flows and variables. Examples: Speed_Type, Luminosity_Type.

Project
A container within a model that represents a product or system. A project contains services and defines the interfaces between the customer, product, and environment.

S​

Sequence Diagram
A UML diagram that shows the interactions between objects (lifelines) over time. In Sim4Sys-Designer, sequence diagrams are used to model use cases, service behaviors, and function interactions.

Service
A high-level capability or function of a system. Services are created at the System Analysis level and contain functions. Each service has its own state machine and sequence diagrams.

State Machine
A behavioral model that describes the different states a service can be in and the transitions between those states. State machines are automatically generated from sequence diagrams.

T​

Type
A data structure used to specify the nature of parameters in flows or variables. Types can be primitive types, data types (structures), or enumerations. Types are defined in Type Diagrams.

Type Diagram
A diagram used to define and manage data types, primitive types, and enumerations used throughout the model.

U​

Use Case
A description of a system's behavior from an external actor's perspective. Use cases are modeled using sequence diagrams and represent specific interactions between actors and the system.

W​

White Box
A view of a system or service where the internal structure and implementation details are visible. Used at the Function level to show how services are decomposed into functions.

XML Export
The process of exporting model information (types, flows) to an XML file for import into Virtual Bench. This enables the connection between models and visualizations.