| Requirements analysis - | (Software Engineering) a modeling activity whose objective is to understand what the customer really wants |
| Requirements engineering - | (Software Engineering) the activities required to elicit, elaborate, negotiate, specify, and validate system or software requirements |
| Reusability - | (Software Engineering) the ability to reuse an already-existing program component in another application |
| Reusable components - | (Software Engineering) configuration items that are reusable |
| Risk - | (Software Engineering) a potential problem or occurrence that put a project in jeopardy |
| Scheduling - | (Software Engineering) the activity that lays out a timeline for work to be conducted on a project |
| Scope - | (Software Engineering) a bounded statement of what must be accomplished |
| Security - | (Software Engineering) the ability of software to operate in a manner that is secure from internal or external attack |
| Security testing - | (Software Engineering) testing tasks that probe the vulnerability of both client-side and server-side software |
| Side effects - | (Software Engineering) errors that occur because of changes |