Model Driven Architecture and Ontology Development
Defining a formal domain ontology is generally considered a useful, not to say necessary step in almost every software project. This is because software deals with ideas rather than with self-evident physical artefacts. However, this development step is h
- PDF / 6,299,355 Bytes
- 316 Pages / 439.37 x 666.142 pts Page_size
- 13 Downloads / 248 Views
Dragan Gaˇsevi´c · Dragan Djuri´c Vladan Devedˇzi´c
Model Driven Architecture and Ontology Development Foreword by Bran Selic With 153 Figures and 7 Tables
123
Authors Dragan Gaˇsevi´c School of Interactive Arts and Technology Simon Fraser University Surrey 13450 102 Ave. Surrey, BC V3T 5X3 Canada [email protected] and [email protected]
Dragan Djuri´c Vladan Devedˇzi´c FON – School of Business Administration University of Belgrade Jove Ili´ca 154 11000 Belgrade Serbia and Montenegro [email protected] [email protected]
Library of Congress Control Number: 2006924633
ACM Computing Classification (1998): D.2.10, D.2.11, H.4.0, I.2.4
ISBN-10 3-540-32180-2 Springer Berlin Heidelberg New York ISBN-13 978-3-540-32180-4 Springer Berlin Heidelberg New York This work is subject to copyright. All rights are reserved, whether the whole or part of the material is concerned, specifically the rights of translation, reprinting, reuse of illustrations, recitation, broadcasting, reproduction on microfilm or in any other way, and storage in data banks. Duplication of this publication or parts thereof is permitted only under the provisions of the German Copyright Law of September 9, 1965, in its current version, and permission for use must always be obtained from Springer. Violations are liable for prosecution under the German Copyright Law. Springer is a part of Springer Science+Business Media springer.com © Springer-Verlag Berlin Heidelberg 2006 Printed in Germany The use of general descriptive names, registered names, trademarks, etc. in this publication does not imply, even in the absence of a specific statement, that such names are exempt from the relevant protective laws and regulations and therefore free for general use. Typeset by the Authors Production: LE-TEX Jelonek, Schmidt & Vöckler GbR, Leipzig Cover design: KünkelLopka Werbeagentur, Heidelberg Printed on acid-free paper
45/3100/YL - 5 4 3 2 1 0
To our families
Foreword
The first time I paid attention to the term “ontology” was in the late 1980s when I was part of an engineering team that was responsible for defining what we would now call a domain-specific modeling language. In our case, the domain was telecommunications software and the purpose of our language was to give system architects the ability to describe the highlevel structure of their software in the most direct and most expressive manner possible. The team members were all experienced designers with deep knowledge of the domain so that we had no trouble putting together the initial list of key language concepts. We knew that we needed to include standard architectural modeling constructs such as components, ports, connectors, and the like. We also wanted our language to be object-oriented, so notions such as class, objects, and inheritance were added to the list. However, soon after this very promising start, all progress ground to a halt. Somehow, the definition of the seemingly trivial fine-grain details of these constructs kept eluding us despite long, passionate, and occasionally acrimonious
Data Loading...
