[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [tsf-dev] TSF process feedback, part 2: evaluating statements
|
On 2026-05-01 08:45, Paul Sherwood wrote:
On 2026-04-22 20:39, Derek M Jones via tsf-dev wrote:
For individual statements, it can be nice for an expert to record how
close we are to achieving some goal, by putting e.g. 0.5 against the
statement to show that we're halfway there.
Given that 33% of estimates are within a factor of two,
and 95% within a factor of 4
https://shape-of-code.com/2024/03/10/what-is-known-about-software-effort-estimation-in-2024/
does any claim of being half-way there mean anything?
I think it does mean something, i.e. the SME believes we've started,
we're not finished, and apparently thinks we still have approximately
as much to do as we've already done.
However, checking the TSF documentation [1] I don't think we've got to
the bottom of probabilities/confidence vs/and progress.
For a claim/statement "Foo is tested", supported by evidence from 100
tests of which 50 are passing, SME could conceivably score
- 100% (there are some passing tests, therefore Foo is tested)
- 50% (half of the tests fail, so Foo is only half-tested)
- <50% (SME believes the 100 tests are insufficient)
[1]
https://pages.eclipse.dev/eclipse/tsf/tsf/model/scoring/implementation.html#calculating-scores-for-all-items
