For years refactoring software has been a common process used to improve the quality, efficiency, and maintainability of an application. However, a recent article by IT World discusses how CIOs may not be getting a valuable return on their investment of time and effort into the refactoring process. While many believe refactoring reduces the risk of future headaches, new findings acquired through a study by Sri Lanka researchers suggests code quality is not improved significantly by refactoring.

Good things come in three! I wouldn’t say we have saved the best for last, but the information we’re covering in this post is an exciting one! If you haven’t been following our series, I encourage you to read about what we have already announced is coming in AIP 7.1 -- the new delivery management tool and the Appmarq industry benchmarking repository. In this post, we wanted to give you an advance preview of a feature that will be made available towards the end of the year, with the next release of AIP. We’re talking about the design of our dashboard.

Applications are built on thousands, millions, maybe even tens of millions, lines of code. They are based on specific architecture gathering technologies, frameworks, and databases set up with their own specific architecture. If you have an action plan to improve your application on a specific issue, what will be your strategy?