“The documentation is the design, the design is the system!” Copyright © SDL Task Force Consortium. All rights reserved.

“The documentation is the design, the design is the system!” Copyright © SDL Task Force Consortium. All rights reserved. The SDL Task Force Mandate Define the simplest, useful, enhanced SDL-subset Structure Consortium of founding members Editorial board Contributing members Review and comment on work of editorial board Recognized by the SDL-Forum A.4 qualified member

“The documentation is the design, the design is the system!” Copyright © SDL Task Force Consortium. All rights reserved. Editorial Board William Skelton Vangelis Kollias Alkis Yiannakoulias SOLINET, Stuttgart TELETEL, Athens National Technical University of Athens Contributing members review and comment on the work of the editorial board.

“The documentation is the design, the design is the system!” Copyright © SDL Task Force Consortium. All rights reserved. Milestones Foundation: July launched: August Version 1.1, 1st draft document: August 2003 Version 1.2 (internal) Version 1.3, 3 rd draft document: March st Release: SAM’04 Workshop June 2004 Update with SAM’04 comments planned 3Q2004 Graphical representation planned 1Q2005

“The documentation is the design, the design is the system!” Copyright © SDL Task Force Consortium. All rights reserved. Background SDL has become big and complex Implementation of tools is expensive New users need to be skilled software engineers SDL not designed for testing No support for test related needs SDL includes ASN.1 types but not PDU encoding External tools needed, e.g ASN.1 compilers

“The documentation is the design, the design is the system!” Copyright © SDL Task Force Consortium. All rights reserved. Goals Identify the simplest, useful SDL-subset Cheaper for tool suppliers to support Easier for new users to learn Add the simplest, useful enhancements for Test Specifications PDU Encoding Ensure automated graphical presentation No need for users to format their designs Promote SDL

“The documentation is the design, the design is the system!” Copyright © SDL Task Force Consortium. All rights reserved. Decision Making Process Pragmatic, fast-moving, target driven approach Start from simplest requirements Consider essential features Applications not possible without these Remain compatible with SDL if possible Avoid constructs with difficult implementation Include constructs used in common applications Focus on completeness, symmetry, simplicity Encourage good style, i.e. data-hiding, scope

“The documentation is the design, the design is the system!” Copyright © SDL Task Force Consortium. All rights reserved. Significant Results Prototype language Limited features covering all goals Innovative Breakthrough Only one language for implementation and testing! Already at least one compatible tool available SAFIRE-SDL Working name for SDL Task Force work: SDL+

“The documentation is the design, the design is the system!” Copyright © SDL Task Force Consortium. All rights reserved. Significant Results SDL Forum votes to recognize the current status of the SDL Task Force work and to build on the identified subset in any work done by an SDL Forum Society work group Subset syntax Subset syntax with extensions for encoding of PDUs

“The documentation is the design, the design is the system!” Copyright © SDL Task Force Consortium. All rights reserved. More help needed! The SDL Task Force works on a voluntary basis No funding The project is getting larger & larger ‘Never ending story’ Contributors and reviewers needed No reward, no thanks, only blood, sweat & tears  But… members names are published Join us at: