SNIP_CLASSIC_STD_FIGURE_Figure_2_15

Figure 2.15: Std_ReturnType Extensions example In case multiple modules of a stack need to extend Std_ReturnT ype in the same way , there is no need to define the extension separately for each module of the stack. The following modeling shall be applied: [TR_BSWMG_00173] Generic Std_ReturnType Extension⌈The generic definition of a Std_ReturnT ype extension specific to multiple modules shall be modeled as an UML Class with stereotypes≪extra_literals≫ and≪generic_type≫.⌋() [TR_BSWMG_00174] Generic Std_ReturnType Extension is no Std_ReturnType Extension⌈The generic definition of a Std_ReturnT ype extension is no extension to be used by BSW modules directly . Therefore it shall not be in an realization relationship to any BSW module.⌋() [TR_BSWMG_00175] Users of Generic Std_ReturnType Extension ⌈The definition of a BSW module specific Std_ReturnT ype extension that has the literals as defined by Generic Std_ReturnT ype Extension shall be modeled as an UML Class with stereotype≪extra_literals≫ and derived from that Generic Std_ReturnT ype Extension. Apart from that it shall be modeled as a usual Std_ReturnT ype Extension. ⌋() Note that Std_ReturnT ype Extensions derived from a Generic Std_ReturnT ype Extension may define their own literals as well, in addition to the literals they derive from the Generic Std_ReturnT ype Extension.