UniPhi FAQ

A: UniPhi is a Matlab/Simulink-based system implementation and data dictionary tool. The tool facilitates centralized data management, a modular and scalable system architecture, "wireless" transfer of signal information, and plug-and-play feature implementation.

A: You may want to consider UniPhi if you are using Matlab/Simulink as your primary control system design platform and you are contemplating a move toward an entirely virtual control system design approach. UniPhi is designed to support an agile model-based system development process. It affords a swift transition across different development stages whithout necessitating any feature rework. Thus, UniPhi is a key tool resource for supporting the rapid development of complex embedded control system applications that are under stringent timelines.

A: UniPhi implements an ingenious data pooling concept that affords wireless signal transfer across the entire model architecture. This data pooling concept along with the modular, task-oriented model structure entailed in the UniPhi template architecture modules facilitates effective plug-and-play algorithm implementation.

A: UniPhi affords system integration and functional debugging at an early system development stage when changes are cheap. UniPhi enforces a modular system architecture and thus maximizes feature reusability at even the lowest implementation level. Due to the modular architecture and due to the use of centralized data management UniPhi provides a literally unlimited level of design freedom and system scalability (adding/removing/altering system tasks, model features, and data objects). The wireless signal transfer specifically eliminates the need for explicit signal connections which can become a major impediment for project progress in the case of complex systems.

A: UniPhi is based on a rigorously systems-based (rather than feature-based) design philosophy. Accordingly, UniPhi embraces systems-based architecture and data abstraction models. These abstraction models reflect an attempt to realize a strict separation between target dependent and target-independent features, to implement an entirely task-oriented architecture design (coherent system tasks) which supports the emulation of the system scheduling functonality, and to implement a scalable, application-independent data pooling concept (that ultimatley affords "wireless" signal transfer throughout the architecture model).