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;
30 Cards in this Set
- Front
- Back
|
component
|
a software module that is fully assembled, is ready to use, and has well-defined interfaces for connection to clients or other parts of the system
|
|
|
test case
|
a formal description of a starting state, one or more events to which the software must respond, and the expected response or ending state
|
|
|
test data
|
a set of starting states and events used to test a module, group of modules, or entire system
|
|
|
unit testing
|
testing of individual methods, classes, or components before they are integrated with other software
|
|
|
driver
|
a method or class, developed for unit testing, that simulates the behavior of a method that sends a message to the method being testing
|
|
|
stub
|
a method or class, deveoped for unit testing, that stimulates the behavior of a method that hasn't yet been written
|
|
|
integration test
|
a test of the behavior of a group of methods or classes
|
|
|
system test
|
an integration test of the behavior of an entire system or independent subsystem
|
|
|
build and smoke test
|
a system test that is performed daily or several times a week
|
|
|
usability test
|
a test to determine whether a method, class, subsystem, or system meets user requirements
|
|
|
performance test
|
an integration and usability test that determines whether a system or subsystem can meet time-based performance criteria
|
|
|
response time
|
the desired or maximum allowable time limit for software response to a query or update
|
|
|
throughput
|
the desired or minimum number of queries and transactions that must be processed per minute or hour
|
|
|
user acceptance test
|
a system test performed to determine whether the system fulfills user requirements
|
|
|
coding buddy
|
a programmer assigned to test code written by another programmer
|
|
|
alpha version
|
a test version that is incomplete but ready for some level of rigorous integration or usability testing
|
|
|
beta version
|
a test version that is stable enough to be tested by end users over an extended period
|
|
|
production version, release version, or production release
|
a system version that is formally distributed to users or made operational for long-term use
|
|
|
maintenance release
|
a system update that provides bug fixes and small changes to existing features
|
|
|
production system
|
the version of the system used from day to day
|
|
|
test system
|
a copy of the production system that is modified to test changes
|
|
|
input, process, output (IPO) development
|
a development order that implements input modules first, process modules next, and output modules last
|
|
|
top-down development
|
a development order that implements top-level modules first
|
|
|
bottom-up development
|
a development order that implements low-level detailed modules first
|
|
|
cooperating peer team
|
a team with members of roughly equal skill and experience with overlapping areas of specialization
|
|
|
chief developer team
|
a team with a single leader who makes all important decisions
|
|
|
collaborative specialist team
|
a team with members who have wide variation in and minimal overlap of skills and experience
|
|
|
source code control system (SCCS)
|
an automated tool for tracking source code files and controlling changes to those files
|
|
|
direct deployment or immediate cutover
|
a deployment method that installs a new system, quickly makes it operational, and immediately turns off any overlapping systems
|
|
|
parallel deployment
|
a deployment method that operates both the old and new systems for an extended time period
|
