Term
input,process, output (IPO) development |
|
Definition
a development order that implements input modules first process modules next and output modules last |
|
|
Term
|
Definition
a development order that implements modules at teh top of a structure chart first |
|
|
Term
|
Definition
a development order that implements modules at teh bottom of a structure chart first |
|
|
Term
|
Definition
a team with members of roughly equal skill and experience and iwth overlapping areas of specialization |
|
|
Term
|
Definition
a team with a single leader who makes all important decisions |
|
|
Term
collaborative specialist team |
|
Definition
a team with members who have wide variation in and minimal overlap skills and experience |
|
|
Term
source code control system (SCCS) |
|
Definition
an automated tool for tacking source code files and controlling changes to those files |
|
|
Term
|
Definition
a system that is incomplete but ready for some level of rigorous testing |
|
|
Term
|
Definition
a system that is stable enough to be test by end users |
|
|
Term
production version, release version or production release |
|
Definition
a system that is formal distributed to users or made opaerational |
|
|
Term
|
Definition
a system update that provides minor bug fixes and minor changes to existing features |
|
|
Term
|
Definition
the process of ensuring that an information system meets minimal quality standards |
|
|
Term
|
Definition
a formal or informal review of design or construction details by a group of developers |
|
|
Term
|
Definition
a formal review of design or construction details by a group of developers, where each person plays a specific role |
|
|
Term
unit testing or module testing |
|
Definition
testing individual code modules or methods before they are integrated with other modules |
|
|
Term
|
Definition
a module developed for unit testing that simulates the calling behavior of a module that hasn't yet been developed |
|
|
Term
|
Definition
a module developed for testing that simulates execution of behavior of a module that hasn't yet been developed |
|
|
Term
|
Definition
a test of the behavior o a group of modules or methodes |
|
|
Term
|
Definition
a test of behavior of an entire system or independent subsystem |
|
|
Term
|
Definition
a system test that is performed daily |
|
|
Term
|
Definition
a test to determine whether a module method class subsystem of system meets user requirements |
|
|
Term
|
Definition
a system test that determines whether a system can meet time based performance criteria |
|
|
Term
|
Definition
the desired or maximum allowable time limit for software response to a query or update |
|
|
Term
|
Definition
the desired or minimum number of queries and transactions that must be processed per minute or hour |
|
|
Term
|
Definition
a system test that determines whether the system fulfills user requirements |
|
|
Term
|
Definition
a programmer assigned to test code written by another programmer |
|
|
Term
direct installation or immediate cutover |
|
Definition
an installation method that installs a new system quickly makes it operational and immediately turns of any overalapping systems |
|
|
Term
|
Definition
an installation method that operates both the old and new systems for an extended time period |
|
|
Term
|
Definition
an installation method that installs a new system and makes it operational in a series of steps of phases |
|
|
Term
|
Definition
descriptions of system functions, architecture, and construction details, as used by maintenance personnel and future developers |
|
|
Term
|
Definition
descriptions of how to interact with and maintain the system, as used by end users and system operators |
|
|
Term
|
Definition
modification of a software product after delivery to correct faults improve performance or other attributes or adapt the product to a changed environment |
|
|
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 |
|
|