A software engineer from ICT Automatisering has built a distributed controller across various Raspberry Pis to replace the Mindstorm controller bricks.
This author has yet to write their bio.Meanwhile lets just say that we are proud email@example.com contributed a whooping 16 entries.
Entries by firstname.lastname@example.org
This Software Strategy Whitepaper gives you some clever insights in how future winners in the race to achieve dominance in “Smart” products and services stay on top of the game.
How the Liteq 500 case points to the future of software development.
“Software is different. Just by editing the text in a file somewhere, the same hunk of silicon can become an autopilot or an inventory-control system. This flexibility is software’s miracle, and its curse”, writes James Somers in his recent article “The Coming Software Apocalypse”.
There’s a new rage sweeping in from the East: Feng Shui for Software Development. For those of you who have never heard of Feng Shui it’s the ancient Chinese practice..
For those of us who read tech news, not a day goes by without another story about utopian technologies that are going to change our lives forever. And yet even today, relatively simple operations are not reliable. Here’s a case in point..
The cost of fixing a defect increases exponentially as the defect propagates. And yet, a conventional approach to software development performs only subjective analysis of specifications and designs. But what if there was a way to verify and validate software specifications and designs?
There are various ways in which an intruder might seek to compromise your operations. One of the simplest, blunt force methods is to look for an application with network interfaces and attempt to disrupt it. How certain are you that your software systems are resilient enough to cope with such an attack?
Written by our North American reseller, Emenda, this article “The time you could fix that bug is gone!” describes how Safety Critical Software Development best practices can help lower QA costs..
Reengineering legacy software is an undesirable but nevertheless occasionally unavoidable necessity. In this paper, we present a technique by which lost or poorly understood behaviour can be recovered and turned into formally verifiable models.