The principal reasons for performing a requirements analysis include:
- Getting the system right the first time
- Supporting easy user access to the system
- Producing reasonable and reliable estimates of costs
- Writing a requirements specification from the approved research information and making it available to the designer of the logical database.
The process includes, at minimum, the following tasks:
- Interviewing notable employees, both management and support staff, for information such as the following:
- What information do they need?
- What is the source of that information?
- What are the tasks involved with creating and reporting the information?
- How is the information used?
- Gathering all input screens and reports generated by the legacy system and interviewing management and support staff about what is right and wrong about these components as well as determining what sorts of new or different input and report items should be added to the new system.
- Compiling and circulating the cumulative research information you have gathered to obtain affirmation of its accuracy from all involved parties.
- Writing a requirements specification from the approved research information and making it available to the designer of the logical database.