What is legacy code? Legacy code is source code that already exists and needs to be used again. It's not necessarily lousy code, but it often needs some effort to integrate into newer systems. That means you need effective ways of overcoming legacy code's issues. What are your chances of working with legacy code? Given that most of the top 10 programming languages on the TIOBE popularity index have been around for at least 20 years, your chances are very high.

For enterprises relying on SAP systems, ensuring smooth operation through updates, integrations, and daily operations is crucial. Manual testing of these complex systems increases time to market and the likelihood of human error. The solution? SAP testing automation, which enables faster, more reliable testing, ensuring your business-critical processes run smoothly without bottlenecks.

Are self-driving cars safe? The software in modern cars contains more than 100 million lines of code that enable many different features — cruise control, speed assistance, and parking cameras. And, the code within these embedded systems only gets more complex. This trend will continue as cars of the future become more connected. Cars are increasingly dependent on technology. And they will progressively become more autonomous — and ultimately self-driving.

Perforce has been contributing and working in open source for decades now. We understand that open source is the linchpin for technology that supports businesses today. Our approach to open source is not unique to the industry at large or a company of our size (we have around 1,700 employees and 800 are on my team), but questions of our approach to open source became much more visible when we acquired Puppet – which has a really dedicated open-source community and a long history with open source.

In January 2025, the European Union (EU) will begin enforcing a new regulation called the Digital Operational Resilience Act (DORA). The DORA regulation mandates sweeping cyber resilience requirements for financial institutions and third-party information and communication technology (ICT) providers. In this blog post, we examine how two core Perforce offerings help financial institutions and their supporting ecosystem of service providers comply with the requirements laid out in the DORA regulation.

The cloud-based GitLab CI/CD platform allows development teams to streamline their Continuous integration (CI) and Continuous Delivery (CD) pipelines and accelerate their Software Development Lifecycle (SDLC). Adding strict, compliance-based static analysis — as provided by Helix QAC — as new stages to existing GitLab CI/CD pipelines will enhance the SDLC still further, and move your DevOps workflows from Continuous Integration to Continuous Compliance.

Developing high-quality products involves careful definition and tracking of both functional and non-functional requirements (NFRs). But what exactly are non-functional requirements? And what's the best way to keep track of them? Let’s dive into what non-functional requirements are and how they compare to functional requirements, review some common types of non-functional requirements with examples, learn best practices for writing them, then discuss how to track and manage them.

The latest release of Helix QAC and Klocwork features significant improvements to the static analysis tools, empowering development teams to shift left by fixing errors early, reducing development costs and releasing faster. Here, we provide an overview of the new features and functionality of the 2024.2 release.

Since HP ALM/Quality Center was acquired by Micro Focus (and now Open Text), users have been outgrowing its functionality. While HP upgraded many of its solutions to be more compatible with Agile and to support automation, ALM/Quality Center was left behind. What was once considered a best-in-class solution is becoming more obsolete by the day, having no resources allocated to development and limited support for customers. Today, there are better ALM options available.