Introduction

Abstract

Twenty-five years of developing requirements for systems have taught us that the only successful approach to analysis is to accept what exists in the user’s environment, however far from ideal those conditions may be, and work within those limitations. It may be very tempting to use analysis time to try to refocus how the user does business. Yet efforts to redesign or reengineer, unless specifically requested by the user, will typically be a waste. Although your assessment may be correct and your suggestions potentially useful, being correct is less important in this situation than being wise and understanding the ability of your users to successfully implement and utilize what they need. Analysts tend to ignore this simple wisdom, much to their own distress and that of their clients.