| Technical risks - | (Software Engineering) the set of potential technical problems or occurrences that may cause the project to fail |
| Test plan and procedure - | (Software Engineering) a description of testing strategy and tactics |
| 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 |
| Unit testing - | (Software Engineering) part of the testing strategy that focuses on tests to individual program components |
| 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 hierarchy - | (Software Engineering) a hierarchical representation of the categories of users that will interact with any type of software |
| User-story - | (Software Engineering) a usage scenario that is used as part of Extreme programming |