Application Testing in NoTA Design Flow 1st International NoTA Conference 2008 Johan Lilius Åbo Akademi University 07.06.0...
Contents <ul><li>Development in NoTA </li></ul><ul><li>Testable Specifications </li></ul><ul><li>Development Flow </li></u...
NoTA Main Architecture 07.06.09 Åbo Akademi - Domkyrkotorget 3 - 20500 Åbo AN = Application Node SN = Service Node
Development with NoTA <ul><li>Designing NoTA Applications is  composing  services </li></ul><ul><li>Building NoTA Systems ...
Development in NoTA <ul><li>Service definition and subsystem implementation are done by differenet entities </li></ul><ul>...
Development in NoTA <ul><li>2 ”Interfacing” points between integrator and vendor </li></ul><ul><ul><ul><li>Delivery of ser...
Testable (NoTA) Specifications <ul><li>3 parts </li></ul><ul><ul><li>XML format for defining NoTA services </li></ul></ul>...
Service Interface Specification (SIS) <ul><li>Interface: specifies functions provided by the services </li></ul><ul><li>Be...
Data Interface <ul><li>FSM describing data-handling </li></ul><ul><li>Describes non-functional properties </li></ul><ul><l...
Service Interactions - Tests <ul><li>Specifies how services are to interact </li></ul><ul><ul><li>includes non-functional ...
Testable Specification <ul><li>XML Schema for NoTA specifications </li></ul><ul><li>Tool independent and machine readable ...
Development Flow <ul><li>Need for a defined way to interact between the integrator and vendor </li></ul><ul><li>Applicatio...
Testing Flow 07.06.09 Åbo Akademi - Domkyrkotorget 3 - 20500 Åbo Integrator Vendor Specification and Validation Loop
Modular Specification <ul><li>Subsystems may depend on each other </li></ul><ul><li>What if a dependency is not available?...
Nota Tester 07.06.09 Åbo Akademi - Domkyrkotorget 3 - 20500 Åbo Interconnect Testing Subsystem File Server Sniffer Audio P...
Conclusions <ul><li>Service Interface Specifications </li></ul><ul><ul><li>Higher quality specifications </li></ul></ul><u...
Acknowledgements <ul><li>Åbo Akademi Team </li></ul><ul><li>Dr. Dragos Truscan </li></ul><ul><li>Mr. Johan Lindqvist </li>...
Upcoming SlideShare
Loading in …5
×

Application Testing in NoTa Design Flow

733 views

Published on

Published in: Technology
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
733
On SlideShare
0
From Embeds
0
Number of Embeds
22
Actions
Shares
0
Downloads
7
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

Application Testing in NoTa Design Flow

  1. 1. Application Testing in NoTA Design Flow 1st International NoTA Conference 2008 Johan Lilius Åbo Akademi University 07.06.09 Åbo Akademi - Domkyrkotorget 3 - 20500 Åbo
  2. 2. Contents <ul><li>Development in NoTA </li></ul><ul><li>Testable Specifications </li></ul><ul><li>Development Flow </li></ul><ul><li>NoTA Tester </li></ul><ul><li>Conclusions </li></ul>07.06.09 Åbo Akademi - Domkyrkotorget 3 - 20500 Åbo
  3. 3. NoTA Main Architecture 07.06.09 Åbo Akademi - Domkyrkotorget 3 - 20500 Åbo AN = Application Node SN = Service Node
  4. 4. Development with NoTA <ul><li>Designing NoTA Applications is composing services </li></ul><ul><li>Building NoTA Systems is partitioning services into subsystems </li></ul><ul><li>Subsystems provide services </li></ul><ul><li>Services may depend on services </li></ul><ul><li>Subsystems may depend on subsystems </li></ul>NoTA 07.06.09 Åbo Akademi - Domkyrkotorget 3 - 20500 Åbo
  5. 5. Development in NoTA <ul><li>Service definition and subsystem implementation are done by differenet entities </li></ul><ul><ul><li>Integrator : entity specifiying and composing services </li></ul></ul><ul><ul><li>Vendor : entity providing subsystem implementation </li></ul></ul><ul><li>Problem: How to make integrator vendor discussion cycle faster </li></ul>07.06.09 Åbo Akademi - Domkyrkotorget 3 - 20500 Åbo
  6. 6. Development in NoTA <ul><li>2 ”Interfacing” points between integrator and vendor </li></ul><ul><ul><ul><li>Delivery of service specification(s) </li></ul></ul></ul><ul><ul><ul><li>Delivery of final subsystem implementation </li></ul></ul></ul><ul><li>Standard subcontracting problem </li></ul><ul><li>TESTABLE SPECIFICATIONS </li></ul>07.06.09 Åbo Akademi - Domkyrkotorget 3 - 20500 Åbo
  7. 7. Testable (NoTA) Specifications <ul><li>3 parts </li></ul><ul><ul><li>XML format for defining NoTA services </li></ul></ul><ul><ul><ul><li>Control Interface </li></ul></ul></ul><ul><ul><ul><ul><li>Interface Specification and Behavior Specification </li></ul></ul></ul></ul><ul><ul><ul><li>Data Interface </li></ul></ul></ul><ul><ul><ul><ul><li>Datatypes (MIME) and Data Handling Patterns </li></ul></ul></ul></ul><ul><ul><li>XML format for describing Service Interactions </li></ul></ul><ul><ul><ul><li>Describe use cases, and tests </li></ul></ul></ul><ul><ul><li>Tool support </li></ul></ul><ul><ul><ul><li>Executes Service Interactions on subsystem implementation </li></ul></ul></ul>07.06.09 Åbo Akademi - Domkyrkotorget 3 - 20500 Åbo
  8. 8. Service Interface Specification (SIS) <ul><li>Interface: specifies functions provided by the services </li></ul><ul><li>Behavior: protocol state machine of the service </li></ul><ul><ul><li>Can include dependencies to other services </li></ul></ul>07.06.09 Åbo Akademi - Domkyrkotorget 3 - 20500 Åbo XML format visualised for presentation purpouses Example: Still Capture
  9. 9. Data Interface <ul><li>FSM describing data-handling </li></ul><ul><li>Describes non-functional properties </li></ul><ul><li>2 FSM:s per service </li></ul><ul><li>Cross-product of FSM:s gives automaton for communication between services </li></ul>07.06.09 Åbo Akademi - Domkyrkotorget 3 - 20500 Åbo XML format visualised for presentation purpouses Audio Player
  10. 10. Service Interactions - Tests <ul><li>Specifies how services are to interact </li></ul><ul><ul><li>includes non-functional constraints </li></ul></ul>07.06.09 Åbo Akademi - Domkyrkotorget 3 - 20500 Åbo
  11. 11. Testable Specification <ul><li>XML Schema for NoTA specifications </li></ul><ul><li>Tool independent and machine readable </li></ul><ul><ul><li>Can be translated to UML, Word, etc </li></ul></ul><ul><ul><li>Can be manipulated with tools e.g NoTA Tester </li></ul></ul><ul><li>Fixed vocabulary </li></ul><ul><ul><li>Stronger semantics </li></ul></ul><ul><ul><li>Improves comprehension </li></ul></ul><ul><li>Service Interactions </li></ul><ul><ul><li>Act as tests </li></ul></ul><ul><ul><li>Improve comprehension </li></ul></ul>07.06.09 Åbo Akademi - Domkyrkotorget 3 - 20500 Åbo
  12. 12. Development Flow <ul><li>Need for a defined way to interact between the integrator and vendor </li></ul><ul><li>Application design flow </li></ul><ul><li>Testing flow </li></ul>07.06.09 Åbo Akademi - Domkyrkotorget 3 - 20500 Åbo
  13. 13. Testing Flow 07.06.09 Åbo Akademi - Domkyrkotorget 3 - 20500 Åbo Integrator Vendor Specification and Validation Loop
  14. 14. Modular Specification <ul><li>Subsystems may depend on each other </li></ul><ul><li>What if a dependency is not available? </li></ul><ul><li>Behavior specification makes simulation possible </li></ul><ul><li>File server can be tested against audio engine dependencies without access to physical audio engine </li></ul>07.06.09 Åbo Akademi - Domkyrkotorget 3 - 20500 Åbo
  15. 15. Nota Tester 07.06.09 Åbo Akademi - Domkyrkotorget 3 - 20500 Åbo Interconnect Testing Subsystem File Server Sniffer Audio Player Sniffer Audio Player Service StorageSubsystem File Server Service Resource Manager Emulated Service Sniffer Implementation Under Test Sniffer Emulated Service
  16. 16. Conclusions <ul><li>Service Interface Specifications </li></ul><ul><ul><li>Higher quality specifications </li></ul></ul><ul><ul><li>Enable tool support </li></ul></ul><ul><ul><li>Allow simulation of dependent services </li></ul></ul><ul><li>Service Interaction Specifications </li></ul><ul><ul><li>Improve comprehension for vendor </li></ul></ul><ul><ul><li>Lowers validation effort for integrator </li></ul></ul><ul><li>Tester tool </li></ul><ul><ul><li>Go watch the demo! </li></ul></ul>07.06.09 Åbo Akademi - Domkyrkotorget 3 - 20500 Åbo
  17. 17. Acknowledgements <ul><li>Åbo Akademi Team </li></ul><ul><li>Dr. Dragos Truscan </li></ul><ul><li>Mr. Johan Lindqvist </li></ul><ul><li>Mr. Mathias Karlå </li></ul><ul><li>Mr. Mats Lövdahl </li></ul><ul><li>Prof. Johan Lilius </li></ul><ul><li>Prof. Ivan Porres </li></ul><ul><li>Nokia Team </li></ul><ul><li>Mr. Timo Eriksson </li></ul><ul><li>Mr. Juha Rakkola </li></ul><ul><li>Mr. Mikko Hurskainen </li></ul><ul><li>Mr. Antti Latva-Aho </li></ul>07.06.09 Åbo Akademi - Domkyrkotorget 3 - 20500 Åbo References <ul><li>D. Truscan et. al, ”Testable Specifications of NoTA-based Modular Embedded Systems”, ECBS’08 Conference </li></ul><ul><li>M. Karlå et. al, ”A Testing Framework for NoTA-based Devices”, MoTIP’08 Workshop </li></ul>

×