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 byRiley Jerrett
Modified about 1 year ago
Automated Test Design ™ © 2011 Conformiq, Inc. CONFORMIQ DESIGNER On ES 202 951 v1.2.1 Stephan Schulz MBT Working Meeting/MTS#56, Göttingen
Automated Test Design ™ © 2011 Conformiq, Inc. Status ES 202 951 DSLs in ETSI test language specification? Test selection standardization Outline
Automated Test Design ™ © 2011 Conformiq, Inc. Work finished early 2011 – published by summer Comments received after finalization –Formalization of concepts (in UML diagram) –Annex for flowchart/activity based modeling –“weak point is missing relation of modeling to testing” –Section on modeling from system vs test perspective –“Missing terms” –Missing modeling/coverage of specific test data Status ES 202 951
Automated Test Design ™ © 2011 Conformiq, Inc. After years of ”unification” a clear & strong trend in industry to specialization in (modeling) languages, i.e., DSLs –So far deployments mainly in MDD UML, TTCN-3, etc – one size fits all? –One size is how many pages of standard? –One language ?= one compiler –XMI ? A(nother) domain specific modeling hype ? –”Everything is a domain specific language” -> what is a ”domain” –Presentation format vs actual language –Strong (Eclipse) open source initiative ”xtext” Test language specification and DSLs
Automated Test Design ™ © 2011 Conformiq, Inc. What is a Domain Specific Modeling? Modeling with a Domain Specific Modeling Language What is a Domain Specific Modeling Language (DSML)? –A formal language defined on a custom, limited set of domain specific concepts, symbols, and rules in a so called meta model –Attempts to achieve a higher level of abstraction than a general purpose language like, e.g., UML Conceptual foundation dating back to the 80s (ISO 10027 ) –Later on popularized in 90s by OMG as “Meta Object Facility” (MOF)
Automated Test Design ™ © 2011 Conformiq, Inc. [Example] Anatomy of a DSML or Meta-Model Concepts [Symbol] s Generators 12 3 4 Rules
Automated Test Design ™ © 2011 Conformiq, Inc. A Layered Definition of ETSI Testing DSLs? [based on Oligschläger, LACTOSE 2012] A DSML definition in multiple levels A new level can add new concepts, properties, relationships etc A new level can refine or restrict already existing concepts, properties, relationships, etc Application Domain Generic Testing SpecificTest Description Specific System Generic System System Operation Specific System Operation input, entity test step initial state SIP UA
Automated Test Design ™ © 2011 Conformiq, Inc. Why DSML(s) in Standardization? Not a new idea in context of TTCN-3 A fast way to nice & free text editors available for anybody (via xtext) –One of the challenges of the ExTRA aka TPLan A nice way to formalize dependencies and ensure consistency between different abstraction levels –ExTRA -> System operation or TDL -> TTCN-3 ? Allow space for tool proprietary presentation formats and even refinements, and extensions –At same time enables enforcing ”tool independent single language” for use in standardization
Automated Test Design ™ © 2011 Conformiq, Inc. Open Issues xtext as common denominator? In ES 202 951 or rather separate standard?
Automated Test Design ™ © 2011 Conformiq, Inc. About Test Selection in ES 202 951 test generation: automatic derivation of abstract test cases in one or more different formats from a model based on user defined test selection criteria test selection: process or the result of choosing a subset of tests during test generation from a larger or infinite set of tests which can be derived from a model test selection criterion: property that is satisfied by a set of test cases generated from a model
Automated Test Design ™ © 2011 Conformiq, Inc. About Test Selection in ES 202 951 Section 4: ”The model is then instrumented for the purpose of test generation by adding or selecting test selection criteria, i.e., coverage goals or test purposes specifying what is to be covered, and heuristics specifying how these goals are to be covered. Test selection is necessary since from every non-trivial model, an infinite or huge amount of tests can be derived. A model-based testing tool then automatically generates an abstract test suite that complies with these criteria.” ”NOTE: The specification of test selection criteria is beyond the scope of the present document.”
Automated Test Design ™ © 2011 Conformiq, Inc. (Part of ) An Earlier Attempt Instrumenting the model for test selection A model of system interface and system behaviour provides the basis for model-based testing. In order to control the generation of a test suite from a model, an engineer will need to provide additional information steering the test selection process. In this section, general concepts for test selection are defined. While these concepts are not necessarily part of a modelling notation itself, they are tightly connected to it, and in some instances are models themselves which relate to the behavioural model via model composition. –Coverage In model-based testing, coverage is defined in terms of the elements of the model. Coverage goals can be used to either prune the generation of the model graph from the model, or to steer the test generation process from the model graph. There is a variety of coverage criteria available. In this standard, only very basic coverage criteria are mentioned; many tools will provide more than those. 1.Test selection instrumentation shall provide a way to define coverage goals in terms of model requirements capture. 2.Test selection instrumentation shall provide one or more ways to define coverage goals in terms of the structure of the model, i.e. rule coverage, branch coverage, arc coverage, parameter range coverage, etc. We need more here!
Automated Test Design ™ © 2011 Conformiq, Inc. Next steps Section Test Selection and Test Suite Coverage? –Concepts & terminology/dictionary for use in context of MBT Revise notion of a state? –What is a test in the context of a model Effectively are the same quality – means to compare –Test selection Paramerization Test case properties like redundancy, priority/cost, differences in general –Test Suite Coverage Something may be measurable Type of coverage: Loop, definition coverage once vs n-times, ”full coverage” Criteria/types incl data and combinations thereof Reachability vs trace/pattern/test purpose (data at certain point) Use model vs specification vs implementation vs usage coverage
Automated Test Design ™ © 2011 Conformiq, Inc. CONFORMIQ DESIGNER MBT Working Meeting Report Stephan Schulz MTS#56, Göttingen.
Automated Test Design © 2011 Conformiq, Inc. CONFORMIQ DESIGNER MBT Working Meeting Report Stephan Schulz MTS#56, Göttingen.
Restricted © Siemens AG All rights reserved Siemens Corporate Technology | Month 20XX Proposed topics for TDL phase 3.
Fraunhofer FOKUS Competence Center MOTION FOKUS VIEW ON MODEL-BASED TEST DESCRIPTION LANGUAGES (TDLS) Alain-G. Vouffo Feudjio.
Language Specification using Metamodelling Joachim Fischer Humboldt University Berlin LAB Workshop Geneva
International Telecommunication Union ITU-T Study Group 17, Moscow, 30 March – 8 April 2005 New Recommendations on ODP Arve Meisingset Rapporteur Q15.
Alignment of ATL and QVT © 2006 ATLAS Nantes Alignment of ATL and QVT Ivan Kurtev ATLAS group, INRIA & University of Nantes, France
Using UML, Patterns, and Java Object-Oriented Software Engineering Chapter 2, Modeling with UML, Part 4 UML 2 Metamodel.
Using UML, Patterns, and Java Object-Oriented Software Engineering Chapter 2, Modeling with UML: UML 2 Metamodel Note to Instructor: The material in this.
2nd TTCN-3 User Conference, June The TTCN-3 Metamodel – A Basis for Tool Integration Ina Schieferdecker TU Berlin/Fraunhofer Fokus Hajo Eichler,
1 Software Requirements l Specifying system functionality and constraints l Chapters 5 and 6 ++
1 CIS224 Software Projects: Software Engineering and Research Methods Lecture 11 Brief introduction to the UML Specification (Based on UML Superstructure.
CSIS 4850: CS Senior Project – Spring 2009 CSIS 4850: Senior Project Spring 2009 Object-Oriented Design.
Introduction to MDA (Model Driven Architecture) CYT.
1 UML – an overview What is UML? UML stands for Unified Modelling Language. ”The Unified Modelling Language is a visual language for specifying, constructing.
The RDF meta model: a closer look Basic ideas of the RDF Resource instance descriptions in the RDF format Application-specific RDF schemas Limitations.
WIGOS Data model – standards introduction. Introduction This presentation briefly introduces ISO standards for conceptual modelling that provide context.
Slide 1 Wolfram Höpken RMSIG Reference Model Special Interest Group Second RMSIG Workshop Methodology and Process Wolfram Höpken.
1 Capturing Requirements As Use Cases To be discussed –Artifacts created in the requirements workflow –Workers participating in the requirements workflow.
Lecturer: Sebastian Coope Ashton Building, Room G.18 COMP 201 web-page: Lecture.
CASE Tools And Their Effect On Software Quality Peter Geddis – pxg07u.
Modeling Formalism Modeling Language Foundations System Modeling & Assessment Roadmap WG SE DSIG Working Group Orlando – June 2016.
Software Engineering, Slide 1 Software Requirements l Descriptions and specifications of a system.
Software Design Deriving a solution which satisfies software requirements.
SEA-1 20 Nov 2014 CCSDS System Engineering Area (SEA): System Architecture WG (SAWG) Restart Peter Shames, SEA AD 20 Nov 2014.
1 Ivano Malavolta, University of L’aquila, Computer Science Department Ivano Malavolta DUALLy: an Eclipse platform for architectural languages interoperability.
Copyright 2002 Prentice-Hall, Inc. Chapter 2 Object-Oriented Analysis and Design Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer Joey.
The RDF meta model Basic ideas of the RDF Resource instance descriptions in the RDF format Application-specific RDF schemas Limitations of XML compared.
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.
Profiles Construction Eclipse ECESIS Project Construction of Complex UML Profiles UPM ETSI Telecomunicación Ciudad Universitaria s/n Madrid 28040,
Creating Architectural Descriptions. Outline Standardizing architectural descriptions: The IEEE has published, “Recommended Practice for Architectural.
CS 4850: Senior Project Fall 2014 Object-Oriented Design.
Assessing the Suitability of UML for Modeling Software Architectures Nenad Medvidovic Computer Science Department University of Southern California Los.
International Telecommunication Union © ITU-T Study Group 17 Integrated Application of SDL Amardeo Sarma NEC Europe Ltd.
CHESS Methodology and Tool Federico Ciccozzi MBEES Meeting Sälen, January 2011 January 2011.
The Software Product Life Cycle. Views of the Software Product Life Cycle Management Software engineering Engineering design Architectural design.
Software Engineering Lecture 10: System Engineering.
Andrea Maurino Web Service Design Methodology Batini, De Paoli, Maurino, Grega, Comerio WP2-WP3 Roma 24/11/2005.
Faculty of Informatics and Information Technologies Slovak University of Technology Peter Kajsa and Ľubomír Majtás Design.
IEC Substation Configuration Language and Its Impact on the Engineering of Distribution Substation Systems Dr. Alexander Apostolov.
Modelling Class T08 Conceptual Modelling – Behaviour Flow-Based Behavior References: –Conceptual Modeling of Information Systems (Chapters 11 and 12) –A.
Comparing M2T & M2M Complementary Approaches © 2008 INRIA, University of York & SINTEF Comparing M2T & M2M Complementary Approaches Hugo Bruneliere,
UML CASE Tool. ABSTRACT Domain analysis enables identifying families of applications and capturing their terminology in order to assist and guide system.
An Introduction to Software Architecture Software Engineering Lab. Summer 2006.
What is MOF? The Meta Object Facility (MOF) specification provides a set of CORBA interfaces that can be used to define and manipulate a set of interoperable.
© 2000 Ian Alexander - Introduction to Scenarios Introduction to Scenarios A range of techniques for engineering better systems Ian Alexander
Lecture a: Additional UML Models: Package, Activity, Deployment Lecture b: Generalization, Aggregation and Additional Domain Model Notation Copyright W.
XASTRO vs RASDS CCSDS SAWG Meeting. CCSDS SAWG2 Presentation Outline XASTRO study analysis phase conclusions Relationship between XASTRO and UML 2 / SysML.
Workshop on Integrated Application of Formal Languages, Geneva J.Fischer Mappings, Use of MOF for Language Families Joachim Fischer Workshop on.
Programming in Java Unit 3. Learning outcome: LO2:Be able to design Java solutions LO3:Be able to implement Java solutions Assessment criteria:
© 2017 SlidePlayer.com Inc. All rights reserved.