The Software Intelligence Blog

Tag: Java

  • Software Risk: 4 Case Studies in Software Quality and Software Schedules by Capers Jones

    This post is taken from Capers Jones, VP and CTO, Namcook Analytics LLC original paper Software Risk Master (SRM) Estimating Examples For Quality and Schedules.

  • Investigating HealthCare.gov: What Went Wrong?

    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.

  • Keep an eye on legacy apps, COBOL’s not dead!

    Here we go again. You probably have heard, since it’s been reported everywhere, that American Airlines was grounded Tuesday, leaving passengers stranded for several hours due to a “computer glitch” in the reservation system. Because of the glitch, gate agents were unable to print boarding passes; and some passengers described being stuck for long stretches on planes on the runway unable to take off or, having landed, initially unable to move to a gate.

  • Show your love for Java

  • Do software frameworks simplify your life?

    We’re covering Java frameworks and their impact on application quality in an upcoming webinar, Java Applications and Coffee: The Variations are Endless, on Jan 29. As part of that, I wanted to share some insights along the lines of what we might discuss during the webinar. But first, what is a software framework?

  • C-suite: It’s time to get techy

    If you’re snickering at the idea of your CIO talking Java (or any programming language for that matter), trust us, you’re not alone. However, CIOs can no longer afford to be in the dark about their IT team’s choice of programming language and tools.

  • Crash Course on CRASH Report, part 3: Technical Debt

    Money isn’t everything…yeah, right!

    There are few, if any, who are so idealistic in this world that they will actually believe money isn’t everything. It doesn’t matter if it’s the scheduled time for a television show or a high-level decision to produce a controversial product, the motivation is money.

  • A Crash Course on CAST’s New CRASH Report

    p>Last week, CAST issued a report on the summary findings of its second annual CAST Report on Application Software Health (aka CRASH), which delves into the structural quality of business application software. The report has earned significant coverage throughout the technology media, including InformationWeek, InfoWorld and Computerworld, as well as the Wall Street Journal.

  • CRASH Report Exposes Millions in Technical Debt

    This year has been marked by high-profile outages and security breaches at global organizations like Sony, Sega, RIM, Citi, RSA, Honda, the International Monetary Fund the International Olympic Committee and multiple airlines, not to mention the U.S. Department of Defense. What each of these have in common is they each have at their root some structural quality flaw that led to malfunctions in their IT systems, failures in their application software or loss of sensitive data.

    It should come as little surprise, therefore, that the 2011 CAST Report on Application Software Health (CRASH) this morning reported that organizations are squandering millions of dollars in technical debt due to issues in their application software – issues that could have been eliminated during pre-production had proper structural assessments taken place.