| Errors - | (Software Engineering) a lack of conformance found before software is delivered to the customer |
| Estimation - | (Software Engineering) a project planning activity that attempts to project effort and cost for a software project |
| Extreme programming - | (Software Engineering) an agile process model that emphasizes scenario-based planning, incremental delivery, refactoring, pair programming and continuous testing. |
| Factoring - | (Software Engineering) a technique that distributes control and work in a top-down manner within a software architecture (used a part of structured analysis) |
| FAST - | (Software Engineering) Facilitated application specification techniques, a structured meeting between developer and customer; intent is to define basic requirementsFormal methods - |
| 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 |