SEBGIS 2005, Agia Napa, Cyprus, October 31 - November 4, 2005 MECOSIG Adapted to the Design of Distributed GIS F. Pasquasy, F. Laplanche, J-C. Sainte &

Slides:



Advertisements
Similar presentations
Database Planning, Design, and Administration
Advertisements

National Environmental Research Institute, University of Aarhus, Denmark GIS Guidance update.
IT Requirements Capture Process. Motivation for this seminar Discovering system requirements is hard. Formally testing use case conformance is hard. We.
L4-1-S1 UML Overview © M.E. Fayad SJSU -- CmpE Software Architectures Dr. M.E. Fayad, Professor Computer Engineering Department, Room #283I.
Revision Session 1.UML Overview 2.Detailed software design : operation specification, designing for re-use.
Chapter 2 Data Models Database Systems: Design, Implementation, and Management, Seventh Edition, Rob and Coronel.
1 COST G9 - Work group 2 meeting Székesfehérvár, Hu Modeling real property transactions Radoš Šumrada Faculty of Civil and Geodetic.
Chapter 6 Methodology Conceptual Databases Design Transparencies © Pearson Education Limited 1995, 2005.
Chapter 6 Database Design
Software Engineering General Project Management Software Requirements
Lecture Fourteen Methodology - Conceptual Database Design
IS550: Software requirements engineering Dr. Azeddine Chikh 4. Validation and management.
9 1 Chapter 9 Database Design Database Systems: Design, Implementation, and Management, Seventh Edition, Rob and Coronel.
6 Chapter 6 Database Design Hachim Haddouti. 6 2 Hachim Haddouti and Rob & Coronel, Ch6 In this chapter, you will learn: That successful database design.
SDLC and Related Methodologies
Methodology Conceptual Database Design
1 SWE Introduction to Software Engineering Lecture 11 - Requirements Engineering Processes.
University of Jyväskylä – Department of Mathematical Information Technology Computer Science Teacher Education ICNEE 2004 Topic Case Driven Approach for.
1 TECO-WIS, 6-8 November 2006 TECHNICAL CONFERENCE ON THE WMO INFORMATION SYSTEM Seoul, Republic of Korea, 6-8 November 2006 ISO 191xx series of geographic.
Department of Computer Science 1 CSS 496 Business Process Re-engineering for BS(CS)
Enterprise Architecture
CSC271 Database Systems Lecture # 21. Summary: Previous Lecture  Phases of database SDLC  Prototyping (optional)  Implementation  Data conversion.
The BIM Project Execution Planning Procedure
MDC Open Information Model West Virginia University CS486 Presentation Feb 18, 2000 Lijian Liu (OIM:
“”Capacity and services to road users” Task descriptions Paul van der Kroon, Paris November 2005.
2 1 Chapter 2 Data Model Database Systems: Design, Implementation, and Management, Sixth Edition, Rob and Coronel.
Database System Development Lifecycle © Pearson Education Limited 1995, 2005.
Overview of the Database Development Process
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 6 Slide 1 Chapter 6 Requirements Engineering Process.
SEMINAR ON :. ORGANISATION Organizations are formal social units devoted to attainment of specific goals. Organizations use certain resources to produce.
ITEC224 Database Programming
Copyright 2002 Prentice-Hall, Inc. Chapter 1 The Systems Development Environment 1.1 Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 6 Slide 1 Requirements Engineering Processes l Processes used to discover, analyse and.
ITEC 3220M Using and Designing Database Systems
Working Together to Advance Terminology Tooling Presentation to OHT Board, Birmingham Jennifer Zelmer & Karen Gibson.
ACCOUNTING INFORMATION SYSTEMS
IST 210 Database Design Process IST 210 Todd S. Bacastow January 2005.
Methodology - Conceptual Database Design Transparencies
Database Systems: Design, Implementation, and Management Ninth Edition
Methodology Conceptual Databases Design
Week 4 Lecture Part 3 of 3 Database Design Samuel ConnSamuel Conn, Faculty Suggestions for using the Lecture Slides.
9/14/2012ISC329 Isabelle Bichindaritz1 Database System Life Cycle.
1 Chapter 15 Methodology Conceptual Databases Design Transparencies Last Updated: April 2011 By M. Arief
Certification and Accreditation CS Phase-1: Definition Atif Sultanuddin Raja Chawat Raja Chawat.
Chapter 10 Information Systems Analysis and Design
Secure Systems Research Group - FAU Classifying security patterns E.B.Fernandez, H. Washizaki, N. Yoshioka, A. Kubo.
INFRASTRUCTURE FOR GIS INTEROPERABLITY APPLICATION FACULTY OF INFORMATION AND COMMUNICATION TECHNOLOGY (FTMK) THE TECHNICAL UNIVERSITY OF MALAYSIA MELAKA.
Methodology - Conceptual Database Design. 2 Design Methodology u Structured approach that uses procedures, techniques, tools, and documentation aids to.
1/26/2004TCSS545A Isabelle Bichindaritz1 Database Management Systems Design Methodology.
Methodology: Conceptual Databases Design
Methodology - Conceptual Database Design
Software Engineering Prof. Ing. Ivo Vondrak, CSc. Dept. of Computer Science Technical University of Ostrava
Unified Modeling Language* Keng Siau University of Nebraska-Lincoln *Adapted from “Software Architecture and the UML” by Grady Booch.
Ajh January 2007 CCSDS “Books” Adrian J. Hooke CMC Meeting, Colorado Springs 26 January 2007.
Rupa Tiwari, CSci5980 Fall  Course Material Classification  GIS Encyclopedia Articles  Classification Diagram  Course – Encyclopedia Mapping.
Topics Covered Phase 1: Preliminary investigation Phase 1: Preliminary investigation Phase 2: Feasibility Study Phase 2: Feasibility Study Phase 3: System.
Logical view –show classes and objects Process view –models the executables Implementation view –Files, configuration and versions Deployment view –Physical.
Requirements Engineering-Based Conceptual Modelling From: Requirements Engineering E. Insfran, O. Pastor and R. Wieringa Presented by Chin-Yi Tsai.
CISB113 Fundamentals of Information Systems IS Development.
Architecture View Models A model is a complete, simplified description of a system from a particular perspective or viewpoint. There is no single view.
IST 210 Database Design Process IST 210, Section 1 Todd S. Bacastow January 2004.
Bavarian Agency for Surveying and Geoinformation AAA - The contribution of the AdV in an increasing European Spatial Data Infrastructure - the German Way.
 The processes used for RE vary widely depending on the application domain, the people involved and the organisation developing the requirements.  However,
Informatics for Scientific Data Bio-informatics and Medical Informatics Week 9 Lecture notes INF 380E: Perspectives on Information.
Methodology Conceptual Databases Design
BIL 424 NETWORK ARCHITECTURE AND SERVICE PROVIDING.
Methodology Conceptual Database Design
Methodology Conceptual Databases Design
, editor October 8, 2011 DRAFT-D
Presentation transcript:

SEBGIS 2005, Agia Napa, Cyprus, October 31 - November 4, 2005 MECOSIG Adapted to the Design of Distributed GIS F. Pasquasy, F. Laplanche, J-C. Sainte & J-P. Donnay Unit of Geomatics, University of Liège, Belgium

2 SEBGIS 2005, Agia Napa, Cyprus, October 31 - November 4, 2005 MECOSIG  A method devoted to GIS design and implementation [published in 1996] considering: GIS as an Information System (IS) where IS  Organization (systemic approach) Organization as the core of the method  The method has been progressively improved (last decade)  Emergence of distributed GIS involved : reassessment of the methodology  new concerns and tools (fitting the requirements of distributed environments) identified

3 SEBGIS 2005, Agia Napa, Cyprus, October 31 - November 4, 2005 MECOSIG - Design protocol  Method covering the complete GIS’s lifecycle using specific tools at different abstraction levels  Descriptive to Logical-Physical level...  Design protocol is summarized into a monitoring matrix every cell relates to  specific tools (formalisms, models, prototyping …)  semantic concerns (metadata, documentation …)  Main concerns are Organization, Data, Data flows, Processes  MECOSIG suggested to go twice through the monitoring matrix analysis stage (not anymore taken into account because of redundancy with the descriptive level in conception step) conception step

4 SEBGIS 2005, Agia Napa, Cyprus, October 31 - November 4, 2005 MECOSIG - Monitoring Matrix

5 SEBGIS 2005, Agia Napa, Cyprus, October 31 - November 4, 2005 Adaptations - Descriptive level  Group of actors of the organization(s) must be identified  Actors have their own: set of privileges specific use cases  More often a specialization relationship exists between them

6 SEBGIS 2005, Agia Napa, Cyprus, October 31 - November 4, 2005 Adaptations - Descriptive level  Concerning processes (in particular crossed processes in distributed GIS), interactions between groups of actors and the System are identified in terms of: textual descriptions UML use cases  Data are identified according to use cases  Data are described in a catalogue and quality must be analysed Use of standards (ISO & 19115) is recommended  Further agreements must be achieved in order to incorporate semantic rules in spatial data domain (interoperability requirements …)

7 SEBGIS 2005, Agia Napa, Cyprus, October 31 - November 4, 2005 MECOSIG - Monitoring Matrix

8 SEBGIS 2005, Agia Napa, Cyprus, October 31 - November 4, 2005 Adaptations - Conceptual level  UML class diagram used to design Data (original formalism proposed in MECOSIG - CONGOO is substituted) is internationally admitted as standard (System modelling) offers more than only one diagram  design can combine serial of models to depict a context  Specificity of spatial data in UML object’s geometry  a lot of studies [e.g. COMOSIG Workshops ER2004, Bédard & al., 2004] dealt with  stereotypes or tagged values allow to adapt UML topological relationships  concept of topological matrix (originally from CONGOO) is added and adapted  two kinds of topological matrix are available the traditional matrix and the strong one

9 SEBGIS 2005, Agia Napa, Cyprus, October 31 - November 4, 2005 Adaptations - Conceptual level

10 SEBGIS 2005, Agia Napa, Cyprus, October 31 - November 4, 2005 Adaptations - Conceptual level  Every use case is extracted from the descriptive level and detailed using UML activity diagrams  Sequence diagrams are used to conceptualize specific scenarios of activity diagrams

11 SEBGIS 2005, Agia Napa, Cyprus, October 31 - November 4, 2005 MECOSIG - Monitoring Matrix

12 SEBGIS 2005, Agia Napa, Cyprus, October 31 - November 4, 2005 Adaptations - Organizational level  Facing the implementation of a distributed infrastructure, important organisational constraints must be met missions of all actors should be assessed and possibly redefined new tasks are introduced in order to guarantee  maintenance, permanent working and growth of the distributed System new data flows are generated and others have to be adapted data exchange must be performed easily and in a transparent way for all users  access to metadata [ISO standards] - particularly metadata related to quality (data usability and appraisal of final results)  some data / services access can be restricted or subject to authorization(s)

13 SEBGIS 2005, Agia Napa, Cyprus, October 31 - November 4, 2005 Adaptations - Organizational level  From these purposes coming up representative’s committees in charge of coordination tasks formalization can also be introduced to depict their tasks (UML use cases, activity & sequence diagrams, …)

14 SEBGIS 2005, Agia Napa, Cyprus, October 31 - November 4, 2005 MECOSIG - Monitoring Matrix

15 SEBGIS 2005, Agia Napa, Cyprus, October 31 - November 4, 2005 Adaptations - Logical-Physical level  Roles and tasks of all actors should be clearly specified key is to associate all actors in the new System which will be set up  e.g.: sensitizing and training sessions to facilitate the understanding of the re-engineered system possible reallocation of human resources  Constitution of the representative’s committees in charge of coordination tasks competent and representative of the various departments or organizations receiving the ability to act decisively  Managerial economies and economies of scale could be achieved Acquisition of common reference data Globalisation of software licenses

16 SEBGIS 2005, Agia Napa, Cyprus, October 31 - November 4, 2005 Adaptations - Logical-Physical level  A technical study must be completed to guarantee the required degree of interoperability to identify precisely  add-on hardware and software  distributed system components  systems for cross-relating items of information across multiple sources  Modelling process is to design objects which must be deployed in a distributed System e.g. data storage structure (components and deployment UML diagrams) previous activity and sequence diagrams (conceptual level) are improved  by adding objects dealing with data flows, procedures and processes according to GIS software, tools and DBMS specificities...

17 SEBGIS 2005, Agia Napa, Cyprus, October 31 - November 4, 2005 Adaptations - Logical-Physical level

18 SEBGIS 2005, Agia Napa, Cyprus, October 31 - November 4, 2005 Adaptations - Logical-Physical level  Whole of the logical-physical level is integrated into a evolutionary project pilot

SEBGIS 2005, Agia Napa, Cyprus, October 31 - November 4, 2005 Thank you… Q / A ?