Having generators produce the speci?¬?cations in XML was anticipated
to give signi?¬?cant productivity and quality improvements.
The starting point for modeling language development was the idea of using
graphical models, already suggested in the CPL speci?¬?cation. The language notation
was brie?¬‚y outlined there with the example model shown in Fig. 5.1. Although only
some modeling concepts were presented in this sketch example, the idea of using ?¬‚ow
models as a computation model was a clear starting point. The rest of the CPL
speci?¬?cation, however, focused on domain concepts and their semantics, not on
modeling language concepts.
DSMwas soon discovered to be of interest for two different kinds of companies: an
operator and a manufacturer of telecom equipment. The actual language speci?¬?cation
was largely the same because the starting point, the domain of call processing, was the
same. The differences were in the process of use and in the extension and integration
with other domains. The operator wanted to integrate CPL speci?¬?cations with other
designs, such as specifying voice messages during the call using VoiceXML. The
equipment manufacturer wanted to generate Java code based on the SIP framework
used in its product platform. This code would con?¬?gure hardware along with CPL.
While when discussing the DSM solution creation in detail, we focus on the common
and publicly available CPL speci?¬?cation.
Pages:
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209