Testing is a crucial part of any software development project, regardless of the industry, preferred methodology or how much you trust your development team. After all we all make mistakes. It is part of what makes us human. When it comes to software leaving a mistake unchecked, especially in terms of safety critical systems, can result in a disastrous outcome.

Of course the identification and removal of bugs is undoubtedly important, but is it the only reason to test software? Certainly not. There is so much more to testing than bug elimination. Just take a look at these top alternative benefits.

Assess If The Stated Requirements Were Met

Testing The Requirements

Behind every system there should be a set of requirements, defining what the system is supposed to do and how it is supposed to behave. Ideally outlined at the start of a development, these requirements should act as a roadmap against which software should be developed and tested.

When it comes to writing code it is all too easy to become tunnel visioned. Focusing on a small collection of tasks and forgetting the system as a whole. By testing against the requirements you ensure that every expected function has been addressed.

Provide Validation That The Solution Meets The Need Of The User

In an ideal world requirements would be crystal clear, outline every desire of the client and never require a single alteration. Unfortunately, this is very rarely the case. User desires, and as a result requirements, have a tendency to grow and change over the course of a development. Therefore, even software that is developed to every single one of the original requirements may in fact, no longer meet the need of the user.

By getting the end user to interact with the software you can quickly find out if the system works as expected, or if there are requirements that have been overlooked or miscommunicated. In having this feedback you can rest assured that you have developed a suitable solution.

Testing Against The Needs Of The End User

Provide Evidence Of Compliance To Safety Standards

Look Closer at Your Testing

When developing safety critical systems, you will need need to be compliant with the relevant safety standards for your industry. E.g. BS EN 50128 for rail, DO-178B for airborne systems.

In order to prove compliance to these standards you need evidence that your software runs both reliably and in accordance to the defined requirements, especially those related to safety. By testing your software, which, in the case of compliance to safety standards should be carried out independently, you can quickly acquire the evidence you need.

In addition to proving that your software system will run reliably, safety standards require evidence that if your system were to fail that it would do so in a safe way.

Allow For Interoperability

It is very unusual for a software system to be truly independent, without any need to interact with other systems or components. So whilst it is important to ensure that your solution runs correctly in its own right, some consideration needs to be given to how successfully it interacts with other systems.

For example, when making a ballpoint pen, each individual part, such as the cap, body and button mechanism, will all be produced and tested separately. When each of these parts have been produced they will be assembled and tested to see if they work together in the correct manner. After all, just because the process to make the cap has been followed to the letter and it has passed all of its individual test, it does not guarantee that it will fit onto the body.

Testing Allows For Interoperability

Ensure Minor Changes Don’t Impact The System As A Whole

Testing Change Helps Avoid System Failure

Software requirements will change over time. Unfortunately, this is an unavoidable truth. Some changes may make themselves known during the original development period, whilst others may take several years to appear.

By making modifications to any pre existing software system, you run the risk of introducing new bugs, and in some cases reintroducing previously resolved bugs. Increasing the chances for working components to fail. However, re-running original test cases, alongside the new, will help to ensure that in making these alterations you don’t break the original system.

Contact Zircon

Address: Telephone: Key Contacts:
Bellefield House
Hilperton Road
BA14 7FP
Tel: 01225 76 44 44
Fax: 01225 75 30 87
Sales & Marketing Director: Phil Cooper
Business Development Manager: Arron Dando