IBM Sustainability Software - Ideas Portal
Hide about this 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
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
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.
Hi,
Thank you for bringing this to our attention.
I have added it to our backlog for review in an upcoming grooming session.
Regards,
Suneel...
Hi Suneel
In many project we have vertical ownership for certain products. This means that a team is responsible to deliver a feature from requirements elicitation up to system integration, verification and validation, including system design and implementation.
Specifically that the system and software architecture are in the responsibility of the same team, even there might be just one "architect" doing changes for system and software architecture relevant for the feature. To enable here an optimal flow for users it is important that they are able with minimal interruptions to change multiple levels of architecture, e.g. in Rhapsody to work in the same model on both system and software architecture.
Our System Architecture method uses SysML wile lour Software Architecture method uses UML.
It is already possible to create models sing both UML and SysML. But it is not possible to use SysML related features while the project is in "UML" mode, and also it is not possible to use UML elements when in "SysML" mode. It is possible to always switch the project type by the user, but this triggers an unnecessary update of the rpyx file, and we don't want that.
Here is how the scenario would look like:
define separate RMM components for System Architecture model and SW architecture model
in a different component, e.g. for a specific feature, share units (packages) parts of these components as "unit" (read/write)
the package that was defined in the SystemArchitecture should behave as if it is SysML
the package that was defined in the SW architecture should behave as if it is UML
Hi,
We need additional details regarding this issue.
Typically, there are separate SysML and UML models. In some cases, the SysML model is included in the UML model as a reference (read-only).
Could you please elaborate on the benefits of modeling both SysML and UML within the same project? Additionally, we would appreciate it if you could provide relevant use cases to help us better understand the context and potential advantages of this approach.
Looking forward to your insights.
Regards,
Suneel...