| Security testing - | (Software Engineering) testing tasks that probe the vulnerability of both client-side and server-side software |
| Smoke testing - | (Software Engineering) an integration testing approach that constructs and tests software on a daily basis |
| Stakeholders - | (Software Engineering) any person of group that has a stake in the successful completion of a software project |
| Stress testing - | (Software Engineering) a testing task that determines how software responds when it is forced to meet or exceed operational limits |
| Task analysis - | (Software Engineering) a software engineering action that is conducted as part of user interface design; intended to better understand how a user is to interact with a system |
| 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 |
| Technical risks - | (Software Engineering) the set of potential technical problems or occurrences that may cause the project to fail |
| 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 |
| White box testing - | a test case design technique that makes use of a knowledge of the internal program logic |