Integration of the Semantic Web and Model-Driven Software

Integration of the Semantic Web and Model-Driven Software

Fernando Silva Parreiras

Language: English

Pages: 249

ISBN: 1118004175

Format: PDF / Kindle (mobi) / ePub


The next enterprise computing era will rely on the synergy between both technologies: semantic web and model-driven software development (MDSD). The semantic web organizes system knowledge in conceptual domains according to its meaning. It addresses various enterprise computing needs by identifying, abstracting and rationalizing commonalities, and checking for inconsistencies across system specifications. On the other side, model-driven software development is closing the gap among business requirements, designs and executables by using domain-specific languages with custom-built syntax and semantics. It focuses on using modeling languages as programming languages.

Among many areas of application, we highlight the area of configuration management. Consider the example of a telecommunication company, where managing the multiple configurations of network devices (routers, hubs, modems, etc.) is crucial. Enterprise systems identify and document the functional and physical characteristics of network devices, and control changes to those characteristics. Applying the integration of semantic web and model-driven software development allows for

(1) explicitly specifying configurations of network devices with tailor-made languages,

(2) for checking the consistency of these specifications

(3) for defining a vocabulary to share device specifications across enterprise systems. By managing configurations with consistent and explicit concepts, we reduce cost and risk, and enhance agility in response to new requirements in the telecommunication area.

This book examines the synergy between semantic web and model-driven software development. It brings together advances from disciplines like ontologies, description logics, domain-specific modeling, model transformation and ontology engineering to take enterprise computing to the next level.

Face Processing: Advanced Modeling and Methods

Internetworking with TCP/IP, Volume 1: Principles, Protocols, and Architecture (6th Edition)

Ontologies for Software Engineering and Software Technology

Python Network Programming Cookbook

Software Engineering 3: Domains, Requirements, and Software Design (Texts in Theoretical Computer Science. An EATCS Series)

Haptics: Perception, Devices and Scenarios: 6th International Conference, EuroHaptics 2008 Madrid, Spain, June 11-13, 2008, Proceedings (Lecture Notes ... Applications, incl. Internet/Web, and HCI)

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

diagram constructs to first-order logic (FOL) formulas and, more specifically, to its fragment description logics (see Chapter 3). 16 Figure 2.7 Structure, Semantics, and Syntax of the UML Language. 2.2 MODEL-DRIVEN ENGINEERING STRUCTURE 2.2.4 17 Model Transformations A transformation definition is a set of transformation rules that together describe the conversion of one model in the source language into another related model in the target language [90]. A transformation rule is a

conjunctive existential subset of first-order logic formulas, i.e., disjunction (Ӡ), negation (¬), or universal quantification (∀) are not allowed. The body of a conjunctive query consists of one or more atoms binding variables or literal values to class expressions or property expressions in the ontology [77]. For example, the query Q( x, y) : −Customer ( x ) ∧ hasOrder ( x, y) is a query for any instance of the concept Customer (x is a distinguished variable) that have some order (y is a

process() process() {disjoint, complete} <> Tax taxAmount() USTax Freight freight() GermanTax USFreight GermanFreight <> USSalesOrder <> <> GermanSalesOrder <> <> <> <> <> Customer <> «owlValue» {someValuesFrom=USCustomer} hasCustomer USCustomer <> {hasValue = USA} country : Country <> GermanCustomer <>

integrated metamodel, namely the package Expressions of the extended OCL metamodel. The class OclExpression enables MBOTL to define the abstract syntax for OCL expressions. The integration with the OWL metamodel is accomplished by expressions of the type PropertyCallExp. Such expression allows for navigating through OWL properties, as explained in Section 11.3.1. The operation call expressions (OperationCallExp) support the declaration of built-in operations and helpers. An operation call

engineering to declaratively specify artifacts (Research Question IV.C). CH A P TE R 14 CONCLUSION This book addresses challenges in composing model-driven engineering and OWL technologies. This work comprises multiple facets of this challenge, namely: (1) classification of existing approaches integrating both paradigms; (2) the specification of a coherent framework for integrated usage of both modeling approaches, comprising the benefits of UML class-based modeling and OWL; and applications of

Download sample

Download