| Task set - | (Software Engineering) a collection fo software engineering tasks that are required to complete an activity or action that is part of a software process framework |
| Test case design - | (Software Engineering) a set of techniques for deriving effective test cases |
| Test cases, derivation of - | (Software Engineering) the creation of data that can be used to uncover errors in the software |
| 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 |
| Unified process - | (Software Engineering) a "use-case driven, architecture-centric, iterative and incremental" software process that emphasizes the use of UML notation |
| Usability - | An informal measure of the ease with which a user interface can be learned and applied with efficiency and without errors |
| 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 |
| User - | (Software Engineering) the person who actually used to software or the product that has software embedded within it |
| User-story - | (Software Engineering) a usage scenario that is used as part of Extreme programming |