Analyzing and Documenting Client Requirements
Analyse data and document client requirements
Inside this reading:
Analysing client requirements 2
Data flow diagrams 3
Data dictionaries 10
CASE tools 14
Confirming client requirements 15
Documenting client requirements 22
Summary 26
Analysing client requirements
Before you can start to analyse the information you have gathered you should think about what you are trying to achieve. The client has presented you with a business problem. In order to solve this problem you need to undertake the following steps:
• identify what the current system does
• identify the new features the client needs in order to solve the problem
• combine the outcomes of steps 1 and 2 to come up with the requirements which will solve the problem.
The information that you have gathered should cover steps 1 and 2. It is important that you identify what information is part of each of those steps so that you can structure the requirements in a logical sequence. This will make it easy for the client to understand the process.
You need to look at the information and ask yourself questions that will help you to:
• clarify in your mind what the client requires
• structure the bits of information given to you by the client
• organise the bits of information the client has given you
• check with your client that you have done a sufficiently thorough analysis of the client's needs.
Some questions you might ask yourself are:
'What happens if the information about products or services requested is not available either before or after installation?'
Sometimes you need to ask what–if questions (hypothetical questions) in order to explore possibilities with the client. You'll also be able to bring out any reservations that you or the client may have.
'Have you specified and documented these information gaps? How will they affect the client?'
This is a probing question that follows from the first question above. Probing questions go deep into the issue or problem.
Inside this reading:
Analysing client requirements 2
Data flow diagrams 3
Data dictionaries 10
CASE tools 14
Confirming client requirements 15
Documenting client requirements 22
Summary 26
Analysing client requirements
Before you can start to analyse the information you have gathered you should think about what you are trying to achieve. The client has presented you with a business problem. In order to solve this problem you need to undertake the following steps:
• identify what the current system does
• identify the new features the client needs in order to solve the problem
• combine the outcomes of steps 1 and 2 to come up with the requirements which will solve the problem.
The information that you have gathered should cover steps 1 and 2. It is important that you identify what information is part of each of those steps so that you can structure the requirements in a logical sequence. This will make it easy for the client to understand the process.
You need to look at the information and ask yourself questions that will help you to:
• clarify in your mind what the client requires
• structure the bits of information given to you by the client
• organise the bits of information the client has given you
• check with your client that you have done a sufficiently thorough analysis of the client's needs.
Some questions you might ask yourself are:
'What happens if the information about products or services requested is not available either before or after installation?'
Sometimes you need to ask what–if questions (hypothetical questions) in order to explore possibilities with the client. You'll also be able to bring out any reservations that you or the client may have.
'Have you specified and documented these information gaps? How will they affect the client?'
This is a probing question that follows from the first question above. Probing questions go deep into the issue or problem.