Сейчас – ведущий архитектор, руководитель сектора архитектуры
В прошлом – разработчик, аналитик, РП
Стаж в ИТ: более 15 лет
В качестве архитектора – 7 лет
Decomposition of a system in practice
A system analyst often has to be a bit of an architect, including decomposition an information system into some parts: modules, components, subsystems.
At the workshop, we will analyse what criteria and principles can be used to ensure that the chosen decomposition at least does not complicate further design and architecture, and we will work out these criteria with examples.
Something about requirements which change everything
Nowadays the software development lifecycle never stops. Customers generate new needs, analysts gather new requirements and developers implement it. In such situations, the probability that every new requirement will change an architecture increases dramatically.
We will discuss why some requirements can be implemented with two strings of code only while others lead to "Seems we should buy another 3 DB Servers"? Why some change requests are "that's OK", but others like "We'll all die!!!". Will try to understand together and discuss how to avoid it.
Four rules for archaeologist: how to dig out an IT system
There is an information system. It works, users are satisfied, the customer is satisfied. The team is at least not disgusted.
And then: someone quit, you need to unload the team a little, or the customer asked for the development of the system.
Then you - an analyst - appear as a new employee - in exchange for another, or a new member - now you are part of a team.
What is known about the system? Are the schemes and processes described? Is it described how the system works and what each part does? Is it reflected what surrounds the system, and how is the environment connected to the system?
If practically nothing is of this and you have nothing to rely on - you should be here.
If you do not know how to get it all, I will share our experience. If you know, I will listen to your comments with pleasure.
As a result, you will learn the 4 rules of the archaeologist of information systems and how to apply them at the excavations.