Pros and Cons of Each Tool

Which tool is the best depends on a number of factors: the nature and complexity of the problem the number of actions resulting from the decision, and the ease of use. In reviewing the benefits and limitations of each tool, we come to the following conclusion:

1. The primary strength of the DFD is its ability to represent data flows. It may be used at high or low level of analysis and provides good system documentation.

However, the tool only weakly shows input and output detail.7 The user often finds it confusing initially.

2. The data dictionary helps the analyst simplify the structure for meeting the data requirements of the system. It may be used at high or low levels of analysis, but it does not provide functional details, and it is not acceptable to many nontechnical users.

3. Structured English is best used when the problem requires sequences of actions with decisions.

4. Decision trees are sued to verify logic and in problems that involve a few complex decisions resulting in limited number of actions.

5. Decision trees and decision tables are best suited for dealing with complex branching routines such as calculating discounts or sales commissions or inventory control procedures.

Given the pros and cons of structured tools, the analyst should be trained in the sue of various tools for analysis and design He/She should use decision table and structured English to get to the heart of complex problems. A decision table is perhaps the most useful tool for communicating problem details to the user.

The major contribution of structured analysis to the system development life cycle is producing a definable and measurable document – the structured specification. Other benefits include increased user involvement, improved communication between user and designer, reduction of total personnel time, and fewer “ kinks” during detailed design and implementation. The only drawback is increased analyst and user time in the process. Overall the benefits outweigh the drawbacks, which make-structured analysis tools viable alternatives in system development.

6.6 Summary

Analysis is the heart of the process. It is the key component of the first two phases of the cycle. In analysis the present system, the analyst collects a great deal of relatively unstructured data through interviews, questionnaires, on–site observations, procedures manuals, and the like. Requirements determination involves studying the current business

system to find out how it works and where improvements should be made. Systems studies result in an evaluation of how current methods are working and whether adjustments are necessary or possible. These studies consider both manual and computer methods, they are not merely computer studies.

The specific methods analysts use for collecting data about requirements are called fact – finding techniques. These include the interview, questionnaire, record inspections (on – site review) and observation. Analysts usually employ more that one of these techniques to help ensure an accurate and comprehensive investigation. Structured analysis is a set of techniques and graphical tools that allow the analyst to develop a new kind of system specifications that are easily understandable to the user. Analysts work primarily with their wits, pencil, and paper. Most of them have no tools. The traditional approach focuses on cost/benefit and feasibility analysis, project management, hardware and software selection and personnel considerations. In contrast, structured analysis considers new goals and structured tools for analysis.

The first step is to draw a data flow diagram (DFD). The DFD was first developed by Larry Constantine as a way of expressing system requirements in a graphical from; this led to a modular design. A data dictionary is a structured repository of data about data. It offers primary advantages of documentation and improving analyst/user communication by establishing consistent definitions of various elements, terms and procedures.

A decision tree sketches the logical structure based on some criteria. It is easy to construct, read, and update. A decision tree is a diagram that presents conditions and actions sequentially and thus shows which conditions to consider first, which second, and so on. It is also a method of showing the relationship of each condition and its permissible actions. A decision table is a table of contingencies for defining a problem and the actions to be taken. It is single representation of the relationships between conditions and actions. The pros and cons of the tools are;

• The primary strength of the DFD is its ability to represent data flows. It may be used at high or low level of analysis and provides good system documentation.

6. The data dictionary helps the analyst simplify the structure for meeting the data requirements of the system. It may be used at high or low levels of analysis, but it does not provide functional details, and it is not acceptable to many nontechnical users.

7. Structured English is best used when the problem requires sequences of actions with decisions.

8. Decision trees and decision tables are best suited for dealing with complex branching routines such as calculating discounts or sales commissions or inventory control procedures.

6.7 Questions

1. What type of information is best obtained through interview. 2. What is systems requirement.

3. What advantages do decision trees present. from analysts. 4. Discuss the pros and cons of the various tools of doing analysis. 5. What is structured analysis.

7.0 Objectives: