[SystemSafety] Collected stopgap measures

[Steve Tockey]

“What was the percentage difference in costs and development time?”

As I said, development time was cut in about half and development cost
also cut in about half (because project staffing was the same as if were
going to be done the mainstream way).

E.g., an estimated 14 month project was done with the same staffing as
would have been used for the mainstream equivalent but delivery happened
in 7 months.

E.g., an estimated 30 month project was done with the same staffing as
would have been used for the mainstream equivalent but the delivery
happened in 15 months.

In one specific case, the original system had been built using an
engineering approach. 15 years later, a critical component of the software
had to be re-done because of a change to the external system I interfaced
with. The organization allocated 4 people and estimated one year for the
re-write. The re-write was actually accomplished in 6 weeks.


― steve



-----Original Message-----
From: Derek M Jones <derek at knosof.co.uk>
Organization: Knowledge Software, Ltd
Date: Friday, November 16, 2018 at 8:58 AM
To: Steve Tockey <Steve.Tockey at construx.com>
Cc: "systemsafety at lists.techfak.uni-bielefeld.de"
<systemsafety at lists.techfak.uni-bielefeld.de>
Subject: Re: [SystemSafety] Collected stopgap measures

Steve,
> I am comparing the actual results of using an engineering approach to
> (successfully) building a system to a somewhat reasonable estimate of
>what
> it would take to (successfully) build that same system using the
> mainstream approach. Their estimate is based on that organization¹s
>actual
> experience of having (successfully) delivered using the mainstream
> approach.

What was the percentage difference in costs and development time?

-- 
Derek M. Jones           Software analysis
tel: +44 (0)1252 520667  blog:shape-of-code.coding-guidelines.com