Karteikarten
Validation and verification
Karten in diesem Stapel (12)
- 1Validation- Will the product satisfy the customer needs
- Are we building the right product - 2Verification- Do we satisfy the requirements
- Are we building the product right - 3Testing vs InspectionTesting: running a program
Inspection: reviewing a document - 4Inspection+ Apply to all documents -> no program needed
+ Quality perspective from the beginning
- Do not cover emergent properties -> most apply to verification
- Added cost early in the process - 5A test case consists of:Tests data, expected outcome, expected behavior
- 6Assessing testsDetecting as many defects as possible
Detecting the most damaging defects
Detecting the most likely defects - 7Black-box testingSource code is not considered (only requirements)
- 8Glass-box testingTests are chosen based on the source code
- all code should be tested at least once - 9Statement coverageEvery statement should be tested
- 10Branch coverageEvery choice/path must be tested
- 11Function coverageEvery function is called at least once
- 12Call coverageEvery function call is executed at least once
Informationen
- Beschreibung
- Information Technology Karteikarten am Validation and verification, erstellt von Johan Isaksson am 20/10/2018.
- Erstellt von
- Johan Isaksson
- Aufrufe
- 5
- Bewertung