The Software Intelligence Blog

Tag: Software Quality

  • It Takes a Craftsman to Uphold Software Quality

    Finding security, complexity and maintainability issues in complex business systems, improving development team throughput, and controlling global outsourcing contracts are not easy tasks; even the best analytics on the market still leave blind spots for technical teams looking to deliver better software and prevent outages. Addressing these issues takes a pragmatic approach to developing software and a passion for coding.
  • Software Complexity Is Killing Us

    While you're reading this article, if you come across words – and even sentences – that you don’t understand, there's a high chance you feel like developers do when they're looking at lines of code with a high level of nested complexity. A high level of software complexity can make it difficult to determine architectural hotspots where risk and cost emanate.

  • Software Analytics, un estímulo para el éxito de negocio

    Con motivo de nuestro 25 aniversario, el pasado 16 de junio tuvo lugar el primer User Workshop a nivel local, una sesión cuyo objetivo reside en crear una comunidad de usuarios de CAST AIP y mantener informados a los clientes de las novedades de nuestras soluciones.

    ¿Hacia dónde evolucionan las soluciones de CAST y cómo pueden influir en las organizaciones?, ¿Estoy optimizando el uso de CAST AIP en mi organización? En formato taller y para crear un ambiente dinámico y participativo se dio respuesta a esta y muchas otras inquietudes y experiencias de un grupo de usuarios de CAST AIP con el objetivo de extraer todo el valor y potencial que la herramienta puede aportar en cada organización y dependiendo del público al que se dirijan los resultados de análisis extraído.

  • Recap: Software Risk Summit 2016

  • Using Code Quality Metrics to Improve Application Performance

    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.

  • A Code Quality Problem in Washington State Puts Dangerous Criminals Back on the Street

    We always hear about issues with systems, applications, or services caused by poor code quality or missed defects, but what happens when these problems become life threatening? Recently an article posted by npr discussed the early release of dangerous prisoners who are now being charged for murder. According to the article, Governor Jay Inslee of Washington State reported that more than 3,200 prisoners were released early due to a software defect.

  • Key Discussion Points from Forrester Webinar: Agile Portfolio Management Requires Rapid Transparency

    Application portfolio analysis was at the center of discussion as Forrester Research Vice President and Principal Analyst, Margo Visitacion, presented how Agile development is affecting the application development process and IT’s portfolio planning. Ms. Visitacion explained that in the “Age of the customer,” they want more for less and expect companies to fluidly change based on their needs and demands. As companies shift their attention to customers’ experiences rather than production figures, it’s leading directly to higher revenue and a longer-lasting relationships.

  • Software Risk: Executive Insights on Application Resiliency

    Software risks to the business, specifically Application Resiliency, headline a recent executive roundtable hosted by CAST and sponsored by IBM Italy, ZeroUno and the Boston Consulting Group.  European IT executives from the financial services industry assembled to debate the importance of mitigating software risks to their business.

  • Faltering Software Quality and Standards: Why Programmers Should Stop Calling Themselves Engineers

    In the current tech scene, it has become common practice to refer to programmers as engineers. It seems that if you aren't part of sales or marketing teams you are now entitled to being designated as an engineer. However, what has been forgotten over the 50 years of looking to turn software development into a legitimate engineering practice, is that we still haven't reached the aspiration of being just that: a legitimate engineering practice. Traditional engineers have to go through stringent regulation, certification, and apprenticeships in order to gain the title. This creates an implicit responsibility of providing reliability and public safety. Software development hasn't reached this point yet - software quality and standards are not universally valued.

    So why is the tech industry using the engineering title to describe its technical workers?

  • Bad Software Quality Crashes Airlines’ IT Systems, Again: When Is Enough Enough?

    Southwest Airlines is the latest victim of the airline scandal. What scandal? It’s the one where airlines continue to cause travel delays due to poorly managed IT systems. It’s the one that caused Southwest to delay 836 flights on Monday and distribute HAND written tickets to passengers because of a ‘software glitch’. Southwest isn’t alone. United Airlines grounded hundreds of flights in July and American Airlines did the same in September and April. How long will consumers have to wait before these organizations figure out that the glitches are caused by bad software quality, which creates bad service?

  • Measuring Legacy Systems for Technical Debt and Quality

    Legacy Code

    When a business develops software, new technologies eventually outgrow the software. But that doesn’t mean the software stops working, which is why businesses continue to use legacy software. In fact, after all the fixes and patches, the legacy software still gets used because it simply works, even if it means the users are forced to run older operating systems and older web browsers to use it.

  • The Importance of Checking Software Risk and Software Quality: A Wake-Up Call to Firms Across the Globe

    If you've read the news lately, you've seen headline after headline (some, even on our blog) about computer glitches, technical failures, software risk, and hacks.  The health of applications is now under more microscopic attention than ever before - because no matter whether internal or external causes prompt a software outage, the security and stability of your applications are paramount.

  • Software Risk: A Tale of Technology Woes and Failures

    In 2014, the IT infrastructure at the Federal government’s Office of Personnel Management (OPM) was upgraded from a security rating of "material weakness" to one of "significant deficiency," according to The Wall Street Journal's CIO Report. Which means that the OPM, even after upgrading to mitigate software risk, wasn’t up to snuff. That is - to put simply - unacceptable. It is also both a dismal and infuriating fact to learn - especially for those who were among the 21 million present and past Federal employees, revealed last week, to have had their Social Security numbers and other personal information stolen in the recent data breach.

  • The Rule of Three: NYSE, UAL, and WSJ Operations Foiled by Their Own Systems

    The events of last Wednesday proved that things often do come in threes. The “rule of three” reared its ugly head, as technical failures occurred at three large American organizations: the New York Stock Exchange, United Airlines, and The Wall Street Journal. United Airlines grounded all flights nationwide, wasn't able to conduct background checks of passengers, and left flight attendants handwriting tickets (many of which were not accepted by TSA agents). Then, the NYSE suspended trading for almost four hours, the first time in a decade that trading was halted during regular business hours. The Wall Street Journal's homepage also faced difficulties and was offline for almost an hour.

  • Key Points dalla CAST CIO CONFERENCE 2015

    Giovedì 11 Giugno 2015 ha avuto luogo la IV Edizione della CAST CIO Conference. Ringraziamo i numerosi aderenti alla manifestazione che hanno contribuito al successo di questo evento consentendoci di analizzare, traendo spunto dai più recenti  casi di malfunzionamento di applicazioni “mission critical”, le strategie di prevenzione dei rischi attraverso la misurazione della qualità strutturale degli asset applicativi critici.

  • CRASH Report: Customized SAP Apps Increase Application Risk, Decrease Business Performance

    Companies worldwide use SAP, but SAP by itself does not resolve all of an organizations issues. As a result, a number of organizations need to customize SAP applications to suit their purposes, but this has met with mixed results.

    CAST today released the results of the 2014-2015 CRASH Report for SAP, which revealed more than half of those organizations opting to customize SAP applications have encountered increased application risk, additional software risk management costs and disruption of critical business processes.

  • Software Quality is More than Good Code

    Over the past decade, advancements in static analysis tools from both commercial and open source communities have dramatically improved the detection of developer violations of good coding practices. The ability to detect these issues in coding practices provides the promise of better software quality.

  • Agile-Waterfall Hybrid Best for Structural Quality According to CRASH Report Findings

    For the last half-decade, a debate has raged over which project management method reigned supreme – Agile or Waterfall. To determine which held the advantage, some looked at the management techniques and fluidity with which projects were completed, others judged the debate by pointing to the structural quality of the applications being developed.

  • Function Points, Software Analytics and Much More! Join Us in DC on June 2nd

    Join software measurement practitioners from government and industry at an event on June 2nd just outside of Washington DC. Discussion topics to include: the use of software analytics in all areas of enterprise program and development management, software measurement, automated function points, and software productivity management.

  • Key Points dal 1° Evento Metrico 2015 GUFPI ISMA

    CAST ha partecipato al 1° Evento Metrico 2015 organizzato dal GUFPI ISMA, associazione di riferimento nazionale per la misurazione del software in Italia, tenuto a Roma lo scorso 14 Maggio. La conferenza ha visto la partecipazione di Cast sui seguenti 3 topics: