Print Friendly, PDF & Email

Introduction to Software Used in Spectrum Management

Besides the potential for injury, the total cost of poor software quality in the U.S. is estimated at $2.08 trillion.

Because software safety is a concept which is only meaningful within a system context, it follows that software safety requirements must be obtained from information about hazards of the wider system.

Consequently, any restriction on information pertaining to these hazards can lead to ambiguous or conflicting software safety requirements.

Needless to say, software safety is extremely important in all sectors, including the Department of Defense. The degree of importance is illustrated in the last revision of Military Standard (MIL-STD) 882E, which added software systems safety techniques and practices.

TheSof during an Urgent Materiel Release (UMR) of PDB-8 and identified firmware as the next target for improvement.

Additionally, as part of development of PDB-8.1 a software and hardware component was changed resulting in a significant reduction in Safety Critical Requirements (SCR) as shown by a reduction in Software Hardware Risk Indexes (SHRI) 1 through 4.

Unlike hardware, software is only susceptible to errors introduced during their design (systematic failures), evolution and maintenance.

Software operational safety is a useful tool for ensuring that the safest possible decisions are made, and allows you to consider the demands of reliability (systems failure resistance, recovery); maintainability (ease of modification, testability); availability (returns on performance, efficiency); and safety (functional capacity) of your software.

Software safety comprises one part of the risk management system from which it inherits its safety objectives. Software Reliability activities tap into a software quality approach.

The different tools of Software safety include:

● Functional Analysis (FA), Preliminary Hazard Analysis (PHA), Preliminary Risk Analysis (PRA)
● Root Cause Analysis (RCA), Software Failure Modes and Effects Analysis (FMEA)
● Analysis of the Effects of Software Defects (AESD) at the functional or code level
● Critical code review

Want to learn more? Tonex offers Software Safety Training, a 3-day course that covers all aspects of Software Safety focusing on philosophies and methods in software safety and its primary objectives.

Additionally, Tonex offers several more courses in Software Safety including:

Software Safety Course for Managers (2 days)

Software Safety Programming and Software Coding Standards (2 days)

Software Safety Training Workshop (2 days)

Software Safety, Hazards Analysis and Risk Management Training Workshop (3 days)

Software System Safety Engineering Training (3 days)

For more information, questions, comments, contact us.


Request More Information

  • Please complete the following form and a Tonex Training Specialist will contact you as soon as is possible.

    * Indicates required fields

  • This field is for validation purposes and should be left unchanged.