ABSTRACT
As a second example of system modeling, I will explore the recovery of legacy system requirements.2 Because system requirements are at the heart of every meaningful system, it is of great importance to understand and maintain a complete set of requirements for every system the business creates. These requirements explain not only the behavior of the system but also provide insight into the minds of the system users who will ultimately benefit. Oftentimes, however, these requirements are either (a) partially captured in an informal or locally developed mechanism or (b) captured in the heads of the developers and the mystery that is code. Unfortunately for most development organizations either of these approaches ultimately leads to mistakes and added costs.
