3Meeting Overview Detailed STF ReviewATM exercise + first ITS models with 4 toolsEarly resultsG&D Presentation and standard feedbackConformiq presentation on open issues & new ideasDefinition of next steps

4Status ES 202 951 Work finished early 2011 – published by summerComments received after finalizationFormalization 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

5About Test Selection in ES 202 951Section 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.”

6Next Steps Reformulate scope of MBT ES WI beyond modelingNew sections in MBT ES on Test Selection and Test Suite CoverageConcepts & terminology/dictionary for use in context of MBTRevise notion of a state?What is a test in the context of a modelEffectively are the same quality – means to compareTest selectionParamerizationTest case properties like redundancy, priority/cost, differences in generalTest Suite CoverageSomething may be measurableType of coverage: Loop, definition coverage once vs n-times, ”full coverage”Criteria/types incl data and combinations thereofReachability vs trace/pattern/test purpose (data at certain point)Use model vs specification vs implementation vs usage coverageDefinition of more formal meta model (concepts) based on [OMG] MOF

9What is a Domain Specific Modeling?Modeling with a Domain Specific Modeling LanguageWhat 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 modelAttempts to achieve a higher level of abstraction than a general purpose language like, e.g., UMLConceptual foundation dating back to the 80s (ISO 10027)Later on popularized in 90s by OMG as “Meta Object Facility” (MOF)

10[Example] Anatomy of a DSML or Meta-ModelRulesGenerators1234Concepts[Symbol]s

12Why DSML(s) in Standardization?Not a new idea in context of TTCN-3A fast way to nice & free text editors available for anybody (via xtext)One of the challenges of the ExTRA aka TPLanA nice way to formalize dependencies and ensure consistency between different abstraction levelsExTRA -> System operation or TDL -> TTCN-3 ?Allow space for tool proprietary presentation formats and even refinements, and extensionsAt same time enables enforcing ”tool independent single language” for use in standardization