| 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 |
| Validation - | (Software Engineering) tests to ensure that the software conforms to its requirements |
| WebApps (Web Applications) - | (Software Engineering) any application that delivers meaningful content or functionality to end users via the Web. |
| Web engineering - | (Software Engineering) the application of software engineering principles, concepts, and methods (or adaptations of them) to the development of Web-based applications or systems. |
| White box testing - | a test case design technique that makes use of a knowledge of the internal program logic |
| Work breakdown structure (WBS) - | (Software Engineering) the set of work tasks required to build the software; defined as part of the process model |
| Work flow - | (Software Engineering) the sequence of tasks that are required to accomplish some activity or action; often (but not always) used in conjunction with software process models |