Software Engineering

The Death of the V-Model
We think the V-Model has had it's day. Find out why here.

Our approach to software engineering focusses on these key points:

All software evolves, so control the evolutionary process.
Harmonise and synchronise design, development and testing.
Ingrain quality, from the bottom up, finding and fixing bugs early.
Iterate frequently, deliver often.

This approach is reinforced through the use of a few standards:-

MISRA C
Misra C, a subset of the C programming language, was created by the automotive industry in an attempt to limit the coding horrors that are allowable within the language. It has since been described as a “shack built on a swamp”! Alarming though this analogy is, it is wise to understand the pitfalls of the C language, and it is also wise to implement procedures to prevent stumbling into these pitfalls. Thus, we welcome the latest release of the MISRA C:2004 specification, and continue to work within its boundaries to produce embedded software for safety critical systems upto and including SIL3.

DEF-STAN 00-55
"Requirements for Safety Related Software In Defence Equipment"
Defines the procedures and mechanisms that the MOD requires all safety releated software to be produced to. It includes requirements for formal design methods, documentation, Verification Validation & Test and defines Safety Integrity Levels (SIL). All software subcontracted out by the MOD must meet these specifications.