Skip to Main Content
Cloud Platform


This is an IBM Automation portal for Cloud Platform products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).


Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.


Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.


Status Not under consideration
Created by Guest
Created on Mar 25, 2013

RSART- Redefined operations don't propagate param changes

Problem description
# in base class define an abstract operation
# in derived class rename it
# in base class rename abstract operation
# in derived class observe operation name has changed (may also work
for cut&pastes of redefined)
# in base class change type of the abstract operations parameter
# observe that the type change DOES NOT propagate

Mattias has the following comment on this issue:

"The requested functionality does not exist. The user needs to update
the signatures of redefined operations manually."

Idea priority Medium
RFE ID 32818
RFE URL
RFE Product Rational Software Architect Real Time Edition
  • Admin
    Osman Burucu
    Reply
    |
    Jan 19, 2024

    As part of the review process, we strive to be transparent about our intentions with each enhancement suggestion.

    This idea is either outdated or has been implemented in one of the versions. Please check with latest version (V 12.0 at the time of writing)

    The offering team has carefully reviewed this idea and has decided that it does not fit into our current plans, so the idea will be closed. The idea will be kept in IBM's ideas repository and may still be voted on. It might be reassessed or reopened for additional feedback in the future. We value your feedback and thank you for allowing us the privilege of partnering with you in developing our products.

  • Guest
    Reply
    |
    Sep 24, 2015

    Due to processing by IBM, this request was reassigned to have the following updated attributes:
    Brand - WebSphere
    Product family - Application Platform
    Product - Software Architect Real Time Edition

    For recording keeping, the previous attributes were:
    Brand - Rational
    Product family - Design & development
    Product - Software Architect Real Time Edition

  • Guest
    Reply
    |
    May 20, 2013

    Unfortunately the UML representation is to duplicate the signature for a redefining operation. So each operation has its own signature representation, even an operation that redefines another operation and hence has exactly the same signature. Perhaps we should implement this RFE in two steps. The first step would be to extend the current way we propagate operation name changes to also cover other changes in the signature, but still limit this propagation to only work for loaded operations. The second step could then be to implement the proper refactoring command that would be able to update the signatures also for unloaded operations. If you agree with this approach we will investigate accordingly.

  • Guest
    Reply
    |
    May 15, 2013

    We can see the usefulness of this, but we typically load the open models into memory first, prior to doing anything else. The initial problem is that when we do so, we see a change to the base class function name take affect in redefined functions. We do not see the same change in parameters take affect.

    We were hoping that something similar to how TC inheritence was being done- that the efx file on disk would have a link to the parent function, and have nothing else in that efx file aside from things that are overriden within that redefinition.

    For example, looking at a TC file on the disk shows that the copyright field is not anywhere in that file, as it is provided by the parent TC. We could override it, which adds to the file, but for any non-overriden things, any updates to the parent get pushed down to the the child.

  • Guest
    Reply
    |
    May 15, 2013

    Currently planned for 8.5.1 CP2. We need to add a new refactoring in the Refactor context menu. The propagation cannot be automatic as this would force all models to be loaded (i.e. it would be slow).

  • Guest
    Reply
    |
    Apr 29, 2013

    Under Consideration