| 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) |
| 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. |
| Make-buy decision - | (Software Engineering) determining whether software should be built internally, acquired, contracted or built from reusable components |
| Navigation analysis - | (Software Engineering) a Web engineering action that establishes how a user will navigate between various elements (e.g., content, functions) of a WebApp |
| Objects - | (Software Engineering) a named element of the problem domain containing data and processing |
| Outsourcing - | (Software Engineering) contracting software work to a third party |
| 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 control - | (Software Engineering) the control of quality and change |
| Software engineering - | (Software Engineering) a discipline that encompasses the process associated with software development, the methods used to analyze, design and test computer software, the management techniques associated with the control and monitoring of software projects and the tools used to support process, methods, and techniques. |