SYSTEM ANALYSTS

System Analysts

System Analysts

In the beginning, the software industry has adopted an organizational approach, like most industries now. This approach calls for the specialization of functions and organizational method. Under this approach, the software construction process is conceived as a highly specialized set of tasks where it is clearly defined the role of each professional category:

The analyst has the task of analyzing a problem and describes the purpose of being solved by a computer system. The designer makes, based on analysis, solution design; the analyst has to define the tests to see what you want to do initially and then give users new options for use. (Kendall, 2007)

Today, these functions have been clearly obsolete even though the professional category still exists as such. Advances in software engineering in his short life have shown that these functions are not sufficient to achieve minimal success in software development.

The most important features are missing:

Address (of projects) to direct resources towards the desired result.

Elicitation of requirements , to determine the expected behavior of the software.

Quality assurance to ensure customer expectations.

Design, so that there is a minimal assurance that the software is effective and feasible with existing technology. (Kendall, 2007)

Configuration management to control the chaos as the software grows.

These functions have been adopted in many cases by analysts, but are not specific regarding this profession. In some organizations (and in some countries) the profession no longer exists, being replaced by other figures such as software engineer, project manager, software modeler or analyst-programmer. The latter figure is very popular because it solves the typical problems of communication that existed between analysts and programmers. These problems are due to the extreme idealization of the specialization of functions. (Santos, 2010) It is also desirable that the systems analyst, at least have basic knowledge-usability. Since any system that is not serving the intended users or user in mind, it makes little sense.

The traditional profile of the analyst is analyzed. The qualities expected of an analyst are essentially the ability of abstraction and analysis. The skills required are those related to systems analysis techniques for information:

Knowledge of the traditional paradigm of software engineering and the traditional software life cycle in cascade.

Functional Modeling: Data flow diagram, state diagram, and so on.

Data modeling and techniques: entity-relationship diagram, relational model, and so on.

Knowledge of technology: software architecture, databases, etc...

These are all matters within the qualification called Engineering (Shelly, 2008)

The Systems Analyst is essential in any organization (Shelly, 2008); because of the range of skills that he possesses and the benefits it produces. It is responsible not only to study the organization and develop a system automated, it is more than that, the work of systems analyst is also to advise, monitor, recommend and modify processes internally and sometimes modify the structure itself of the company , with In order to achieve the objectives proposed.

All development Led or not a systems analyst has phases that can be divided logically into discrete elements, but they undeniably are continuous, in a cyclic ...