Very often It happens that software system development process looks like the following chain: "analyst create specification (a.k.a. SRS or FSD) - developer creates code - repeat until the production software is ready". We put an architect in this process not even beside but in the middle. During this talk, we will discuss:
1. How and why we did that.
2. Which problems were led but which were solved.
3. How we solved the ones which were led.
The talk will be interested for an audience including all IT persons (analysts especially) who involved in the custom development projects where developers don't read specifications, analysts don't understand developers, the architect draws presentations and swears at everyone, and a manager "can't hold a candle to" and doesn't understand when this stops.