Analysis of Problems and Software

Analysis of problems and software

What do I need to include in the analysis of a problem?

You need to find out as much information about the problem from the client as possible. This could include:

•  An interview with the client

•  Viewing the current system in operation and looking for problems

Looking at people working in an organisation helps to see where the problems occur.

•  Viewing documentation from the current system

Looking at the current documentation is a good way of finding out what is going on in the current system. It is also useful for locating the inputs, processing and outputs that we will need later in the analysis.

•  Producing a questionnaire from the client and / or the users

Breaking the problem down

A large problem should be broken down into smaller ones and then each of these analysed to help with the design section.

Produce requirements specification for the identified problem to match the client’s needs

The requirement specification should be clear and concise as this lays out the plan of what the client wants from the new system. A description of the client’s requirements will give a clear picture of what you are aiming to solve. Having produced the requirements you need to go back to the client to see if what you produced is what they wanted; if it is then they can sign it; if not then changes can be made and then signed.

Describe the input, processing & output needs to match the requirements specification

Having described what the client wants from any new system you now need to describe the inputs that are needed to achieve this, followed by a description of any processing that needs to be carried out and finally a description of the information that is produced following this processing. These inputs, processing and output must match what the client wants not what you think the client wants. Having a clear idea at the end of the analysis leads onto a good starting point for the designs....