| High-order tests - | (Software Engineering) black-box tests conducted once the software has been integrated |
| Interface design - | (Software Engineering) a software engineering action that establishes the structure and workflow for a user interface; follows three "golden rules:" place the user in control, reduce the user's memory leoad, make the interface consistent. |
| Load testing - | (Software Engineering) a testing task that determines how software (often a WebApp) will respond to various loading conditions |
| Make-buy decision - | (Software Engineering) determining whether software should be built internally, acquired, contracted or built from reusable components |
| Object-oriented - | (Software Engineering) an approach to software development that makes use of a classification approach and packages data and processing together |
| Outsourcing - | (Software Engineering) contracting software work to a third party |
| Pair programming - | (Software Engineering) two people work together (side-by-side) to design and construct a software component, providing real-time problem solving and quality control. |
| PDL - | (Software Engineering) program design language; a combination of natural language with programming language-like constructs |
| Process framework - | (Software Engineering) a relatively small set of fundamental software engineering activities that define a software process |
| Productivity - | (Software Engineering) work output per unit time |