Ushurova Tamara
Начальник отдела аналитики и проектирования - РТЛабс
Moscow, Russia

Образование - инженер информационных систем и технологий.
В аналитике с 2013 года.

Talks (3)
  • 13.12.2019
    The Analyst as a Physician for a System

    Analysts are not psychics: they are not able to foresee all the nuances in the system’s evolvement. I would compare analysts to physicians who diagnose the state of the systems by symptoms, give treatment recommendations and monitor their further functioning. 

    In my talk, I will explain how to identify symptoms of deviations in the system functioning and interpret them correctly. I will discuss the anchor method that helps to detect problems quickly and to reduce the maintenance cost. I will tell you how analysts can implement this method in their team, as well as convince developers and testers of its usefulness. This will help to bring the processes of systems development and maintenance to a higher level and to prevent further "diseases".

    • Average
    • 40 min
    • Analyst Days / 11
  • 27.02.2019
    Requirements Management when Working with a Remote Team

    For many companies, working with a remote team has become a common practice. However, when organising such kind of work, the requirements management stage is often neglected. It should be remembered when working with a remote team, the requirements management process does not disappear, however, it adjusts slightly.

    In the first part of my talk, I will tell you how professional books and articles on specialized resources advise you to manage requirements when you work with a remote team.

    In the second part of my talk, I will share our experience in organizing the analyst’s work with a remote team and demonstrate you how the classical process of requirements management (RUP) changes in this case. Moreover, I will show you a set of tools that can be helpful in this respect, and tell you how to provide remote access to requirements management tools.

    • Average
    • 40 min
    • Analyst Days / 10
  • 27.09.2018
    Requirements Management with Enterprise Architect

    Every system analyst knows what requirements are, where they come from, what kinds of requirements exist, how to collect and analyse them. Unfortunately, requirements management is often confined to these aspects only. In fact, requirements management is needed until the customer accepts the product.

    I’ll present you a set of practices, which we use in requirements management. I’ll tell you how to record requirements collected, their estimation and distribution of resources, how to create patterns on the basis of common requirements, how to track changes to requirements and what should be done to prevent losing requirements in the process of engineering.

    Then I’ll show you the examples of how to apply these “analytics lifehacks” in Enterprise Architect. This tool allows establishing the connection between the documented need of the customer and the function that implements this need, via connection with the formalised requirement. I’ll outline the advantages of EA. 

    • Average
    • 40 min
    • Analyst Days / 9
To leave a feedback you need to

Chat with us, we are online!