Гертовская Ирина Григорьевна
Опыт в ИТ-разработке 25+ лет, работала практически во всех ролях. Занималась разработкой ИТ-систем для крупных промышленных предприятий и финансовых организаций. С 2007 года занимаюсь анализом и проектированием, организацией работ аналитиков, их обучением (от начальника отдела системного анализа до зам.директора Производственного центра крупной ИТ-компании).
Соавтор профессионального стандарта РФ «Бизнес-аналитик».
"How to avoid the trap". About impacting of non-functional requirements on the system's performance
Business digitalization, merging of business and IT leads not only to the growth of functionality of IT systems but also to criticality for a business of availability, reliability, the safety of IS. Let 's talk about how an analyst can and should influence such properties of IT systems, that is, non-functional requirements, their identification, application, reflection in project documents. Let 's look at the main classifications (international, state, industry) and scenarios of quality attributes, their application in the work of analytics. The report is based on its own experience. I will share my vision of the analyst 's work checklist to ensure the system is operational.
Immersion in a new domain, analyst checklist
Many of us are familiar with the situation: the customer received a request for a presale, an urgent task for analysts, an opportunity to conclude a promising contract, but there are no experts among the Company's analysts in this subject area. Is this a reason to refuse a deal? Or is there a way out?
At the workshop, I will share my experience, how in a few days I immersed myself in a new domain, what problems arose and how they were solved. We will discuss examples of successful and unsuccessful experience and the reasons for failures. Consider using the method of mental maps (Impact Mapping), as a way to determine the boundaries of the project and the main hypotheses created by the joint efforts of the developer and the Customer. Together, we will develop a checklist of analyst immersion in a new domain.
From scratch and turnkey
The analyst's participation is necessary at every stage of software development, from survey to implementation. At the master class, we will review the entire software development process and the role of the analyst at each stage. Let's talk about what sources of information are used by the analyst at each stage, what results are obtained and how they are applied in the future. What you should see, take into account, provide for the successful development, implementation and operation of the software. Consider the typical problem points and resolution paths. Of course, in an hour and a half, it is impossible to consider the details, but we will have time to highlight the main stages, discuss the goals and results of each stage.
Assessment of labor costs of the analyst: practice of application
The topic of the talk was inspired by discussions in close circles of analysts - is it possible to assess the labor work of analysts and clearly defined turnaround time? It will be demonstrated which assessment methods of labor costs and the dates of performance of the work of systems analysts we use in our daily practice.
This talk is not for you if you have:
- experienced analysts who are able to assess own the dates of performance of the work with precision acceptable by a project manager;
- diversified, often research works;
- innovative directions of works, mostly brainstormings and researches.
Management functionality and interface requirements related systems
Information system of a large industrial enterprise or a government department consist of several software systems. Also these software systems interact with other organizations software systems. For various reasons, changes to the software is the constant necessities of life. Inconsistent changes of software systems have a risk of stopping work the Information System and the enterprise (the organization, the government department) in whole. The report describes the sample of the management functional requirements of the automated system. We explain about changing the documents, the system operation on the documents, the user operation on the documents and the interfaces of exchanging document between subsystem. We suggest the requirements storage structure and the methods of monitoring changes in adjacent subsystems. Change monitoring allows stable operation of an organization. In additional the system requirements management makes it possible to generate project documentation.