I’ve been working in OT as a supplier to utility companies now for nearly twenty years. OT stands for “Operational Technology” – distinct, but a sister to, the more familiar IT – Information Technology. OT shares much of the characteristics of IT – it’s about hardware and software – but focuses on managing assets in the field, rather than, say, helping users in offices.
The WITS-DNP3 Protocol is an open communications protocol designed to allow Field Devices to talk to Master Stations within the water industry. For the first time the protocol gives the water industry a common language for communication between devices in the field and their telemetry masters. In turn this provides the users with a genuine choice of Field Device instead of being tied into using the Field Devices made by the vendor of the Master Station they have deployed.
The country goes to the polls for the EU in/out Referendum on 23rd June 2016. I was recently discussing voting habits with some other small business owners, when one queried why we couldn’t vote using our mobile phones, and if/when that option would be available? Whatever the type of vote – national, local or referendum, I don’t believe it will be anything but paper-based for quite some considerable time, and here’s why.
I’m often meeting other software developers. If things get a little more formal and we need to convey a potted history of our careers, a 2 minute run-through usually starts with “I graduated with a degree in Physics in 1998” or similar. It’s shorthand for “this is my education and background for the time before I started my working life”.
Many other developers seem to have a background in the sciences. Apart from scientists and developers being “technical”, I wondered why one would often lead on to the other. So I started researching studies and information on the web, and found surprisingly little. So in the absence of hard facts from other sources, this article is generally based on my experience and speculation….
In the years that I have been involved in software, it seems that the methods I followed in developing and testing software often revisit me with a different name and a heightened sense of hype. Luckily, the second coming of these ideas often cement sensible lessons I should have learned from my first experience and result in new methods which invariably seem to improve on my original experience. I have found this to be the case, given some poetic licence, with testing and the test automation pyramid. In this article, I look at what the test automation pyramid is and compare it with the older techniques I used to use.