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;
30 Cards in this Set
- Front
- Back
|
Define CRUD Technique... |
CRUD is a table that show the links between processes and data. Create Read Update Delete |
|
|
What are some validation techniques... |
-Reviews - Walkthroughs - Formal Inspection - Focused Inspection - Active Inspection - Checklists -Testing -Prototyping -Formal validation |
|
|
We are currently on the testing validation techniques. There are two kinds of testing that affect requirements engineering what are they? |
- There are two kinds of testing that affect requirements engineering:
1. Testing the requirements themselves (aka. validation)
2. Planning for the testing of the implementation against requirements (aka verification)
|
|
|
What is the deference between quantifiable & non-quantifiable requirements? |
Quantifiable Requirements -The system must respond quickly to customer enquiries - It is a scale for measurement within the context (e.g. min) Non-Quantifiable Requirements -The automated interfaces of the system must be easy to learn/user |
|
|
What is Testing Requirements |
-Running an executable specification and checking certain scenarios -The boundary between testing a specification and demonstrating a prototype for customer feedback is difficult to define. |
|
|
What is BEST when testing requirements? |
When the tests being performed are not done by they author of specification. |
|
|
What are the advantages of requirements testing? |
-Low-level details checking is usually done more reliable when done by tools -Requirements testing can be done earlier in the development lifecycle than most other testing |
|
|
What are the disadvantages of requirements testing? |
- Most notations for requirements specifications are not executable or checkable - It is labour intensive - No clear stopping rule (when would you know to stop testing, presence of errors but not their absence.) |
|
|
What is acceptance testing? |
The requirements specification that describes how to ascertain if the final product satisfies the requirements.
|
|
|
What should be included in an acceptance test? |
a complete test plan - an extensive collection of test cases, where each test case specify the expected response of the system |
|
|
For large systems what document is should be separated? |
Test Plan |
|
|
In test case planning there are two basic kinds of test cases what are they? |
1. Black Box 2. White Box |
|
|
What is black box testing? |
Test cases where that are generated from the specification. - Test what the system is supposed to do according to the specification or interface, treating the implementation (at the system level) as a black box. |
|
|
What is white box testing? |
Test cases that are generated from code / implementation. - Design ==structure, so this is testing of the representation of the system, rather than the idea of the system (the specification) - Metaphorically, structural testing is about looking for likely weak spots in the structure, ignoring the black box semantics. |
|
|
From the requirements stage, what kind of testing can be considered? |
Only black box, generated from the requirements. |
|
|
When we are testing code what tests do we start with? |
Unit Tests |
|
|
At what level are unit tests on? |
at the level of a class/module/file depending on the language |
|
|
What are unit tests? |
a software development process in which the smallest testable parts of an application, called units, are individually and independently tested for proper operation. |
|
|
What specific tests should we include in unit testing? |
Black box and white box |
|
|
What is a good black box tests design in unit testing? |
Good black box are designed against the externally visible interfaces of the unit. ie. for each method think of ways of testing it using only your knowledge of what it is supposed to do, not how it is implemented. |
|
|
What is a good white box test design in unit testing? |
The white box tests are designed against ways in which the code is written. For example: try to test all paths through a method/exercise all conditions in statements and loops, boundary values...etc |
|
|
Integration Testing is... |
Gradually combining the units into logical subsystems and then testing it (black box tests and white box tests on the whole subsystem) |
|
|
System Testing is... |
-Black box testing on the system as a whole. -White box testing designed around our understanding of the system structure. -integration testing at the top level |
|
|
Testing Granularity is when the... |
System-level cases are based on what the system can do, not what the customer expects. |
|
|
Another Validation technique is... |
Prototyping |
|
|
What is the purpose of prototyping? |
To obtain a credible validation response. |
|
|
What are ways to prototype? |
Mock-ups, interfaces, Screens and Prototypes |
|
|
What is the last Validation Technique discussed in this course? |
Formal Validation |
|
|
How would you check if a formal specification has a desirable property? |
1. Completeness 2. Consistency 3. Mutual exclusion 4. Particular temporal properties |
|
|
What are some techniques of formal validation? |
- Model Checking - Theorem proving - Formal verification involves checking all possible execution paths of the specification |
