DOCSLIB.ORG

3. Data Models for Engineering Data

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text

Load more

3. Data Models for Engineering Data Conventional and Specific Ways to Describe Engineering Data Overview • Conventional Models – Overview of Data Models – Logical Models • Databases and the Relational Data Model • Object-oriented Data Models • Semi-structured Data Models – Conceptual Models • The Entity Relationship Model (ER) • The Unified Modeling Language (UML) • Engineering Data Models – The Standard for the Exchange of Product Model Data (STEP) • STEP EXPRESS as a modeling language • EXPRESS-G as a graphical/conceptual model – STEP files Schallehn: Data Management for Engineering Applications Reminder: Data Model A data model is a model that describes in an abstract way how data is represented in an information system or a database management system. • A data model defines syntax and semantics, i.e. – How can data be structured (syntax) – What does this structure mean (semantics) • Very generic term for many applications – Programming languages have their data models (e.g. C++ and Java have object-oriented data models) – Conceptual design methods (e.g. ER, UML) represent a data model – File formats either apply a data model (e.g. XML) or implement their own – Database management systems implement data(base) models Schallehn: Data Management for Engineering Applications Information System Design Phases Conceptual Models: Requirements ER, UML, EXPRESS-G Analysis Conceptual Logical Models: Design Relational, Object-oriented, Document-oriented, EXPRESS Logical Design Physical Models: SQL-92, SQL:2011, XML, JSON, C++, Physical Java Design Implementation Schallehn: Data Management for Engineering Applications Types of Data Models • Conceptual Models – Describing the concepts of the given Universe of Discourse and their relationships – Information requirements of system/users – Independent of final structure implementation – Often using graphical notation • Logical Models – Describes the logical structure of information (data) in the system to be developed – Independent of specific (database) systems or (programming) languages • Physical/Implementation Models – Describes all details of how information is represented Schallehn: Data Management for Engineering Applications The Relational Model (RM) • Developed since early 1970s based on mathematical theory of relations and operations performed on them (relational algebra) • SQL (Structured Query Language) as a strong standard to access relational databases • Relational Database Management Systems (RDBMS) implement RM, most often based on SQL • RDBMS are state of the art for database storage Schallehn: Data Management for Engineering Applications SQL/RM: Basic Concepts • Data is stored as rows/records (tuples*) in tables (relations) with values for each column (attribute) • Rows can be identified by special columns called primary keys, for which a unique value must exist • Foreign keys can be used to establish connections across data in different tables • Constraints can be specified to grant consistency * Terms in brackets relate to relational theory/mathematics Schallehn: Data Management for Engineering Applications SQL/RM: Simple Example PartID Name Weight SupplierID GT-876-140425 Plunger 143.5 1 FT-852-130707 Shaft 77.0 3 FT-855-140809 Bolt 15.7 1 TT-707-778 Case 22.8 2 SupplierID Name Location 1 Reed & Sons New York 2 CaseStudio Boston 3 ToolTime Austin Schallehn: Data Management for Engineering Applications SQL/RM: Tables Column PartID Name Weight SupplierID GT-876-140425 Plunger 143.5 1 Table FT-852-130707 Shaft 77.0 3 FT-855-140809 Bolt 15.7 1 Row TT-707-778 Case 22.8 2 Schallehn: Data Management for Engineering Applications SQL/RM: Primary Keys Primary Key PartID Name Weight SupplierID GT-876-140425 Plunger 143.5 1 FT-852-130707 Shaft 77.0 3 Primary Key Value FT-855-140809 Bolt 15.7 1 TT-707-778 Case 22.8 2 Schallehn: Data Management for Engineering Applications SQL/RM: Foreign Keys Foreign Key PartID Name Weight SupplierID GT-876-140425 Plunger 143.5 1 FT-852-130707 Shaft 77.0 3 FT-855-140809 Bolt 15.7 1 TT-707-778 Case 22.8 2 SupplierID Name Location 1 Reed & Sons New York 2 CaseStudio Boston 3 ToolTime Austin Schallehn: Data Management for Engineering Applications The Structured Query Language (SQL) • Language to access databases structured according to Relational Model – Developed based on RM – Introduces some minor differences to RM – Not a programming language • Consists of several parts, most importantly: – Actual query language to read data – Data Definition Language (DDL) to create (empty) databases, tables, etc. – Data Manipulation Language (DML) to insert, modify and delete data Schallehn: Data Management for Engineering Applications SQL: Query Language SELECT <columns> FROM <tables> WHERE <condition>; • Declarative language: – Result is described, not how it is computed – Actual execution can be optimized by DBMS • Typical structure: SFW-block (SELECT-FROM-WHERE) • Input as well as result are always tables • Used from programming languages via standardized or proprietary application programming interfaces (ODBC, JDBC, etc.) Schallehn: Data Management for Engineering Applications SQL: Query Language Example 1 SELECT name, weight FROM part WHERE weight > 50; Name Weight Plunger 143.5 Shaft 77.0 Schallehn: Data Management for Engineering Applications SQL: Query Language Example 2 SELECT p.name, s.name FROM part p, supplier s WHERE p.supplierid = s.supplierid AND s.name LIKE ‘Reed%’; Part.Name Supplier.Name Plunger Reed & Sons Bolt Reed & Sons Schallehn: Data Management for Engineering Applications SQL: Data Definition Language CREATE TABLE part ( partid INTEGER PRIMARY KEY, name VARCHAR(50) NOT NULL, weight DECIMAL(10,2), supplierid INTEGER REFERENCES supplier(supplierid) ); • DDL= Part of SQL language used to define schema elements (tables, constraints, views, etc.) Schallehn: Data Management for Engineering Applications SQL: Data Manipulation Language (DDL) INSERT INTO supplier VALUES (4,’Rex & Smith’, ‘Baltimore’); UPDATE supplier SET location=‘Woburn’ WHERE supplierid=2; DELETE FROM part WHERE supplierid=1; • DML = Part of SQL language to insert, modify and delete data Schallehn: Data Management for Engineering Applications Engineering and RDBMS • RDBMS often used for – Product Lifecycle Management (Product Data Management, Engineering Data Management) – Applications for generic tasks, e.g. Enterprise Resource Planning, Workflow Management Systems, Supply Chain Management, etc. • RDBMS less often or not used for – Direct structured storage of product definition data • Details in Section 4 Schallehn: Data Management for Engineering Applications Object-oriented Data Models • Enhanced semantic modeling – Allows more flexible and re-usable definitions – More semantic concepts add complexity to data model/languages • Developed gradually until major breakthrough in 1980s • Similar concepts of data modeling applied for numerous application fields in computer science, e.g. – Object-oriented Analysis and Design (e.g. UML) – Object-oriented Programming (e.g. C++, Java) – Object-oriented Databases (e.g. db4o, Versant) – Object-relational Databases (SQL since SQL:1999) – Object-oriented User Interfaces Schallehn: Data Management for Engineering Applications OO: Enhanced Semantic Modeling • Objects as instances (data) of classes • User-defined Classes as definitions (schema) of – The structure of objects with Attributes and Relationships – The behavior of objects by Methods (class functions) • Encapsulation to differentiate between appearance to use user of objects of classes (interface) and their internal structure and behavior (implementation) • Re-usability of definitions by Specialization among classes – Inheritance: specialized classes (subclasses) also posses the attributes, relationships and methods of the classes they were derived from (superclasses) – Polymorphism: objects of a subclass are also objects of the superclass and can be used accordingly Schallehn: Data Management for Engineering Applications OO: Attributes • Attributes represent properties of class Part objects of a class, for which an { object carries concrete values ... string name; • Defined based on data types int version_id; – Basic data types defined of Date lastModified; implementation model (e.g. ... int, float, char in C++) }; – Pre-defined complex types (e.g. string in C++) This and all following – User-defined complex types (e.g. examples on OO are in C++ classes for Address, Date, Coordinates, etc.) Schallehn: Data Management for Engineering Applications OO: Methods • Specification of behavior of objects in class Part { terms of functions on that object ... • Interface (Signature, declaration): Part(string n); void createNewVersion(); – Specifies how the method can be used ... – External view of the method }; – Name, parameters and return value ... • Implementation (definition): – Provides executable source code for Part::Part(string n) method { name = n; – Internal view of the methode version_id = 1; • Interface and implementation } may be separated (e.g. in C++) void Part::createNewVersion() • Constructors as special methods to { version_id++; create objects of that class } Schallehn: Data Management for Engineering Applications OO: Relationships class Part • 1:1 and N:1 Relationships { between different objects ... Engineer* responsibleEngineer; most often represented by ... }; pointers (physical address, e.g. C++) or references class Engineer (logical, e.g. Java) { ... • Bidirectional, 1:N and N:M string name; string department; relationships require set<Part*> designedParts; ..
Recommended publications
  • Powerdesigner 16.6 Data Modeling

    Powerdesigner 16.6 Data Modeling

    SAP® PowerDesigner® Document Version: 16.6 – 2016-02-22 Data Modeling Content 1 Building Data Models ...........................................................8 1.1 Getting Started with Data Modeling...................................................8 Conceptual Data Models........................................................8 Logical Data Models...........................................................9 Physical Data Models..........................................................9 Creating a Data Model.........................................................10 Customizing your Modeling Environment........................................... 15 1.2 Conceptual and Logical Diagrams...................................................26 Supported CDM/LDM Notations.................................................27 Conceptual Diagrams.........................................................31 Logical Diagrams............................................................43 Data Items (CDM)............................................................47 Entities (CDM/LDM)..........................................................49 Attributes (CDM/LDM)........................................................55 Identifiers (CDM/LDM)........................................................58 Relationships (CDM/LDM)..................................................... 59 Associations and Association Links (CDM)..........................................70 Inheritances (CDM/LDM)......................................................77 1.3 Physical Diagrams..............................................................82
  • Justice XML Data Model Technical Overview

    Justice XML Data Model Technical Overview

    Justice XML Data Model Technical Overview April 2003 WhyWhy JusticeJustice XMLXML DataData ModelModel VersionVersion 3.0?3.0? • Aligned with standards (some were not available to RDD) • Model-based Æ consistent • Requirements-based – data elements, processes, and documents • Object-oriented Æ efficient extension and reuse • Expanded domain (courts, corrections, and juvenile) • Extensions to activity objects/processes • Relationships (to improve exchange information context) • Can evolve/advance with emerging technology (RDF/OWL) • Model provides the basis for an XML component registry that can provide • Searching/browsing components and metadata • Assistance for schema development/generation • Reference/cache XML schemas for validation • Interface (via standard specs) to external XML registries April 2003 DesignDesign PrinciplesPrinciples • Design and synthesize a common set of reusable, extensible data components for a Justice XML Data Dictionary (JXDD) that facilitates standard information exchange in XML. • Generalize JXDD for the justice and public safety communities – do NOT target specific applications. • Provide reference-able schema components primarily for schema developers. • JXDD and schema will evolve and, therefore, facilitate change and extension. • Best extension methods should minimize impact on prior schema and code investments. • Implement and represent domain relationships so they are globally understood. • Technical dependencies in requirements, solutions, and the time constraints of national priorities and demands
  • Object Query Language Reference Version: Itop 1.0

    Object Query Language Reference Version: Itop 1.0

    Object Query Language Reference Version: Itop 1.0 Overview OQL aims at defining a subset of the data in a natural language, while hiding the complexity of the data model and benefit of the power of the object model (encapsulation, inheritance). Its syntax sticks to the syntax of SQL, and its grammar is a subset of SQL. As of now, only SELECT statements have been implemented. Such a statement do return objects of the expected class. The result will be used by programmatic means (to develop an API like ITOp). A famous example: the library Starter SELECT Book Do return any book existing in the Database. No need to specify the expected columns as we would do in a SQL SELECT clause: OQL do return plain objects. Join classes together I would like to list all books written by someone whose name starts with `Camus' SELECT Book JOIN Artist ON Book.written_by = Artist.id WHERE Artist.name LIKE 'Camus%' Note that there is no need to specify wether the JOIN is an INNER JOIN, or LEFT JOIN. This is well-known in the data model. The OQL engine will in turn create a SQL queries based on the relevant option, but we do not want to care about it, do we? © Combodo 2010 1 Now, you may consider that the name of the author of a book is of importance. This is the case if should be displayed anytime you will list a set of books, or if it is an important key to search for. Then you have the option to change the data model, and define the name of the author as an external field.
  • Arcgis Marine Data Model Reference

    Arcgis Marine Data Model Reference

    ArcGIS Marine Data Model Reference ArcGIS Marine Data Model (June 2003) This document provides an Dawn J. Wright, Oregon State U. overview of the ArcGIS Marine Patrick N. Halpin, Duke U. Data Model. This model focuses on Michael Blongewicz, DHI important features of the ocean realm, both natural and manmade, Steve Grisé, ESRI Redlands with a view towards the many Joe Breman, ESRI Redlands applications of marine GIS data. ArcGIS Data Models TABLE OF CONTENTS Acknowledgements ................................................................................................................... 4 Introduction ............................................................................................................................... 5 Why a Marine Data Model?.................................................................................................... 6 Intended Audience and Scope of the Model............................................................................ 8 The Process of Building a Data Model ..................................................................................... 10 Final Data Model Content, Purpose and Use........................................................................ 14 Data Model Description ........................................................................................................... 16 Overview ............................................................................................................................. 16 Conceptual Framework....................................................................................................
  • Data Model Standards and Guidelines, Registration Policies And

    Data Model Standards and Guidelines, Registration Policies And

    Data Model Standards and Guidelines, Registration Policies and Procedures Version 3.2 ● 6/02/2017 Data Model Standards and Guidelines, Registration Policies and Procedures Document Version Control Document Version Control VERSION D ATE AUTHOR DESCRIPTION DRAFT 03/28/07 Venkatesh Kadadasu Baseline Draft Document 0.1 05/04/2007 Venkatesh Kadadasu Sections 1.1, 1.2, 1.3, 1.4 revised 0.2 05/07/2007 Venkatesh Kadadasu Sections 1.4, 2.0, 2.2, 2.2.1, 3.1, 3.2, 3.2.1, 3.2.2 revised 0.3 05/24/07 Venkatesh Kadadasu Incorporated feedback from Uli 0.4 5/31/2007 Venkatesh Kadadasu Incorporated Steve’s feedback: Section 1.5 Issues -Change Decide to Decision Section 2.2.5 Coordinate with Kumar and Lisa to determine the class words used by XML community, and identify them in the document. (This was discussed previously.) Data Standardization - We have discussed on several occasions the cross-walk table between tabular naming standards and XML. When did it get dropped? Section 2.3.2 Conceptual data model level of detail: changed (S) No foreign key attributes may be entered in the conceptual data model. To (S) No attributes may be entered in the conceptual data model. 0.5 6/4/2007 Steve Horn Move last paragraph of Section 2.0 to section 2.1.4 Data Standardization Added definitions of key terms 0.6 6/5/2007 Ulrike Nasshan Section 2.2.5 Coordinate with Kumar and Lisa to determine the class words used by XML community, and identify them in the document.
  • Integration Definition for Function Modeling (IDEF0)

    Integration Definition for Function Modeling (IDEF0)

    NIST U.S. DEPARTMENT OF COMMERCE PUBLICATIONS £ Technology Administration National Institute of Standards and Technology FIPS PUB 183 FEDERAL INFORMATION PROCESSING STANDARDS PUBLICATION INTEGRATION DEFINITION FOR FUNCTION MODELING (IDEFO) » Category: Software Standard SUBCATEGORY: MODELING TECHNIQUES 1993 December 21 183 PUB FIPS JK- 45C .AS A3 //I S3 IS 93 FIPS PUB 183 FEDERAL INFORMATION PROCESSING STANDARDS PUBLICATION INTEGRATION DEFINITION FOR FUNCTION MODELING (IDEFO) Category: Software Standard Subcategory: Modeling Techniques Computer Systems Laboratory National Institute of Standards and Technology Gaithersburg, MD 20899 Issued December 21, 1993 U.S. Department of Commerce Ronald H. Brown, Secretary Technology Administration Mary L. Good, Under Secretary for Technology National Institute of Standards and Technology Arati Prabhakar, Director Foreword The Federal Information Processing Standards Publication Series of the National Institute of Standards and Technology (NIST) is the official publication relating to standards and guidelines adopted and promulgated under the provisions of Section 111 (d) of the Federal Property and Administrative Services Act of 1949 as amended by the Computer Security Act of 1987, Public Law 100-235. These mandates have given the Secretary of Commerce and NIST important responsibilities for improving the utilization and management of computer and related telecommunications systems in the Federal Government. The NIST, through its Computer Systems Laboratory, provides leadership, technical guidance,
  • Metamodeling and Method Engineering with Conceptbase”

    Metamodeling and Method Engineering with Conceptbase”

    This is a pre-print of the book chapter M. Jeusfeld: “Metamodeling and method engineering with ConceptBase” . In Jeusfeld, M.A., Jarke, M., Mylopoulos, J. (eds): Metamodeling for Method Engineering, pp. 89-168. The MIT Press., 2009; the original book is available from MIT Press http://mitpress.mit.edu/node/192290 This pre-print may only be used for scholar, non-commercial purposes. Most of the sources for the examples in this chapter are available via http://merkur.informatik.rwth-aachen.de/pub/bscw.cgi/3782591 for download. They require ConceptBase 7.0 or later available from http://conceptbase.cc. Metamodeling and Method Engineering with ConceptBase Manfred Jeusfeld Abstract. This chapter provides a practical guide on how to use the meta data repository ConceptBase to design information modeling methods by using meta- modeling. After motivating the abstraction principles behind meta-modeling, the language Telos as realized in ConceptBase is presented. First, a standard factual representation of statements at any IRDS abstraction level is defined. Then, the foundation of Telos as a logical theory is elaborated yielding simple fixpoint semantics. The principles for object naming, instantiation, attribution, and specialization are reflected by roughly 30 logical axioms. After the language axiomatization, user-defined rules, constraints and queries are introduced. The first part is concluded by a description of active rules that allows the specification of reactions of ConceptBase to external events. The second part applies the language features of the first part to a full-fledged information modeling method: The Yourdan method for Modern Structured Analysis. The notations of the Yourdan method are designed along the IRDS framework.
  • A Model-To-Model Transformation of a Generic Relational Database Schema Into a Form Type Data Model

    A Model-To-Model Transformation of a Generic Relational Database Schema Into a Form Type Data Model

    Proceedings of the Federated Conference on Computer Science DOI: 10.15439/2016F408 and Information Systems pp. 1577–1580 ACSIS, Vol. 8. ISSN 2300-5963 A Model-to-Model Transformation of a Generic Relational Database Schema into a Form Type Data Model Sonja Ristić, Slavica Kordić, Milan Čeliković, Vladimir Dimitrieski, Ivan Luković University of Novi Sad, Faculty of Technical Sciences, Trg D. Obradovića 6, 21000 Novi Sad, Serbia Email: {sdristic, slavica, milancel, dimitrieski, ivan}@uns.ac.rs ฀ engineering and review different database meta-models Abstract—An important phase of a data-oriented software (MM) that are used in the database reengineering process system reengineering is a database reengineering process and, applied in IIS*Studio. In [5] we propose an MD approach to in particular, its subprocess – a database reverse engineering data structure conceptualization phase of database reverse process. In this paper we present one of the model-to-model engineering process that is conducted through a chain of transformations from a chain of transformations aimed at transformation of a generic relational database schema into a M2M transformations. In this paper we present the final step form type data model. The transformation is a step of the data of the conceptualization phasethe M2M transformation of structure conceptualization phase of a model-driven database a generic relational database schema into a form type model. reverse engineering process that is implemented in IIS*Studio The form type concept and the IIS*Studio architecture are development environment. given in Section 2. Classifications of form types and relation schemes are described in Section 3. The transformation of a I.
  • Foundations of the Unified Modeling Language

    Foundations of the Unified Modeling Language

    Foundations of the Unified Modeling Language. CLARK, Anthony <http://orcid.org/0000-0003-3167-0739> and EVANS, Andy Available from Sheffield Hallam University Research Archive (SHURA) at: http://shura.shu.ac.uk/11889/ This document is the author deposited version. You are advised to consult the publisher's version if you wish to cite from it. Published version CLARK, Anthony and EVANS, Andy (1997). Foundations of the Unified Modeling Language. In: 2nd BCS-FACS Northern Formal Methods Workshop., Ilkley, UK, 14- 15 July 1997. Springer. Copyright and re-use policy See http://shura.shu.ac.uk/information.html Sheffield Hallam University Research Archive http://shura.shu.ac.uk Foundations of the Unified Modeling Language Tony Clark, Andy Evans Formal Methods Group, Department of Computing, University of Bradford, UK Abstract Object-oriented analysis and design is an increasingly popular software development method. The Unified Modeling Language (UML) has recently been proposed as a standard language for expressing object-oriented designs. Unfor- tunately, in its present form the UML lacks precisely defined semantics. This means that it is difficult to determine whether a design is consistent, whether a design modification is correct and whether a program correctly implements a design. Formal methods provide the rigor which is lacking in object-oriented design notations. This provision is often at the expense of clarity of exposition for the non-expert. Formal methods aim to use mathematical techniques in order to allow software development activities to be precisely defined, checked and ultimately automated. This paper aims to present an overview of work being undertaken to provide (a sub-set of) the UML with formal semantics.
  • Using Telelogic DOORS and Microsoft Visio to Model and Visualize Complex Business Processes

    Using Telelogic DOORS and Microsoft Visio to Model and Visualize Complex Business Processes

    Using Telelogic DOORS and Microsoft Visio to Model and Visualize Complex Business Processes “The Business Driven Application Lifecycle” Bob Sherman Procter & Gamble Pharmaceuticals [email protected] Michael Sutherland Galactic Solutions Group, LLC [email protected] Prepared for the Telelogic 2005 User Group Conference, Americas & Asia/Pacific http://www.telelogic.com/news/usergroup/us2005/index.cfm 24 October 2005 Abstract: The fact that most Information Technology (IT) projects fail as a result of requirements management problems is common knowledge. What is not commonly recognized is that the widely haled “use case” and Object Oriented Analysis and Design (OOAD) phenomenon have resulted in little (if any) abatement of IT project failures. In fact, ten years after the advent of these methods, every major IT industry research group remains aligned on the fact that these projects are still failing at an alarming rate (less than a 30% success rate). Ironically, the popularity of use case and OOAD (e.g. UML) methods may be doing more harm than good by diverting our attention away from addressing the real root cause of IT project failures (when you have a new hammer, everything looks like a nail). This paper asserts that, the real root cause of IT project failures centers around the failure to map requirements to an accurate, precise, comprehensive, optimized business model. This argument will be supported by a using a brief recap of the history of use case and OOAD methods to identify differences between the problems these methods were intended to address and the challenges of today’s IT projects.
  • Modelling, Analysis and Design of Computer Integrated Manueactur1ng Systems

    Modelling, Analysis and Design of Computer Integrated Manueactur1ng Systems

    MODELLING, ANALYSIS AND DESIGN OF COMPUTER INTEGRATED MANUEACTUR1NG SYSTEMS Volume I of II ABDULRAHMAN MUSLLABAB ABDULLAH AL-AILMARJ October-1998 A thesis submitted for the DEGREE OP DOCTOR OF.PHILOSOPHY MECHANICAL ENGINEERING DEPARTMENT, THE UNIVERSITY OF SHEFFIELD 3n ti]S 5íamc of Allai]. ¿Hoot (gractouo. iHHoßt ¿Merciful. ACKNOWLEDGEMENTS I would like to express my appreciation and thanks to my supervisor Professor Keith Ridgway for devoting freely of his time to read, discuss, and guide this research, and for his assistance in selecting the research topic, obtaining special reference materials, and contacting industrial collaborations. His advice has been much appreciated and I am very grateful. I would like to thank Mr Bruce Lake at Brook Hansen Motors who has patiently answered my questions during the case study. Finally, I would like to thank my family for their constant understanding, support and patience. l To my parents, my wife and my son. ABSTRACT In the present climate of global competition, manufacturing organisations consider and seek strategies, means and tools to assist them to stay competitive. Computer Integrated Manufacturing (CIM) offers a number of potential opportunities for improving manufacturing systems. However, a number of researchers have reported the difficulties which arise during the analysis, design and implementation of CIM due to a lack of effective modelling methodologies and techniques and the complexity of the systems. The work reported in this thesis is related to the development of an integrated modelling method to support the analysis and design of advanced manufacturing systems. A survey of various modelling methods and techniques is carried out. The methods SSADM, IDEFO, IDEF1X, IDEF3, IDEF4, OOM, SADT, GRAI, PN, 10A MERISE, GIM and SIMULATION are reviewed.
  • Principles of the Concept-Oriented Data Model Alexandr Savinov

    Principles of the Concept-Oriented Data Model Alexandr Savinov

    Principles of the Concept-Oriented Data Model Alexandr Savinov Institute of Mathematics and Computer Science Academy of Sciences of Moldova Academiei 5, MD-2028 Chisinau, Moldova Fraunhofer Institute for Autonomous Intelligent System Schloss Birlinghoven, 53754 Sankt Augustin, Germany http://www.conceptoriented.com [email protected] Principles of the Concept-Oriented Data Model Alexandr Savinov Institute of Mathematics and Computer Science, Academy of Sciences of Moldova Academiei 5, MD-2028 Chisinau, Moldova Fraunhofer Institute for Autonomous Intelligent System Schloss Birlinghoven, 53754 Sankt Augustin, Germany http://www.conceptoriented.com [email protected] In the paper a new approach to data representation and manipulation is described, which is called the concept-oriented data model (CODM). It is supposed that items represent data units, which are stored in concepts. A concept is a combination of superconcepts, which determine the concept’s dimensionality or properties. An item is a combination of superitems taken by one from all the superconcepts. An item stores a combination of references to its superitems. The references implement inclusion relation or attribute- value relation among items. A concept-oriented database is defined by its concept structure called syntax or schema and its item structure called semantics. The model defines formal transformations of syntax and semantics including the canonical semantics where all concepts are merged and the data semantics is represented by one set of items. The concept-oriented data model treats relations as subconcepts where items are instances of the relations. Multi-valued attributes are defined via subconcepts as a view on the database semantics rather than as a built-in mechanism.