Fixes are available
APAR status
Closed as program error.
Error description
Summary: ********* Modification of Entity type doesn't work properly with a type for added element. Description: ********** When working with a user-defined Rhapsody Type Analysis and trying to re-analyze/re-load the projects in gateway, error message(s) similar to the below are reported: 'The current project defines the following modifications to elements that no longer exist in the loaded documents. You can either delete the modifications, or recreate the missing elements in the document. You can select 'Copy' to place this message in the clipboard, or select 'OK' and review the rules for this project for more information. - entity 'GUID 283aea20-7b34-46a7-85f0-365e2abac977 - SFB_MC_L2_TICompCheckECUResistCompTemperature' Elements added from IBM Rational Rhapsody Gateway which parent do not exist anymore in original document: - reference 'Reference to 'Requirement: 4.14.2.1.c.1TCOMP SDD Review'' on 'GUID 283aea20-7b34-46a7-85f0-365e2abac977 - SFB_MC_L2_TICompCheckECUResistCompTemperature''. The intention is to establish traceability (coverage) between safety requirements and software architectural elements. The safety requirements are specified in a simple XML format and the software architectural elements are specified by a Rhapsody model. The required software architectural elements are captured as 'Entity' elements. The coverage links are stored in Rhapsody Gateway only (in a modification file), i.e. they will not be imported to the Rhapsody model. As a result, all the entity elements and coverage links are handled as invalid and have to be removed. It is observed that the source of the reported problem is the user-defined type that has been created to analyze the Rhapsody project (i.e. VW MQB EPS SWA - Safety View - SysML). It was found that, if we change the type of analysis of the Rhapsody project to 'Rhapsody SysML' from the existing 'VW MQB EPS SWA - Safety View - SysML', the reported error is no longer observed and the 'SafetySatisfaction' links are also preserved. User is aware that, for 'Rhapsody SysML' analysis type, the reported error is no longer observed. However, that is not the same configuration as the specific customized analysis type contains a definition for Entities, Rhapsody SysML doesn't.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: * **************************************************************** * PROBLEM DESCRIPTION: * **************************************************************** * RECOMMENDATION: * **************************************************************** Modification of Entity type doesn't work properly with a type for added element.
Problem conclusion
Fixed in Scorpio
Temporary fix
Comments
APAR Information
APAR number
PM56563
Reported component name
TLOGIC RHAPSODY
Reported component ID
5724V74RP
Reported release
753
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2012-01-23
Closed date
2012-09-21
Last modified date
2012-09-21
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
R753 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":"7.5.3","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]
Document Information
Modified date:
28 October 2021