LYNX MOSA.ic anticipates that developers will have a design, whether it is an informal drawing of boxes and arrows on whiteboards and paper napkins, or formally modeled systems with design tools such as Simulink or SCADE. Architectural details that transcend functionality such as spatial, relational, and timing requirements of system subjects and objects can natively plug into the configuration interface of LYNX MOSA.ic. 

LYNX MOSA.ic includes hardware discovery tools to learn about the capabilities and capacities of the CPU, memory, and devices available for the target design. These details will be used to improve fidelity in controlling the execution behavior of the system.

LYNX MOSA.ic can formalize the relationship of abstract design and physical hardware with a system modeling language and configuration tools that accounts for the system’s:

• Abstract subject (virtual machine) and objects
• Resource bindings to subjects and objects
• Capability privileges of subjects
• Full mesh information flow
• Execution timing of subject
  
  

When completed, this model will serve as input to a compiler that will create the necessary hardware parameters that will inform to processor to enforce a structural policy. The hardware parameters will confine a design with specific temporal and spatial boundaries in accordance to an expected behavior derived from the concrete system model. This model can also serve a record for system level verification and validation of safety and security processes.

For each subject defined within the concrete system model, a virtual space (static virtual machine) is reserved to host an executable image (guest) that must be built with the provided CDK or a third-party toolchain. The LYNX MOSA.ic CDK includes three distinct tool chains to build the following types of guest images:

• LynxOS-178 RTOS
• Buildroot Linux
• Lynx Simple App (LSA) bare-metal application

The LYNX MOSA.ic tools include IPC libraries to connect guests and sophisticated linking tools to integrate boot images to manage project nuances like integrating third-party components, tailoring the low-level boot process, integration with hardware boot security features, etc. 

Run integrated system images on production, development, and even virtual hardware platforms. For systems early in the development stage, an added benefit of the distributed architecture of Lynx MOSA.ic is the ability to debug independent subjects/guest of the system in parallel, as if each guest had their independent computer

LYNX MOSA.ic provides numerous fine-tuning options, such as reducing application complexities by porting RTOS dependencies to bare-metal, tracing resource allocation for hazard analysis, and tracking clock ticks for maximizing performance.