I used to know that there is a development method in system analysis: prototype development, although I know it, but I don't have any deep experience; some time ago, the author had a further understanding of it because he wanted to design and develop a user-defined platform.
When we are working on a project, when the business participants and business requirements are clear, it is easier to do system modeling, design and development later. But last time I happened to encounter a situation where the business participants were unclear and there were no business requirements, and I was asked to find requirements from similar software. Not to mention how depressing it was. In the end, I had no choice but to develop a simple software prototype based on the vague requirements obtained from similar software and some of my own ideas; after the software prototype development was completed, it was directly sent to the planning and R&D colleagues to collect requirements and user operations. Experience, and then iteratively improve on the basis of the software prototype step by step.
Seriously, but I didn't realize that this kind of development is prototyping until I read books on it. Thinking about it, if you know more development methods, if you don't have that kind of practical experience in the project, you really only know them.