UML static and Dynamic Models

UML static and Dynamic Models

1. RELATED WORKS

   • The meaning of the meta model is the implementation of modeling and models facilitate handling of UML tools
   • no need to redesign the scheme change in the model structure or behavior
   • This is next to the ' Object- at -a-time ' ' queries in a highly complex logical scheme they are much easier to implement with EAV with conventional structure
   • By mapping static and behavioral elements of the UML metamodel in the abstract state machine (ASM )

2. THE ENTITY-ATTRIBUTE-VALUE CONCEPT

   • EAV is widely used in the medical and clinical information system as a general purpose means of knowledge representation
   • Unlike the conventional database the EAV design does not support or conform to rules of database normalization
   • For convenience, atomic data describing an entity may also be represented within an element's open-tag as attribute-value pairs, each component of a pair being separated by an equal sign

3. MODEL AND METAMODEL REPRESENTATION

   • Normally, metamodels sitting in a level higher than it is instance model
   • At check-in time they obtain boarding cards if there are still seats available. Due to overbooking of flights they may be rescheduled on later flights.
   • The State Machine diagram is a UML diagram that shows systems behavior and dynamic characteristics
   • Another issue is that a relational schema It requires certain attributes for each table are declared to be the key for the table
   • Structure-oriented queries are important in Modelling tool applications. For example, a state machine can have an initial state (a state with no transitions in) or a final state (a state with no transitions out). These states can be identified respectively by the following two views
   • Some modeling languages allow constraints to be represented by annotations on static model, but it may not tell a designer how to concretely represent a design

4. INTEGRATION BETWEEN STATIC AND DYNAMIC MODELS

   • The structure that can include several attributes separated by “.” to address different areas in the representation of the dynamic models and static metamodels.
   • Diferentes escenarios pueden ser implementadas en el modelo instantánea dinámica se puede abordar sin su estructura estática metamodelo o viceversa.

5. RESULTS AND DISCUSSION

   • The different in context can include the structural and behavioral characteristics beside the consideration of their different level of abstractions.
   • a integración y la coherencia entre modelos que presenta el mismo tipo de punto de vista es uno de los intereses clave de tener uno estático y modelos dinámicos en el mismo repositorio
   • The limitation of this approach is inherited from EAV representation drawbacks
   • Consequently, performing complex attribute-centric queries, which are based on values of attributes, and returning a set of objects is both significantly less efficient as well as technically more difficult

6. CONCLUSION AND FUTURE WORK

   • The paper focused on the representation and integration of structural and behavioral models under the MDA context
   • Both static and its dynamic model represented in a single repository
   • Also it intends in the text using this approach representation platform for the support of a transformation to a particular platform executable code.