Why software defects remain a challenge

We are all aware that finding defects early in the product lifecycle saves time, money and reputations. The cost of fixing a defect increases exponentially as the defect propagates, so one would think that there would be huge pressure on engineers to eliminate defects in software specifications and designs. And yet, a conventional approach to software development performs only subjective analysis of specifications and designs. Specifications and designs are not subject to formal verification or validation and therefore potentially represent a veritable hive of defects, waiting to sting engineers further down the line.

Model Driven Development

Conventional software engineering

Consequentially conventional software engineering has diminished the role of specification and design, instead emphasizing the importance of coding and testing. The unavoidable result is rework, late in the development lifecycle. Add back into the equation the exponentially rising cost of fixing a defect as it propagates and it is easy to see why conventional software development suffers from poor predictability, high costs, delays and questionable quality.

Of course, Agile methods, Test Driven Development and Continuous Testing have tightened the loop between coding and testing to an extent, resulting in better efficiency. But what if there was a way to verify and validate software specifications and designs?

Related: Reengineering legacy software with Dezyne

How Dezyne prevents defects

Dezyne enables engineers to write specifications that define the externally visible behaviour of software components, subsystems and systems. It provides the means to validate these specifications through the construction and replay of use/test cases in the Dezyne simulator. Specifications are also automatically formally verified for completeness and a range of correctness properties by Dezyne. The result is the elimination of a wide range of specification defects early in the development lifecycle.

During specification

By incorporating the Dezyne simulation and verification engines into a continuous integration and automated testing environment, specifications can be constantly “tested”, establishing that they remain complete and correct during the development lifecycle.

Model Driven Development

During design

Dezyne provides engineers with ability to design software components that implement the behaviour defined by their related specifications. Component designs and their specifications are validated through the construction and replay of use/test cases in the Dezyne simulator. Dezyne’s automatic, formal verification also establishes early in the development lifecycle that designs are behaviourally complete and correct for a range of properties.

Continuous integration and automated test of designs can be achieved by including the Dezyne simulation and verification engines in your build environment, establishing that invariant behaviour always remains present in design models and that they continue to be complete and correct.

During implementation

Dezyne automatically generates robust and reliable code from validated and verified models, reducing programming effort and the risk of defects creeping in during implementation. Ultimately Dezyne eliminates a wide range of specification and design defects early in the development lifecycle and earns you money by reducing conventional coding and testing effort and cutting out expensive rework.

Model Driven Development

Related: Using the power of Dezyne’s verification and validation features to build cyber resilient applications

Model Driven Software Case Study

Related Articles

Enjoy this article? Don't forget to share.
google-site-verification:google656c7703ab521151.html