APAR status
Closed as program error.
Error description
Requirements should be treated like notes on an Activity Diagram so they can be dragged on to the canvas for traceability purposes. They should not re scope when you do this. In this instance the customer has requirements coming from multiple requirement documents, so finding out where it came from to move them back is a nightmare. Enforcing requirements around the edge is difficult from a process enforcement perspective. Fundamentally, you should be able to put a requirement into a swim lane without re-scoping it. To reproduce: --------------- 1.Create an AD 2. add a swim lane frame and divider. 3. Drag a requirement from browser to the lane. 4. See that the requirement in browser is moved under AD
Local fix
Problem summary
When you drag a requirement from the browser to a swimlane in an activity diagram, the requiremnt is moved (reparented) in the browser.
Problem conclusion
Set the General:Graphics:AllowRequirementReparenting property for the diagram (or at the project level) to Cleared (clear the check box).
Temporary fix
Comments
APAR Information
APAR number
PK98191
Reported component name
TLOGIC RHAPSODY
Reported component ID
5724V74RP
Reported release
750
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2009-10-08
Closed date
2009-12-04
Last modified date
2009-12-04
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
R750 PSN
UP
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SS7P9W","label":"Rational Rhapsody"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.5","Edition":"","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]
Document Information
Modified date:
04 December 2009