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:
Post your ideas
Start by posting ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,
Post an idea
Upvote ideas that matter most to you
Get feedback from the IBM team to refine your idea
Help IBM prioritize your ideas and requests
The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The offering manager team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.
Receive a notification on the decision
Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.
If you encounter any issues accessing the Ideas portals, please send email describing the issue to firstname.lastname@example.org for resolution.
For more information about IBM's Ideas program visit ibm.com/ideas.
Addition of a Decision point that has multiple inputs and outputs
In Rational Rose we have models that use a decision point as a combination of a decision node and merge node. We converted our old models over and would like to keep this functionality, whether or not it strictly adheres to the UML 2.1 spec.
Right now our workaround has been to add a blank small merge point before the decision point so that we can have 2 inputs and 2 outputs on one "decision".
Something similar to the model validation constraints in the preferences would be nice, so that those who choose to not follow the exact specification of UML 2.1 can still use the tool without adding a bunch of needless nodes to diagrams.
Being able to customize what rules are used to draw the diagrams would be nice.
1. Create a new Activity diagram
2. Create an initial point
3. Create a decision point called "Check Fuel level" with 2 outputs, Fuel fine and fuel low.
4a. Fuel low output goes to an action called refuel.
4b. Fuel fine goes to a decision point "Takeoff?".
5. Refuel action then goes to decision point "Takeoff".
6. Decision point "Takeoff?" has 2 outputs, Yes and No.
7. And so on.
Do not place IBM confidential, company confidential, or personal information into any field.