Term
| Implementation activities |
|
Definition
1. Program the software
2. Unit test the software
3. Identify and build test cases
4. Integrate and test components |
|
|
Term
|
Definition
1. Perform system and stress tests
2. Perform user acceptance tests
3. Convert existing data
4. Build training materials and conduct training
5. Configure and set up production environment
6. Deploy the solution |
|
|
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 modules or entire system |
|
|
Term
|
Definition
| test 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 simulates the behavior of a method that sends a message to the method being tested |
|
|
Term
| Functions a driver module implements: |
|
Definition
1. Sets the value of input parameters
2. Calls the tested unit, passing it the input parameters
3. Accepts return parameters from the tested unit and prints them, displays them or tests their values against expected results and then prints or displays the results |
|
|
Term
|
Definition
| a method or class developed for unit testing that simulates the behavior of a method that hasn't yet been written |
|
|
Term
|
Definition
| test of the behavior of a group of methods, classes or components |
|
|
Term
| problems within integration testing |
|
Definition
1. Interface incompatibility
2. Parameter values
3. Run-time exception-due to conflicting resource needs
4. Unexpected state interactions-complex failures |
|
|
Term
| Additional factors that complicate object-oriented programming |
|
Definition
1. many methods can call other methods and distributed among many other classes
2. Classes may inherit methods and state variables from other classes
3. specific method to be called is dynamically determined at run time based on the number and type of message parameters
4. Objects can retain internal variable values between calls, response may be different for two identical calls |
|
|
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 subsystems |
|
|
Term
|
Definition
| A system test that is performed daily or several times a week |
|
|
Term
| performance test or stress test |
|
Definition
| an 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 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 performed to determine whether the system fulfills user requirements |
|
|
Term
|
Definition
1. Performing system and stress test
2. Perform user acceptance tests
3. Convert existing data
4. Build training materials and conduct training
5. Configure and set up production environment
6. Deploy the solution |
|
|
Term
|
Definition
| descriptions of system requirements, architectures, and construction details, as used by maintenance personnel and future developers |
|
|
Term
|
Definition
| descriptions of how to interact with and use the system, as used by end users and system operators |
|
|
Term
| input, process, output (IPO) development order |
|
Definition
| a development order that implements input modules first, process modules next, and output modules last |
|
|
Term
|
Definition
| a development order that implements top-level modules first |
|
|
Term
|
Definition
| a development order that implements low-level detailed modules first |
|
|
Term
| source code control system |
|
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 an extended period of time. |
|
|
Term
| production release or release version |
|
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
| Typical change control procedures |
|
Definition
1. Standard reporting methods
2. Review of requests by a project manager or change control committee
3. For operational systems, extensive planning for design and implementation |
|
|
Term
| activities included in planning for a change |
|
Definition
1. Identify what parts of the system must be changes
2. Secure resources to implement the change
3. Schedule design and implementation activities
4. Develop test criteria and a testing plan for the changed system. |
|
|
Term
|
Definition
| the version of the system used from day to day |
|
|
Term
|
Definition
| a copy of the production system that is modifies to test changes |
|
|
