| Project size - | (Software Engineering) an indication of the overall effort to be expended or the number of people working on the project |
| Quality - | (Software Engineering) the degree to which a product conforms to both explicit and implicit requirements |
| Quality function deployment (QFD) - | (Software Engineering) a technique that translates the needs of a customer in technical requirements for software by assessing the value of each requirement |
| Re-engineering - | (Software Engineering) a series of activities that transform legacy systems (with poor maintainability) into software that exhibits high quality |
| Refactoring - | (Software Engineering) changing software in a way that improves its internal structure but does not change it external behavior; often conducted iteratively as design evolves into code. |
| Requirements engineering - | (Software Engineering) the activities required to elicit, elaborate, negotiate, specify, and validate system or software requirements |
| Resources - | (Software Engineering) anything that is required to get the project done, people, hardware, materials, information, etc. |
| Reverse engineering - | (Software Engineering) trying to develop design models or an understanding of design using program code as a starting point |
| Risk - | (Software Engineering) a potential problem or occurrence that put a project in jeopardy |
| Risk analysis - | (Software Engineering) a techniques for identifying and evaluating risks |