| Domain analysis - | (Software Engineering) an object-oriented software engineering activity that attempts to identify classes that are relevant to an entire application domain, rather than a specific application |
| Engineering change order (ECO) - | (Software Engineering) a mini-specification that describes the technical aspects of a change |
| FAST - | (Software Engineering) Facilitated application specification techniques, a structured meeting between developer and customer; intent is to define basic requirementsFormal methods - |
| Integration - | (Software Engineering) the specific approach to integration testing |
| Joint application development (JAD) - | (Software Engineering) a specific FAST technique |
| Requirements engineering - | (Software Engineering) the activities required to elicit, elaborate, negotiate, specify, and validate system or software requirements |
| Software Requirements Specification - | (Software Engineering) a deliverable that describes all data, functional and behavioral requirements, all constraints, and all validation requirements for software |
| Time-boxing - | (Software Engineering) a project scheduling and control technique that establishes time boundaries for the completion of a specific project task |
| Use-case - | (Software Engineering) a written description that defines a very specific interaction between a user and a system, often (but not always) written in the form of a usage scenario |
| Absolute Volume | (Concrete Engineering) The volume of an ingredient in its solid state, without voids between individual pieces or particles, in the case of fluids, the cubic content occupied. In concrete, the actual volume occupied by the different ingredients determined by dividing the weight of each ingredient pounds, by ifs specific gravity, times the weight of one cubic foot of water in pounds. Example: Absolute Volume of one sack of cement equals: 94 ๗ (3.15X62.4) = 0.478 cubic feet |