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;
9 Cards in this Set
- Front
- Back
|
Sequential Development Model |
This is a development model that describes the process to be a linear flow of activities. Each phase can only begin when the previous phase has been complete. |
|
|
Incremental Development Model |
Establishing requirements, designing, building and testing a system in pieces so that the software can grow incrementally. The size of each feature increment can vary in size. |
|
|
Iterative Development Model |
This is when groups of features are specified, designed, built and tested together in a series of cycles, often of a fixed duration. Iterations may involve changed to features developed in earlier iterations along with project scope. Such as Scrum. |
|
|
Component Testing |
Otherwise known as Unit/Program/Structure/Module/Code Testing. This searches for defects and verifies the functioning of software modules programs, objects, classes etc. Often used to test core functionality or specific non-functional behaviour such as resource behaviour. |
|
|
Use/User Cases |
These are common test basis across integration, system and acceptance testing. |
|
|
Risk Analysis Report |
Is a common test basis for system and acceptance testing. |
|
|
Confirmation Testing |
After a bug has been raised and fixed, confirmation Testing is carried out to ensure the bug is now fixed. |
|
|
Regression Testing |
This is often done after confirmation Testing. This is to ensure nothing else has broken when the fix was implemented. |
|
|
Maintenance Testing |
This is testing that follows after Modifications (planned enhancements), upgrades, patches for defects and vulnerability, migration, retirement. |
