dido:public:ra:1.4_req:2_nonfunc:20_maintainability:testability
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
dido:public:ra:1.4_req:2_nonfunc:20_maintainability:testability [2021/08/13 11:29] murphy |
dido:public:ra:1.4_req:2_nonfunc:20_maintainability:testability [2021/10/03 13:23] (current) 50.19.247.197 ↷ Links adapted because of a move operation |
||
|---|---|---|---|
| Line 5: | Line 5: | ||
| [[dido:public:ra:1.4_req:2_nonfunc:20_maintainability:testability| Return to Top]] | [[dido:public:ra:1.4_req:2_nonfunc:20_maintainability:testability| Return to Top]] | ||
| - | //[[dido:public:ra:xapend:xapend.a_glossary:t:testability]]//, //Testable//, //Testing// and //Test// are not synonyms for each other. Just because a system or program is undergoing //testing// using various //tests// does not necessarily mean that the system or program is actually //Testable//. The following table provides definitions for each of these four terms, associates each with the appropriate Structured [[dido:public:ra:xapend:xapend.a_glossary:a:assurance|Assurance]] Case, as well as, level in the Cognitive Model's Science and Knowledge Management [[dido:public:ra:xapend:xapend.i_cog_model|DIKW]] (Data, Information, Knowledge and Wisdom) pyramid. | + | //[[dido:public:ra:xapend:xapend.a_glossary:t:testability]]//, //Testable//, //Testing// and //Test// are not synonyms for each other. Just because a system or program is undergoing //testing// using various //tests// does not necessarily mean that the system or program is actually //Testable//. The following table provides definitions for each of these four terms, associates each with the appropriate Structured [[dido:public:ra:xapend:xapend.a_glossary:a:assurance|Assurance]] Case, as well as, level in the Cognitive Model's Science and Knowledge Management [[dido:public:ra:xapend:xapend.i_cog_model:start|DIKW]] (Data, Information, Knowledge and Wisdom) pyramid. |
| ^ DIKW pyramid level ^ Structured Assurance Case ^ Term ^ Description ^ | ^ DIKW pyramid level ^ Structured Assurance Case ^ Term ^ Description ^ | ||
| Line 44: | Line 44: | ||
| * **Jigsaw puzzles:** Requirements distributed across a document and then cross-referenced | * **Jigsaw puzzles:** Requirements distributed across a document and then cross-referenced | ||
| * **Duckspeak:** Requirements included merely to conform to standards that have no or little relationship to the problem at hand. Perhaps required as part of a boilerplate. | * **Duckspeak:** Requirements included merely to conform to standards that have no or little relationship to the problem at hand. Perhaps required as part of a boilerplate. | ||
| - | * **Terminology invention:** “user input/presentation function”; “airplane reservation data validation function”. For example, | + | * **Terminology invention:** “user input/presentation function”; “airplane reservation data [[dido:public:ra:xapend:xapend.a_glossary:v:validation|validation]] function”. For example, |
| * The system shall use a double blind logged journal entry (huh, what is that?) | * The system shall use a double blind logged journal entry (huh, what is that?) | ||
| * **Putting the onus on developers and testers:** to guess what the requirements really are. | * **Putting the onus on developers and testers:** to guess what the requirements really are. | ||
dido/public/ra/1.4_req/2_nonfunc/20_maintainability/testability.1628868587.txt.gz · Last modified: 2021/08/13 11:29 by murphy
