The IFML metamodel is divided in three packages: the Core package, the Extension package and the DataTypes package. The Core package contains the concepts that build up the interaction infrastructure of the language in terms of InteractionFlowElements, InteractionFlows and Parameters. Core package concepts are extended by concrete concepts in the Extension package with more complex behaviors. The DataTypes package contains the custom data types defined by IFML. The IFML metamodel uses the basic data types from the UML metamodel, specializes a number of UML metaclasses as the basis for IFML metaclasses, and presumes that the IFML ContentModel is represented in UML.. Enumeration specifying the different possible directions of parameters. An input Parameter allows an InteractionFlowElement to receive one or more values through an incoming NavigationFlow or DataFlow. in A Parameter of kind input-output allows for both behaviours. out An output Parameter allows an InteractionFlowElement to expose one or more values through an outgoing NavigationFlow or DataFlow. inout Direction Enumeration specifying the different system event types. System event of time kind, such as absolute time event, periodic time event and time out event time System special condition event such as data base connection loss, network loss, etc. specialCondition Kind of Event triggered by a business operation completion. actionCompletion SystemEventType Enumeration specifying the different scope levels for ContextVariables Scope of the ContextVariable is the application ApplicationScope Scope of the ContextVariable is the user session SessionScope Scope of the ContextVariable is the ViewContainer (for instance, the Web page or the window) ViewContainerScope ContextVariableScope DataTypes An InteractionFlow is a directed connection between ViewElements or ViewElements and Actions, which enables communication between them by means of Parameter passing. InteractionFlows are divided into NavigationFlows and DataFlows. NavigationFlows cause navigation or change of focus to the target element and Parameter passing, while DataFlows cause only Parameter passing to the target element. Group of parameters that are passed to the target interaction flow element by following the InteractionFlow. parameterBindingGroup public composite Source InteractionFlowElement of the InteractionFlow. sourceInteractionFlowElement public Target InteractionFlowElement of the InteractionFlow. targetInteractionFlowElement public InteractionFlow true An InteractionFlowExpression is used to determine which of the InteractionFlows will be followed as a consequence of the occurrence of an Event. When an Event occurs and it has no InteractionFlowExpression, all the InteractionFlows associated with the event are followed. At least two InteractionFlows must be associated with an InteractionFlowExpression. An InteractionFlowExpression uses the ViewElement Parameter values and the InteractionFlows for the evaluation of the expression. InteractionFlows for which the expression is evaluated. 2 * interactionFlow public InteractionFlowExpression A SystemEvent is an Event produced by the system, which triggers a computation reflected in the user interface. Examples of SystemEvents are time events, which are triggered after an elapsed frame of time, or system special conditions events, such as a database connection loss event. Expressions that determines when or under what conditions the SystemEvent should be triggered. * triggeringExpressions public composite Determines the kind of SystemEvent. type public SystemEvent A ParameterBinding determines how data flow between components. A ParameterBinding connects an output Parameter of a source InteractionFlowElement with an input Parameter of a target InteractionFlowElement. When an Event is triggered, InteractionFlows are followed and Parameter values flow from source InteractionFlowElements to target InteractionFlowElements, according to how they have been bound. Output Parameter of the source InteractionFlowElement that participates in the ParameterBinding. sourceParameter public Input Parameter of the target InteractionFlowElement that participates in the ParameterBinding. targetParameter public ParameterBinding Outgoing InteractionFlows. A_interactionFlowElement_outInteractionFlow An ActionEvent is an Event that may be triggered by an Action such as a normal termination event or exception event. ActionEvent The DomainModel is a model that contains content elements that ViewComponents may access to retrieve information, process it, and show it to the user. The DomainModel also stores information captured from the user. The DomainModel is presumed to be represented in UML and therefore consists of a set of UML model elements . References to the DomainElements of the DomainModel. * domainElements public DomainModel Composite association to the elements of the ContentModel. References to the elements of the DomainModel. domainModel public A_contentModel_element ViewPoints of the InteractionFlowModel. ifmlModel public A_ifmlModel_interactionFlowModelViewPoint A NamedElement is an Element that requires a name for easy visual identification in diagrams or for being handled as a named variables in a concrete textual syntax. Element name. name public NamedElement true PortDefinitions represent interaction points with a ModuleDefinition. They are defined within a ModuleDefinition. They hold Parameters, for transferring values to and from the ModuleDefinition. An input PortDefinition has outgoing InteractionFlows to the inside of the Module. An output PortDefinition has incoming InteractionFlows from the inside of the Module. Modules that reference a ModuleDefinition may comprise Ports, which in turn reference the corresponding PortDefinitions. Set of Ports referencing the current PortDefinition in some Modules implementing the ModuleDefinition within which the current PortDefinition is defined. * ports public PortDefinition A ContentBinding allows the system to access a given source of content. A content source access may be done through a DataBinding or a DynamicBehavior of a DomainModel element. self.viewElementEvent -> isEmpty() OCL2.0 noViewElementEvent URI used to identify or locate the resource from which the content may be obtained. uniformResourceIdentifier public ContentBinding true InteractionFlowModelElements contained by the Module. module public A_module_interactionFlowElement Nested ViewComponentParts A_parentViewComponentPart_subViewComponentPart ViewElements are elements of the user interface that display content. ViewElements are divided into ViewContainers and ViewComponents. ViewContainers are aggregations of other ViewContainers and/or ViewComponents. ViewElementEvents contained by the ViewElement. * viewElementEvents public composite Reference to an ActivationExpression whose evaluation result determines whether the ViewElement is active or inactive. If no ActivationExpression is given, by default the ViewElement is active. activationExpression public ViewContainer of the current ViewElement. viewContainer public ViewElement An Expression is an element that, in a given context, evaluates to a single instance, a set of instances. or an empty result. An Expression must be side effect free. Specific expression types, such as BooleanExpression, etc., specialize this concept. Language in which the Expression is written, e.g. OCL, Java, etc. language public Code of the Expression. body public Expression true DynamicBehavior represents the binding of the system with a service or operation, which may be invoked in order to carry out business logic or return content. self.behavioralFeature -> notEmpty() xor self.behavior -> notEmpty() OCL2.0 eitherBehavioralFeatureOrBehavior BehavioralFeatureConcept representing a procedure, method, function etc, that may be invoked by a ViewComponent to carry out business logic or obtain content. behavioralFeatureConcept public Representing a procedure, method, function etc, that may be invoked by a ViewComponent to carry out business logic or obtain content. behaviorConcept public DynamicBehavior ContextDimensions the user context must satisfy to have access to one or more ViewPoints. context public A_context_contextDimension The complete model that describes the interaction of the user with the system. ifmlModel public A_ifmlModel_interactionFlowModel InteractionFlowExpression determining the InteractionFlows to be followed after the occurrence of the Event. event public A_event_interactionFlowExpression Incoming InteractionFlows. A_interactionFlowElement_inInteractionFlow A Viewpoint is a reference to an interrelated set of InteractionFlowModelElements, which as a whole define a functional portion of the system. The purpose of a Viewpoint is to facilitate the comprehension of a complex system, to allow or disallow access to the system by a specific UserRole, or to adapt the system to a specific context change. InteractionFlowModelElements that build up this Viewpoint. * interactionFlowModelElements public Application context that determines the Viewpoint to be used. context public Viewpoint Reference to a BooleanExpression whose evaluation result if the ViewContainer is active or inactive. The default expression is true. viewElement public A_viewElement_activationExpression Constraints applied to the Element. element public A_element_constraint Port that collects the InteractionFlows and parameters going out from the module. module public A_module_outputPorts A DataFlow is a kind of InteractionFlow used for passing context information between InteractionFlowElements. DataFlows are triggered by NavigationFlows causing Parameter passing but no navigation. not self.targetInteractionFlowElement.oclIsTypeOf(IFML::Core::Event) OCL2.0 targetNotInstanceOfEvent DataFlow A ViewComponentPart is an InteractionFlowElement that may not live outside the context of ViewComponent. A ViewComponentPart may trigger Events and have incoming and outgoing InteractionFlows. Events that this ViewComponentPart may trigger. * viewElementEvents public composite Reference to an ActivationExpression whose evaluation result determines whether the ViewComponentPart is active or inactive. If no ActivationExpression is given, by default the ViewComponentPart is active. activationExpression public Parent ViewComponentPart. parentViewComponentPart public Nested ViewComponentParts. * subViewComponentParts public composite ViewComponentPart Expression that determines how to access the content. dataBinding public A_dataBinding_conditionalExpression A ViewContainer is an element of the interface that aggregates other ViewContainers and/or ViewElements displaying content. self.isXor implies self.viewElements -> select(c|c.oclTypeOf(ViewContainer) and c.asOclTypeOf(ViewContainer).isDefault) -> size()=1 OCL2.0 xorMustHaveADefaultParent self.viewContainer and self.viewContainer.isXor OCL2.0 defaultMustHaveXorParent If true, the ViewContainer is directly reachable from any ViewElement from any ViewElement contained, directly or indirectly, in the same ViewContainer. It represents an implicit link between all the other ViewElements and the ViewContainer. isLandmark public If true, the ViewContainer will be presented to the user when its enclosing ViewContainer is accessed. This attribute is relevant when this vViewContainer shares the same parent ViewContainer with other ViewContainers. isDefault public If true, the contained ViewElements of thisViewContainer will be presented to the user only one at the time, as the user interacts with the system. isXOR public The ViewElements owned by the ViewContainer. * viewElements public composite * actions public composite ViewContainer Composite relation of ParameterBindings parameterBindingGroup public A_parameterBindingGroup_parameterBinding ActivationExpressions are used by ViewElements, Events or ViewComponentParts to determine if they are enabled or not. An ActivationExpression is a BooleanExpression such that, if it evaluates to true, the element is active, otherwise the element is inactive. ActivationExpressions use Parameter values for the expression evaluation. ActivationExpression An InteractionFlowModel aggregates all the elements modeling interaction with the user. Elements of the InteractionFlowModel. * interactionFlowModelElements public composite InteractionFlowModel ContextDimensions are dimensions of the Context that represent not only the user’s identity and preferences, but also the interaction environment of the system. ContextDimension has the specializations UserRole, Device, and Position. When the user context satisfies all required ContextDimensions, access is granted to the ViewElements of the Viewpoint and to the Events that may be triggered on them. ContextDimension An IFMLModel is the top-level container of all other elements in an IFML model. All model elements are grouped into two submodels, the InteractionFlowModel and the DomainModel. An IFMLModel may also contain a number of Viewpoints of the InteractionFlowModel. The complete model that describes the interaction of the user with the system. interactionFlowModel public composite Model that holds the business model of the system being described in IFML. domainModel public composite Viewpoints of the InteractionFlowModel. * interactionFlowModelViewpoint public composite IFMLModel Interactions flows for which the expression is evaluated. interactionFlowExpression public A_interactionFlowExpression_interactionFlow A ModuleDefinition is a fully functional collection of user InteractionFlowModelElements and their corresponding Actions, which may be reused for improving IFML model maintainability. ModuleDefinitions can be aggregated in a hierarchical structure of ModulePackages. ModuleDefinitions may comprise PortDefinitions. A ModuleDefinition receives Parameter values from outside and provides Parameter values to the outside. ModuleDefinitions exchange Parameters by mean of input and output PortDefinitions. InteractionFlowModelElements contained in a Module may not be shared or referenced by other Modules or by the main InteractionFlowModel. A ModuleDefinition may comprise a reference to a BPMN Activity (meaning that the Module implements that Activity). Reuse of ModuleDefinition is obtained by adding Modules referencing that ModuleDefinition in IFML models.s. Ports that distributes InteractionFlows and Parameters coming into the Module. * inputPorts public composite Ports that collect the InteractionFlows and Parameters going out from the Module. * outputPorts public composite InteractionFlowModelElements contained by the Module * interactionFlowModelElement public composite The set of Modules that are defined in the IFML model and reference the current ModuleDefinition. * modules public Reference to a process activity (e.g., a BPMN Activity). If present, the current module is describes the technical implementation of the process activity. activityConcept public ModuleDefinition A BooleanExpression is a kind of Expression that evaluates to true or false. BooleanExpression InteractionFlowElements represent pieces of the system such as Actions, Events, ViewElements, and ViewComponentParts, which participate in user interaction flows through InteractionFlow connections. Usually there is a flow of Parameter values between InteractionFlowElements as a consequence of user, action, or system events. Parameters contained by the InteractionFlowElement. * parameters public composite Outgoing InteractionFlows. * outInteractionFlows public composite Incoming InteractionFlows. * inInteractionFlows public InteractionFlowElement true VisualizationAttribute determining the StructuralFeatures that should be shown to the user, such as a data base column or an XML element or attribute. dataBinding public A_dataBinding_visualizationAttribute Parts of the ViewComponent. viewComponent public A_viewComponent_viewComponentPart Elements of the InteractonFlowModel interactionFlowModel public A_interactionFlowModel_interactionFlowModelElement Model describing the domain concepts and behaviors used in the user interaction modeled by the IFML model. ifmlModel public A_ifmlModel_contentModel Composite relation of ViewElements hold by the current ViewContainer. A_viewContainer_viewElement InteractionFlowModelElements that build up this ViewPoint. * viewpoints public A_viewPoint_interactionFlowModelElement Annotations, comments, tags, etc., owned by the element. element public A_element_annotation Port that collects InteractionFlows and parameters coming to the module. module public A_inputPorts_module An Action is an InteractionFlowElement that represents a piece of business logic triggered by an Event. Actions may reference behavior models describing the actual business logic to be performed. Actions may trigger different Events called ActionEvents as the result of business logic computation termination or the occurrence of exceptions. Actions may reside on the server or on the client side. If no ActionEvent (and corresponding outgoing flow) is specified, IFML assumes as default an ActionEvent and NavigationFlow that lead back to the ViewComponent or ViewContainer from which the navigation to the Action was launched. self.actionEvent->forAll(e | e.navigationFlow->forAll(nf | not nf.targetInteractionFlowElement.oclIsTypeOf(IFML::Core::Action))) OCL2.0 actionsCannotCallActions Events triggered by the Action. * actionEvents public composite The business logic to be carried out by the Action. dynamicBehavior public The ViewContainer that contains the current Action. viewContainer public Action Events triggered by the Action. action public A_action_actionEvent Reference to a BooleanExpression whose evaluation result determines if the ViewComponentPart is active or inactive. The default expression is true. viewComponentPart public A_activationExpression_viewComponentPart A NavigationFlow represents navigation or change of ViewElement focus, the triggering of Action processing, or a SystemEvent. NavigationFlows are followed when Events are triggered. NavigationFlows connect Events of ViewContainers, ViewComponents, ViewComponentParts, or Actions with other InteractionFlowElements. When a NavigationFlow is followed, Parameters may be passed from the container of the source Event to the target InteractionFlowElement through ParameterBindings. When a NavigationFlow is triggered, a corresponding set of DataFlows may be triggered, at the purpose of carrying further parameters to the target InteractionFlowElement. The DataFlows that are triggered are all the ones having some parameter values available and pointing to the same target as the current NavigationFlow. NavigationFlow Group of parameters that are passed to the target interaction flow element by following the InteractionFlow. interactionFlow public A_interactionFlow_parameterBindingGroup A ParameterBindingGroup aggregates all the ParameterBindings of an InteractionFlow. The ParameterBindings composing the ParameterBindingGroup. * parameterBindings public composite ParameterBindingGroup Element is the base class for the representation of all model elements in an IFML model. String for unequivocally identifying a model element. id public Constraints applied to the Element. * constraints public composite Annotations, comments, tags, etc., owned by the Element * annotations public composite Element true A Constraint is a BooleanExpression that may be defined for any model Element in order to restrict its behavior. Constraint ViewElementEvents contained by the ViewElement A_viewElement_viewElementEvent A ViewComponent is an element of the user interface that displays content or accepts input. A ViewComponent may be bound to a ContentBinding through its association with ViewComponentPart. Parts of the ViewComponent. * viewComponentParts public composite ViewComponent A Parameter is a typed name, whose instances hold values. Parameters are held by InteractionFlowElements, i.e., ViewElements, ViewComponentParts, Ports, and Actions. Parameters flow between InteractionFlowElements when Events are triggered. Parameters may correspond to elements of the user interface (for instance, fields in a form), determining whether the element of the user interface is read-only or modifiable. Parameters have a direction property, which can be input (in), output (out) or input-output (inout). Default direction is input. The scope of a Parameter (i.e., the model space where it can be used or referenced) is the InteractionFlowElement that holds the Parameter, plus the incoming and outgoing InteractionFlows. This means that: if the parameter is held by a ViewComponent, it can be referenced only within the ViewComponent itself and the contained ViewComponentParts (plus the incoming and outgoing InteractionFlows); if the parameter is held by a ViewContainer, it can be referenced within the ViewContainer itself, and within the contained ViewContainers, ViewComponents, and ViewComponentParts (plus the incoming and outgoing InteractionFlows).s). Determines if the parameter is input, output or input-output. direction public defaultValue public Parameter DataBinding represents the binding of the system with an instance of an element of the DomainModel such as a table, an object, an XML file etc. ConditionalExpressions that determine how to access the content. * conditionalExpression public composite VisualizationAttributes that determine the StructuralFeatures that should be shown to the user, such as a data base column or an XML element or attribute. * visualizationAttribute public composite Reference to the ContextVariable that makes use of the DataBinding, * dataContextVariables public A concept specifying the data structure to which the ViewComponent is bound, such as a UML class, a table in a relational data base or an XML file. domainConcept public DataBinding Parameters contained by the InteractionFlowElement. interactionFlowElement public A_interactionFlowElement_parameter A ConditionalExpression is a predefined query expression associated with a DataBinding. When a ConditionalExpression is present, the DataBinding is queried by applying the query in the ConditionalExpression for retrieving content.t. ConditionalExpression Parameter of the target InteractionFlowElement that participates in the binding. parameterBinding public A_parameterBinding_trgtParameter Application context that determines the ViewPoint to be used. viewpoint public A_viewPoint_context The Context is a runtime aspect of the system that determines how the user interface should be configured. A Context has several dimensions that represent not only the user’s identity and preferences, but also the interaction environment of the system. Context is composed of one or more ContextDimensions and may comprise ContextVariables. ContextDimensions the user context must satisfy to have access to one or more Viewpoints. * contextDimensions public composite ContextVariable – set of ContextVariables whose values are relevant for the current Contextt * contextVariables public composite Context Parameter of the source InteractionFlowElement that participates in the binding. parameterBinding public A_parameterBinding_srcParameter Events that this ViewComponentPart may trigger. viewComponentPart public A_viewElementEvents_viewComponentPart The VisualizationAttributes used by a ViewComponent to determine the features obtained from a DataBinding that may be shown to the user, such as a data base column or an XML element or attribute. A feature is represented using a UML::StructuralFeature. featureConcept public VisualizationAttribute An Event is an occurrence that can affect the state of the application. Events can be ThrowingEvent (events that are thrown by the modeled interaction) or CatchingEvent (events that are captured by the modeled interaction and used as triggers causing navigation and/or Parameter value passing between InteractionFlowElements. self.outInteractionFlow -> size() <= 1 and self.inInteractionFlow -> size() <= 1 OCL2.0 onlyOneInAndOutFlow Reference to an ActivationExpression whose evaluation result determines if the Event is active or inactive. If no ActivationExpression is given, the default is that the Event is active. activationExpression public InteractionFlowExpression determining the InteractionFlows to be followed after the occurrence of the Event. interactionFlowExpression public composite Event Reference to a BooleanExpression whose evaluation result determines if the Event is active or inactive. The default expression is true. event public A_event_activationExpression An InteractionFlowModelElement is the top-level class that generalizes all the elements that are part of an InteractionFlowModel. InteractionFlowModelElement true A ViewElementEvent represents a user interaction Event, which may be triggered by ViewElements (ViewContainers and ViewComponents). viewElement public ViewElementEvent An Annotation represents a comment, note, explanation, or other type of documentation that can be attached to any Element. Annotation text. text public Annotation Expression that determines when the event is should be triggered or under which conditions. systemEvent public A_systemEvent_triggeringExpression action public A_Action_dynamicBehavior A_viewContainer_actions A ModulePackage is a container of ModuleDefinitions. ModulePackages can be nested in arbitrarily deep hierarchical structure. * modularizationElements public composite ModulePackage A ModularizationElement is an abstract concept that represents both ModulePackages and ModuleDefinitions. modulePackage public ModularizationElement A_modulePackage_modularizationElements A Module is a named reference to a ModuleDefinition, which allows reuse of the model part specified in the ModuleDefinition. Module has a reference to the relevant ModuleDefinition and may be associated with a set of Ports, which in turn reference the corresponding PortDefinitions. For every PortDefinition in the ModuleDefinition there shall be 0 or 1 Ports in each corresponding Module. An input Port (i.e., a Port referencing an input PortDefinition) has incoming InteractionFlows from the outside of the Module, for receiving input Parameters. An output Port has outgoing InteractionFlows to the outside of the Module, for shipping output Parameters. self.moduleDefinition.portDefinitions -> forAll(pd | pd.ports -> select(p|p.module = self) -> size() = 1) OCL2.0 onlyOnePortPerPortDefinition The ModuleDefinition that is instantiated by the current Module. moduleDefinition public Ports that collect InteractionFlows and Parameters incoming or outgoing from the Module. * ports public Module A_moduleDefinition_modules A Port is an interaction point between a Module and the surrounding model within which it is defined. Module is associated with a set of Ports, which in turn reference the corresponding PortDefinitions. An input Port (i.e., a Port referencing an input PortDefinition) has incoming InteractionFlows from the outside of the Module, for receiving input Parameters. An output Port has outgoing InteractionFlows to the outside of the Module, for shipping output Parameters. Reference to the PortDefinition that defines the interface of the current Port portDefinition public Module that contains the current Port module public Port A_portDefinition_ports A_module_ports A CatchingEvent is an occurrence that can affect the state of the application, by causing navigation and/or Parameter value passing between InteractionFlowElements. CatchingEvents may be produced by a user interaction (ViewElementEvent), by an action when it finishes its execution (ActionEvent), or by the system in the form of notifications (SystemEvent), or by a navigational jump (JumpEvent) in the model that reaches a LandingEvent. CatchingEvent A ThrowingEvent is an occurrence of event that is generated by the modeled application. Event occurences generated by ThrowingEvent can be captured by CatchingEvents. ThrowingEvent BPMNActivityConcepts are a specialization of ActivityConcept for representing the particular case of BPMN Activities. activity public BPMNActivityConcept ContextVariable is a name-value pair that allows to store information associated to the current Context. It can be a SimpleContextVariable, storing a primitive type value, or a DataContextVariable, referencing a DataBinding. context public scope public ContextVariable A_context_contextVariables SimpleContextVariable is a typed name-value pair that can be associated to the current Context. Allowed types are the primitive ones SimpleContextVariable DataContextVariable allows to associate a DataBinding to the current Context. Reference to the DomainModel concept used as ContextVariable. dataBinding public DataContextVariable A_dataContextVariable_dataBinding The DomainConcept represents a generic concept, class, entity of the DomainModel, which can be referenced in a DataBinding. Its purpose is to allow extensibility in terms of concepts from different modeling languages representing the DomainModel. Reference to the DataBinding in a ViewComponent that uses the current DomainConcept. dataBinding public DomainConcept FeatureConcept represents the generic attribute or property of a DomainModel element, which can be referenced as VisualizationAttribute. Placeholder in a DataBinding of the FeatureConcept to be visualized. visualizationAttribute public FeatureConcept BehaviorConcept represents the generic Behavior (for instance, a UML dynamic diagram) which can be referenced as DynamicBehavior in a ContentBinding. Placeholder in a ContentBinding of the Behavior to be executed by the Action or ViewComponent. dynamicBehavior public BehaviorConcept BehavioralFeatureConcept represents the generic BehavioralFeature of a DomainModel element (for instance, a Class method) which can be referenced as DynamicBehavior in a ContentBinding. Placeholder in a ContentBinding of the BehavioralFeature to be executed by the Action or ViewComponent. dynamicBehavior public BehavioralFeatureConcept A_visualizationAttribute_featureConcept A_dataBinding_domainConcept A_dynamicBehavior_behavioralFeatureConcept A_dynamicBehavior_behaviorConcept UMLBehavior represents a Behavior specified in UML (that is, a UML dynamic diagram) which can be referenced as DynamicBehavior in a ContentBinding. UML Behavior to be executed by the Action or ViewComponent. behavior public UMLBehavior umlBehavior public A_UMLBehavior_behavior UMLBehavioralFeature represents a BehavioralFeature specified in UML (typically, a UML method in a Class) which can be referenced as DynamicBehavior in a ContentBinding. UML BehavioralFeature to be executed by the Action or ViewComponent. behavioralFeature public UMLBehavioralFeature umlBehavioralFeature public A_UMLBehavioralFeature_behavioralFeature The UMLDomainConcept is a specific DomainConcept referring to a UML Classifier. Reference to the UML Classifier of the DomainModel that will be connected to a ViewElement through a DataBinding. classifier public UMLDomainConcept umlDomainConcept public A_UMLDomainConcept_classifier The UMLStructuralFeature is a specific FeatureConcept referring to a UML StructuralFeature. Reference to the UML element of the DomainModel. structuralFeature public UMLStructuralFeature umlStructuralFeature public A_UMLStructuralFeature_StructuralFeature ActivityConcepts are an abstract concept describing the idea of business action that can be implemented through an IFML ModuleDefinition. Typical examples could be BPMN Activities or Activities in UML Activity Diagrams The ModuleDefinition that implements the business process ActivityConcept. moduleDefinition public ActivityConcept A_moduleDefinition_activityConcept The DomainElement represents a generic element of the DomainModel, which can describe a concept, a property, a behavior, or a behavioral feature. It is a generic representative for classes DomainConcept, FeatureConcept, BehavioralFeatureConcept, BehaviorConcept DomainElement A_BPMNActivityConcept-activity References to the corresponding BPMNActivityConcepts. concept public Core An OnSubmitEvent triggers the Parameter passing of a ViewComponent to the target ViewElement or Action of its corresponding NavigationFlow. An OnSubmitEvent is typically found in Form ViewComponents. OnSubmitEvent A ValidationRule is a Constraint, which, when evaluated, determines if the content of a Field or group of Fields is valid or not. ValidationRule The List ViewComponent is used to display a list of DataBinding instances. When the List ViewComponent is associated with an Event, it means that each DataBinding instance displayed by the component may trigger the Event. The Event will in turn cause the passing of the Parameter values mapped to the DataBinding instance to a target InteractionFlowElement. self.viewComponentPart -> select(v | v.oclIsTypeOf(DataBinding)) -> size() = 1 OCL2.0 mustHaveOneDataBinding Events that represent the selection of a DataBinding instance of the List ViewComponent and the passing of the value as a Parameter. * selectEvent public composite List A Position is a ContextDimension representing the location and orientation of a device from which the application is accessed. A Position is associated with one or more ViewPoints (through the association between ViewPoint and Context). When the user context indicates having reached the location or orientation described by a Position, the ContextDimension is satisfied and access is granted to the ViewPoint elements and presented to the user. Position A UserRole is a ContextDimension that represents a role played by a human user or external system that accesses the application through its user interface. A UserRole is associated with one or more ViewPoints (trough the association between ViewPoint and Context). When the user context has the same user role as the one specified by the UserRole, the ContextDimension is satisfied and access is granted to the ViewPoint elements. UserRole A Slot is a value placeholder for a Field. When the Field is a SelectionField, its associated Slots contain the available selection options and the selected one. When the Field is a SimpleField, the Slot contains the Field value. A Slot value of a SimpleField and the Slots corresponding to the selected options of SelectionFields are copied to Parameters in order to be passed to other ViewElements or Actions when an Event is triggered. Slot An OnSelectEvent is a kind of Event that, when triggered, results in a selected value being passed as a Parameter to the target InteractionFlowElement of its associated NavigationFlow. OnSelectEvent A Field is a value-type pair whose value may be displayed to the user or serves as a mean for capturing input from the user. Fields are usually mapped to Parameters for passing their values to other InteractionFlowElements. There are two kinds of fields, SimpleFields and SelectionFields. Field true Event that represents the selection of a DataBinding instance of the List ViewComponent and the passing of the value as Parameter. index public A_index_selectEvent The Form ViewComponent represents input forms where user can submit information through Fields (SimpleFields or SelectionFields). It comprises at least one Field and typically at least one OnSubmitEvent. self.viewComponentPart -> select(v | v.oclIsTypeOf(Field)) -> notEmpty() OCL2.0 mustHaveAtLeastOneField Form A Device is a ContextDimension that represents any device such as desktop, laptop, smart phone, tablet, or any other device from which the application may be accessed. A Device is associated with one or more Viewpoints (through the association from Viewpoint to Context). When the user context specifies the same device as the one specified by Device, the ContextDimension is satisfied and access is granted to the Viewpoint elements. Device A SelectionField is a kind of Field that enables the selection of one or more values from the predefined set of values given in its Slots. If true, the SelectionField allows the selection of multiple values. isMultiSelection public SelectionField A SimpleField is a kind of Field that displays a value or captures a textual input from the user. A SimpleField also behaves as a Parameter,so that its value may be passed to other ViewElements or Actions. SimpleField A Details ViewComponent is used to display the details of a DataBinding instance. When the Details ViewComponent is associated with an Event, it means that the DataBinding instance displayed by the component may trigger the Event. The Event will in turn cause the passing of the Parameter values mapped to the DataBinding instance to a target InteractionFlowElement. select(v | v.oclIsTypeOf(DataBinding)) -> size() = 1 self.viewComponentPart -> select(v | v.oclIsTypeOf(DataBinding)) -> size() =1 OCL2.0 mustHaveOneDataBinding Details A Window is a special kind of ViewContainer used to model the concept of a window in IFML. If true, the Window will be rendered as a modal window. isModal public If true, the Window will be opened as a new window. isNewWindow public Window An OnLoadEvent is triggered by the system when a ViewElement is completely computed and rendered. OnLoadEvent A Menu is a special kind of ViewContainer used to model the concept of a menu of options in IFML. It cannot contain ViewComponents or sub-ViewContainers. self.viewElements -> select(e | e.oclIsTypeOf(ViewContainer) or e.oclTypeOf(ViewComponent) ) -> isEmpty() OCL2.0 CannotContainViewComponentOrContainer Menu A JumpEvent is a ThrowingEvent that, when launched, redirects the NavigationFlow entering the event to a referenced LandingEvent. Reference to the LandingEvent targeted by the JumpEvent. landingEvent public JumpEvent A LandingEvent is the destination of a JumpEvent. Reference to the JumpEvents targeting the current LandingEvent. * jumpingEvents public LandingEvent A_jumpEvent_landingEvent A SetContextEvent is launched every time a ContextVariable is set or assigned a new value. SetContextEvent Extensions IFML http://www.omg.org/spec/IFML/20140301 org.omg.xmi.nsPrefix ifml IFML