1. Oak Systems @ TIFAC-VIT 1
Introduction to TTCN-3 and
AUTOSAR Conformance Testing
Abhijit Gadgil
Manager, New Technology Initiatives,
Oak Systems Pvt. Ltd.
contact@oaksys.net

2. Oak Systems @ TIFAC-VIT 2
Agenda
• A brief overview of Oak Systems
• Introduction to AUTOSAR
• Aspects of AUTOSAR Conformance
Testing
• Introduction to TTCN-3

3. Oak Systems @ TIFAC-VIT 3
Oak Systems
• Founded in 1998
• Independent V&V Company having offices in
Bangalore and Pune
• Specialization in Embedded systems for
Defence, Aerospace, Telecom, Automotive
sectors and major clients in BFSI domain.
• Resellers of tools

4. Oak Systems @ TIFAC-VIT 4
“Strive to transform every customer’s business
vision into a reality through quality
engineering methods for a better, faster and
cost-effective solution”

5. Oak Systems @ TIFAC-VIT 5

6. Oak Systems @ TIFAC-VIT 6
Key Members
• Mr. Pradeep Oak - M Tech., IIT Kanpur
– Worked with TCS, Index, …
– Consulted with HPISO, Philips, DRDO, Robert Bosch, …
– Coauthored book on s/w testing (McGraw Hill, 2004)
– Chairmain, Gov Council of Amruta Institute of Engineering &
Management Sciences, Bangalore
• Mr. Narendranath Pai - B Tech
– expertise in Business & Web Applications
– worked with ANZIT, SAP Labs, PSI, …
• Ms Tejaswini - B Tech
– consulted with DRDO, Motorola, …
• Ms Asmita Oak - B Tech
– expertise in Quality Management Systems
– worked on V & V projects at DRDO, Synopsys, …
• Mr Abhijit Gadgil - M Tech., IIT Mumbai
– expertise in Embedded, Real Time & Telecom projects
– Indian Language computing
AND .. 100+ others

7. Oak Systems @ TIFAC-VIT 7
Services Offered
Managed Testing Service
Software Test Planning & Strategy development
QA for the complete SDLC
Test case design and driver development
Test Environment setup & Test Execution
Development of Test Automation Framework
User Acceptance Testing
Sales and support of Third party test tools
In short, everything in Software Testing

8. Oak Systems @ TIFAC-VIT 8
Our research initiatives
• OAK-BVB Center of Excellence in V&V (2003)
• In association with BVB college of Engineering, Hubli
• Focusing on research and propagation of new techniques in
software Verification & Validation, deriving new methods of
analysing test metrics, ..
• OAK-PDA Center of Excellence in Software
Automation (2005)
• In association with PDA College of Engineering, Gulbarga
• Focusing on test automation, tool evaluation, productivity
improvement etc.

9. Oak Systems @ TIFAC-VIT 9
Projects’ Snapshot ..
IV & V of of Mission Critical Avionics Software (LCA and others) under 2167A,
DO-178B, IEEE 12207, …
Test automation of telecom data validation system
Requirement analysis of Avionics system using formal methods (ESTEREL)
System Testing, Test automation & UAT of HRMIS products
Testing & Test Automation in Insurance, Banking, CRM domains
System Testing, Automation and UAT of products under Insurance domain
• Cross-platform Testing of a Network Management Product
• Testing WAP based internet software in Medical services domain
Testing and reverse engineering of a B2B software (Automotives)
Test design, development and execution of ISDN v110 protocol
Internet/Intranet based Pension administration software
System Testing of Internet Payment Security System
Test Automation of Telecom applications
Managed Testing of a Global Core Banking Application with CMMi L5
processes

10. Oak Systems @ TIFAC-VIT 10
Agenda
• A brief overview of Oak Systems
• Introduction to AUTOSAR
• Aspects of AUTOSAR Conformance
Testing
• Introduction to TTCN-3

11. Oak Systems @ TIFAC-VIT 11
What is AUTOSAR
• AUTOSAR – Stands for Automotive Open
Systems Architecture.
• A Layered Software Architecture that
describes
– In a Top-Down approach the hierarchical
structure of AUTOSAR software
– Maps Basic Software Modules to software
layers
– Shows their Relationship

12. Oak Systems @ TIFAC-VIT 12
What is AUTOSAR

13. Oak Systems @ TIFAC-VIT 13
What is AUTOSAR

14. Oak Systems @ TIFAC-VIT 14
What is AUTOSAR

15. Oak Systems @ TIFAC-VIT 15
AUTOSAR Layers Overview
• Microcontroller Abstraction Layer
– Implementation is uC dependent, upper interface is uC independent
• ECU Abstraction Layer
– Implementation is uC independent, ECU hardware dependent. Upper interface is
uC and ECU hardware independent
• Complex Drivers
– Not specified within AUTOSAR or for migration or having very high timing
constraints.
• Services Layer
– Typical Operating System Services (watchdog, memory services, Communication,
Diagnostics)
• RTE Layer
– Provides communication services to application layer
– Above RTE Layer the architecture style changes from Layered to Component
style, where components speak with each other through RTE services.

16. Oak Systems @ TIFAC-VIT 16
An Overview of AUTOSAR Software
Layers on Multicore uC

17. Oak Systems @ TIFAC-VIT 17
AUTOSAR Interfaces

18. Oak Systems @ TIFAC-VIT 18
Interfaces and Interactions

19. Oak Systems @ TIFAC-VIT 19
AutoSAR Configuration Overview
• Pre-compile Time
– Preprocessor
– Code Generation (Selection,
• Link Time
– Post compile, uses constant data outside modules
• Post – Build Time
– Reflashing
– Single or multiple Configuration Sets (only one active
at runtime

20. Oak Systems @ TIFAC-VIT 20
Agenda
• A brief overview of Oak Systems
• Introduction to AUTOSAR
• Aspects of AUTOSAR Conformance
Testing
• Introduction to TTCN-3

21. Oak Systems @ TIFAC-VIT 21
AUTOSAR Conformance Testing
• Modules, Clusters, Variants and Family
• Confrmance Tests are typically run on a
Variant (ie. A concrete implementation)
• The operative mode of the variant should
be Production for Conformance Testing
• Conformance Testing is not a replacement
for Quality or Functional Testing

22. Oak Systems @ TIFAC-VIT 22
Purpose & Nature of Conformance Tests
• Conformance Test specifications are a part of
formally released AUTOSAR document set and a
direct relationship with SWS documents
• Since the tests and test results directly depend
upon a lot of factors not directly contained in test
specifications, these tests require traceability of
– Test Environment
– Tools and Tool Parameters used for compilation of
executable binaries
– The variants of the test object actually tested
– Target Platform and its configuration

23. Oak Systems @ TIFAC-VIT 23
AUTOSAR CTSpec process
• Since the conformance test specification facilitates
communication between several stake holders like AUTOSAR,
Tool vendors and CTAs and product suppliers, following items
are described in a Test Specification
– Test Items
– Test Procedures
– Test case Specification
– Test Architecture Specification
• Steps involved in preparing CTSpec
– Test preparation
• Refinement of SWS
• TestCase identification
– Test specification
• CTSpec Design
• Test Case Implementation

24. Oak Systems @ TIFAC-VIT 24
AUTOSAR Conformance Paths

25. Oak Systems @ TIFAC-VIT 25
A Test Harness for test object and Interfaces

26. Oak Systems @ TIFAC-VIT 26
Test System Architecture – an example

27. Oak Systems @ TIFAC-VIT 27
Process of Conformance Test
Implementation and Execution
• Preparation of dynamic test cases
– Determination of a set of configuration sets
– Determination of expected results
– Creation of test executable
– Preparation of the framework
• Performing Conformance Tests
– Documentation regarding process, description about tools, process
logs
• Execution of Tests
– Static Tests (inspections of linker logs, if possible, automate).
– Dynamic Tests – Log files should indicate the results of running the
tests

28. Oak Systems @ TIFAC-VIT 28
Agenda
• A brief overview of Oak Systems
• Introduction to AUTOSAR
• Aspects of AUTOSAR Conformance
Testing
• Introduction to TTCN-3

29. Oak Systems @ TIFAC-VIT 29
Overview of a TTCN-3 Test System

30. Oak Systems @ TIFAC-VIT 30
Features of TTCN-3
• Modular
– TTCN3 Test cases are written as modules with ability to import
definitions from one module to another this helps substantially in building
reusable test components.
– It is possible to pass parameters to a module (eg. Configuration
information)
• Component base architecture
– A test system comprises of a main test component and parallel test
components that allows concurrent execution of test cases.
• Verdicts and Templates
– TTCN3 defines language constructs called verdicts, that determine
modular execution results of a test case and aggregated results of a test
case.
– Templates are useful in matching received data and/or sending data for a
particular test purpose

31. Oak Systems @ TIFAC-VIT 31
Features Continued
• Components and Ports
– Components define a basic unit of testing in a test
system.
– Components are made up of ports and internal state
(timers etc.)
• Message and Procedure based communication
– Support for message based communication between test
components and SUT (peer systems, typical
applications in Telecom protocols)
– Support for procedure based communication ports (used
in AUTOSAR)

32. Oak Systems @ TIFAC-VIT 32
Agenda
• A brief overview of Oak Systems
• Introduction to AUTOSAR
• Aspects of AUTOSAR Conformance
Testing
• Introduction to TTCN-3

33. Oak Systems @ TIFAC-VIT 33
For further details, please write
to contact@oaksys.net
Thank you