[SystemSafety] Koopman replies to concerns over Toyota UA case

[Matthew Squair]

That’s exactly the point of using McCabe as a measure of ‘economy of
effort’ for critical code. If your critical code comes up high then you
know that you’ve got a problem to deal with in terms of verifying that
critical part. Assuming that you treat such code differently of course. So
McCabe (in principal) can be a metric (not the only one) for a key safety
principle.

On 30 December 2017 at 6:24:39 pm, paul_e.bennett at topmail.co.uk (
paul_e.bennett at topmail.co.uk) wrote:

> On 30/12/2017 at 7:33 PM, "Matthew Squair" <mattsquair at gmail.com> wrote:
>
>
> Hi Derek,
>
> I agree, relying purely on McCabes metric as evidence would be
> unwise, even
> for a forensic exercise.
>
>
> Specifying a McCabe Code Complexity limit for individual software
> components is, in my eyes, more of a trigger to begin asking the questions
> that need to be asked. If the development policy set the MCC at say 9,
> then
> any component submitted for review with a number above that should begin
> to get questions asked.
>
> I have a very nice graph which correlates the required effort in hours to
> do
> the test of a software component at various MCC's. Considering that each
> software component's review includes a full Fagan Inspection, a Functional
> Test and a Limitations Test, and that the higher the MCC value
> expenonetially
> more time is required to thoroughly review the component.
>
> However, some specifications could do with being measured with McCabe to
> guide reduction of the inherent complexity specified into a project in the
> first
> place.
>
>
> Regards
>
> Paul E. Bennett IEng MIET
> Systems Engineer
> Lunar Mission One Ambassador
> --
> ********************************************************************
> Paul E. Bennett IEng MIET.....
> Forth based HIDECS Consultancy.............
> Mob: +44 (0)7811-639972
> Tel: +44 (0)1392-426688
> Going Forth Safely ..... EBA. www.electric-boat-association.org.uk..
> ********************************************************************
>
> _______________________________________________
> The System Safety Mailing List
> systemsafety at TechFak.Uni-Bielefeld.DE
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.techfak.uni-bielefeld.de/mailman/private/systemsafety/attachments/20171230/63c0c0d7/attachment-0001.html>