80 likes | 82 Views
A Tool Vendor View on ITU-T Language Standardization. Anders Ek. Why Standards?. Money!!! Following a standard is a sales argument. Sometimes even a requirement. Customer’s view. More than one tool Cheaper Safer (can switch tools) Training costs
E N D
A Tool Vendor View on ITU-T Language Standardization Anders Ek
Why Standards? • Money!!! • Following a standard is a sales argument. • Sometimes even a requirement
Customer’s view • More than one tool • Cheaper • Safer (can switch tools) • Training costs • Wide-spread standard better than proprietory solution • Same notation in many teams • Subcontractors / joint development • Import / export • Standardized protocols / APIs / applications • Cheaper development
Telelogic and Language Standards • SDL since 1984 • MSC since 1992 • TTCN-2 since 1990 • TTCN-3 since 2002 • UML since 1999 • UML-2 since 2002
Language Wars 1 • Early 90s: SDL vs LOTUS • SDL winner • Graphics • Easier to understand • Industrial strength tools
Language Wars 2 • Late 90s: • SDL vs UML • UML winner • Marketing: UML better known (in particular in US) • More books, more tools, more conferences, more ads ... • Broader application area • Applicable to early phases • But if we lost, how come we’re still here?
Telelogic Solution • Basics: SDL & SDL tools are good! • ...but not enough. • 2000 • Co-existance SDL / UML • SDL-2000: UML harmonization • 2002 • One integrated language • UML-2 ongoing • 2004 • SDL profile? • ITU / ETSI acceptance?
Telelogic Standardization Priorites • SDL profile (”SDL part of UML”) • MSC profile • Application standards using the SDL profile • Outside ITU • UML-2 finished (”UML compatible with SDL”) • SysML (systems engineering profile)