Phase 2 – System Analysis

1.8 Phase 2 – System Analysis     

In this phase, the current business system is studied in detail to find out how it works and how to improve it. The emphasis is placed on what the system will do, not how will it do.

1.8.1    Need Analysis

It is also known as requirements analysis. The analyst sums up all requirements of the system from users and managers. The developed system should satisfy all requirements mentioned in this phase.

1.8.2    Data Gathering Techniques

Data gathering techniques are used to collect detailed information about the system.

These techniques are s follows:

       I. Written Documents

The written documents of the current system are important source of information for the analyst. The analyst can study these documents in detail to find out drawbacks of the system. The reports, forms, memos, business plans, policy statements and organizational charts are some important documents.

     II. Interviewing

Interviewing is a technique used by an analyst to get information from managers, department heads and functional heads. The analyst asks questions to understand the problem and nature of the desired solution. The questions help to focus on overall goals and get better understanding of problem. These questions must be precise and relevant.

  III. Questionnaires

Questionnaires are used to collect information from a large number of people. Questionnaires are very useful in this situation because a lot of time is required to interview such a large group. It is also convenient and inexpensive method of collecting information.

  IV. Observation

Observation is a process of watching the people while they are working. Observation helps the analyst in detecting problems that exist in the current system. Users are either unaware of the problems or hesitate to talk about them. The analyst must get the permission from the management for observing certain activities.

    V. Sampling

A system in a large organization may involve many people or events. Sampling is a technique in which the analyst may select certain events or people instead of all.

  VI. Facilitated Application Specification Techniques (FAST)

FAST is based on the team-oriented approach to requirements gathering. A joint team of users and developers work together to identify the problem, propose the possible solution, identify the different strategies and approaches to solve the problem.

VII. Quality Function Deployment (QFD)

QFD is a quality management technique. It translates the needs of user into technical requirements for software. QFD emphasizes on understanding what is valuable to the customer and then deploying these valuables throughout the engineering process. There are three types of requirements according to QFD:

·         Normal Requirements

·         Expected Requirements

·         Exciting Requirements

Once the requirements have been gathers, the development team needs to examine them and categorize them. They need to set priorities of all requirements. They should also give a solution stating which part of the system should be automated first.

1.8.3    Analyst Modeling

Models are created to get a better understanding of the actual system to be built. A software model must be capable of modeling the information that software transforms its functions and behaviors. The models focus on what the system must do, and not on how it does it. Analysis modeling is the first technical representation of a system. Most important methods for analysis modeling are follows:

·         Structured Analysis—emphasizes on dividing the programs into independent sections. It is based on function-based decomposition. It focuses on the functions performed by the system and the data used by them.

·         Object-oriented Analysis—is the process during which concise model of the problem in terms of real world objects is developed.