Integrating Formal Verification and Conformance Testing for Reactive Systems

Integrating Formal Verification and Conformance Testing for Reactive Systems: Nice boring title, huh? Well, if it's one thing that I don't like, it is boring the hell out of people. That is why I have been trying to think of the least obvious publications to write my translation in. The first thoughts that came to my mind were either a fitness magazine like Men's Health or a reputable magazine like Playboy. Unfortunately, I soon realized that I couldn't write well enough to pull that one off. So I needed a fitness/naked women hybrid that allowed me a little more leeway in the technologial/software engineering field. Then I was hit with the spirit of inspiration and plagarism:

Esquire!

It's the perfect audience for my style of writing: People who like to keep themselves well informed about the world around them, but simple enough to be easily distracted by half-naked women. It's like shooting fish in a barrel! Although I may not be able to pull this one off. In that case, I'll probably repost in this blog saying that I've switched to an IEEE publication. But for now I want to test myself and see if I can do this. I have all weekend to rework the translation if I can't do it.

My article may be styled after something like this, the difference being that this article is about bioengineering instead of computers/software: http://www.esquire.com/features/ESQ1204-DEC_B&B_SCIENCE_rev_2_1?click=main_sr


What I would like people to get out of this article is that there is more to software then sitting in front of a computer frantically typing out code. I also want to prove that real coding isn't random button mashing and looking at pretty visuals on a screen like the movie Swordfish (although there was a naked Halle Berry, which brings me full circle to my Esquire audience). I want to show that it takes a lot of planning and mental work to figure out if a software system is secure and complete. I want to also explain that just because a software system does what it is supposed to do does not mean it is a good system. Testing a software system is a very extensive series of events and should not be taken lately or a critical error may occur that could have been prevented.