[trustable-software] Exploring the "Hypothesis for software to be trustable"
Andrew Banks
andrew at andrewbanks.com
Tue Jan 23 13:56:10 GMT 2018
Generally, I like this - but I'd like to debate your Specifications bit:
Specifications state:
- the problem
- the expected solution
- how to verify the solution
How about:
Specifications state the WHAT:
- the requirements that need to be met
Plans will state the HOW:
- the HOW it will be DONE = the design plan
- the HOW it will be VERIFIED = the verification (test?) plan
- the HOW it will be MANAGED = the management plan
- etc
A
More information about the trustable-software
mailing list