The objective of the model-based testing principles and methods of D-MINT is to develop model-based testing technology. This includes test modeling, test generation, test processes, test validation, test prioritization, test selection, and model-based monitoring. Model-based testing principles and methods are developed based on the D-MINT industrial case studies and realized in the development of D-MINT tools and tool chains. The D-MINT project has established solutions from the requirements resulting from several industrial cases (telecommunication, automotive, etc.). The project has developed prototype implementations to verify and validate the theories and proposed solutions of model-based testing principles and methods in the context of the industrial cases against their requirements.
Buy Cheap Software Microsoft Office 2000 Premium Edition Microsoft Office 2003 Professional Edition
The Asset Box is a collection of the research and development results achieved in the D-MINT project. It is presented as a multifaceted collection, including the ensuing aspects: 1) Test Modelling, Test Generation and Test Execution with Model-Based Testing, 2) Model-Based Test Process, Test Validation, Test Prioritization and Selection, 3) Model-Based Monitoring, 4) Prototypes and Tools, and 5) Demonstrators. Each of these facets offers a specific view on the work of the D-MINT consortium. The cooperative work of the project partners from the research and industry is reflected into the presentation of assets that reference to each other across different facets.
Note: Reference number in the table below refer to the D-MINT white paper
| PROCESS |
5.1 Requirements Management & Documentation |
5.2 Modelling for Test Derivation |
5.3 Test Derivation |
5.4 Test Implementation |
5.5 Test Exectution |
5.6 Test Reporting |
| ABSTRACTION  |
Abstraction Level: System Architecture
Viewpoints: Requirements (all), Logical (all), Technical (most), Topological (possibly of interest, but not realized) |
| METHODS |
5.1.1 Structured Requirements
MATERA |
5.2.1.1/5.2.2.1  State/sequence charts. Priorities by annotations
MiLEST, MBST, ADT, MotesWF, MATERA
|
5.3.1.1/5.3.2.1 Architecture models and behaviour
MiLEST, MBST, ADT, MotesWF |
5.4.1 Abstract test cases in a test model or test specific language "compiled" to byte code
|
5.5.1 Online, offline, HIL,SIL,PIL |
5.6.1 Pass/Fail; Statistical analysis; Test execution traces; Back-tracing of Req's
MATERA |
| NOTATIONS |
5.1.2 Textual format, tabular format, sequence-based specification, TPLan, SysML |
5.2.1.2/5.2.2.2 UML, SysML, OCL, MSC, TPT, PTML, Domain specific languages, Model Annotations for priority |
5.3.1.2/5.3.2.2 QML, TTCN-3, Tool specific |
5.4.2 QML/EAST, TTCN-3 |
5.5.2 Machine code, Java byte code, EAST scripts |
5.6.2 HTML+UML |
| TOOLS |
5.1.3 Text based tools, DOORS, PREEvision, MATERA, TestWORKFLOW, MagicDraw (UML) |
5.2.1.3/5.2.2.3 MagicDraw, EA, StarUML, TTmodeler, Jumbl, TPT, Qtronic, PREEvision, MATERA, MDTester, RSA |
5.3.1.3/5.3.2.3 Qtronic, TTmodeler, MOTES, MDTester, PREEvision |
5.4.3 Qtronic, TTworkbench, JUMBL, TPT, TTCN-3 Express |
5.5.3 Qtronic, EAST, TTworkbench, TestRig, TTCN-3 Express, TestWORKFLOW, MessageMagic |
5.6.3 Qtronic, EAST, TTworkbench, MATERA, TTCN-3 Express, TestWORKFLOW |
Note: D-MINT methods/tools are in bold
The Common Approach buttons will act as links to delve deeper into the subject presented on the button according to the internal structure of the White Paper of D-MINT Project.
Note: Web pages containing 1) the main results of the deliverables, 2) prototypes and tools, and 3) demonstrators will be retained separately.
WP2 related content
WP3 related content
|