1 Domain Management in a Hierarchical Generic Models Library University Pascal Paoli of Corsica SPE Laboratory Fabrice BERNARDI, Jean-François SANTUCCI.

Slides:



Advertisements
Similar presentations
Chapter 19 – Service-oriented Architecture
Advertisements

CMSC 611: Advanced Computer Architecture
A component- and message-based architectural style for GUI software
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 12Slide 1 Software Design l Objectives To explain how a software design may be represented.
Object-Oriented Analysis and Design
1 SWE Introduction to Software Engineering Lecture 13 – System Modeling.
7M701 1 Software Engineering Object-oriented Design Sommerville, Ian (2001) Software Engineering, 6 th edition: Chapter 12 )
©Ian Sommerville 2006Software Engineering, 8th edition. Chapter 8 Slide 1 System models.
Object-Oriented Databases v OO systems associated with – graphical user interface (GUI) – powerful modeling techniques – advanced data management capabilities.
1 SWE Introduction to Software Engineering Lecture 23 – Architectural Design (Chapter 13)
Requirements Specification
Modified from Sommerville’s originalsSoftware Engineering, 7th edition. Chapter 8 Slide 1 System models.
1 Introduction The Database Environment. 2 Web Links Google General Database Search Database News Access Forums Google Database Books O’Reilly Books Oracle.
©Ian Sommerville 2000Software Engineering, 6/e, Chapter 71 System models l Abstract descriptions of systems whose requirements are being analysed.
Requirements Analysis Concepts & Principles
Marakas: Decision Support Systems, 2nd Edition © 2003, Prentice-Hall Chapter Chapter 1: Introduction to Decision Support Systems Decision Support.
Modified from Sommerville’s originalsSoftware Engineering, 7th edition. Chapter 8 Slide 1 System models.
Soft. Eng. II, Spring 02Dr Driss Kettani, from I. Sommerville1 CSC-3325: Chapter 6 Title : The Software Reuse Reading: I. Sommerville, Chap. 20.
Course Instructor: Aisha Azeem
Introduction to Software Design Chapter 1. Chapter 1: Introduction to Software Design2 Chapter Objectives To become familiar with the software challenge.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 11 Slide 1 Architectural Design.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 7 Slide 1 System models l Abstract descriptions of systems whose requirements are being.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 14Slide 1 Design with Reuse l Building software from reusable components.
Organizing Information Digitally Norm Friesen. Overview General properties of digital information Relational: tabular & linked Object-Oriented: inheritance.
Object and component “wiring” standards This presentation reviews the features of software component wiring and the emerging world of XML-based standards.
Lecture 6 Data Flow Modeling
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 7 Slide 1 System models l Abstract descriptions of systems whose requirements are being.
Chapter 4 System Models A description of the various models that can be used to specify software systems.
System models Abstract descriptions of systems whose requirements are being analysed Abstract descriptions of systems whose requirements are being analysed.
1 CS 456 Software Engineering. 2 Contents 3 Chapter 1: Introduction.
DEVS Namespace for Interoperable DEVS/SOA
Software Requirements Engineering CSE 305 Lecture-2.
SOFTWARE DESIGN AND ARCHITECTURE LECTURE 07. Review Architectural Representation – Using UML – Using ADL.
Discrete Event Modeling and Simulation of Distributed Architectures using the DSSV Methodology E. de Gentili, F. Bernardi, J.F. Santucci University Pascal.
1 Another group of Patterns Architectural Patterns.
RELATIONAL FAULT TOLERANT INTERFACE TO HETEROGENEOUS DISTRIBUTED DATABASES Prof. Osama Abulnaja Afraa Khalifah
Chapter 7 System models.
Software Architecture and Patterns
System models l Abstract descriptions of systems whose requirements are being analysed.
Pertemuan 19 PEMODELAN SISTEM Matakuliah: D0174/ Pemodelan Sistem dan Simulasi Tahun: Tahun 2009.
CS 4310: Software Engineering Lecture 4 System Modeling The Analysis Stage.
Modified by Juan M. Gomez Software Engineering, 6th edition. Chapter 7 Slide 1 Chapter 7 System Models.
Sommerville 2004,Mejia-Alvarez 2009Software Engineering, 7th edition. Chapter 8 Slide 1 System models.
Language Concepts Ver 1.1, Copyright 1997 TS, Inc. VHDL L a n g u a g e C o n c e p t s Page 1.
5 - 1 Copyright © 2006, The McGraw-Hill Companies, Inc. All rights reserved.
Dr.Basem Alkazemi
DEVS Based Modeling and Simulation of the CORBA POA F. Bernardi, E. de Gentili, Pr. J.F. Santucci {bernardi, gentili, University.
Electrical and Computer Engineering University of Cyprus LAB 1: VHDL.
Introduction to VLSI Design – Lec01. Chapter 1 Introduction to VLSI Design Lecture # 11 High Desecration Language- Based Design.
Chapter 6 – Architectural Design Lecture 1 1Chapter 6 Architectural design.
Introduction to VHDL Simulation … Synthesis …. The digital design process… Initial specification Block diagram Final product Circuit equations Logic design.
SWEN 5231 FORMAL METHODS Slide 1 System models u Abstract presentations of systems whose requirements are being analyzed.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 8 Slide 1 System models.
Digital Libraries1 David Rashty. Digital Libraries2 “A library is an arsenal of liberty” Anonymous.
Architecture View Models A model is a complete, simplified description of a system from a particular perspective or viewpoint. There is no single view.
1 Software Design Lecture What’s Design It’s a representation of something that is to be built. i.e. design  implementation.
Model Design using Hierarchical Web-Based Libraries F. Bernardi Pr. J.F. Santucci {bernardi, University of Corsica SPE Laboratory.
Slide 1 Service-centric Software Engineering. Slide 2 Objectives To explain the notion of a reusable service, based on web service standards, that provides.
©Ian Sommerville 2006Software Engineering, 8th edition. Chapter 4 Slide 1 Software Processes.
Digital Design Using VHDL and PLDs ECOM 4311 Digital System Design Chapter 1.
Lesson 1 1 LESSON 1 l Background information l Introduction to Java Introduction and a Taste of Java.
Software Engineering Lecture 10: System Engineering.
Introduction to Service Orientation MIS 181.9: Service Oriented Architecture 2 nd Semester,
Week 1 Reference (chapter 1 in text book (1)) Dr. Fadi Fayez Jaber Updated By: Ola A.Younis Decision Support System.
Extension du formalisme SES pour l’intégration de la hiérarchie d’abstraction et la granularité temporelle au sein de la modélisation et la simulation.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 8 Slide 1 System models.
IAY 0600 Digital Systems Design VHDL discussion Structural style Modular design and hierarchy Part 1 Alexander Sudnitson Tallinn University of Technology.
Structural style Modular design and hierarchy Part 1
Neuro-DEVS An hybrid methodology to describe complex systems
University of Houston-Clear Lake
Presentation transcript:

1 Domain Management in a Hierarchical Generic Models Library University Pascal Paoli of Corsica SPE Laboratory Fabrice BERNARDI, Jean-François SANTUCCI 20 Décembre 2002 UMR CNRS 6134

2 Introduction Modeling and simulating complex systems involves some complementary works Costly to build a system (model or environment) from scratch Preferable to reuse predefined elements : –Pre-validated models for simulation –Modules for a modeling and simulation environment Basic modules : GUI, models library,... This presentation : How to integrate a new model format in a generic models library

3 Topics Basics of the Approach –Notion of modeling component –Objectives of the models library –The notion of context –Elements of the architecture The Domain Parser –Definition –XML Document Type Definition Case Study : the JDEVS Domain Conclusion and Perspectives

4 Basics of the Approach Notion of Modeling Component Basic concept of our work : the component Two complementary notions : –Software component : Software object Presents well-defined interfaces –Modeling Component : Software component Described using a specific formalism Interfaces Communication ports

5 Basics of the Approach A Component-Oriented Modeling and Simulation Process Problem Formulation Simulation of the complete model Design of the complete model Storage of the Components Selection or Creation of the Components Components Identification Application Builder Librarian Final User

6 Basics of the Approach Models and Modeling Components Complete model : –Set of modeling components –Can be seen as a modeling component In the following : Model Modeling component

7 Basics of the Approach Two Types of Models Non-Decomposable Model : atomic model for modeling Decomposable Model : model constituted by other interconnected models M3 M4 M5 Decomposable Model M2 M1 Non-Decomposable Model Input Ports Output Ports

8 Basics of the Approach Objectives of our Work To define a generic architecture to store modeling components Main functionnalities : –Abstraction hierarchy management –Inheritance hierarchy management –Reusable storage format –Human-understandable storage format

9 Basics of the Approach The Notion of Context – Definition Storage architecture : a model is passive Modeling environment : a model is (can be) active Two representations of a same model : –Context-out model : Abstraction of a model Encapsulated in a special format Directly storable in its storage architecture –Context-in model : Context-out model extracted from the storage architecture Directly usable in its modeling and simulation environment

10 Basics of the Approach The Notion of Context – Illustration Library IEEE; use IEEE.std_logic_1164.all ENTITY counter PORT(clk, en, clr: IN std_logic; rco: OUT std_logic; q: OUT INTEGER RANGE 0 TO 9); END counter; ARCHITECTURE behav OF counter IS SIGNAL cnt: INTEGER RANGE 0 TO 9; BEGIN... END behav; library IEEE; use IEEE.std_logic_1164.all ENTITY counter PORT(clk, en, clr: IN std_logic; rco: OUT std_logic; q: OUT INTEGER RANGE 0 TO 9); END counter;... Context-in model Context-out model

11 Basics of the Approach Elements of the Architecture Element : object that can be stored in a library Completely independent from the modeling environment (notion of context) Common characteristics : –Associated with keys –Associated with a documentation Two categories : –Classification elements –Storage elements

12 Basics of the Approach Classification Elements –Library : high level element –Domain : theoretical domain of the elements. Usually, a formalism or a modeling and simulation environment –Application Domain : domain of use of the models –Classification Intermediate Model : simple element for the structuration of a library

13 Basics of the Approach Storage Elements –Inheritance Intermediate Model : allow a share of characteristics between models –Model File : basic storage element Decomposable Model File Non-Decomposable Model File

14 Basics of the Approach Relationships between Elements InheritanceIntermediateModel DecomposableModelFile ClassificationIntermediateModel NonDecomposableModelFile ApplicationDomain Domain Library 0..1 * * * * * * * * *

15 The Domain Parser Notion of Domain Parser Essential point : unique storage format Two different and domain-oriented procedures : –Context Transition : “context-in” towards “context-out” –Context Reconstitution : “context-out” towards “context-in” Domain Parser : –Analysis Mode Context Transition –Creation Mode Context Reconstitution

16 The Domain Parser Basics Relies on a Distinction Methodology : –Separate the extent of the model from its format –Specific to each defined domain –Defined by the librarian Difference between decomposable models and non-decomposable models => Type Selector

17 The Domain Parser The DomainParser Class ParserTypeSelector NonDecomposableModelFileParser DecomposableModelFileParser DomainParser DecomposableModelFileParser1 NonDecomposableModelFileParser1 TypeSelector1 Parser1

18 The Domain Parser Format of the Context-Out Models Use of the XML language Multiple advantages : –Text format easily readable –Facility for reusability (can be translated in other various formats) –Web-enabled

19 The Domain Parser Context-Out Models Document Type Definition ]>

20 Case Study : the JDEVS Domain Example of a JDEVS Non-Decomposable Model public class DevsAtom extends AtomicModel { Port i1 = new Port(this, ''i1'', ''IN''); Port o1 = new Port(this, ''o1'', ''OUT''); public DevsAtom() { super(''DevsAtom''); states.setProperty(''A'', '' ''); } EventVector outFunction(Message m) { return new EventVector(); } void intTransition() {} EventVector extTransition(Message m) { return new EventVector(); } double advanceTime() { return Double.MAXVALUE; }

21 Case Study : the JDEVS Domain Generation of the Context-Out Model Two steps : –Context-in model analysis –Context-out generation Implementation of the DecomposableModelFileParser abstract class : –Four methods for the analysis –Four methods for the generation

22 Case Study : the JDEVS Domain The Context-Out Model JDEVS this public { super(''DevsAtom''); states.setProperty(''A'', '' ''); } Message m EventVector { return new EventVector(); }...

23 Conclusion and Perspectives Main point : notion of context Implementation using the J2EE TM technology (HMLib Prototype) : –Validation using the JDEVS M&S Environment –Applications : environmental studies, VHDL fault simulation, CORBA-based architectures modeling and simulation Perspectives : –Management of other formalisms –Improvement of the performances of the storage engine –Study of the distribution of storage engines over a network