Bugs of systems design can be avoided
It is always good to study the best practices of designing systems and try them in your projects. And it is even better to know about possible pitfalls.
It is signs that something went wrong during the designing process:
- the team asks a lot of questions about the problem statement;
- developers find unrealizable requirements and ask to change them;
- testers find many unreported cases in the testing process;
- a change request for functionality comes from the customer, and you need to add "crutches" to support it.
The talk is devoted to the bugs of design that I encountered in my practice, how to avoid them, and how to take them under control. It will be helpful for both systems analysts working with systems architecture design and business analysts collecting and describing development requirements.