Chapter 3 Object Oriented Systems and Open GIS. Objectives of the Chapter Establish place of O-O in OpenGIS cover basics of O-O emphasise design issues.

Slides:



Advertisements
Similar presentations
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 14 Slide 1 Object-oriented Design 1.
Advertisements

Ch:8 Design Concepts S.W Design should have following quality attribute: Functionality Usability Reliability Performance Supportability (extensibility,
UML an overview.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 12Slide 1 Software Design l Objectives To explain how a software design may be represented.
Chapter 2 – Software Processes Lecture 1 1Chapter 2 Software Processes.
Chapter 7 – Object-Oriented Design
Introduction to Databases
Chapter 22 Object-Oriented Systems Analysis and Design and UML Systems Analysis and Design Kendall and Kendall Fifth Edition.
Object-Oriented Analysis and Design
2-1 © Prentice Hall, 2007 Chapter 2: Introduction to Object Orientation Object-Oriented Systems Analysis and Design Joey F. George, Dinesh Batra, Joseph.
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.
L4-1-S1 UML Overview © M.E. Fayad SJSU -- CmpE Software Architectures Dr. M.E. Fayad, Professor Computer Engineering Department, Room #283I.
Object-Oriented Databases v OO systems associated with – graphical user interface (GUI) – powerful modeling techniques – advanced data management capabilities.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 8 Slide 1 System models September 29, 2008.
©Ian Sommerville 2000Software Engineering, 6/e, Chapter 71 System models l Abstract descriptions of systems whose requirements are being analysed.
7M701 1 Class Diagram advanced concepts. 7M701 2 Characteristics of Object Oriented Design (OOD) objectData and operations (functions) are combined 
Object-Oriented Databases
Lecturer: Dr. AJ Bieszczad Chapter 66-1 Object-Oriented analysis and design Special nature of OO development Use cases Design with UML OO system design.
Modified from Sommerville’s originalsSoftware Engineering, 7th edition. Chapter 8 Slide 1 System models.
© Copyright Eliyahu Brutman Programming Techniques Course.
Chapter 10 Class and Method Design
Architectural Design Establishing the overall structure of a software system Objectives To introduce architectural design and to discuss its importance.
Software Process Activities. Process activities Real software processes are inter-leaved sequences of technical, collaborative and managerial activities.
Chapter 1 The Systems Development Environment
The Design Discipline.
©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.
An Introduction to Software Architecture
Copyright 2002 Prentice-Hall, Inc. Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich Chapter 20 Object-Oriented.
Database Management System Prepared by Dr. Ahmed El-Ragal Reviewed & Presented By Mr. Mahmoud Rafeek Alfarra College Of Science & Technology Khan younis.
Object Oriented Analysis & Design & UML (Unified Modeling Language)1 Part V: Design The Design Workflow Design Classes Refining Analysis Relationships.
©Ian Sommerville 1995/2000 (Modified by Spiros Mancoridis 1999) Software Engineering, 6th edition. Chapter 7 Slide 1 System models l Abstract descriptions.
11 Chapter 11 Object-Oriented Databases Database Systems: Design, Implementation, and Management 4th Edition Peter Rob & Carlos Coronel.
RELATIONAL FAULT TOLERANT INTERFACE TO HETEROGENEOUS DISTRIBUTED DATABASES Prof. Osama Abulnaja Afraa Khalifah
1 UML Basic Training. UML Basic training2 Agenda  Definitions: requirements, design  Basics of Unified Modeling Language 1.4  SysML.
Chapter 7 System models.
System models l Abstract descriptions of systems whose requirements are being analysed.
Modified by Juan M. Gomez Software Engineering, 6th edition. Chapter 7 Slide 1 Chapter 7 System Models.
Software Engineering, 8th edition Chapter 8 1 Courtesy: ©Ian Somerville 2006 April 06 th, 2009 Lecture # 13 System models.
Sommerville 2004,Mejia-Alvarez 2009Software Engineering, 7th edition. Chapter 8 Slide 1 System models.
Chapter 10 Analysis and Design Discipline. 2 Purpose The purpose is to translate the requirements into a specification that describes how to implement.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 14 Slide 1 Object-oriented Design.
L6-S1 UML Overview 2003 SJSU -- CmpE Advanced Object-Oriented Analysis & Design Dr. M.E. Fayad, Professor Computer Engineering Department, Room #283I College.
Object-Oriented Analysis and Design. Lesson 1: Introduction to Software Engineering.
SWT - Diagrammatics Lecture 4/4 - Diagramming in OO Software Development - partB 4-May-2000.
What is Object-Oriented?  Organization of software as a collection of discreet objects that incorporate both data structure and behavior.
OBJECT ORIENTED AND FUNCTION ORIENTED DESIGN 1 Chapter 6.
Architecture View Models A model is a complete, simplified description of a system from a particular perspective or viewpoint. There is no single view.
Chapter 5 System Modeling. What is System modeling? System modeling is the process of developing abstract models of a system, with each model presenting.
©Ian Sommerville 2006Software Engineering, 8th edition. Chapter 4 Slide 1 Software Processes.
1 SWE Introduction to Software Engineering Lecture 14 – System Modeling.
Wrap up. Structures and views Quality attribute scenarios Achieving quality attributes via tactics Architectural pattern and styles.
Chapter 5 – System Modeling Lecture 1 1Chapter 5 System modeling.
Engineering, 7th edition. Chapter 8 Slide 1 System models.
Chapter 1: Introduction to Systems Analysis and Design
CS 389 – Software Engineering
Object-Oriented Analysis and Design
Systems Analysis and Design With UML 2
Abstract descriptions of systems whose requirements are being analysed
Chapter 2 – Software Processes
Chapter 20 Object-Oriented Analysis and Design
An Introduction to Software Architecture
Introduction to Systems Analysis and Design Stefano Moshi Memorial University College System Analysis & Design BIT
Chapter 1: Introduction to Systems Analysis and Design
Design Yaodong Bi.
Chapter 22 Object-Oriented Systems Analysis and Design and UML
Chapter 1: Introduction to Systems Analysis and Design
Presentation transcript:

Chapter 3 Object Oriented Systems and Open GIS

Objectives of the Chapter Establish place of O-O in OpenGIS cover basics of O-O emphasise design issues of O-O provide overview of complex technical issues of O-O inOpenGIS illustrate O-O system

Objectives of the Chapter show why O-O is important in OpenGIS provide example of O-O system set exercise in O-O design for GIS link to other OpenGIS issues

Structure of the Chapter introduction basics of O-O use of O-O merits of O-O project methods a sample system

Structure of the Chapter Technical sytems background on –interoperability and O-O –geosystems and O-O OpenGIS –systems design in O-O environment –system examples of O-O use –related issues in an open environment

O-O in general The nature of object oriented thinking the use of objects throughout the analysis and design stages the benefits of objects

What are O-O Systems Source of materials overview of approach to O-O analysis design

What are O-O Systems Characterisitcs of an O-O system are: abstraction encapsulation hierarchies communication via messages

What are O-O Systems? Object Orientation is not defined by O-O language but by the four characteristics O-O design is the key Design preceeds coding

Object Statics Instances Classes Attributes defaults probability multiplicity qualifiers constraints derived attributes

Object Relations Relationships arity Features cardinality qualifiers Constraints Parametric realtional Instances Collections

Object Dynamics Problem of Describing Behaviour Transition networks Parallelism Ensembles States

Object Interaction One and two way interaction Guards Transitions and events Sending and Receiving Protocols

O-O Software Engineering Basic elemenets of methods Waterfall Model O-O Methods spcifics O-O Methods types O-O Methods sequences of stages

O-O Analysis User Perspectives in Analysis Problem Specification Object Discovery –evaluation Object hierarchies and attributes Object messages and methods

O-O from Analysis to Design Ideally with an O-O approach analysis and design mesh seamlessly. The Design follows a series of: –transformations which correspond to –design phases

O-O from Analysis to Design Design Criteria based on classes basic issue is coupling basis of interoperability set of design issues related to »representation »values »protocols »code ruling ideas are cohesion and reliability

O-O from Analysis to Design Management of Design –Roles support teams –Reuse and Tools controling components evaluating components evaluating use

Method Default steps –requirements –system context –sub-systems –vocabulary –classes and relations –models Alternative Approaches

Project Methods Approaches to system analysis and design are based in genral on the waterfall model this is weak in many respects alternative approches are based on O-O and other technologies which allow rapid modification and re-use and therefore demand a different sequence of design stages and allow prototyping

Relative Merits of O-O Considered in relation to system functions and to business benefits system fucntion benefits realte to compatability and ease of use business benefits are manifold realting to better design and more focussed operations which produce effectiveness and efficiency gains

Object-Orientation and OpenGIS What does O-O mean for GIS?

OGIS and O-O Basics of Interoperable GIS –Interoperability by means of specification manufacturers comliance with Open criteria these are based on the object model at each design level –Open systems are based on Distributed Computing Platforms OGIS will be independent of these this is the challenge!!

OGIS and O-O –based on O-O ideas and technology –but requiring a hybrid approach key issues are – encapsulation –inheritance

OGIS and O-O OGIS model is – Pluggable Computing Model –high level design model –basis for links to non-spatial software, services and systems

Figure 4-4

Figure 4-5

Services in the Pluggable Component Model Human-Technology Interface Services Tool Services Data Management Services Distributed Computing Platform (DCP) Services Operating System Services Hardware Platforms

OGIS and O-O Benefits of the Pluggable Computing Model –clarity of design issues –resource sharing –data transfer –enhanced functionality –incorporate legacy systems

Benefits of model Scalability extendibility diversity interoperability

OGIS and O-O The Open Geodata Model –levels of abstraction –entities and phenomena

Geodata model- time/ location

Features and Coverages Views of the world

Coverages and features

Components of features Geometry properties metadata

Definitions of elements Associated with elements are detailed definitions open geoprocessing and interoperability rely on definitions and their use the open model can cope with some inconsistencies

OGIS community model Making it work requires agreement this is a question of organisation and of designing agreeable specifications it is all a question of the information community and how it works

Community and semantics Five assumptions of community semantics

Community and semantics The other three assumptions

What does this mean for Open GIS and O-O Semantics is at the heart of the open GIS problem issues of design are bound up with user definitions business benefits are bound up with openness and interoperability therefore semantic issues and translators are vital

Design issues - an example See the paper by Peter Batty on O-O Some objectivity please. gives some details of design questions and the role of O-O Also see the paper on legacy data and its challenges

Design issues - second example See the paper by Gebhart and Porter which raises the key issues for what is perhaps the most difficult area for interoperability and open systems - legacy data

Open systems To date there have been no true interoperable systems the creation of the vision is a long term objective elements of the vision exist in network systems and partial open functionality

example One example of a network system is Map Objects Internet Map Server Map Objects has a object structure seen in its system diagram this structure is basically the same as classic Arc Info but translated into object form it operates over the internet visit the diagram and the web site to familiarise yourself with them

Example An example of partial interoperable GIS is Geomedia already the leader but not fully interoperable visit the web site and use it in the practical classes

Exercise