Who is system analyst?

An analyst is an expert engaged in analytical studies and generalizations in a certain field of activity, who is fluent in analysis methods, usually good at predicting processes and designing promising development programs.

There are four types of system analyst:

IT-analyst is an expert whose main task is to create the infrastructure of a future IT project.
IS-analyst is an expert who is responsible for the creating of adversary models, models of information security threats, business risk assessment. In addition, IS-analyst develops technical and analytical documentation on the project outcomes (penetration testing, security analysis of web applications, etc.).
A business analyst is an intermediary between stakeholders, who collects, analyzes, communicates and verifies requirements for changing business processes, regulations and information systems. The business systems analyst understands business opportunities and threats of requirements and recommends solutions that enable the organization to achieve its goals.
System analyst is responsible for analyzing user needs and satisfying them through the relevant information system. He is also called the "task manager".

The main product of the system analyst is administrative and technical solutions, drawn up as technical specifications for a system or software.

Next, consider the role of the systems analyst and the issues he (this expert) deals with in the project.

The role

The key role of an IT systems analyst in a company's automation project is to develop a consistent and complete model of business requirements for deployed software.

First, a data system analyst evaluates requirements for a new software product, develops the terms of reference for software, supports the ongoing documentation for the system and IT system architectures, sets the tasks for development and testing. At the end of the project, he partners with stakeholders, resolves various issues at all stages of the system life cycle.

The software systems analyst in the field of IT is most often involved in the process automation. He gets the feedback from all participants in the production process, analyzes it and thoroughly describes the functionality of the software. In general terms, the software system analyst is responsible for producing specifications to the software development task.

The tasks

The main tasks of the systems analyst are:

Collection, analysis and documentation of requirements (interviewing customers). Software development begins when a customer, orally or in writing, sets out to the performer his vision of the future system. Though they are not requirements and such statements are not systematic by nature, but resemble a set of customer wishes. At the initial stage of software design, the analyst must identify with the customer the goals of the software development: the main tasks the system should solve when it is introduced into the enterprise’s business process.
Interviewing business experts and stakeholders for better awareness of the current principles of organizing business processes.
Documenting customer requirements.
coordination of requirements with the customer, for their equal perception by both the customer and the developers of the project;
definition of the project users;
definition of access rights;
study and systematization of project documentation regarding the allocation of automated processes;
preparation of documentation for the description of entities, relationships and processes of the subject area using special notations.
Developing technical specifications and task setting. At the design stage the analyst produces the technical task for development, agreed with the customer.
Building the necessary models, algorithms, prototypes.
Working out software and integrated systems design.
Coordination of software development, testing, acceptance and implementation. The system analyst prepares functional testing schemes to identify deviations from business requirements and functional requirements. The system analyst is also involved in testing a prototype system that is under development and fix the bugs if it is necessary.