DOT’98 Heidelberg 1 A. Hoffmann & M. Born Requirements for Advanced Distribution and Configuration Support GMD FOKUS Andreas Hoffmann & Marc Born Email:

Slides:



Advertisements
Similar presentations
1 Aspects of IEEE P1471 Viewpoints in Unified Modeling Language (UML) Manzur Ashraf, BRAC University Humayra Binte Ali, Dhaka University Md.Mahfuz Ashraf,
Advertisements

Tool support for Distributed Object Technology
Architecture Representation
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 12Slide 1 Software Design l Objectives To explain how a software design may be represented.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 12 Slide 1 Distributed Systems Design 2.
Lecturer: Sebastian Coope Ashton Building, Room G.18 COMP 201 web-page: Lecture.
A Brief Introduction. Acknowledgements  The material in this tutorial is based in part on: Concurrency: State Models & Java Programming, by Jeff Magee.
Approaches to EJB Replication. Overview J2EE architecture –EJB, components, services Replication –Clustering, container, application Conclusions –Advantages.
Reseach in DistriNet (department of computer science, K.U.Leuven) General overview and focus on embedded systems task-force.
1 © Wolfgang Pelz UML3 UML 3 Notations describe how to use reusable software. Package Component Deployment Node.
Distributed Systems Architectures
A brief look at CORBA. What is CORBA Common Object Request Broker Architecture developed by OMG Combine benefits of OO and distributed computing Distributed.
CS 501: Software Engineering Fall 2000 Lecture 16 System Architecture III Distributed Objects.
Simulation concepts and architectures. Simulation Basics System: a collecting of entities that act and interact together toward the accomplishment of.
Using Architecture Frameworks
CS CS 5150 Software Engineering Lecture 13 System Architecture and Design 1.
Communication in Distributed Systems –Part 2
Using UML Models for the Performance Analysis of Network Systems Nico de Wet and Pieter Kritzinger Department of Computer Science University of Cape Town.
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.
Basic Concepts The Unified Modeling Language (UML) SYSC System Analysis and Design.
31 January 2007Craig E. Ward1 Large-Scale Simulation Experimentation and Analysis Database Programming Using Java.
©Ian Sommerville 2006Software Engineering, 8th edition. Chapter 18 Slide 1 Software Reuse.
Software Engineering Muhammad Fahad Khan
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 18 Slide 1 Software Reuse.
Formalizing ODP Computational Viewpoint Specification in Maude Raúl Romero and Antonio Vallecillo EDOC 2004 Dpto. Lenguajes y Ciencias de la Computación.
©Ian Sommerville 2006Software Engineering, 8th edition. Chapter 12 Slide 1 Distributed Systems Architectures.
Workshop on Integrated Application of Formal Languages, Geneva J.Fischer Mappings, Use of MOF for Language Families Joachim Fischer Workshop on.
Interoperating with Services in a Mobile Environment Andreas Dahl, Pål Rolfsen Grønsund, Per Thomas Kraabøl,
An Introduction to Software Architecture
MILCOM 2001 October page 1 Defense Enabling Using Advanced Middleware: An Example Franklin Webber, Partha Pal, Richard Schantz, Michael Atighetchi,
1 of of 25 3 of 25 ORBs (Object Request Broker) – A distributed software bus for communication among middleware services and applications – To.
Information System Development Courses Figure: ISD Course Structure.
A Web-based Distributed Simulation System Christopher Taewan Ryu Computer Science Department California State University, Fullerton.
1 Introduction to Software Engineering Lecture 1.
Documenting Software Architectures 1.Uses and Audiences for Architecture Documentation Architecture documentation serves as a means of education Architecture.
DISTRIBUTED SYSTEMS Principles and Paradigms Second Edition ANDREW S
07/09/04 Johan Muskens ( TU/e Computer Science, System Architecture and Networking.
Understanding Code Mobility A Fuggetta, G P Picco and G Vigna Presenter Samip Bararia.
UML 2 Models for ODP Engineering/Technology Viewpoints – An Experiment - Daisuke Hashimoto Hiroshi.
Grid programming with components: an advanced COMPonent platform for an effective invisible grid © 2006 GridCOMP Grids Programming with components. An.
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.
Computing and SE II Chapter 9: Design Methods and Design Models Er-Yu Ding Software Institute, NJU.
Logical view –show classes and objects Process view –models the executables Implementation view –Files, configuration and versions Deployment view –Physical.
1 Choices “Our object-oriented system architecture embodies the notion of customizing operating systems to tailor them to support particular hardware configuration.
Laboratory of Model Driven Engineering for Embedded Systems An Execution Framework for MARTE-based Models UML&AADL’2008 workshop Belfast, Northern Ireland.
A Component Platform for Experimenting with Autonomic Composition A component framework for supporting composition of autonomic services and bio-inspired.
OBJECT ORIENTED AND FUNCTION ORIENTED DESIGN 1 Chapter 6.
ProActive components and legacy code Matthieu MOREL.
Slide title In CAPITALS 50 pt Slide subtitle 32 pt Robust Reconfigurable Erlang Component System ErlCOM Gabor Batori, Zoltan Theisz, Domonkos Asztalos.
Architecture View Models A model is a complete, simplified description of a system from a particular perspective or viewpoint. There is no single view.
Modeling the ODP Computational Viewpoint with UML 2.0: The Templeman Library Example José Raúl Romero, Antonio Vallecillo Universidad de Málaga, Spain.
Object Oriented Analysis and Design 1 Chapter 9 From Design to Implementation  Implementation Model  Forward, Reverse, and Round-Trip Engineering  Mapping.
Integrated application of eODL 1 J.Fischer Integrated application of eODL Workshop Integrated application of eODL Geneva, 13 September 2003 Harald Böhme,
Distributed System Architectures Yonsei University 2 nd Semester, 2014 Woo-Cheol Kim.
Science and Technology Norwegian University of NTNU Rolv Bræk, January Introduction to Systems Engineering by Rolv Bræk NTNU.
Slide 1 Service-centric Software Engineering. Slide 2 Objectives To explain the notion of a reusable service, based on web service standards, that provides.
Slide no. 1  =====!"§!“!Nova§ ITU-T work on technical languages and general software issues Amardeo Sarma Chairman, ITU-T Study Group 10.
A Pattern Language for Parallel Programming Beverly Sanders University of Florida.
INFSO-RI JRA2 Test Management Tools Eva Takacs (4D SOFT) ETICS 2 Final Review Brussels - 11 May 2010.
TTCN-3 Testing and Test Control Notation Version 3.
1 Distributed Systems Architectures Distributed object architectures Reference: ©Ian Sommerville 2000 Software Engineering, 6th edition.
Distributed Systems Architectures Chapter 12. Objectives  To explain the advantages and disadvantages of different distributed systems architectures.
Object-Oriented Analysis and Design
Systems Analysis and Design With UML 2
Workplan for Updating the As-built Architecture of the 2007 GEOSS Architecture Implementation Pilot Session 7B, 6 June 2007 GEOSS Architecture Implementation.
ITU languages for ODP - a personal view - I may be wrong!
Service-centric Software Engineering
Arve Meisingset WP3/10 chairman Telenor R&D, Norway
Analysis models and design models
Presentation transcript:

DOT’98 Heidelberg 1 A. Hoffmann & M. Born Requirements for Advanced Distribution and Configuration Support GMD FOKUS Andreas Hoffmann & Marc Born { a.hoffmann, born

DOT’98 Heidelberg 2 A. Hoffmann & M. Born Problems concerning deployment of distributed applications Requirement for engineering language Requirement for platform extensions Conclusion Overview

DOT’98 Heidelberg 3 A. Hoffmann & M. Born Need for distribution and configuration information ODLSDL System Design Validation MSC UML Requ. Captering Design Implementation Analysis Java C++ Coding Execution Information for distribution and configuration needed

DOT’98 Heidelberg 4 A. Hoffmann & M. Born Partitioning of specification and implementation into parts ready for distribution What is the unit for partitioning and distribution? –Depends from used language! –SDL: system, block, process –C++: CORBA objects? –ODL: objects, groups The partitioning problem

DOT’98 Heidelberg 5 A. Hoffmann & M. Born Assignment of the entities resulting from the partitioning (server, clients) to entities of the target environment (nodes, capsules...) Configuration (setting of properties) The installation or initial configuration problem

DOT’98 Heidelberg 6 A. Hoffmann & M. Born Re-assignment of the entities resulting from the partitioning to entities of the target environment Caused by several reasons: –QoS (or other constraints) violation –Version control –Changes of the environment The re-configuration problem

DOT’98 Heidelberg 7 A. Hoffmann & M. Born Partitioning of specification/implementation Target environment description Assignment of engineering spec. parts to target environment Configuration of target environment and spec. parts Dynamic update of Deployed System The process of configuration and distribution

DOT’98 Heidelberg 8 A. Hoffmann & M. Born What is needed to support deployment of distributed applications ? Engineering Language Partioning Assignment Configuration Platform Extensions Dynamic re-configuration

DOT’98 Heidelberg 9 A. Hoffmann & M. Born ODP - background for engineering Language ODP => Framework for open distributed systems Viewpoint Model => Managing the complexity of concurrent systems Only concepts; no methodology or concrete language Several appropriate languages for Computational Viewpoint ODL=>System structure (on Type Level Only) SDL=>System structure and behaviour... Need for an Engineering Viewpoint language

DOT’98 Heidelberg 10 A. Hoffmann & M. Born Advantages of separation of computational and engineering model Computational model remains stable Computational model serves for several purposes => Validation & simulation, test case gen., performance analysis Several engineering-mappings for the same computational model possible

DOT’98 Heidelberg 11 A. Hoffmann & M. Born Concepts of Engineering Language Defines engineering issues of the system –Partitioning of the system –Properties like binding mechanisms for interfaces (binder, stub, protocoll) –Communication mechanisms Defines the target environment –Nodes, capsules, cluster –Ressources and properties Allows assignment of constraints –QoS –Performance Textual and graphical representation?

DOT’98 Heidelberg 12 A. Hoffmann & M. Born Mapping from Computational to Engineering Viewpoint (2) O1 O3 O4 O2 Node1 Node2 Engineering1 Node2 Node1 Node4 Engineering3 O1 O3 O4 O2 Node3 O2 O1 O3 O4 Node1 Node2 Engineering2 O1 O3 O4 O2 Computational Environment1 Environment2

DOT’98 Heidelberg 13 A. Hoffmann & M. Born Support for Constraints Static and dynamic constraints –Static:Evaluation before CO instantiation Compiling constraints Instantiation constraints –Dynamic:Evaluation after CO instantiation Runtime constraints Types of constraints –Ressource constraints (e.g. band width, memory) –Execution constraints (e.g. shutdown coordination) –QoS constraints (e.g. response time) Constraints for –Types of COs and Groups of COs –Instances of those types –Both combined => Instance constraints must be compliant to type constraints QoS ObjectiveSubjective PerformanceTimeCostUsability

DOT’98 Heidelberg 14 A. Hoffmann & M. Born Support for Constraints(2) Computational ModelO1 O3 O4 O2 Instance Level Engineering Model Configuration Assignment Constraints Node1 Node2 Environment Model Constraints T1 T3 T4 T2 Type Level Constraints

DOT’98 Heidelberg 15 A. Hoffmann & M. Born Environment description Model for soft-/hardware –Equipment, devices, OS, DPE (Distr.Proc. Env.) functions Concepts –ODP concepts: node, capsule, cluster,... –Ressources and ressource types (for execution, communication) –Representations of DPE functions –Technology aspects (for practical reasons) Purpose –Description of an existing target environment –Abstract deployment requirements for a service Kinds of environment model –Abstract (DPE transparency) –Concrete (To support a concrete DPE)

DOT’98 Heidelberg 16 A. Hoffmann & M. Born Environment Model (2) Computational Model Abstract Environment Model Assignment (Abstract configuration) Assignment (Concrete configuation) Concrete Environment Model Concrete Environment Model Mapping Compliance Concrete DPE

DOT’98 Heidelberg 17 A. Hoffmann & M. Born Required platform extensions Monitoring of properties and analysis Evaluation of constraints (QoS, Performance...) Advanced management functions Cloning Replication Migration Version control

DOT’98 Heidelberg 18 A. Hoffmann & M. Born Conclusions Problems are: –Partitioning –Initial configuration (installation) –Dynamic re-configuration Possible solutions are: –Development of engineering language –Enhancement of execution platforms Starting points for development are: –ODP as theoretical background –UML and other notations for language development –Existing distributed processing environments (P715, GMD...)