Because the world of software development is so incredibly complex and modular, quality assurance and testing for software risk has become costly, time-consuming, and at times, inefficient. That’s why many organizations are turning towards a risk-based testing model that can identify problem areas in the code before it’s moved from development to testing. But be careful, because hidden risks can still exist if you don’t implement the model properly throughout your organization.
The future challenges for Software Quality assurance (SQA) follow a few software trends, including:
Complex and large software packages
Integration with external components and interfaces
The need to deliver quickly
The need to deliver bug free software
The standard software quality activities defined by IEEE, such as verification and validation, are integrated into the software development cycle. We see dedicated SQA roles and resources in major organizations. Also, many multi-national companies are pushing to have a central team drive and manage the quality processes, methodologies, and tools across all their sites and teams.
After watching application after application fail on launch day or during a routine upgrade, it seems the IT industry is finally waking up and focusing its attention on software quality and software risk. Because of this and other factors, we have seen positive growth numbers in software revenue in the third quarter of this year. And we expect this number to continue trending upward from here on.
You can read more about our growth in a press release we issued this morning, but I wanted to highlight a few key details here on the blog.
The media has been a firestorm of ‘glitchy’ reporting since the botched launch of the Obama Administration’s healthcare exchange marketplace, mainly because no one’s quite sure what did or didn’t happened.
If you missed it, the exchange’s Oct. 1st launch was mired with complaints, outages, and glitches. Many pundits and talking heads claimed that this was simply because of the enormous amount of Americans who were all trying to log into the brand new system. But we dived into the code to figure out what was actually going on, and what we found was much more nefarious.
Nobody disputes the promises made by enterprise application portfolio analysis tools made over the past 20 years – visibility, risk identification, faster, better budgeting decisions.
What has been disputed is the belief that organizations can actual get there – to have objective, critical information in a single location without breaking the bank or stopping everything else they are doing.
Like most ‘enterprise’ software efforts, organizations choke and eventually lose their appetite trying to eat the elephant in one bite.
But what if you paused and dissected APA for a moment? How might you break it down into smaller chunks? What capabilities are more important than others? How could you disrupt the typical deployment approach?
We’re less than a month into the launch of HealthCare.gov, and as each day passes we’re finding out about more glitches, shoddy code quality, a lack of end-to-end testing, and rushed changes made days before the healthcare exchange was to go live. All of which are symptomatic of a software project being rushed to completion to meet a deadline without considering the implications of a botched launch.
The Obama Administration has already announced that HealthCare.gov was not properly tested before launch, but with top contractors of the site being questioned by Congress, we’re learning the problem lies much deeper than that. In fact, on the surface, it looks like each contractor handled a very small part of the overall website and left it to someone else to tie them all together at the last minute.
What draws me to Anaheim, Calif., in October is not the walking Disney characters (though there are plenty of those), but instead the STARWest, the West Coast’s largest conference on software testing analysis and review.
After a day listening to James Bach teach critical thinking for testers, I wake up extra early on Tuesday to attend the opening keynote — Michael D. Kelly and Jeanette Thebeau discussing “What Executives Value in Testing.”
I know Michael well; he is a former president of the Association for Software Testing who worked as a test manager at Liberty Mutual, a Fortune 500 company, then went on to start his own company that is going well. His partner, Jeanette, is a bit of wild card; her background is in working with executives to shape the business message.
With this pair, I’m not quite sure what to expect.