Term
An approach to software development that emphasizes a flexible and ready response to meet a shifting target |
|
Definition
| 1) agile software development |
|
|
Term
Running a program on many data sets to be sure its performance falls within required limits; timing the same algorithm on two different machines |
|
Definition
|
|
Term
Collection of thoroughly tested object code for various useful tasks |
|
Definition
|
|
Term
The process of translating detailed designs into computer code |
|
Definition
|
|
Term
The process of locating and correcting program errors |
|
Definition
|
|
Term
A program design strategy in which tasks are broken down into subtasks, which are broken down into sub-subtasks, and so on, until each piece is small enough to code comfortably |
|
Definition
|
|
Term
Designing a special set of test cases and running a program using these test data |
|
Definition
|
|
Term
The resulting object code after a linker inserts requested code from code libraries |
|
Definition
|
|
Term
Any materials assembled to clarify the program's design and implementation |
|
Definition
| 9) external documentation |
|
|
Term
A step in the software development life cycle that evaluates a proposed project and compares the costs and benefits of various solutions |
|
Definition
|
|
Term
Same as procedural language |
|
Definition
|
|
Term
A collection of programs that support software development, such as debuggers, editors, toolkits, and libraries, that lets programmers perform several tasks within the shell of a single application |
|
Definition
| 12) integrated development environment (IDE) |
|
|
Term
After unit testing, integration testing is done to see that the modules communicate the necessary data between and among themselves and that all modules work together smoothly |
|
Definition
|
|
Term
Documentation that is part of the program code itself |
|
Definition
| 14) internal documentation |
|
|
Term
A piece of system software that inserts requested object code from code libraries into the object code for the requesting program |
|
Definition
|
|
Term
An error in the algorithm used to solve a problem |
|
Definition
|
|
Term
Machine language instructions |
|
Definition
|
|
Term
Involves two programmers at a single workstation; at any given point in time, one is writing code and the other is actively observing, watching for possible errors but also thinking about the overall approach. |
|
Definition
|
|
Term
A step in the software development life cycle that involves developing a clear, concise, and unambiguous statement of the exact problem the software is to solve |
|
Definition
| 19) problem specification |
|
|
Term
A program written in a procedural language consists of sequences of statements that manipulate data items |
|
Definition
|
|
Term
A step in the software development life cycle that plans the structure of the software to be written |
|
Definition
|
|
Term
The process of adapting an existing software product due to errors, new system requirements, or changing user needs |
|
Definition
|
|
Term
Used to prove that if the input data to a program satisfies certain conditions, then, after the program has been run on these data, the output data satisfies certain other conditions |
|
Definition
|
|
Term
Sample graphical user interfaces (GUIs) created early in the software development process in order to get user input |
|
Definition
| 24) prototype 24) prototype |
|
|
Term
If anything is changed on an already-tested module, regression testing is done to be sure that this change hasn't introduced a new error into code that was previously correct |
|
Definition
|
|
Term
Error that occurs when the program is run using certain sets of data that result in some illegal operation, such as dividing by zero |
|
Definition
|
|
Term
The meaning of correctly written programming statements |
|
Definition
|
|
Term
The overall sequence of steps needed to complete a large-scale software project |
|
Definition
| 28) software development life cycle |
|
|
Term
An organized process for large-scale software development |
|
Definition
|
|
Term
High-level language instructions |
|
Definition
|
|
Term
The rules for exactly how programming statements must be written; the grammatical structure of a programming language |
|
Definition
|
|
Term
An error that occurs because a program statement fails to follow the correct rules of syntax |
|
Definition
|
|
Term
Documentation that enables programmers who later have to modify the program to understand the code |
|
Definition
| 33) technical documentation |
|
|
Term
Another name for high-level programming language as opposed to machine language (first generation) or assembly language (second generation) |
|
Definition
| 34) third-generation language |
|
|
Term
A program design strategy in which tasks are broken down into subtasks, which are broken down into sub-subtasks, and so on, until each piece is small enough to code comfortably |
|
Definition
| 35) top-down decomposition |
|
|
Term
Testing each module of code as it is completed |
|
Definition
|
|
Term
Documentation that helps users run the program |
|
Definition
|
|
Term
The traditional model of software development that follows a series of steps |
|
Definition
|
|
Term
For more study material on this topic
click here and go to
my Computer Science Study Help page
|
|
Definition
For more study material on this topic
click here and go to
my Computer Science Study Help page
|
|
|
