Re: [SystemSafety] Modelling and coding guidelines: "Unambiguous Graphical Representation"

From: Coq, Thierry < >
Date: Tue, 1 Mar 2016 15:50:34 +0000


Hi,
I would suggest state-of-the-art hard-realtime software should be build using source weavers using hierarchical synchronous active objects (combining state machines and algorithmic code) in models. These models should be verified both automatically and by humans.

If humans still write some part of the sources, then these sources should also be inspected, but the most efficient approach today is a combination of automatic inspection with human drill-down once the automation has flagged the more defect-prone pieces of software. Evidence shows the defects are not distributed equally. Today, there are methods such as SQALE and its variant for automation software to assess source quality automatically and even calculate some form of technical debt.

Like other people have mentioned, processes like these will only remove part of the errors in the software, there will be defects in the requirements (or in the absence of requirements in these modern times), or in the manuals or in the implicit assumptions nobody can ever capture entirely. Still, the results are usually worth the efforts.

Thierry Coq
www.dnvgl.com

-----Original Message-----
From: systemsafety [mailto:systemsafety-bounces_at_xxxxxx Sent: 01 March 2016 15:51
To: systemsafety_at_xxxxxx Subject: Re: [SystemSafety] Modelling and coding guidelines: "Unambiguous Graphical Representation"

Paul,

> Bad code is code which does not conform to the standards you

We need to stop calling code good, bad or indifferent.

A certain amount of resources is invested in finding problems in code. Finding problems in the code does not make it bad, if you had invested less the problems might not have been found. Finding no problems does not make the code good because a greater investment might find problems.

--
Derek M. Jones           Software analysis
tel: +44 (0)1252 520667  blog:shape-of-code.coding-guidelines.com
_______________________________________________
The System Safety Mailing List
systemsafety_at_xxxxxx

**************************************************************************************
This e-mail and any attachments thereto may contain confidential information and/or information protected by intellectual property rights for the exclusive attention of the intended addressees named above. If you have received this transmission in error, please immediately notify the sender by return e-mail and delete this message and its attachments. Unauthorized use, copying or further full or partial distribution of this e-mail or its contents is prohibited.
**************************************************************************************
_______________________________________________
The System Safety Mailing List
systemsafety_at_xxxxxx
Received on Tue Mar 01 2016 - 16:50:51 CET

This archive was generated by hypermail 2.3.0 : Tue Apr 23 2019 - 01:17:08 CEST