A fix is available
APAR status
Closed as program error.
Error description
According to product help, it's possible to define "Class" or "Object" as Variant. When applying stereotype <<Variant>> against an object and mapping the object Type to a class. Stereotype of <<Variation Point>> and <<Variant>> shouldn't be applied to Part/Object but actually those two stereotype are accessible from the feature dialog of Part/Object.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: * * Rhapsody 8.1.3 * **************************************************************** * PROBLEM DESCRIPTION: * * Stereotype <<Variant>> is accessible by Part in SysML, but * * cannot be chosen as the used variant in the component * **************************************************************** * RECOMMENDATION: * ****************************************************************
Problem conclusion
Fixed in Rhapsody 8.2 - Added support for SysML parts as variant
Temporary fix
Comments
APAR Information
APAR number
PI72339
Reported component name
TLOGIC RHAPSODY
Reported component ID
5724V74RP
Reported release
813
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2016-11-15
Closed date
2016-12-05
Last modified date
2016-12-05
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
TLOGIC RHAPSODY
Fixed component ID
5724V74RP
Applicable component levels
R813 PSN
UP
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SS7P9W","label":"Rational Rhapsody"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.1.3","Line of Business":{"code":"LOB02","label":"AI Applications"}}]
Document Information
Modified date:
19 October 2021