[SystemSafety] Collected stopgap measures

[Steve Tockey]

How about this?

‹ cut here ‹

You make a reasonable estimate of what you think it should take in terms
of schedule, staffing, and cost based on your past experience with
mainstream development.

If you properly apply the engineering process (as described in the new
book) then your actual schedule and cost will almost certainly be about
half of your estimated schedule and cost given the same level of staffing.
We are highly confident in stating this because these are the results we
have already seen on projects.

‹ end cut here ‹


And, if you want, I can even give you an explanation of why cost and
schedule are being cut in half.




-----Original Message-----
From: Derek M Jones <derek at knosof.co.uk>
Organization: Knowledge Software, Ltd
Date: Friday, November 16, 2018 at 9:19 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,

> ³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).

Don't you mean: "Estimated to be 'cut in about half' based on
'a somewhat reasonable estimate of what it would take...'"

This time I am suggesting words you should be saying.


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