| Abstraction - | (Software Engineering) (1) the level of technical detail of some representation of software; (2) a cohesive model of data or an algorithmic procedureAction (also called Software engineering action) - |
| Aspect-oriented development - | (Software Engineering) a development approach that emphasizes "concerns" (also called "aspectual requirements" that incorporate features, functions and information content) that cut across multiple system functions |
| Change management - | (Software Engineering) a set of software engineering actions that helps ensure that changes are properly identified, controlled, and reportedChange report - |
| Component (also called Software component) - | (Software Engineering) a named, modular building block for computer software |
| Configuration - | (Software Engineering) the collection of programs, documents and data that must be controlled when changes are to be madeConfiguration audit - |
| Configuration items - | (Software Engineering) the individual pieces of programs, documents and data that are controlled using SCM |
| Design - | (Software Engineering) an activity that translates the requirements model into a more detailed model that is the guide to implementation of the software |
| Stepwise refinement - | (Software Engineering) a technique for accomplishing functional decomposition or procedural design (also called partitioning) |
| White box testing - | a test case design technique that makes use of a knowledge of the internal program logic |
| Cement, Portland (ASTM C150) (Concrete Engineering) | A powdery substance made by burning, at a high temperature, a mixture of clay and limestone producing lumps called “clinkers” which are ground into a fine powder consisting of hydraulic calcium silicates. For non-portland cements, see aluminous cement. |