Reading...
Play button
Play button
Use LEFT and RIGHT arrow keys to navigate between flashcards;
Use UP and DOWN arrow keys to flip the card;
H to show hint;
A reads text to speech;
18 Cards in this Set
- Front
- Back
|
Dynamic Testing
|
Testing that involves the execution of the software of a component or system.
|
|
|
Static Testing
|
Testing of a software development artifact, e.g., requirements, design or code, without execution of these artifacts, e.g., reviews or static analysis.
|
|
|
Entry Criteria
|
The set of generic and specific conditions for permitting a process to go forward with a defined task, e.g. test phase. The purpose is to prevent a task from starting which would entail more (wasted) effort compared to the effort needed to remove the failed entry criteria.
|
|
|
Formal Review
|
A review characterized by documented procedures and requirements, e.g. inspection.
|
|
|
Informal Review
|
A review not based on a formal (documented) procedure.
|
|
|
Inspection
|
A type of peer review that relies on visual examination of documents to detect defects, e.g. violations of development standards and non-conformance to higher level documentation. The most formal review technique and therefore always based on a documented procedure.
|
|
|
Metric
|
A measurement scale and the method used for measurement.
|
|
|
Moderator
|
The leader and main person responsible for an inspection or other review process.
|
|
|
Peer Review
|
A review of a software work product by colleagues of the producer of the product for the purpose of identifying defects and improvements. Examples are inspection, technical review and walkthrough.
|
|
|
Reviewer
|
The person involved in the review that identifies and describes anomalies in the product or project under review. The person can be chosen to represent different viewpoints and roles in the review process.
|
|
|
Scribe
|
The person who records each defect mentioned and any suggestions for process improvement during a review meeting, on a logging form. The person should ensure that the logging form is readable and understandable.
|
|
|
Technical Review
|
A peer group discussion activity that focuses on achieving consensus on the technical approach to be taken.
|
|
|
Walkthrough
|
A step-by-step presentation by the author of a document in order to gather information and to establish a common understanding of its content.
|
|
|
Compiler
|
A software tool that translates programs expressed in a high order language into their machine language equivalents.
|
|
|
Complexity
|
The degree to which a component or system has a design and/or internal structure that is difficult to understand, maintain and verify.
|
|
|
Control Flow
|
A sequence of events (paths) in the execution through a component or system.
|
|
|
Data Flow
|
An abstract representation of the sequence and possible changes of the state of data objects, where the state of an object is any of: creation, usage, or destruction.
|
|
|
Static Analysis
|
Analysis of software development artifacts, e.g. requirements or code, carried out without execution of these software development artifacts. It is usually carried out by means of a supporting tool.
|
