ABSTRACT
Defining requirements can be an involved and time-consuming affair where every detail is captured and presented in a voluminous document. There are different ways of establishing requirements. The aim is to identify the processes, establish what they do and define the key issues that need to be addressed. The requirements have been defined the question arises as to how to meet them. One thought may be that one package provided by an Enterprise Resource Planning vendor is able to meet all requirements. Special requirements can be highlighted, for example languages, currencies, decimal places. Statutory requirements should not be overlooked as a foreign software product may not meet local requirements, for example VAT records. In both cases, the routine should be captured. What may be overlooked in both approaches is the deviation from the norm. The handling of such deviations may constitute an essential requirement for the new system.
