When you are a consumer credit company, victimized recently by a serious security breach where hackers exploited an application vulnerability to steal the personal information of roughly 143 million people, what do you do for an encore? For Equifax, the encore may be “get hacked a second time.”
Scope, Quality and Complexity in Cost Assessment
Now that we’ve made the case for Application Mass Index (AMI) as a tool to standardize applications and make comparisons in Part One, it’s important to outline the key steps for success when utilizing this metric.
Insurance companies still spend a lot of money maintaining the infrastructure for their core legacy apps. This is an opportunity cost for them as they could have spent that money to change and innovate on other fronts like new product development, distribution channels and customer experience.
All too often, software projects both exceed their budgetary limitations and are labeled too slow by stakeholders. What is the root of this problem? To isolate the cause of—and fix—this phenomenon, project managers need a new approach.
Last week, CAST attended the Gartner Sourcing Summit in Nashville with more than 800 senior sourcing, procurement and vendor management executives from Fortune 500 companies.
The biggest lesson learned from the Equifax breach is that executives and application owners need a software risk scorecard that clearly outlines KPIs around software structural quality and security.
Open source is the lifeblood of modern software development, there’s no getting around it. It makes sense that development teams want to get a head-start when beginning a new project and don’t want to have to start from scratch every time. Because open source software is designed and “certified” with public use in mind, it is prevalent throughout the app dev community.