Naughty engineers need discipline

The software engineering industry is in need of some tough love, the kind of attention more commonly known as 'bondage and discipline' to pull it into shape and transform it into a serious profession.

It is an industry in dire need of standards, according to Sydney University of Technology professor John Leaney, as well as a stiff regulatory framework that includes penalties and government-driven legislation.

The current landscape, Leaney said, lacks accountability and isn't likely to change until people are (literally) killed.

That is, a major accident with an ugly death toll, caused by a software glitch or failure of an information system that underpins so much of the world's critical infrastructure today.

In a presentation entitled Bondage or Discipline, Professor Leaney proposed formal standards for software engineering and explored the pitfalls of runaway software technology development that without quality and safety standards.

"Software impacts every aspect of our modern lives, yet whom do we call to account when its failure causes serious economic or human loss; there is no other industry so lacking in basic standards and quality control," he said, adding that it is not only doctors that bury their mistakes.

Leaney cited an example of a software error in a dosing machine used in cancer patient treatments that led to the death of seven people in 1993. "Software engineers aren't held liable; it's not like civil engineering where you would be facing manslaughter charges. Civil engineering has evolved over thousands of years and professionals are registered, certified and adhere to standards," he said.

"Computing is a relatively new profession dominated by commercial pressures like time-to-market allowing vendors to sidestep liability; end users really should have greater expectations and be more forthright and outspoken."

Investigating ways to build discipline into software development, Leaney said standards are often seen as a form of bondage by developers who believe it stifles creativity.

He said one example is CMM (Capability Maturity Model); another is the ISO 9001 standard, which is in widespread use.

"There is a huge difference between what is preached and what is practised because the ISO 9001standard isn't really applied, it doesn't include guarantees," Leaney said.

"If a building collapses there is compensation, because builders are in a profession that has the right infrastructure in place to support good practices; this [standards] problem is really unique to the software engineering profession."

The problem also lies with organizations which reduce testing times and won't buy sophisticated tools in a bid to cut costs.

Leaney said IT professionals have a responsibility to ensure this doesn't happen as there is plenty of evidence that poor software constrains organizations.

"These products are fundamental to business, shouldn't they be tested?"

Local organizations such as Software Engineering Australia (SEA) have introduced programs such as SoftwareMark which is a software process certification product similar to the Woolmark program used by the wool industry and is akin to a quality stamp of approval.

Join the newsletter!


Sign up to gain exclusive access to email subscriptions, event invitations, competitions, giveaways, and much more.

Membership is free, and your security and privacy remain protected. View our privacy policy before signing up.

Error: Please check your email address.

More about ISOSidestep

Show Comments