| Formal technical reviews - | (Software Engineering) a structured meeting conducted by software engineering with the intent of uncovering errors in some deliverable or work product |
| Formulation - | (Software Engineering) a Web engineering action that identifies business need, describes WebApp objectives, defines major features and functions, and establishes mechanisms for requirements gathering |
| Function points - | (Software Engineering) a measure of the utility delivered by an application |
| Functional decomposition - | (Software Engineering) a technique used during planning, analysis and design; creates a functional hierarchy for the software |
| Go, no-go decision - | (Software Engineering) a point at which manager or the customer decides whether the project should proceed |
| GQM (Goal, Question, Metric) paradigm - | (Software Engineering) a technique for defining meaningful metrics for any part of the software process |
| Grammatical parse - | (Software Engineering) a technique that is used during analysis and intended to help isolate basic data objects and functions |
| High-order tests - | (Software Engineering) black-box tests conducted once the software has been integrated |
| Independent test group (ITG) - | (Software Engineering) a group of people whose primary responsibility is software testing |
| Interface design - | (Software Engineering) a software engineering action that establishes the structure and workflow for a user interface; follows three "golden rules:" place the user in control, reduce the user's memory leoad, make the interface consistent. |