| Stakeholders - | (Software Engineering) any person of group that has a stake in the successful completion of a software project |
| State transition diagram (STD) - | (Software Engineering) a notation for behavioral modeling |
| Statistical quality assurance - | (Software Engineering) techniques for process improvement that are based on measurements of the product and the process |
| Stepwise refinement - | (Software Engineering) a technique for accomplishing functional decomposition or procedural design (also called partitioning) |
| Stress testing - | (Software Engineering) a testing task that determines how software responds when it is forced to meet or exceed operational limits |
| Structured programming - | (Software Engineering) a design method that limited design constructs to only three basic forms and constrains program flow for better quality |
| System engineering - | (Software Engineering) focuses on the analysis and design of all elements of a complete product, service, or technology for the transformation of information or control |
| 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 |