Conceptually, an Application is a group of processes that are being developed together, typically within the same project within an IDE. Within the model, this means an Application is a container for Process Parts representing Processes, where the Processes themselves are contained in an Application Project linked with the Application. Applications and their linked Application Projects are created automatically when an Application Part is created.
An Application types an Application Part.
An Application Part models the <ProcessEntry> element of an ARINC 653 configuration. Most of the <ProcessEntry> attributes are generated from properties of the Application that types the Application Part.
The structure of the <ProcessEntry> element is as follows for PikeOS:
The profile creates an Application when you create an
Application Part on a
Configuration Diagram: click the Application Part toolbar button, and then click inside a
Partition Part. You are prompted to specify the name of the application. When you create an Application Part on a Partition Part, the profile creates the following items in the model:
• An Application Part on the Configuration Diagram.
• An Application Project in which to model the application.
• An Application item that types the Application Part. The Application item is scoped to the Integration Project.
Specify the startup properties of the application through the Application's Property Pages: on the Application's Property Pages, click the Application tab, and then set the tagged values of the properties.
You can view all the Applications in the model through the Application folder in the ARINC 653 Profile pane.
An Application is based on a UML Class.
The following sections provide information about how an Application is used in the model.
Shown on these diagrams
None.
ARINC properties
These properties are set on the Application tab of the Application's Property Pages.
• Application Project - specifies the Application Project package that contains the model items for the application
• CmdLine - generated as the CmdLine attribute of the <ProcessEntry> element.
• ExecInPlace - generated as the ExecInPlace attribute of the <ProcessFileEntry> element.
• FileName - generated as the FileName attribute of the <ProcessFileEntry> element. Possible values are TRUE or FALSE.
• HasEntryPoint - generated as the HasEntryPoint attribute of the <ProcessFileEntry> element. Possible values are TRUE or FALSE.
• MaxChildTasks - generated as the MaxChildTasks attribute of the <ProcessEntry> element.
• MaxPrio - generated as the MaxPrio attribute of the <ProcessEntry> element.
• MaxThreads - generated as the MaxThreads attribute of the <ProcessEntry> element.
• PoolName - generated as the PoolName attribute of the <ProcessFileEntry> element.
• ResourceName - generated as the ResourceName attribute of the <ProcessMapEntry> element.
• UsePool - generated as the UsePool attribute of the <ProcessFileEntry> element. Possible values are TRUE or FALSE.
• VirtAddr - generated as the VirtAddr attribute of the <ProcessMapEntry> element.
Application Part toolbar button, and then click inside a
Partition Part. You are prompted to specify the name of the application. When you create an Application Part on a Partition Part, the profile creates the following items in the model: