We think you have liked this presentation. If you wish to download it, please recommend it to your friends in any social system. Share buttons are a little bit lower. Thank you!
Presentation is loading. Please wait.
Published byAdele Matthews
Modified about 1 year ago
Sponsored by the U.S. Department of Defense © 2005 by Carnegie Mellon University 1 Pittsburgh, PA 15213-3890 Dennis Smith, David Carney and Ed Morris DEAS Workshop May 21, 2005 Interoperability Issues for Autonomic Computing
© 2005 by Carnegie Mellon University Smith - 2 DEAS Workshop Context for Interoperability Most modern systems are usually a heterogeneous collection of custom and commercial products Integration provided by some third-party technology Modern systems are seldom expected to function independently Expected to cooperate with existing systems The ability to achieve “cooperation” is generally termed "interoperability“ Elements of these cooperating systems undergo frequent (e.g., upgrades of commercial products) Thus: boundaries within and between systems begin to blur Distinction between a "system of systems" and a single, complex, distributed system disappears
© 2005 by Carnegie Mellon University Smith - 3 DEAS Workshop System “C” We know quite a lot about constructing systems from components (over which we may have little or no control). Current State of Our Knowledge We know something about composing systems of systems from individual systems (over which we may have little or no control). System “B” We know very little about constructing an interoperable network of systems…the key distinction being that the network is unbounded (or very loosely bounded) and has no single controlling authority. System “A” “SYSTEM D” Unplanned, unexpected, emergent behavior here…
© 2005 by Carnegie Mellon University Smith - 4 DEAS Workshop Autonomic Computing Requires Attention to Interoperability Issues Selected relevant autonomic characteristics: Reflexivity: detailed knowledge of a system’s components and their inter-dependencies Self-configuration: reconfiguring at run-time and adaptive algorithms can benefit from research in interoperability on “emergent algorithms” Evolving: the evolution of systems relies directly on understanding how to add components and systems to an existing system or system of systems
© 2005 by Carnegie Mellon University Smith - 5 DEAS Workshop Interoperability Issues That Can Impact Autonomic Systems Tests to verify interoperability often fail to identify interoperability shortfalls When interoperability is achieved, it is often difficult to maintain as new versions of constituent systems are released Planned interoperability between new systems is often scaled back to maintain compatibility with older systems Strict specification of standards for achieving desired levels of interoperability is often insufficient because organizations constructing compliant standards often interpret them in different ways
© 2005 by Carnegie Mellon University Smith - 6 DEAS Workshop Principles Required to Address Interoperability for Autonomic Systems- 1 No clear distinction can be made between Systems and Systems of Systems. One man’s system-of-systems is another’s system. The critical factor is less where a boundary might lie and more where control lies -most systems are now created with some components over which the integrator has less than complete control There will always be new things to integrate into the system.
© 2005 by Carnegie Mellon University Smith - 7 DEAS Workshop Principles Required to Address Interoperability for Autonomic Systems- 2 Interoperability problems are independent of domain Most complex systems in almost every domain are now expected to interact with other complex systems Solutions cannot rely on complete information Classic software engineering practice assumes a priori understanding of the system being built, including complete and precise comprehension of assumptions, functionality, services, data and quality attribute needs. Multiple organizations have multiple—and rarely parallel—sets of expectations about the constituent parts and the entire system of systems
© 2005 by Carnegie Mellon University Smith - 8 DEAS Workshop Principles Required to Address Interoperability for Autonomic Systems- 3 No one-time solution Is possible As a result, new approaches are needed to -vet proposed requirements changes at the system and system-of-systems level -analyze the effect of proposed requirements and structural changes to systems and systems of systems -structure systems and systems of systems to avoid (or at least delay) the effect of changes -verify interoperability expectations to avoid surprises when systems are deployed
© 2005 by Carnegie Mellon University Smith - 9 DEAS Workshop Principles Required to Address Interoperability for Autonomic Systems- 4 Networks of interoperability demonstrate emergent properties Emergent properties are those properties of a whole that are different from, and not predictable from, the cumulative properties of the entities that make up the whole In very large networks, it is not possible to predict the behavior of the whole network from the properties of individual nodes. -Such networks are composed of large numbers of widely varied components (hosts, routers, links, users, etc.) that interact in complex ways with each other, and whose behavior “emerges” from the complex set of interactions that occur
© 2005 by Carnegie Mellon University Smith - 10 DEAS Workshop Common Observed Interoperability Problems- 1 Need for understanding on scope and mechanisms of interoperability Divisions of responsibility Many divisions in responsibility, obligation, and management Potential results of these divisions: -Things will fall through cracks -When problems occur, finger pointing can occur Requirements Requirements for interoperability are often ill –defined except to “work together” Requirements for different components and systems often continue to evolve Functionality Not all capabilities of different versions are compatible Achieving backward compatibility represents a major challenge
© 2005 by Carnegie Mellon University Smith - 11 DEAS Workshop Common Observed Interoperability Problems- 2 Processes (development and integration) There is often some degree of misfit between processes, methods and tools employed by different contributors to the system Other potential showstopper issues Scalability Performance Security Testing
© 2005 by Carnegie Mellon University Smith - 12 DEAS Workshop Selected Emerging Research Areas on Interoperability Issues for Autonomic Computing Models of interoperability Evolution of components Semantic issues Testing and validation Migration to net centric services Impact of joint interoperability and survivability requirements Characteristics of interoperability Implications of Service Oriented Architectures
CPSC 871 John D. McGregor Module 6 Session 3 System of Systems.
Software Engineering Techniques for the Development of System of Systems Seminar of “Component Base Software Engineering” course By : Marzieh Khalouzadeh.
Sponsored by the U.S. Department of Defense © 2006 by Carnegie Mellon University Version E-Gov 2006Benefits, Misconceptions and SOA Governance Issues -
Systems Engineering in a System of Systems Context Dr. Judith Dahmann The MITRE Corporation.
© 2006 Carnegie Mellon University Establishing a Network Centric Capability: Implications for Acquisition and Engineering Dennis Smith Complex System Symposium.
Software Architecture Quality. Outline Importance of assessing software architecture Better predict the quality of the system to be built How to improve.
Component Technology. Challenges Facing the Software Industry Today’s applications are large & complex – time consuming to develop, difficult and costly.
Lecture 7: Requirements Engineering. Waterfall Model.
Interoperability: Issues, Challenges, Solutions Bill Lober, MD MS Associate Professor, Health Informatics and Global Health Schools of Medicine, Nursing,
UML Unified Markup Language Ziya Karakaya Atılım University, Computer Engineering
Distribution and components. 2 What is the problem? Enterprise computing is Large scale & complex: It supports large scale and complex organisations Spanning.
Quality Management. What is a software product? Software product = computer programs (sources and executable) + associated documentation Software products.
Unified Modeling (Part I) Overview of UML & Modeling Elizabeth Bigelow Carnegie Mellon University.
Computational Thinking Related Efforts. CS Principles – Big Ideas Computing is a creative human activity that engenders innovation and promotes exploration.
The roots of innovation Future and Emerging Technologies (FET) Future and Emerging Technologies (FET) The roots of innovation Proactive initiative on:
Service Oriented Architecture (SOA) Dennis Schwarz November 21, 2008.
Welcome to DEAS 2005 Design and Evolution of Autonomic Application Software David Garlan, CMU Marin Litoiu, IBM CAS Hausi A. Müller, UVic John Mylopoulos,
On Roles of Models in Information Systems (Arne Sølvberg) Gustavo Carvalho 26 de Agosto de 2010.
SAMANVITHA RAMAYANAM 18 TH FEBRUARY 2010 CPE 691 LAYERED APPLICATION.
THE VISION OF AUTONOMIC COMPUTING. WHAT IS AUTONOMIC COMPUTING ? “ Autonomic Computing refers to computing infrastructure that adapts (automatically)
Copyright 2007 by Linda J. Vandergriff All rights reserved. Published 2007 System Engineering in the 21st Century - Implications from Complexity.
1 Ontological Foundations For SysML Henson Graves September 2010.
Ævol : A Tool for Planning Architecture Evolution David Garlan & Bradley Schmerl Carnegie Mellon University.
Software Engineering Principles. SE Principles Principles are statements describing desirable properties of the product and process.
System Requirement Specification and System Planning.
Introduction Infrastructure for pervasive computing has many challenges: 1)pervasive computing is a large aspect which includes hardware side (mobile phones,portable.
Basic Concepts and Definitions Software Architecture: a “set” of principal design decisions made about the system Software Reference Architecture: a set.
1 Chapter 2 Socio-technical Systems (Computer-based System Engineering)
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 20 Slide 1 Critical systems development 3.
Rational Unified Process Fundamentals Best Practices of Software Engineering Rational Unified Process Fundamentals Best Practices of Software Engineering.
Basic Concepts of Software Architecture. What is Software Architecture? Definition: – A software system’s architecture is the set of principal design.
Software Architecture for DSD DSD Team. Overview What is software architecture and why is it so important? The role of architecture in determining system.
Computer Engineering 203 R Smith Requirements Management 6/ Requirements IEEE Standard Glossary A condition or capability needed by a user to solve.
Copyright © Richard N. Taylor, Nenad Medvidovic, and Eric M. Dashofy. All rights reserved. NFP Design Techniques Software Architecture Lecture 20.
© 2011 Carnegie Mellon University System of Systems V&V John B. Goodenough October 19, 2011.
System Management Network Environment Vehicle Characteristics Traveler Characteristics System Traveler Influencing Factors Traveler: traveler characteristics,
Smart Home Technologies System Engineering. System Engineering in Intelligent Environments Intelligent Environments are complex systems consisting of.
©Ian Sommerville 2000 Software Engineering, 6th edition. Slide 1 Component-based development l Building software from reusable components l Objectives.
© City University London, Dept. of Computing Distributed Systems / Distributed Systems Session 1: Motivation Christos Kloukinas Dept. of Computing.
UML - Development Process 1 Software Development Process Using UML (2)
1 ISA&D7/8/ ISA&D7/8/2013 Systems Development Life Cycle Phases and Activities in the SDLC Variations of the SDLC models.
1 FM Overview of Adaptation. 2 FM RAPIDware: Component-Based Design of Adaptive and Dependable Middleware Project Investigators: Philip McKinley, Kurt.
©Ian Sommerville 2006Software Engineering, 8th edition. Chapter 12 Slide 1 Distributed Systems Architectures.
CS223: Software Engineering Lecture 13: Software Architecture.
1 From Grids to Service-Oriented Knowledge Utilities research challenges Thierry Priol.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 10Slide 1 Architectural Design l Establishing the overall structure of a software system.
June 05 David A. Gaitros Jean Muhammad Introduction to OOD and UML Dr. Jean Muhammad.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 18 Slide 1 Software Reuse.
Lockheed Martin Aeronautics Company Candidate Collaborative Projects for Net-Centric Application Michael F. Siok, PE Lockheed Martin Aeronautics Company.
© 2017 SlidePlayer.com Inc. All rights reserved.