System Monitoring using Constraint Checking as part of Model Based System Management 2007 Monitoring using Constraint Checking as part.

Slides:



Advertisements
Similar presentations
2009 – E. Félix Security DSL Toward model-based security engineering: developing a security analysis DSML Véronique Normand, Edith Félix, Thales Research.
Advertisements

From Model-based to Model-driven Design of User Interfaces.
Introducing Formal Methods, Module 1, Version 1.1, Oct., Formal Specification and Analytical Verification L 5.
Testing and Quality Assurance
LIFE CYCLE MODELS FORMAL TRANSFORMATION
Page 1 Automatic Evaluation of Modelling Rules and Design Guidelines, July 2006 Automatic Evaluation of Modelling Rules and Design Guidelines Tibor Farkas,
SWE Introduction to Software Engineering
Analysis Stage (Phase I) The goal: understanding the customer's requirements for a software system. n involves technical staff working with customers n.
Software Requirements
©Ian Sommerville 2000Software Engineering, 6/e, Chapter 91 Formal Specification l Techniques for the unambiguous specification of software.
Testing Components in the Context of a System CMSC 737 Fall 2006 Sharath Srinivas.
School of Computer ScienceG53FSP Formal Specification1 Dr. Rong Qu Introduction to Formal Specification
AOSE-2003, Melbourne July 15 th 1 Agent Oriented modeling by interleaving formal and informal analysis Anna Perini 1, Marco Pistore 2,1, Marco Roveri 1,
©Ian Sommerville 2006Software Engineering, 8th edition. Chapter 10 Slide 1 Formal Specification.
Principle of Functional Verification Chapter 1~3 Presenter : Fu-Ching Yang.
MCA –Software Engineering Kantipur City College. Topics include  Formal Methods Concept  Formal Specification Language Test plan creation Test-case.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 5 Slide 1 Requirements engineering l The process of establishing the services that the.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 2 Slide 1 Systems engineering 1.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 10 Slide 1 Critical Systems Specification 3 Formal Specification.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 10 Slide 1 Formal Specification.
Romaric GUILLERM Hamid DEMMOU LAAS-CNRS Nabil SADOU SUPELEC/IETR ESM'2009, October 26-28, 2009, Holiday Inn Leicester, Leicester, United Kingdom.
10 December, 2013 Katrin Heinze, Bundesbank CEN/WS XBRL CWA1: DPM Meta model CWA1Page 1.
Romaric GUILLERM Hamid DEMMOU LAAS-CNRS Nabil SADOU SUPELEC/IETR.
Do we need theoretical computer science in software engineering curriculum: an experience from Uni Novi Sad Bansko, August 28, 2013.
1. Human – the end-user of a program – the others in the organization Computer – the machine the program runs on – often split between clients & servers.
Chapter 1- Introduction Lecture 1 Ready, fire, aim (the fast approach to software development). Ready, aim, aim, aim, aim... (the slow approach to software.
DOT’98 Heidelberg 1 A. Hoffmann & M. Born Requirements for Advanced Distribution and Configuration Support GMD FOKUS Andreas Hoffmann & Marc Born
©Ian Sommerville 2000Software Engineering, 6th edition. Chapter 9 Slide 1 Formal Specification l Techniques for the unambiguous specification of software.
Chapter 4 – Requirements Engineering
المحاضرة الثالثة. Software Requirements Topics covered Functional and non-functional requirements User requirements System requirements Interface specification.
Software Models (Cont.) 9/22/2015ICS 413 – Software Engineering1 -Component-based software engineering -Formal Development Model.
©Ian Sommerville 2000, Mejia-Alvarez 2009 Slide 1 Software Processes l Coherent sets of activities for specifying, designing, implementing and testing.
Software Requirements Presented By Dr. Shazzad Hosain.
Overview of Formal Methods. Topics Introduction and terminology FM and Software Engineering Applications of FM Propositional and Predicate Logic Program.
WXGE6103 Software Engineering Process and Practice Formal Specification.
University of Southern California Center for Systems and Software Engineering Model-Based Software Engineering Supannika Koolmanojwong Spring 2013.
Dimitrios Skoutas Alkis Simitsis
Verification and Validation in the Context of Domain-Specific Modelling Janne Merilinna.
Lecture 7: Requirements Engineering
Rob Smith April 21, /18 GOLD Project Update Meeting GOLD an infrastructural approach to virtual organisations.
Model Checking and Model-Based Design Bruce H. Krogh Carnegie Mellon University.
Requirements Engineering Overview Senior Design Don Evans.
UML 2 Models for ODP Engineering/Technology Viewpoints – An Experiment - Daisuke Hashimoto Hiroshi.
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 Software Requirements l Specifying system functionality and constraints l Chapters 5 and 6 ++
Formal Methods in Software Engineering Credit Hours: 3+0 By: Qaisar Javaid Assistant Professor.
16/11/ Semantic Web Services Language Requirements Presenter: Emilia Cimpian
Architecture View Models A model is a complete, simplified description of a system from a particular perspective or viewpoint. There is no single view.
Software Engineering1  Verification: The software should conform to its specification  Validation: The software should do what the user really requires.
A Mediated Approach towards Web Service Choreography Michael Stollberg, Dumitru Roman, Juan Miguel Gomez DERI – Digital Enterprise Research Institute
GYTE - Bilgisayar Mühendisliği Bölümü Bilgisayar Mühendisliği Bölümü GYTE - Bilgisayar Mühendisliği Bölümü AN ARCHITECTURE FOR NEXT GENERATION MIDDLEWARE.
Version 02U-1 Computer Security: Art and Science1 Correctness by Construction: Developing a Commercial Secure System by Anthony Hall Roderick Chapman.
Requirements Analysis
Formal Methods in Software Engineering1 Today’s Agenda  Mailing list  Syllabus  Introduction.
UML Profile BY RAEF MOUSHEIMISH. Background Model is a description of system or part of a system using well- defined language. Model is a description.
Software Engineering, COMP201 Slide 1 Software Requirements BY M D ACHARYA Dept of Computer Science.
From Use Cases to Implementation 1. Structural and Behavioral Aspects of Collaborations  Two aspects of Collaborations Structural – specifies the static.
Requirement Elicitation Review – Class 8 Functional Requirements Nonfunctional Requirements Software Requirements document Requirements Validation and.
Choosing a Formal Method Mike Weissert COSC 481. Outline Introduction Reasons For Choosing Formality Application Characteristics Criteria For A Successful.
1 Software Requirements Descriptions and specifications of a system.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 6 Slide 1 Software Requirements (utvalgte foiler fra Kap 6 og 7 i Sommerville)
Model Checking Early Requirements Specifications in Tropos Presented by Chin-Yi Tsai.
Formal Specification.
Chapter 4 – Requirements Engineering
Software Requirements
Programming Languages 2nd edition Tucker and Noonan
Department of Computer Science Abdul Wali Khan University Mardan
Subject Name: SOFTWARE ENGINEERING Subject Code:10IS51
Programming Languages 2nd edition Tucker and Noonan
Presentation transcript:

System Monitoring using Constraint Checking as part of Model Based System Management 2007 Monitoring using Constraint Checking as part of Model Based System Management Nashville, October 2, 2007 Christian Hein, Tom Ritter, Michael Wagner Fraunhofer FOKUS

System Monitoring using Constraint Checking as part of Model Based System Management Outline – Monitoring using Constraint Checking as part of Model Based System Management Introduction Monitoring using Constraint Checking Application on CORBA Components Conclusion

System Monitoring using Constraint Checking as part of Model Based System Management Introduction system management is always difficult in particular for self-managing systems complex systems in many cases critical points are - size, distribution or heterogeneity many stakeholders with different viewpoints and different interests technical viewpoint - managing resources and technologies system viewpoint - managing system organization and non-functional policies (including security) operational (business) viewpoint - managing operational capabilities in order to optimize business effects information basis is the same but needs to be presented differently

System Monitoring using Constraint Checking as part of Model Based System Management Introduction use of model-base engineering techniques, methods and tools also in case of system management model-based system management - MBSM is an approach in which the medium that interfaces between the system manager and the system itself is a model of the system. [ModelPlex Deliverable D5.1a] constraint checking is part of model-base verification technique can be understood as analysing models against expected properties constraint checking and system management to identify malfunction

System Monitoring using Constraint Checking as part of Model Based System Management Introduction example of properties which could be monitored homogenous distribution of components to different nodes is a component more used than other components security or safety aspects: definition of security or safety boundaries with constraints e.g.: - maximum number of interconnections - maximum number of specific components

System Monitoring using Constraint Checking as part of Model Based System Management Introduction our idea: we use tools which are normally used for development also for management activities use of same models and notation Real-World system development tools Operational manager System manager Technical manager Management stakeholder

System Monitoring using Constraint Checking as part of Model Based System Management Monitoring using Constraint Checking Constraint Checker Real-World System run time model run time meta model constraint set Operational manager System manager Technical manager Management stakeholder Adapter conformsTo result provides input models

System Monitoring using Constraint Checking as part of Model Based System Management constraints are represented as OCL constraints Traditional formal languages (e.g. Z) require good mathematical understanding from users - mostly applied in academic world, not in industry - hard to learn, to complex in application The Object Constraint Language (OCL), provided by the OMG, has been developed to achieve the following goals: - formal, precise, unambiguous - applicable for a large number of users (business or system modeler, programmers) - Specification language - not a Programming language many tools already available Monitoring using Constraint Checking

System Monitoring using Constraint Checking as part of Model Based System Management Content – Monitoring using Constraint Checking as part of Model Based System Management Introduction Monitoring using Constraint Checking Application on CORBA Components Conclusion

System Monitoring using Constraint Checking as part of Model Based System Management Application on CORBA Components CORBA Component Model platform used for distributed systems support of design, deployment and execution support introspection mechanism; a good candidate to proof the concept

System Monitoring using Constraint Checking as part of Model Based System Management Application on CORBA Components example scenario a Plane can be tracked by a radar station a Radar has its area of observation a SimulationServer retrieves the position of all planes a Display presents information from all radar stations a SimulationController creates new Planes at random as well as new Radar instances RadarRadarSimulationServer Display SimulationController Planes

System Monitoring using Constraint Checking as part of Model Based System Management Application on CORBA Components

System Monitoring using Constraint Checking as part of Model Based System Management Application on CORBA Components

System Monitoring using Constraint Checking as part of Model Based System Management Application on CORBA Components

System Monitoring using Constraint Checking as part of Model Based System Management Application on CORBA Components

System Monitoring using Constraint Checking as part of Model Based System Management Application on CORBA Components maximum number of specific component e.g. Planes context CCM inv: ComponentInstantiation.allInstances()->select (c|c.type.absoluteName=`Simulation:PlaneSessionImpl`)- >size() Problem: How to deal with potential inconsistency of a snapshot ?

System Monitoring using Constraint Checking as part of Model Based System Management Application on CORBA Components context HomeInstantiation def: HelpSet: OrderedSet(Integer) = HomeInstanstiation.allInstances()->Iterate( i: HomeInstantiation ; sum: Sequence(Integer)=Sequence{} | sum->append(i.comp.size())).asOrderedSet() context HomeInstantiation def: Range: Integer = HelpSet.last()- HelpSet.first() context HomeDef inv: if (identifier='PlaneHome') then homeImpl->forAll(h|h.instance->forAll(Range<4)) else true endif The number of planes running on one computing device shall not be significantly different from the number of planes on other computing devices. difference is significant if the difference is greater than 3

System Monitoring using Constraint Checking as part of Model Based System Management Application on CORBA Components constraint checker introspection mechanism

System Monitoring using Constraint Checking as part of Model Based System Management Conclusion Advantages use of the same tools and techniques of development process also for management already existing tool and run time model Disadvantages performance getting a consistency formal representation of the system Further research topics adequate representation in development tools for management stakeholder Model Repairing improve introspection mechanism constraint checking with fuzzy semantic

System Monitoring using Constraint Checking as part of Model Based System Management Thank you !!! Any comments or questions?