No Software Hindenburgs

Curtis Franklin Jr., Executive Editor | 2/14/2013 | 3 comments

Curtis Franklin Jr.
OEMs are accustomed to operating to standards in hardware. While software standards are less common, they might be even more useful for improving product quality.

If your company builds equipment for either aviation or industrial use, then you're already aware of two of the most significant software standards. DO-178B is the standard for software used in avionics. OEMs working to build equipment for the manufacturing sector are more likely to be familiar with IEC 61508, the most significant standard for assuring operational safety in industrial control applications. This standard has, in fact, been used as the model on which standards for specific industries like the automotive, medical, railway, nuclear, and process industries have been based. All of these are based on a stacking model that can be useful whether you're required to conform to one of these standards or not.

Safety Integrity Levels define, in their most basic forms, what happens if something goes wrong with the software. Think of the ISO/OSI network stack for consequences and you have a picture of SILs. A typical list of SILs might look like this:

  • Level 1: Catastrophic -- If the software doesn't work, life as we know it will end.
  • Level 2: Hazardous -- If the software doesn't work, it will make the national news.
  • Level 3: Major -- If the software doesn't work, you'll hear about it from your CEO.
  • Level 4: Minor -- If the software doesn't work, you'll hear about it from your boss.
  • Level 5: No effect -- If your software doesn't work, it will be a dark secret that nags at your professional sensibilities.

The reason you establish these levels is that they help guide the effort that goes into debugging and quality testing the software in question. Obviously, the testing for Level 1 software should be far more rigorous than that for Level 5, and the organization's tolerance for errors much lower. The difficult first step is to accurately assess which pieces of software, which subroutines, and which library components fall onto which levels. Once that is done, a formal process of development, debugging, and quality control can be applied.

Safety Integrity Levels are a good example of concepts from one vertical market that can be applied to many others. The same principle could easily apply to financial services software, security applications, or courseware. Defining risk, defining response, and following through are steps that can be taken in essentially any development practice.

Are you using a discipline like this in your software development? Could you? We'd like to hear what you think about taking this OEM lesson and applying it to your enterprise. Let us know in the comments, below.

Related posts:

View Comments: Newest First | Oldest First | Threaded View
batye   No Software Hindenburgs   3/3/2013 10:19:22 PM
Re: secure development
could not agree more... with Curtis and Sara this days you must write any code with security idea in mind - no if or but's... security is a must... and only this way at least gives fighting chance... so to say...
Sara Peters   No Software Hindenburgs   2/20/2013 4:37:54 PM
secure development
Good stuff Curt. This sounds like another thing to add to "secure development" efforts. If a company has recognized that they need to write code that is secure to begin with -- hopefully free of a zillion SQL injection vulnerabilities -- then it should also recognize that each application has different levels of criticality. Seems like it should be a factor in your software quality assurance process.
singlemud   No Software Hindenburgs   2/18/2013 7:15:05 PM
What is the best practice?
I did not do this practice before, it looks pretty interesting. What is the best practice to apply the principle?


The blogs and comments posted on EnterpriseEfficiency.com do not reflect the views of TechWeb, EnterpriseEfficiency.com, or its sponsors. EnterpriseEfficiency.com, TechWeb, and its sponsors do not assume responsibility for any comments, claims, or opinions made by authors and bloggers. They are no substitute for your own research and should not be relied upon for trading or any other purpose.

More Blogs from Curtis Franklin Jr.
Curtis Franklin Jr.   4/18/2014   15 comments
When a difficult problem rears its head, modern business has a reliable response: Start a contest.
Curtis Franklin Jr.   4/11/2014   18 comments
In 1960, Carroll Shelby was told he had two years to live. He spent the next 50 years making the most of that two-year sentence.
Curtis Franklin Jr.   4/8/2014   16 comments
Speed. It's what every user and every enterprise wants from IT. And it's what we're talking about this week on E2 Radio.
Curtis Franklin Jr.   3/28/2014   25 comments
It took Microsoft CEO Satya Nadella about two months to put his mark on the company. And his first mark could completely change enterprise IT.
Curtis Franklin Jr.   3/27/2014   2 comments
Interop 2014 takes place in Las Vegas March 31 through April 4, and Enterprise Efficiency will be there to bring all the excitement to our community members who can't make it to the annual ...
E2 IT Migration Zones
IT Migration Zone - UK
Why PowerShell Is Important
Reduce the Windows 8 Footprint for VDI
Rethinking Storage Management
IT Migration Zone - FR
SQL Server : 240 To de mémoire flash pour votre data warehouse
Quand Office vient booster les revenus Cloud et Android de Microsoft
Windows Phone : Nokia veut davantage d'applications (et les utilisateurs aussi)
IT Migration Zone - DE
Cloud Computing: Warum Unternehmen trotz NSA auf die „private“ Wolke setzen sollten
Cloud Computing bleibt Wachstumsmarkt – Windows Azure ist Vorreiter
Like Us on Facebook
Twitter Feed
Enterprise Efficiency Twitter Feed
Site Moderators Wanted
Enterprise Efficiency is looking for engaged readers to moderate the message boards on this site. Engage in high-IQ conversations with IT industry leaders; earn kudos and perks. Interested? E-mail:
moderators@enterpriseefficiency.com
SPONSORED BY DELL
A Video Case Study – Translational Genomics Research Institute
e2 OEM Video


On the Case
TGen IT: Where We're Going Next

7|11|12   |   08:12   |   10 comments


Now that TGen has broken new ground in genomic research by using Dell's storage, cloud, and high-performance computing solutions, the company discusses what will come next for it and for personalized medicine.
On the Case
Better Care Through Better Communications

6|6|12   |   02:24   |   12 comments


The achievements of the TGen/Dell project could improve how all people receive healthcare, because they are creating ways to improve end-to-end communication of medical data.
On the Case
TGen IT: Where We Are Now

5|15|12   |   06:58   |   5 comments


TGen is breaking new ground in genomic research by using Dell's storage, cloud, and high-performance computing solutions.
On the Case
TGen IT: Where We Were

4|27|12   |   06:45   |   10 comments


The Translational Genomics Research Institute wanted to save lives, but its efforts were hobbled by immense computing challenges related to collecting, processing, sharing, and storing enormous amounts of data.
On the Case
1,200% Faster

4|18|12   |   02:27   |   12 comments


Through their partnership, Dell and TGen have increased the speed of TGen’s medical research by 1,200 percent.
On the Case
IT May Improve Children's Chances of Survival

4|17|12   |   02:12   |   8 comments


IT is helping medical researchers reach breakthroughs in a way and pace never seen before.
On the Case
Medical Advances in the Cloud

4|10|12   |   1:25   |   5 comments


TGen and Dell are pushing the boundaries of computing, and harnessing the power of the cloud to improve healthcare.
On the Case
TGen: Living the Mission

4|9|12   |   2:25   |   3 comments


TGen's CIO puts the organizational mission at the heart of everything the IT staff does.
On the Case
TGen Speeding Up Biomedical Research to Save More Lives

4|5|12   |   1:59   |   8 comments


The Translational Genomics Research Institute is revamping its computing to improve speed, storage, and collaboration – and, most importantly, to save lives.
On the Case
Computing Power Helping to Save Children's Lives

3|28|12   |   2:13   |   3 comments


The Translational Genomics Institute’s partnership with Dell is enabling them to treat kids with neuroblastoma more quickly and save more lives.
Curtis Franklin Jr.
OEMs Change Roles

1|18|13   |   1:55   |   3 comments


OEMs can change markets – here's why IT should have a say in the decision.
Tom Nolle
The Enterprise Side of Amazon Fire

9|29|11   |   2:04   |   6 comments


Amazon Fire’s split-browser model hosts some of the GUI in the cloud, which could have a major impact on virtual desktop thinking.
Curtis Franklin Jr.
The OEM Relationship

9|13|11   |   02:02   |   1 comment


The growth of OEM relationships means that enterprise IT execs must pay closer attention to who's responsible for support and development.
Pablo Valerio
Can't Land on the Runway Behind You

8|15|11   |   1:36   |   1 comment


One lesson from aviation also applies to big IT projects: Give yourself plenty of leeway and have room to maneuver.
Ivan Schneider
Flecksequence Explained

7|28|11   |   2:46   |   3 comments


How to use the term in a sentence and, more importantly, how flecksequence can help manufacturers.
Sara Peters
E2 Has a New Look!

7|20|11   |   2:53   |   6 comments


E2's gotten a makeover. Take a tour through some of our new features.