search.noResults

search.searching

saml.title
dataCollection.invalidEmail
note.createNoteMessage

search.noResults

search.searching

orderForm.title

orderForm.productCode
orderForm.description
orderForm.quantity
orderForm.itemPrice
orderForm.price
orderForm.totalPrice
orderForm.deliveryDetails.billingAddress
orderForm.deliveryDetails.deliveryAddress
orderForm.noItems
Feature: Software and tools


So, as this year’s TrustInSoſt’s ‘2025


Today, teams are not just asking if software works, but whether it can fail at all. This is a trend that will define the next decade of software assurance


As hybrid codebases expose blind


spots, we are seeing modern system programming languages like Rust gaining traction, especially where safety and performance are important. Rust focuses on safety, speed and concurrency, but it is rarely used alone, which can introduce errors. Legacy programming languages like C and C++ are well established and widely used, but when combined with others it can introduce new risks. Te report captures developer concerns around mixed-language projects, where existing test pipelines oſten fall short. Te report also highlights another


crucial aspect among developers: those most invested in testing are also the most frustrated with the status quo. Tey’ve reached the limits of what traditional approaches can do, seeking better results from new ones.


Compliance sets the pace New industry standards are also pushing soſtware teams toward traceable, auditable testing processes, making it more than just a paperwork problem, but a technical one. Tis is also making tools that offer mathematical assurance more relevant than ever.


State of Soſtware Assurance Report’ highlights, there is a pivot from detection to prevention. Teams are not just asking if soſtware works, but whether it can fail at all. Tis is a trend that will define the next decade of soſtware assurance.


Code coverage is not a size that fits all Many agree that, in theory, the more code coverage there is, the better, even though this is not always evident in practice. In practice there are many factors affecting outcomes, including testing maturity, legacy systems and hardware-constrained environments. Testing time and effort vary greatly


depending on many factors in the code, making efficiency an ever-present factor when aiming to achieve quality and reliability. Different sectors are addressing these issues differently, and more can be learned from the report.


www.electronicsworld.co.uk September 2025 15


Page 1  |  Page 2  |  Page 3  |  Page 4  |  Page 5  |  Page 6  |  Page 7  |  Page 8  |  Page 9  |  Page 10  |  Page 11  |  Page 12  |  Page 13  |  Page 14  |  Page 15  |  Page 16  |  Page 17  |  Page 18  |  Page 19  |  Page 20  |  Page 21  |  Page 22  |  Page 23  |  Page 24  |  Page 25  |  Page 26  |  Page 27  |  Page 28  |  Page 29  |  Page 30  |  Page 31  |  Page 32  |  Page 33  |  Page 34  |  Page 35  |  Page 36  |  Page 37  |  Page 38  |  Page 39  |  Page 40  |  Page 41  |  Page 42  |  Page 43  |  Page 44