These reports analyzed
models for the kinds of rules that cannot or should not be checked after each modeling
action. For instance, an unreachable part of the call model and a missing default path
are best warned about with reports. Similarly, if choices based on a location lookup
110 IP TELEPHONY AND CALL PROCESSING
include the same lookup value multiple times (e.g., more than one success choice),
their occurrence can be reported.
Model checking results were accessed in two different ways: separately from a tool
menu and by placing the current status and warnings next to a separate model element.
A third option would show the warning next to each model element having an error,
but combining them in one place was preferred.
5.3.3 Modeling Notation
Lennox et al. (2004) proposes a very basic notation for the language: directed arrows
between boxes (see Fig. 5.1). This is a typical starting point when de?¬?ning a concrete
syntax for a language. The notation was made by a consultant. During the notation
de?¬?nition, no customer feedback was given, perhaps because there was no established
practice in either of the companies??”anything was considered better than writing
speci?¬?cations directly in XML. First, the notation was just boxes but later symbols
that clearly distinguished the concepts were used.
Pages:
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229