This tutorial on Model Based Testing gives you a brief overview how to re-use system models to generate test cases with the software BPM-X. This tutorial covers the following topics: 1. Introduction 2. Use models for agile development 3. From system model to test cases 4. Summary 5. Next webinars

1. TransWare AG
How to re-use existing system models to generate test cases?
Webinar, hosted by TransWare AG, 6 Dec 2017
www.transwareag.com

2. Introduction
Use models for agile development
From system model to test cases
Summary
Next webinars
Q&A
Agenda of this Webinar
2

3. TransWare AG
Independent software vendor
HQ in Germany, subsidiary in
St. Petersburg, FL US
Global business with partners in
consulting and software business
Specialized in model transformations
and test automation using BPM-X®
BPM-X® is a registered trademark and
product of the TransWare
Company and Presenters
3
Heinz-Jürgen Scherer
CEO
20 years in software development
Specialized in EA, BPM and QM
Volker Rautenberg
VP Product Management
15 years in software development
Specialized in EA, BPM and QM

4. 4
Use models
for agile
development

5. 5
Software Engineering Institute, Carnegie Mellon University, US, The Tester's Double V Model
https://insights.sei.cmu.edu/sei_blog/2013/11/using-v-models-for-testing.html
State based
System
behavior
Technically driven
System model vs. test model

6. Common situations in solution delivery (ERP, legacy apps, …)
6
Do we test our solution too less (regarding
customizing) or too much (test vendor standards)?
Are our business requirements covered as well as the
law & regulations implemented by the solution?
Why do we have such a high testing effort (20% up
to 50% of project costs)?
Bulky Word specifications are non-transparent, use
business process documentation with E2E paths
This is caused by the traceability gap between
solution design and solution delivery.
How can the time for preparation and execution of
regression testing be lowered to avoid bottlenecks?
Time is wasted because of not focusing on impacts
of changes and too less automation of test
Why do business and IT misunderstand each other
and essential testing information is missing
Add meta-data required for testing directly to the
data properties of process documentation
Question Answer
Not only the testing for functional defects, coverage
analysis of requirements & risks is essential

7. How to align business with IT being more agile
7
Scoping
Requirements
Regulations & compliance
Functional and e2e processes
Change/Requests
Delivery
Parameterization
Customizing
Development
Change/Request
Model-based testing
Business Analyst
Requirement Manager
Risk Manager Test Engineer Application Engineer
Business-to-IT

8. BPM-X® model-based testing adds no new modeling (Editor)
nor additional testing tool to the existing SDLC tool landscape
and test frameworks.
BPM-X® leverages system model documentation and adds
value to the existing tool landscape by bridging management
with development domains, being tool agnostic and
modeling-language agnostic.
.
Our approach with BPM-X®
8

9. BPM-X® core technology
9
BPM-X® service for model interchange and transformation
SAP Solution
Manager
SAP ERP
ERP
Sparx Enterprise
Architect
XMI
Software Design
XPDL
BPMN
BPM(S)
HP UCMDB
CMDB
UDDI
Services
SharePoint
ECM
Excel
XML
SQL
ETL
Arbitrary data
Oracle BPA
Casewise
MEGA
Tibco Control
iGrafx
IBM Process Modeler
IBM System Architect
Sparx
Enterprise Architect
ProVision
ARIS
EA, BPA
Microsoft Visio
IBM Blueworks Visual Studio
HP ALM / QC
QAS
JIRA
Zehyr for JIRA Cloud
TestLink
Microsoft TFS

10. System Model
10
From System Model to Test Cases templates
1x
Test Case 1
Test Case 2

11. Process flow model or interaction diagram
11
Interaction between
participants (humans,
systems)
Modeling languages
like BPMN process or
UML activity flows
Tools like ARIS, Visio,
Sparx and others

12. 12
From
System
Model
To
Test
Cases

13. Showcase of re-using process documentation
13
Processing of end-to-end flows
to test cases
Process architecture
down to
implementation level
Test cases and
- scripts
ToolsContent

14. 14
Summary

15. Key takeaways
15
Leverage the system models (business process flows,
documentation, blueprints, …) as single point of truth.
No redundant test model to be maintained,
quicker turn-arounds for iterations, regression tests
Connect existing modeling tools with testing tools in
the SDLC landscape
Re-use the existing tool landscape of
modeling, requirements and testing tools
No tool training, concentrate on methodology
and automation of test-cases
Sustainable investments in tools, configurations
and know-how
Generate real end-to-end paths directly from
requirements documentation
Increase quality of test-case design, much lower
efforts for test-case generation
Add meta-data required for testing directly to the
system model data properties
Transfer knowledge from business to IT,
traceability of requirements
Value proposition Benefits

16. Get your personal trial
16
Sent us a request: http://bit.ly/Get_BPM-X

17. Requirements modeling and coverage testing
Cloud based testing
Compare productivity of easy to more complex tools
Microsoft TFS and HP ALM used for model-based testing
Generating test data (pre- and path –conditions)
Enhance business process documentation for testing
Model-based testing and test automation
Next monthly webinars
17

19. TransWare AG
Fritz-Wunderlichstrasse 49
66869 Kusel – Germany
info@transwareag.com
www.transwareag.com
+49 6381 916 0
19