In the next three chapters, I will present some common system modeling problems using examples from Business Workflow Analysis, Software Requirements Archaeology, and System Architecture Documentation. Each of these areas requires the modeler to interact with different groups of people whose modeling needs vary widely. An executive looking for gains in workflow efficiencies is quite different from a software engineer looking to maintain a 30-year-old computer system. Thus, the purpose, form, theme, and views for each of these models should be considered separately. The techniques used for investigation, however, will have a great deal of overlap.