I've been picking up formal specifications, predicate calculus, etc rather well I think. I'm not afraid of doing the work: it's important!
And besides, the maths are beautiful.
I've been picking up formal specifications, predicate calculus, etc rather well I think. I'm not afraid of doing the work: it's important!
And besides, the maths are beautiful.
I view the PE in software as being for managers on software-intensive engineering projects, say for example, plant controls or electronic medical devices. If you look at the current licensing path, you'll see that it requires deep domain-specific engineering knowledge (e.g., mechanical engineering) or broad engineering knowledge (e.g., statics and dynamics + fluid dynamics + materials science + ...), neither of which are common among self-labeled software engineers: this is why I view a PE in software as being intended for a controls engineer who does a lot of software projects (as one example). It's not really relevant for most software domains, nor is it intended to be.
I'm still enthused about introducing more formal methods and "engineering" practices into software development. I think it is very useful and indeed as the world becomes more reliant on open-source software... there needs to be some sort of protection of the public good, no?
Thanks for taking to time to respond to my, sometimes naïve, comments.