| Project risks - | (Software Engineering) the set of potential project problems or occurrences that may cause the project to fail |
| Project scope - | (Software Engineering) a statement of basic requirements of the software to be built |
| Project size - | (Software Engineering) an indication of the overall effort to be expended or the number of people working on the project |
| Project tracking - | (Software Engineering) the activity that enables a manager to understand the status of a 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 |
| Quality management - | (Software Engineering) a set of software engineering actions that helps ensure that software is built in a way that achieves high quality |
| 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. |
| Reliability - | (Software Engineering) a measure of the degree to which software operates reliably over some period of time |