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.
The following two is regarding UML to LDM transformation feature.
a) Right now we cannot specify data type transformation rule. For example, an attribute with property String in UML model need to be transformed to attribute with data type varchar(254) in LDM. can we get such facility to specify in the transformation config file OR elsewhere?. Right now all String data types are converted to Varchar(32k); this is not preferable as it would require large data storage area in physical schema though it might not be really needed.
b) In UML to LDM transformation Is it possible to assign label names in LDM by parsing original attribute or entity names?; eg: an attribute bearing name firstName in UML, is transformed to firstName in LDM; but when we perform LDM to PDM transformation we would like to apply standard abbreviations to various words. In this instance we would like firstName to be transformed to FST_NME; whereas it is not possible now because these two words appear concatenated. So if only we can have a facility to apply transformation rule such as: label of each attribute (note that attributes have name and label properties in LDM ) need to be assigned using attribute name in UML, which has to be parsed at the beginning of a uppercase letter. If this facility is available, then the label will be assigned with name 'first Name' during UML to LDM transformation. And we can use Lable name to be used during LDM to PDM transformation.
The above two features are useful for the data modelers when they source their data model from UML. The change request mentioned against a), will essentially give the flexibility for the data modelers to specify data type transformation rule.
The change request mentioned against b), will essentially give the flexibility for the data modelers to specify the transformation rule for changing the name since the naming conventions in UML and LDM are different. This will further facilitate the data modelers to apply the glossary model (for abbreviations) in LDM to PDM transformation.
Do not place IBM confidential, company confidential, or personal information into any field.