Modeling concepts can also be used to remove, or more accurately to
ignore, certain model elements during code generation. Following the same language
structure as above, one way is to have a property for those elements that can
be optionally ignored. The modeler can then just change the property values for those
elements that are not included in the generated code. If the excluded elements
are connected with othermodel elements, then they can be excluded too. An alternative
mechanism to ignore some model elements is to connect them to a model element
that is used just for excluding parts of the design based on the required variability. Such
exclusion elements may have their own properties that the generator reads while
selecting the exclusion elements and ignoring the related model elements during
code generation. Often, though, having multiple relationships just for exclusion may
make the model complex since it now has both application data and exclusion data.
This becomes even more complex if there are multiple variability objects, one for each
variation point. Then, it often becomes better to create a con?¬?guration diagramjust for
describing the variation. This variation diagram then usually works also as a starting
point for code generation: it is related to other models and the generator already knows
the desired variation when accessing the actual speci?¬?cations.
Pages:
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444