Analysis

After studying the new system plans, you have to check if it is possible to create the new system by looking at these options The project will only continue to the next stage if the answer to both of these questions is yes. At this point the decision makers in the organisation make the decision Top down Design is a drawing technique used as part of the design stage in the Systems Life Cycle. A top down design is a technique that starts with the highest level of an idea and works its way down to the lowest level of detail. It shows the development of a new system, broken down into small logical 'chunks' of work. Each small 'chunk' will represent a complete section of work. The diagram will show the order in which work needs to be completed.
 * __Feasibility study __**
 * **Technically feasible ** - is the new system technically possible to implement in the time available?
 * **Economically viable ** - will the cost of the new system be offset by savings once it is implemented, for example will it save the organisation time, money or increase its performance?
 * __Top down Design __**

**__ Analysis Stage: __** This method includes observation of how the current system works, who uses it, how efficient it is. Ways of collecting data are giving out questionnaires, interviewing people and looking at existing paper work
 * //1) //****//__Fact Finding/collecting data from the current system __//**
 * //2) //****//__Description of the current system- establishing the inputs, outputs and processing being done. __//**

How it works, its efficiency the time tables of it and how user friendly it is.


 * //3) //****//__<span style="font-family: 'Arial','sans-serif'; font-size: 16px;">Identification of the problems with the current system __//**

Conducting interviews with people who have used the current system and what could be improved. As well as giving questionnaires about people’s opinions and belief about the current system.


 * //<span style="font-family: 'arial','sans-serif'; font-size: 16px;">4) //****//__<span style="font-family: 'Arial','sans-serif'; font-size: 16px;">Agreeing the objectives with the customer __//**

At this stage the employee and the customer have to agree on what the objectives of the system or business is.


 * //<span style="font-family: 'arial','sans-serif'; font-size: 16px;">5) //****//__<span style="font-family: 'Arial','sans-serif'; font-size: 16px;">Identifying and agreeing the customer’s requirements __//**

At this stage the employee must be able to identify what the customers’ expectations and demands are from the business.


 * //<span style="font-family: 'arial','sans-serif'; font-size: 16px;">6) //****//__<span style="font-family: 'Arial','sans-serif'; font-size: 16px;">Interpreting the customer’s requirements __//**

<span style="font-family: 'Arial','sans-serif'; font-size: 16px;">At this stage you would need to find out exactly what the customer needs and wants from the system.


 * //<span style="font-family: 'arial','sans-serif'; font-size: 16px;">7) //****//__<span style="color: #333333; font-family: 'Arial','sans-serif'; font-size: 16px;">Producing a cost-benefit analysis __//**

At this stage you would need to determine the costs of the system and the benefits that would come out from the system and if it’s worth going ahead to do it.

Data flow diagram is a significant modeling technique for analyzing and constructing information processes.
 * //<span style="font-family: 'arial','sans-serif'; font-size: 16px;">8) //****//__<span style="font-family: 'Arial','sans-serif'; font-size: 16px;">Producing a data flow diagram __//**