Integrations (PTC products, 3rd party products and code) > Code integration (Ada, ARINC 653, C, C#, C++, IDL, Java, SQL and VB) > ARINC 653 for PikeOS 653 code > ARINC 653 for PikeOS 653 profile items > Process part (ARINC for PikeOS code)
  
Process part (ARINC for PikeOS code)
A process part represents the use of a process within an Application. Process Parts are scoped to Applications. Process Parts can be created explicitly on Applications or implicitly via Application Parts. Processes are created automatically when a Process Part is created.
Create a Process Part on a Configuration Diagram: click the Process Part toolbar button, and then click within an Application Part. You are prompted to specify the name of the process.
When you create a Process Part on an Application Part, the profile creates the following items in the model:
A Process Part on the Configuration Diagram.
A Process item that types the Process Part. The Process item is scoped to the Application Project that is associated with the Application Part.
For the associated Process that is created, specify the BasePriority, Deadline, EntryPoint, Period, StackSize and TimeCapability properties of the Process through the Process' Property Pages: on the Process' Property Pages, click the Process tab, and then set the tagged value of each property. Note that the EntryPoint property references the entrypoint operation that is created on the Process.
When shown on a Configuration Diagram a Process Part's notation is as follows:
You can view all the Process Parts in the model through the Process Part folder in the ARINC 653 Profile pane.
A Process Part is based on a UML Attribute.
The following sections provide information about how a Process Part is used in the model.
Shown on these diagrams
Configuration Diagram
ARINC properties
None.
* 
Note that properties can be set on the Process Part's associated Process.