| Security - | (Software Engineering) the ability of software to operate in a manner that is secure from internal or external attack |
| Software Requirements Specification - | (Software Engineering) a deliverable that describes all data, functional and behavioral requirements, all constraints, and all validation requirements for software |
| Software safety - | (Software Engineering) an SQA activity that focuses on the identification and assessment of potential hazard that may have a negative impact on the operation of software |
| 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 |
| 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 |
| 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 |