GEOSS Model Based System Engineering Session Plan By Lawrence E. McGovern, DSC International Council on System Engineering/Blue Heron Services.

Slides:



Advertisements
Similar presentations
Overview: Guide for applying RM-ODP with UML Profile for EDOC
Advertisements

Global Earth Observation System of Systems
2/11/2014 8:44 AM The CDA Release 3 Specification Stack September 2009 HL7 Services-Aware Enterprise Architecture Framework (SAEAF)
ITU-T/SG 17 Mar ITU-T and ISO/IEC Joint Standards for Open Distributed Processing Bryan Wood Convenor, JTC1/SC7/WG19
1 UK e-Science All-Hands Meeting Nottingham, 2004 Enterprise specification of the NERC DataGrid Andrew Woolf, Ray Cramer.
Halifax, 31 Oct – 3 Nov 2011ICT Accessibility For All Recent Standardization Activities on Cloud Computing Kishik Park, Kangchan Lee, Seungyun Lee TTA.
Open Distributed Processing in SC7 - Status and Future Bryan Wood (Convenor WG19) SC7 AG 12 May 2002.
Research and Innovation Research and Innovation Introduction 2013 Sprint to Summit (StoS) Barcelona, 16 April 2013 Alan EDWARDS Earth Observation Sector.
Aligning Business Processes to SOA B. Ramamurthy 6/16/2015Page 1.
Using Architecture Frameworks
Applying the ISO RM-ODP Standard in e-Government B. Meneklis 1, A. Kaliontzoglou 2,3, D. Polemi 1, C. Douligeris 1 1 University of Piraeus, Department.
1 ECCF Training 2.0 Introduction ECCF Training Working Group January 2011.
Architecture A system architecture is the conceptual design that defines the structure and/or behavior of a system There is no universally agreed definition.
Systems Engineering Foundations of Software Systems Integration Peter Denno, Allison Barnard Feeney Manufacturing Engineering Laboratory National Institute.
Roles and Responsibilities Jahangheer Shaik. Service Specification Specification requires development of three inter-related documents CIM, PIM and PSM.
OMG ADTF, 24 June ITU-T X.906 | ISO/IEC Use of UML for ODP system specifications Bryan Wood Convenor, JTC1/SC7/WG19, Modelling Languages.
International Telecommunication Union ITU-T Study Group 17, Moscow, 30 March – 8 April 2005 New Recommendations on ODP Arve Meisingset Rapporteur Q15.
Training of master Trainers Workshop 10 – 15 November 2012 e-Services Design and Delivery Module VI Emilio Bugli Innocenti.
Formalizing ODP Computational Viewpoint Specification in Maude Raúl Romero and Antonio Vallecillo EDOC 2004 Dpto. Lenguajes y Ciencias de la Computación.
1 ECCF Training 2.0 Platform Specific Model (PSM) ECCF Training Working Group January 2011.
Geospatial Systems Architecture Todd Bacastow. GIS Evolution
TF-DI Meeting 13-Aug Agenda Discovery presentation from William Miller Review of discussions at F2F Sunnyvale Interaction patterns of tech landscape.
International Telecommunication Union Geneva, 9(pm)-10 February 2009 ITU-T Security Standardization on Mobile Web Services Lee, Jae Seung Special Fellow,
These materials are prepared only for the students enrolled in the course Distributed Software Development (DSD) at the Department of Computer.
WP5 Synthesis, recommendations and defining of the SRA Karel Charvat, Sarka Horakova, Ota Cerba WirelessInfo.
Web Services based e-Commerce System Sandy Liu Jodrey School of Computer Science Acadia University July, 2002.
Enterprise Architecture [Product Name] [Enterprise Architect] [Discipline and Names] To-Be Powerpoint Presentation v
Slide # 1 GEO Task AR Architecture Implementation Pilot George Percivall GEO ADC Meeting, 14 & 15 May 2007.
Ocean Observatories Initiative Data Management (DM) Subsystem Overview Michael Meisinger September 29, 2009.
Geospatial Systems Architecture Todd Bacastow. Views of a System Architecture Enterprise Information Computational Engineering Technology.
UML 2 Models for ODP Engineering/Technology Viewpoints – An Experiment - Daisuke Hashimoto Hiroshi.
1 ECCF Training 2.0 Implemental Perspective (IP) ECCF Training Working Group January 2011.
FDT Foil no 1 On Methodology from Domain to System Descriptions by Rolv Bræk NTNU Workshop on Philosophy and Applicablitiy of Formal Languages Geneve 15.
1 ECCF Training 2.0 Introduction ECCF Training Working Group January 2011.
ANKITHA CHOWDARY GARAPATI
GRID Overview Internet2 Member Meeting Spring 2003 Sandra Redman Information Technology and Systems Center and Information Technology Research Center National.
EGOS LLC CCSDS 14/ Question Question; Why a Service Viewpoint? Short Answer; Because a service viewpoint provides a useful additional level.
Modeling the ODP Computational Viewpoint with UML 2.0: The Templeman Library Example José Raúl Romero, Antonio Vallecillo Universidad de Málaga, Spain.
Geospatial Systems Architecture
These materials are prepared only for the students enrolled in the course Distributed Software Development (DSD) at the Department of Computer.
Science and Technology Norwegian University of NTNU Rolv Bræk, January Introduction to Systems Engineering by Rolv Bræk NTNU.
1 ECCF Training Computationally Independent Model (CIM) ECCF Training Working Group January 2011.
Slide no. 1  =====!"§!“!Nova§ ITU-T work on technical languages and general software issues Amardeo Sarma Chairman, ITU-T Study Group 10.
DISCUSSION ABOUT REGISTRATION OF RM-ODP LIBRARY EXAMPLE BASED ON MFI Yuan Lin, Wang Jian, Wang Chong, Liang Peng, Feng Zaiwen.
WG2 Roadmap Discussion Denise Warzel May 25, 2010 WG2 Convenor SC32 WG2N1424SC32 WG2N1424.
ISWG / SIF / GEOSS OOSSIW - November, 2008 GEOSS “Interoperability” Steven F. Browdy (ISWG, SIF, SCC)
® Reference Architecture and Agile Development George Percivall OGC Chief Engineer 4 April 2014 Copyright © 2014, Open Geospatial Consortium.
GEOSS Model Based System Engineering Challenge team report for GEOSS AIP-6 By Lawrence E. McGovern, DSC INCOSE/WYLE Aerospace/Timothy Woodard, Tellus /Kenneth.
INTRODUCTION: This report contains the results of the International Council on System Engineering (INCOSE) UML/SySML Team efforts to produce UML/SySML.
ISWG / SIF / GEOSS OOS - August, 2008 GEOSS Interoperability Steven F. Browdy (ISWG, SIF, SCC)
Developing an IDM Information Delivery Manual Part 1. Industry Workgroup Training, Creating IDMs Alliance NA 2010 Dianne Davis, NA-IDM Coordinator Jan.
INTRODUCTION: This report contains the results of the International Council of System Engineer (INCOSE) UML/SySML Team efforts to produce UML/SySML Architecture.
7/2/2016 1:52 AM HL7 SOA-Aware Enterprise Architecture Executive Summary HITSP October 28, 2008 Executive Summary HITSP October 28, 2008.
OGC’s role in GEO: Results from the Architectural Implementation Pilot (AIP) George Percivall Open Geospatial Consortium GEO Task IN-05 Coordinator
1 CASE Computer Aided Software Engineering. 2 What is CASE ? A good workshop for any craftsperson has three primary characteristics 1.A collection of.
HL7 SOA-Aware Enterprise Architecture
Workplan for Updating the As-built Architecture of the 2007 GEOSS Architecture Implementation Pilot Session 7B, 6 June 2007 GEOSS Architecture Implementation.
CV-1: Vision The overall vision for transformational endeavors, which provides a strategic context for the capabilities described and a high-level scope.
University of Central Florida COP 3330 Object Oriented Programming
Measuring Outcomes of GEO and GEOSS: A Proposed Framework for Performance Measurement and Evaluation Ed Washburn, US EPA.
Live-Virtual-Constructive (LVC) Technologies – Introduction
Quality management standards
Geospatial Service Architecture Viewpoints
More Requirements Models
واسط كاربري هوشمند Intelligent User Interface
FDA-08 FDA Whitepaper Update
ENVRI Reference Model (RM) Information Viewpoint components
Sample Test Questions Please identify the use cases of the system that cover all the behaviors described in the system specification. Please identify.
Recent Standardization Activities on Cloud Computing
Presentation transcript:

GEOSS Model Based System Engineering Session Plan By Lawrence E. McGovern, DSC International Council on System Engineering/Blue Heron Services

Agenda for INCOSE GEOSS MBSE Session Societal Benefit Area(SBA) Alignment and Support effort plan – Development of Enterprise View by completing Use case realization for each SBA Use Case Realization of GEOSS Transverse Technology Use Cases and completion of the RM-ODP Five Viewpoints

Societal Benefit Area(SBA) Alignment and Support effort plan

RM-ODP Viewpoints and Modeling Reference Model of Open Distributed Processing (RM-ODP) is a reference model in computer science, which provides a coordinating framework for the standardization of open distributing processing (ODP) It supports distribution, Internet working, platform and technology independence, and portability, together with an enterprise architecture framework for the specification of ODP systems

RMP-ODP Standards RM-ODP, also named ITU-T Rec. X.901-X.904 and ISO/IEC 10746, is a joint effort by the International Organization for Standardization (ISO), the International Electromechanical Commission (IEC) and the Telecommunication Standardization Sector (ITU-T) RMP View Model Viewpoints addressed in Volume 3 of ISO/IEC 10746

ODP Frameworks Descriptions The RM-ODP framework provides five generic and complementary viewpoints on the system and its environment: The enterprise viewpoint, which focuses on the purpose, scope and policies for the system. It describes the business requirements and how to meet them. The information viewpoint, which focuses on the semantics of the information and the information processing performed. It describes the information managed by the system and the structure and content type of the supporting data. The computational viewpoint, which enables distribution through functional decomposition on the system into objects which interact at interfaces. It describes the functionality provided by the system and its functional decomposition. The engineering viewpoint, which focuses on the mechanisms and functions required to support distributed interactions between objects in the system. It describes the distribution of processing performed by the system to manage the information and provide the functionality. The technology viewpoint, which focuses on the choice of technology of the system. It describes the technologies chosen to provide the processing, functionality and presentation of information.

ENTERPRISE VIEW The Enterprise view contains the results of the Use Case Realization in the form of a Use case Diagram and an Activity Diagram, and Sequence Diagram for each Use Case of the Use Case Diagram. The steps of the Use Case Narrative in definition of the Use Case become activities in activity diagram

Enterprise View-Use Case Diagram

Enterprise View – Activity Diagram

Enterprise View – Sequence Diagram

Information View Diagram (Class) Information View- Information/Changes to Information/Constraints

COMPUTATIONAL VIEW The computational viewpoint, enables distribution through functional decomposition on the system into objects which interact at interfaces. It describes the functionality provided by the system and its functional decomposition.

Computational View Templates

Computational View – Object Template

Computational View Data Types

Computational View –Interface Signature

ENGINEERING VIEWPOINT The engineering viewpoint, which focuses on the mechanisms and functions required to support distributed interactions between objects in the system. It describes the distribution of processing performed by the system to manage the information and provide the functionality.

Engineering View

TECHNOLOGY VIEWPOINT The technology viewpoint, which focuses on the choice of technology of the system. It describes the technologies chosen to provide the processing, functionality and presentation of information.

Technology Viewpoint Example- Deployment Diagram

USE CASE REALIZATION OF GEOSS TRANSVERSE TECHNOLOGY USE CASES AND COMPLETION OF THE RM-ODP FIVE VIEWPOINTS

Transverse Use Case Realization Steps in use cases are defined by the Transverse use groups Use Cases will be subject to a Realization process that will yield an Activity Diagram and Sequence Diagram that will be part of the RM-ODP Enterprise Viewpoint Transvers Use Cases provide for the Registering of data in Clearinhouse, Discover and Get Access and allowing User to Access Data from the provider

Transverse Use Cases