Model evolution and system evolution

In this paper we define an evolution mechanism with formal semantics using the metamodeling methodology [Geisler et al.98] based on dynamic logic. A remarkable feature of the metamodeling methodology is the ability to define the relation of intentional and extensional entities within one level, allowing not only for the description of structural relations among the modeling entities, but also for a formal definition of structural constraints and dynamic semantics of the modeled entities. While dynamic semantics on the extensional level means run-time behavior, dynamic semantics on intentional level describes model evolution in the system life cycle.Eje: Ingeniería de softwareRed de Universidades con Carreras en Informática (RedUNCI

Model evolution and system evolution

In this paper we define an evolution mechanism with formal semantics using the metamodeling methodology [Geisler et al.98] based on dynamic logic. A remarkable feature of the metamodeling methodology is the ability to define the relation of intentional and extensional entities within one level, allowing not only for the description of structural relations among the modeling entities, but also for a formal definition of structural\nconstraints and dynamic semantics of the modeled entities. While dynamic semantics on the extensional level means run-time behavior, dynamic semantics on intentional level describes model evolution in the system life cycle

DoMoRe – A recommender system for domain modeling

Domain modeling is an important activity in early phases of software projects to achieve a shared understanding of the problem field among project participants. Domain models describe concepts and relations of respective application fields using a modeling language and domain-specific terms. Detailed knowledge of the domain as well as expertise in model-driven development is required for software engineers to create these models. This paper describes DoMoRe, a system for automated modeling recommendations to support the domain modeling process. We describe an approach in which modeling benefits from formalized knowledge sources and information extraction from text. The system incorporates a large network of semantically related terms built from natural language data sets integrated with mediator-based knowledge base querying in a single recommender system to provide context-sensitive suggestions of model elements

Model-based Semantic Conflict Analysis for Software- and Data-Integration Scenarios

The semantic conflict analysis, which is the focus of this technical report, is an approach to automate various design-time verification activities which can be applied during software- or data-integration processes. Specifically, the aspects of semantic matching of business processes and the underlying IT infrastructure as well as of technical aspects of the composite heterogeneous systems will be investigated. The report is part of the BIZYCLE project, which examines applicability of model-based methods, technologies and tools to the large-scale industrial software and data integration scenarios. The semantic conflict analysis is thus part of the overall BIZYCLE conflict analysis process, comprising of semantic, structural, communication, behavior and property analysis, aiming at facilitating and improving standard integration practice. Therefore, the project framework will be briefly introduced first, followed by the detailed semantic annotation and conflict analysis descriptions, and further backed up with the semantic conflict analysis motivation/illustration scenario

Integrating object-oriented modeling techniques with formal specification techniques

The increasing complexity of software systems makes their development complicated and error prone. A widely used and generally accepted technique in software engineering is the combination of different models (or views) for the description of software systems. The primary benefit of this approach is to model only related aspects (Iike structure or behavior). Using different models cIarifies different important aspects of the system, but it has to be taken into consideration that these models are not independent and they are semantically overlapping.\nThe models constitute the fundamental base of information upon which the problem domain experts, the analysts and the software developers interact. Thus, it is of a fundamental importance that it clearly and accurately expresses the essence of the problem. On the other hand, the model construction activity is a critical part in the development process.\nSince models are the result of a complex and creative activity, they tend to contain errors, omissions and inconsistencies. Model verification is very important, since errors in this stage have an expensive impact on the following stages of the software development process.Eje: Teorí

Integrating object-oriented modeling techniques with formal specification techniques

The increasing complexity of software systems makes their development complicated and error prone. A widely used and generally accepted technique in software engineering is the combination of different models (or views) for the description of software systems. The primary benefit of this approach is to model only related aspects (Iike structure or behavior). Using different models cIarifies different important aspects of the system, but it has to be taken into consideration that these models are not independent and they are semantically overlapping. The models constitute the fundamental base of information upon which the problem domain experts, the analysts and the software developers interact. Thus, it is of a fundamental importance that it clearly and accurately expresses the essence of the problem. On the other hand, the model construction activity is a critical part in the development process. Since models are the result of a complex and creative activity, they tend to contain errors, omissions and inconsistencies. Model verification is very important, since errors in this stage have an expensive impact on the following stages of the software development process.Eje: TeoríaRed de Universidades con Carreras en Informática (RedUNCI

Model evolution and system evolution

In this paper we define an evolution mechanism with formal semantics using the metamodeling methodology [Geisler et al.98] based on dynamic logic. A remarkable feature of the metamodeling methodology is the ability to define the relation of intentional and extensional entities within one level, allowing not only for the description of structural relations among the modeling entities, but also for a formal definition of structural constraints and dynamic semantics of the modeled entities. While dynamic semantics on the extensional level means run-time behavior, dynamic semantics on intentional level describes model evolution in the system life cycle.Eje: Ingeniería de softwareRed de Universidades con Carreras en Informática (RedUNCI

Metamodels and Transformations for Software and Data Integration

Metamodels define a foundation for describing software system interfaces which can be used during software or data integration processes. The report is part of the BIZYCLE project, which examines applicability of model-based methods, technologies and tools to the large-scale industrial software and data integration scenarios. The developed metamodels are thus part of the overall BIZYCLE process, comprising of semantic, structural, communication, behavior and property analysis, aiming at facilitating and improving standard integration practice. Therefore, the project framework will be briefly introduced first, followed by the detailed metamodel and transformation description as well as motivation/illustration scenarios

Disruption of ERBB2IP Is not Associated with Dystrophic Epidermolysis Bullosa in Both Father and Son Carrying a Balanced 5;13 Translocation

Mutations in the type VII collagen gene (COL7A1) cause autosomal recessive and autosomal dominant inherited dystrophic epidermolysis bullosa (DEB). We report a family with three individuals who present blistering, scarring, hypo- and hyperpigmentation, and nail dystrophy suggestive for DEB. Whereas father and son carry a 5;13 translocation, the daughter shows a normal karyotype. Segregation analysis revealed that all affected family members inherited the same COL7A1 allele. Mutation analysis disclosed a heterozygous missense mutation, c.6227G>A (p.G2076D), in COL7A1 in all affected individuals. Delineation of the translocation breakpoints showed that the ERBB2IP (erbb2 interacting protein or Erbin) gene is disrupted in 5q13.1 and GPC6 in 13q32. GPC6 encodes glypican 6 belonging to a family of cell surface heparan sulfate proteoglycans. The binding partners of Erbin, BP230 (BPAG1) and the integrin β4 subunit, both involved in hemidesmosome (HD) function, and the presence of Erbin in HD suggested that it plays a role in establishment and maintenance of cell-basement membrane adhesions. However, loss of function of one ERBB2IP copy or expression of a putative novel ERBB2IP fusion protein did not apparently modulate the DEB phenotype in both translocation patients. Nonetheless, one cannot yet exclude that ERBB2IP is a candidate for human blistering disorders such as epidermolysis bullosa