Specification of telecom services with a UML profile and production of SDL skeletons

1
 Specification of telecom serviceswith a UML
profileand production of SDL skeletons

• M.Belaunde, F.Dubois, B.Nicolas
• France Télécom RD BD/DTL/MSV/TOM

OMG Technical Meeting,April in Paris, April 26
2001
2
The Myrtille Project
A component-based approach for enablingfast
analysis design and validation of new telecom
services
3
Contents

• 1. Introductory material- UML/LDS comparison-
  Whats a UML profile- The ITU-T Z109 profile for
  LDS 2000
• 2. The UML profile for Telecom Service
• 3. UML to LDS conversion
• 4. Conclusions and perspectivesconcerning UML
  for telecom

4
UML and LDS Comparison
SDL
UML

• General purposeno exec semantics
• Intuitive notation forcapturing structureand
  functionality
• wide-spread tool support
• Not stable

• Formal spec for reactive systems simulation
• Supported formalism
• Stable

5
What s a UML Profile

• Specializes UML toa specific domain
• Uses an extension mechanism (stereotypes, tags,
  constraints, icons)
• Tool support (example Objecteering Softeam)

6
The UML Profile forTelecom Services
Summary of the concepts
7
The UML Profile forTelecom Services
Analysis Phases

• Two main phases for analysis
• Domain analysis
• captures reusable concepts and
• populates a domain repository
• System Analysis
• models one service using the domain
• repository

8
The UML Profile forTelecom Services
An example of a reusableGeneric Service
9
The UML Profile forTelecom Services
An example of a reusableService Feature
IdentificationPurposePreconditionPostcondition
exceptions
10
The UML Profile forTelecom Services
An example of a reusableservice feature
resources
11
The UML Profile forTelecom Services
An example of a specificservice VPN
12
Generating SDL skeletons
Tool sequencing
13
Generating SDL skeletons
Conversion rules

• Service Block Type
• SF (definition) Process Type
• SF (instance) Process in Block
• SF operation Exported procedure
• Ressource Data (newtype)

UML analysismodels
SDL squeletons
Service Pack
BlockType
Feature Pack
F
Ressource Pack
Proc1Proc2
14
Conclusions (1)

• A platform neutral telecom servicespecification
  / platform dependent mappings (LDS, CORBA)
• Standards are needed to allow bettercooperation
  operators/constructors
• Future use of UML for precise behavioralspecifica
  tions

15
Conclusions (2)
UML for Telecom initiative
interaction
Profile for TMN
Profile for Telecom Services
Profile for Other telecom specific stuff...