1 Modelio Metamodel
Welcome to the Modelio Metamodel User Guide! The Modelio metamodel contains the most accurate description of the information managed by Modelio, as well as its definition and links. This user guide describes all predefined classes (Modelio metaclasses), and constitutes a working base for programmers and MDA Modeler users wishing to implement new services based on the metamodel (such as model transformation, code or documentation generation, metrics calculation or model requests). So what exactly is a metamodel? A metamodel is quite simply the model of a model, and the Modelio metamodel provides a detailed description of the model supported by Modelio. The Modelio tool is built using automated model transformation and code generation techniques, based on the presented metamodel. All its component elements (model dialog boxes, graphic editors, model manager, ...) are deduced from the metamodel, meaning that you have here the model of the actual model of Modelio itself. Within the Modelio metamodel, each metaclass is documented by a description of its attributes and relationships going to and from it. The names used in the Modelio metamodel are exactly those that must be used when working with the metamodel (attribute names, names of the roles concatenated with those of the opposite classes, and class names). The services provided by each metaclass are also presented. In addition, element composition graphs are provided, thereby illustrating the way in which new instances are created. This Modelio metamodel corresponds to the first iteration of UML 2.0 implementation. Modelio will progressively implement all UML 2.0 semantics. The semantics of the models supported remain the same. However, the metamodel corresponds to Modelio's implementation of the UML model. Correspondence is generally simple and straightforward, and differences are the result of backward compatibility, the single generalization constraint within Modelio, and a pragmatic vision of the best way to support UML. Softeam, one of the main contributors to the definition of the UML standard, knows UML's strong and weak points, as well as those areas where compromises have led to intermediary proposals within the standard, and is therefore ideally positioned to implement a useful solution.
TagParameterPinSubstitutionInterruptibleActivityRegionTransitionPartDecompositionMessageStateInvariantNodeFinalNodeAbstractPseudoStatePackagePackageImportStructuredActivityNodeInteractionFragmentObjectNodeRequiredInterfaceGateForkJoinNodeGeneralClassInterfaceLinkStateMachineTemplateParameterLinkEndLoopNodeNoteObjectFlowTaggedValueInitialNodeMessageFlowInputPinOperationStateVertexManifestationPortGeneralizationInterfaceRealizationGeneralOrderingFeatureUsageUseCaseModelElementProjectInstanceProvidedInterfaceExtensionPointUseCaseDependencySignalLifelineStereotypeInteractionOperandInteractionUseOpaqueBehaviorRaisedExceptionOutputPinNoteTypePackageMergeDurationConstraintTemplateParameterSubstitutionFlowFinalNodeInformationItemInteractionOpaqueActionNameSpaceSendSignalActionOccurrenceSpecificationParameterMessageEndModelTreeStateInternalTransitionTemplateBindingInstanceNodeExecutionOccurenceSpecificationTagTypeExecutionSpecificationEventEnumerationLiteralEnumerationElementRealizationElementImportElementDependencyDecisionMergeNodeDataTypeDataStoreNodeDataFlowControlNodeControlFlowConstraintConnectorEndConnectorConditionalNodeComponentCommunicationNodeCommunicationMessageCommunicationInteractionCommunicationChannelCombinedFragmentCollaborationUseCollaborationClauseClassifierClassAssociationClassCentralBufferNodeCallOperationActionCallBehaviorActionCallActionBindingBindableInstanceBehaviorParameterBehaviorAttributeLinkAttributeAssociationEndAssociationArtifactActorActivityPartitionActivityParameterNodeActivityNodeActivityGroupActivityFinalNodeActivityEdgeActivityActionActivityAcceptTimeEventActionAcceptSignalActionAcceptChangeEventActionAcceptCallEventActionAbstraction
Package
Summary