Overview

I'll go and find out what they need, and the rest of you start coding!

In Analysis you define the requirements for the system you will buy or build. It consists of the following main tasks:

1. Identify the users goals, and describe the business processes that the system will support.

2. Analyse, describe and structure the data the users will process.

3. Find out where data will come from, and go to.

4. Describe what use will be made of the data (the reporting functions).

5. Plan how to test that the functions have been delivered.

Note that we haven t made any mention of the system structure which will support the functions. This is not an Analysis issue. You must concentrate on the business processes which any system must support, not specific implementations of these processes, whether existing or planned.

This is equally true when you are defining enhancements to an existing system: base the Analysis on understanding the business functions and data currently supported and the changes required to that structure. Only then can you be sure that the changes to the system design will have the right result for the business.

I assume you will be doing at least part of the analysis work. If not, then make sure your architect or analyst reads this, and make sure you fully understand the requirements and models he or she produces.

What Do They Need?

The main aim of Analysis is to take the scope and high-level description...