| Analysis - | (Software Engineering) a set of activities that attempt to understand and model customer needs and constraintsAnalysis methods - |
| Architecture - | (Software Engineering) the overall structure of software components, the data and/or content that components manipulate, and the relationships between them |
| Classes - a basic construct in object - | (Software Engineering) oriented methods that categorizes elements of the problem |
| Constraints - | (Software Engineering) an restrictions or limitations placed on requirements or design |
| Data design - | (Software Engineering) an activity that translates the data model developed during analysis into implementable data structures |
| 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 |
| 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. |
| Integration testing - | (Software Engineering) a testing step that constructs the software while testing it |