There is a lot of talk about DevOps these days. I guess you’ve noticed that too, if you have anything to do with tech and haven’t been living in the woods the last three years.
I spoke on a panel a few weeks ago at the MIT CIO Symposium called Running IT Like a Factory. One of my co-panelists talked a lot about cloud-native companies, and how Netflix does 3,000 releases per month and Amazon does 11,000 releases per year. He also referenced the robustness of AWS and how companies like this can create a ton of value very quickly.
The key to security is to ensure that your most sensitive data is handled with proper controls in place. This should include working with your architects to explore the architecture of applications that handle the most critical data, starting from the data elements themselves and fanning out via impact diagrams (for example, CAST does this with the Application Intelligence Platform). Over time, your team will be able to establish secure architecture components that should handle all sensitive data.
In software maintenance and evolution, it is important to assess both code health and application architecture in order to identify issues impeding software quality goals. One way to move the needle toward software quality is to use Technical Debt (TD) indexing as a method to evaluate development projects.
We recently presented a paper at MTD 2016, the International Workshop on Managing Technical Debt put on by the Software Engineering Institute at Carnegie Mellon, where we discussed the way five different and widely known tools used to compute Technical Debt Indexes (TDI), for example numbers synthesizing the overall quality and/or TD of an analyzed project.
Fintech is the hot new thing. It’s the industry that will carry the UK through Brexit. It’s the latest wave of startup mania in NYC. It’s becoming the darling of Silicon Valley. Chinese tech investors are all over it. It’s fresh. It’s sexy. But, wait a minute. What is Fintech?
Recently I attended MIT’s Fintech conference (#MITFinTech). We heard Brad Peterson, CIO of NASDAQ, talk about his firm as the original Fintech founded 45 years ago. Brad told us that NASDAQ no longer thinks of itself as an exchange, but as a Fintech company. A couple MIT professors told us there are 1800 Fintech companies out there today, and that number is quickly growing. There are some that promote robo-advisors as autonomous correctors for investor freak-out during volatile markets, and others that collect live market data from the web in order to predict real economic indicators, as opposed to statistics collected by government technocrats. Blockchain, we were told, is like the Internet was back in 1993.
CAST Italy users’ group conference
On June 22nd, CAST held its annual User Group in Italy, hosting software measurement professionals from major companies in the Banking, Insurance, Telco, Public Sector and IT Consulting industries for a four-hour working session. Attendees walked away from the event with a better understanding of best practices in establishing objective software measurement standards and creating better visibility in to application portfolios.
Among CAST Application Intelligence Platform presentations and updates regarding the new CISQ RFC for Automated Enhanced Points and its relationship with the AFP OMG standard, attendees also discussed software measurement in Agile and DevOps environments.
Recently, CAST co-authored a paper with The Boston Consulting Group titled, Will Your Software Help or Hinder Digital Transformation? Navigating the digital transformation journey is a challenge, often wrought with roadblocks and IT complexities related to technical debt, disparate application development techniques and more. So how can CIOs help their company achieve digitization goals?
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.