Term
|
Definition
| A formal description of a starting state one or more events to which the software must respond and the expected response or ending state |
|
|
Term
|
Definition
| a set of starting states and events used to test a module group of module or entire system |
|
|
Term
|
Definition
| of an individual method class or component before it is integrated with other software |
|
|
Term
|
Definition
| a method or class developed for unit testing that simulate the behavoir of a method that sends a message to the method being tested |
|
|
Term
|
Definition
| a method or class developed for unit testing that simulate the behavior of a method that hasnt yet been written |
|
|
Term
|
Definition
| test of the behavior of a group of methods classes or components |
|
|
Term
|
Definition
| a test to determine whether a method class subsystem or system meets user requirements |
|
|
Term
|
Definition
| an integration test of an entire system or independent subsystem |
|
|
Term
|
Definition
| a system test that is performed daily or several times a week |
|
|
Term
| performance test or stress test |
|
Definition
| a integration and usability test that determines whether a system or subsystem can meet time based performance criteria |
|
|
Term
|
Definition
| the desired or maximum allowable time limit for software response to a query r update |
|
|
Term
|
Definition
| the desired or munimum number of quiries and transactions that must be processed per minute or hour |
|
|
Term
|
Definition
| A system test performed to determined whether the system fulfills user requirements |
|
|
Term
|
Definition
| descriptions of system requirements architecture, and construction details as used by maintenance personnel and future developers |
|
|
Term
|
Definition
| description of how to interact with and use the system as used by end users and system operators |
|
|
Term
| IPO Input, process output development order |
|
Definition
| development order that implements inputs modules first process modules next and output modules last |
|
|
Term
|
Definition
| a development order that implements top level first |
|
|
Term
|
Definition
| a development order that implementation low level detailed modules first |
|
|
Term
| Source code control system (SCCS) |
|
Definition
| an automated tool for tracking source code files and controlling changes to those files |
|
|
Term
| Direct deployment or immediate cutover |
|
Definition
| A deployment method that installs a new system, quickly makes it operational and immediately turns off any overlapping systems |
|
|
Term
|
Definition
| a deployment method that operates the old and the new systems for an extended time period |
|
|
Term
|
Definition
| a deployment method that installs a new system and makes it operational in a series of steps or phases |
|
|
Term
|
Definition
| a test version that is incomplete but ready for some level of rigorous integration or usability testing |
|
|
Term
|
Definition
| a test version that is stable enough to be tested by end users over extended period of time |
|
|
Term
| Production release, release version, or production release |
|
Definition
| a system version that is formally distributed to users or made operational for long term use |
|
|
Term
|
Definition
| a system update that provides bug fixes and small changes to existing features |
|
|
Term
|
Definition
| the version of the system used from day to day |
|
|
Term
|
Definition
| a copy of the production system that is modified to test changes |
|
|
