IBM Sustainability Software - Ideas Portal


This portal is to open public enhancement requests against the products and services belonging to IBM Sustainability Software. 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.

Add a new idea Subscribe
Status Future consideration
Workspace IBM Engineering - Systems Design Rhapsody/RMM
Created by Guest
Created on Dec 16, 2022

RELATED IDEAS

Integrate entities of model-based and text-based specification

I often get the question by user of the Jazz platform, why the model-based elements (Rhapsody model elements) and the text-based elements (DNG artifacts) are not in fact the same entities.
We have some engineering entities which we represent on the one hand in the model, e.g. for functional decomposition, and on the other hand within the specification, e.g. as headings with requirements to the artifact beneath. If for example the name of the engineering entity is changed, we need to change it on both sides. (And the name is an example here)

How cool would it be, if the Entity is only defined one single time ->  the modeling views and the textual specification are  then only different views on the entities. 
Best case working is possible as well from the model view as from the specification view ->  e.g. also working on requirements directly from Rhapsody would be possible and not only to reference DNG artifacts.

I think this is often the expectation from our users when they hear we have one platform with modelling capability and requirements engineering.

Idea priority Medium
Needed By Not sure -- Just thought it was cool
  • Post comment
  • Admin
    SANTHARAM SUNEEL
    Reply
    |     Jan 16, 2023

    Hi,

    Thank you for bringing this to our notice, the RFE Review board looked at this and decided to keep it on the future release backlog.

    Regards,
    Suneel...

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.