The introduction of such a qualification will bring discussion professional problems investment activities to a new level. Investing has always been and remains a process in which it is impossible to make absolutely accurate forecasts. However, qualified professionals can and should help investors to gain a clear understanding of risks and their relationship to profitability.

The range of tasks of a business analyst is quite wide, and depends mainly on the stage of the project at which the analyst works. As a rule, in implementation projects information systems several analysts are involved, and each is responsible for their own functional area.

ProfGuide continues the column "From the first person", and today an analyst of one of the largest IT companies in Tatarstan, Lyudmila Davydova, talks about her profession.

What is the essence of the tasks performed by the analyst?

In the activities of each company there are many business processes, and how bigger business, the more there are. Each process uses and generates information that must be considered and controlled. For example, on manufacturing plant sales plan generates production plan, which, in turn, determines the procurement plan (based on the production needs for materials and components). Purchase orders are formed on the basis of material consumption rates (this data is contained in the description of technical processes), taking into account the availability of material in the warehouse. Production and sales processes - from the release of materials from the warehouse to shipment finished products— are complex and require high-quality management and accounting. Of course, this applies to any company in all industries - from manufacturing to the service sector.

Manual business management is a thing of the past, now there are a huge number of information systems on the market that make life easier for both business owners and ordinary employees. Each level has its own tasks - the manager wants to control, for example, financial flows, and a specialist in the sales department wants to have an up-to-date client base. Requirements at all levels can be satisfied by the introduction of one or the combination of several information systems. This is where the analyst's work begins - to determine the list of automated processes, find bottlenecks in them (as you know, the strength of the chain is determined by the strength of the weakest link), find ways to eliminate bottlenecks, select a platform (system), determine the amount of necessary improvements, etc. .

The range of tasks of a business analyst is quite wide, and depends mainly on the stage of the project at which the analyst works. As a rule, several analysts participate in information systems implementation projects, and each is responsible for his own functional area. At the start of the project, the analyst should study the customer's business processes (and preferably document them using functional diagrams), and work out together with the customer his requirements, on the basis of which the Terms of Reference will be drawn up. After the approval of the TOR, the modeling (or design) stage begins, where the analyst develops a model of the processes “as it should be”. After discussions, searching for bottlenecks in models, repeated “this is not done” and “this will not work” from system analysts, the business analyst draws layouts of the interfaces of the future system and writes task statements to developers. At the development stage, the analyst is also involved, since it is necessary to test what the developer has done, compare it with the customer's expectations (and your own too), clarify requirements, adjust the TOR (and sometimes write several additional TOR), etc. Upon completion of the development, the analyst writes a script for acceptance testing of the system (or PMI - a program and test methodology), according to which the Customer accepts the development, and the implementation phase begins. At this stage, the analyst works closely with users - trains, answers questions, consults specialists in his functional area, and, if necessary, writes instructions and user manuals.
At the final stage, when the system is put into commercial operation, the analyst takes an active part in maintaining the system, because it is impossible to foresee everything in advance, and some shortcomings will emerge only now. The analyst studies the problem, looks for solutions, and again writes tasks for developers (or new technical tasks, depending on the degree of spoiled developers).

What skills and competencies do you need to have? Do I need to have IT education?

To work in the IT-sphere, I think you need an appropriate education. Knowledge in the field of databases, networks, object-oriented programming was very useful to me in my work, and even the lectures "Microprocessors and microcomputers" were not superfluous. However, I met people with specialties that are far from it, but with a lot of practical knowledge in this area. The IT-sphere is now so wide that people of various specialties can find their niche.

Key skills that will help a lot are systematic and logical thinking, the ability to identify cause-and-effect relationships in a large amount of information, scrupulousness and meticulousness (an extremely useful quality when collecting requirements from a customer). Since each customer and each project is individual, analysts are highly valued, who have not only experience, but also a flexible mind, able to go beyond patterns and come up with something new.

And, of course, great success cannot be achieved without perseverance (it can take several hours to develop one layout!)

As for the set of tools that analysts should have, each working group has its own. But the mandatory, in my opinion, is the ability to use application software for drawing layouts, and knowledge of any process modeling notation.

For interfaces, I like Balsamiq Mockups for the variety of tools and fun design:

Who absolutely can't do it?

Far from mathematics and logic, not thinking, superficial people. Humanitarians are also unlikely to like the work of an analyst.

Who is higher than this kind of analyst? Is there room to grow?

In our company, analysts have their own grading system. At the first stage, you are an analyst. You gain experience, study the subject area, pass certification, and you are a leading analyst. After the next certification - an expert analyst. Further growth depends on the management of the company. Most often, the analyst, if there is a desire, becomes the project manager. However, there are times when a customer, not wanting to part with a capable analyst, offers him a job in his company.

There is also an opportunity to retrain from a business analyst to a systems analyst, or to a product manager (although this is more of a “horizontal” growth).

What is the main joy and meaning of being at work? What moments bring joy and what sorrows?

Joy is when you manage to find a solution to a complex problem, great joy is when the customer likes it. It is frustrating when the algorithm you invented does not pass system analysis, and you have to start all over again.

Like any specialist, there are tasks that are very interesting to deal with, you can forget about everything in the world, and think, think, build schemes in your head, consider options ... most often these are new developments - new functionality in the system - appearance and the algorithm of which depends on you. It is very exciting, such work brings pleasure.

And there are tasks that come from the technical support line and require extensive consultations or minor improvements (“add a field to the report for us, you forgot to specify it in the TOR”, “please close these requests urgently, otherwise we are finished”, “how to do it, so that everything is calculated for me? ”,“ Nothing works for me ”, etc.). This work is not so pleasant, but there is no getting away from it, because it is impossible to invent and develop endlessly. All the same, the result is not a software product, but a solution to the customer's problems.

Are there many communications and with whom? What kind of people do you have to deal with?

A lot of. No communication anywhere, the analyst works in a team. Communication takes place both with the customer (key specialists or members of the implementation team) and within the team. You have to communicate most closely with developers and system analysts. In our country, these are special people, with a particularly technical mindset, who do not allow “lyrics” and demand “to explain the essence”. I am extremely interested in working with them. There are also technical writers, project managers, other analysts, technical support specialists, department heads - the field for communication is huge.

It happens that on the side of the customer you have to work with people who are not the most advanced in it, who test your patience and positive attitude. But they are always pros in their subject area, and they themselves will teach you a lot.

What is the salary range?

The minimum salary of an analyst, as far as I know, is 20 thousand. The highest I've heard of is 50, but I don't think that's the ceiling.

Does the job give you enough challenges? After all, they are the only way to grow.

On any project there are complex and routine tasks. In my work, the ratio is about 40/60, and I'm fine with that. Every day is an exercise for the mind, and the opportunity to relax while writing instructions.

Here are some examples of tasks from practice:

1. There is system X and system Y. To complete one of the processes (by a certain date, not earlier, not later), system Y needs data from X. System X, in turn, needs confirmation of the successful transfer of data to system Y, their correctness and completeness. It is necessary to develop an algorithm acceptable for the customer for automatic two-way data exchange between systems. It is necessary to ensure that the remaining applications on the X and Y servers can function normally during the data exchange process.

Solution: The interaction of X and Y is implemented through web services. File exchange is carried out 24/7, from the moment a certain event occurs in the Y system, until the upload is completed / until the deadline occurs / until the process is manually stopped. An exchange format has been developed, a cross (between two systems) matrix of download statuses, return codes have been approved. Files at input Y are checked for correctness, and in case of errors they are rejected until the errors are corrected and reloaded. A form of monitoring has been implemented, detailed logs are kept. Upon completion of downloading each file, Y confirms or does not acknowledge the receipt of the file. Load testing of X and Y was carried out during the period of the data exchange service (the test results were disappointing, so we had to come up with a tricky download sequence algorithm active work users Y). Developed instructions for setting up the service and working with it. At the moment, data exchange between X and Y is carried out only through the developed service.

2. There is an approved list of standards (about 700 lines), with which several companies work, including the customer. One of the companies is challenging part of the regulations in court, offering its own version. The court grants the request. At the same time, a certain expert organization recalculates part of the standards, putting forward a new list (about 150 more lines).

A task: provide the customer's system with an up-to-date regulatory framework.

The complexity of the task is that each set of standards differed in units of measurement and item names. The resulting list of standards did not exist.

Solution: attempts to automate the process of matching strings did not give a result, since in each case the decision must be made by a person. Therefore, the lists had to be verified manually, looking for matches (Canceled by the court? Recalculated?) and included or not included in the resulting list.

3. Enter a new parameter for settlement operations in the system.

Performance:

1) Determine the "entry" point of the parameter into the System: is it entered by the user? Calculated from other parameters (What? How? At what point in time?)?

2) Determine the functions in which the new parameter will be used.

3) For each function: Check if the new parameter affects the execution of subsequent operations, enter the parameter into the calculation formulas.

4) Determine how and where the parameter is displayed in the interface. Draw layouts.

5) Find out if the new parameter should appear in the output forms: in which ones, in what way.

6) What output forms will be implicitly affected by this parameter? If yes, determine the degree of influence, bring the issue up for discussion.

7) Determine the amount of necessary improvements.

8) Write a statement of the task for development, or TK (depending on the amount of refinement).

9) Test the result.

Questions were asked by Elmira Davydova.

This article addresses the questions:

1. Misconceptions of the people.
2. So what, after all, does an IT analyst do?
3. secrets successful work(what qualities should an analyst have).
4. Analytics tools.
5. Where to go next?

Also in our blog there is an article "", which complements the current one.

Misconceptions of the townsfolk

Systems analyst is a profession that has appeared relatively recently on Russian market vacancies in the IT field. Understanding who a system analyst is, arises from candidates for this position either from the requirements described in the vacancy, or from their own conjectures. Let's take a look at some of the most common candidate misconceptions. This vacancy is not for everyone who was previously someone "systemic". Our company often receives responses to this vacancy, for example, from system administrators.

An analyst is one who analyzes

In principle, it is correct, but when you ask a candidate about what he analyzes, this is where fantasies and reflections begin on various themes. Some argue that the analyst should tell the project manager what it would be good to do this way or that way when developing the project, or generally monitor the developers and analyze whether they are doing the right thing or not. All these are erroneous opinions.

Analyst should not be able to program

This is a logical conclusion, assuming that the first conjectures are correct. In fact, the analyst does not need special knowledge in programming, but he needs to know the basics, or at least have experience in developing in any programming language that supports OOP.

Analyst is not responsible for anything

In fact, this is far from the case, and candidates who want to take the position of a systems analyst in an IT company think that they will not have to answer for the job. Analyst errors in a project are the most expensive and can even be fatal to a project.

So what does an analyst do anyway?

Requirement Identification

An analyst starts a project, participates in development, and completes it. Software development begins with the fact that the customer sets out to the contractor his vision of the future system. This presentation can be both oral and written. This presentation cannot be called requirements, since they are not systematic, but resemble a set of wishes of the client. At the initial stage of software design, the analyst is obliged to identify the goals of software development from the customer, that is, what main tasks the System should solve when it is introduced into the business process of the enterprise. This stage of the project is the initial stage and is called the requirements identification process. All identified requirements and business processes must be formalized in a certain way. Formalization of requirements is necessary for their coordination with the customer, as well as their equal perception by both the customer and the project developers. In addition to the identified requirements, at this stage of project development, project users with certain access rights are also determined. In the process of identifying requirements, the customer may not provide all the necessary information for the full functioning of the project. The analyst should be able to identify this information and agree with the customer on this functionality of the work. The result of the analyst's work at this design stage is the terms of reference for the development, agreed with the customer.

Requirements Management

At subsequent stages of development, situations are possible when the requirements formulated at the stage of identifying requirements become obsolete for one reason or another, and new requirements appear instead. The analyst must minimize changes in requirements, whether the new requirements come from the customer or developers. In the event of a change in requirements, the analyst should, keeping the project practically in his head, evaluate all changes in the project that will entail the introduction of new requirements into the project. Changes in requirements can be costly in project development, so changes should be kept to a minimum, but nonetheless modern world Requirements changes are almost inevitable on any project. The analyst must be able to anticipate such situations in order to manage changes in project requirements to minimize risks.

Project implementation

Upon completion of the development of any IT project, the stage of introducing the developed project into the customer's business process begins. This stage also lies on the shoulders of the analyst, he must prepare the documentation necessary for users, conduct a demonstration of the project, and train the customer's employees. In order for this stage to be completed at the proper level, the analyst must know the work of the entire project from "A" to "Z", as well as navigate the possible errors that will be eliminated in subsequent releases. Before the implementation phase, the analyst should take part in testing the project in order to make sure that all the functional requirements specified in the TOR are fulfilled correctly.

Secrets of successful work

I would like to touch on the topic of the personal qualities of an analyst in the IT field. Personal qualities of the analyst give 60% of his result. The work of an analyst is connected with direct communication with the customer, so the analyst must have a well-delivered speech so that the customer sees a competent specialist and a pleasant person in the interlocutor. The ability to communicate lies at the heart of great success at work. So, the first quality of an analyst is sociability. The next quality of an analyst, which allows him to perform his duties with high quality, is analytic mind. It allows you to "filter out" unnecessary information that the customer conveys to the contractor, and on the basis of the information received, analyze the customer's activities and formalize the requirements. Perhaps this is the main quality of an analyst, because it directly affects the quality of projects being developed. The analyst must be able to keep a large amount of information on the entire project, and sometimes more than one, in his head and be able to quickly calculate the impact of certain changes required by the customer or the development team on the system as a whole in order to timely coordinate these changes and their consequences with all stakeholders. To build business models of customer processes, an analyst needs to have a high learnability. This quality is necessary for a quick study of the subject area in which the customer works. The analyst must become a "specialist" in each of the subject areas, which change with work on each new project. At the stage of formation of requirements, the analyst draws up the terms of reference (TOR) for the development of the project, which must be agreed with the customer and which will be studied by the developers.

Based on this, the system analyst must state the requirements in the TOR in such a way that they are understandable to both the customer and the project executor. For this, it is necessary to have literacy in writing texts and make as few mistakes as possible. In the process of building business models, the analyst will need programming skills and understanding of OOP. Most often, the model of a process can be represented as a set of objects, and actions on them can be represented as methods. Model objects can also have properties. Objects in models can use all OOP principles. When building system models, as a rule, the project data model is also determined.

When designing large projects for large customers, analysts face many difficulties associated with the development of technical specifications. These difficulties can arise due to constantly changing requirements, a large number of users, and other factors. All this leads to frequent changes in the TOR. Analytics sometimes have to rewrite up to 30-40% terms of reference several times. Naturally, this affects his nervous system, so the analyst needs to have considerable patience and stress resistance. Stress tolerance also useful in training users of new projects, since most users are forced to work in a new project by business organizers (customers), which they strongly resist. The analyst has to listen to a lot of unflattering words addressed to him, but he must calmly respond to criticism from users and complete his task.

Analytics tools

The main tools of a system analyst are pen, paper and pencil. For a good analyst, this is enough to formulate requirements and draw up a business model. In practice, analysts use various modeling tools that support IDEFx, UML, BPMN notations. Such tools allow you to reduce the time for building models and diagrams, as well as get the result in graphical form and in the form of text reports. Tools like these help keep project requirements under control and keep them up to date. An example of modeling tools are such applications as: Enterprise Architect (EA), Rational Rose, RUP, etc. Also, office packages such as MS Office, iWork, Open Office come to the aid of analytics.

Where to go next?

In conclusion, I would like to reflect on the development of a further career as a systems analyst. A system analyst is a versatile person who is able to negotiate with customers, set tasks and monitor their implementation by developers. His knowledge and ability to navigate in various subject areas of human life are able to assist in the implementation of duties, for example, a project manager, or manage a team of analysts on large projects. One way or another, the profession of a system analyst is promising in the IT market today.

Other blog materials on the topic "Analyst in IT".