We conducted an interview with one of of customers for our marketing purposes but some positive statements came out of it about adopting Model Driven Development techniques and specifically UML. I have edited the interview to include just the questions that may be of interest to you...
Companies across the globe are continuing to allow legacy technology negatively impact their business because they either don’t know what to do or feel it is too risky or costly to modernise their applications. The reality is that there will come a point when they cannot ignore it anymore and they have to do something about their legacy systems.
We asked one of our customers who we supported migrating from HOOD to UML...
What was the main reason for migration?
There were three main reasons:
What benefits does migrating to UML give you for the future?
- To have a single toolset for both Software Analysis and Software Design work
- To reduce the number of toolsets in use on the project (thus reducing maintenance renewal costs)
- To move to a company preferred toolset
- To increase integration with other company preferred toolsets (i.e. DOORS and Dimensions CM)
We now have both our software analysis and software implementation models in the same toolset; with both of these models integrated with our requirements database and our configuration management system. All three toolsets are “current” toolsets widely used across the company and across industries.
Will code generation be a consideration going forward?
Code generation has to be ultimate aim; but for now we are happy that what is in Rhapsody can be shown (via the compare functionality) to be a reasonably accurate representation of the code.