| Test cases, derivation of - | (Software Engineering) the creation of data that can be used to uncover errors in the software |
| Test plan and procedure - | (Software Engineering) a description of testing strategy and tactics |
| Testing - | (Software Engineering) a set of activities that attempt to find errors |
| Time-boxing - | (Software Engineering) a project scheduling and control technique that establishes time boundaries for the completion of a specific project task |
| Tools - | (Software Engineering) application software used to perform software engineering tasks (e.g., design tools, testing tools); see also CASE tools |
| Total quality management - | (Software Engineering) a company commitment to develop a process that achieves high quality product and customer satisfaction |
| UML (Unified Modeling Language) - | (Software Engineering) a comprehensive diagrammatic notation for the analysis and design of software |
| Unified process - | (Software Engineering) a "use-case driven, architecture-centric, iterative and incremental" software process that emphasizes the use of UML notation |
| Unit testing - | (Software Engineering) part of the testing strategy that focuses on tests to individual program components |
| Use-case - | (Software Engineering) a written description that defines a very specific interaction between a user and a system, often (but not always) written in the form of a usage scenario |