| Make-buy decision - | (Software Engineering) determining whether software should be built internally, acquired, contracted or built from reusable components |
| Measurement - | (Software Engineering) collecting quantitative data about the software or the software engineering processMetrics - |
| Modularity - | (Software Engineering) an attribute of a design that leads to the creation of high quality program components |
| Object-oriented analysis (OOA) - | (Software Engineering) a technique for defined classes of objects, their relationships and basic structure |
| Object-oriented design (OOD) - | (Software Engineering) a technique for translating the OOA model into an implementation model |
| Pair programming - | (Software Engineering) two people work together (side-by-side) to design and construct a software component, providing real-time problem solving and quality control. |
| Project scope - | (Software Engineering) a statement of basic requirements of the software to be built |
| Project control - | (Software Engineering) the control of quality and change |
| 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 |