I did not expect the article "upgrade from software developers to system analysts must change two inconspicuous habits" published some time ago.ArticleThe original Article address is http://blog.csdn.net/yzsind/archive/2010/02/02/5280056.aspx. There are some things to be done with a single question, and more people refer to the title party. Here I will make some small supplementary remarks:
1: This article does not show that you can become a system analyst without having changed these two habits. I hope some friends will not misunderstand this article. The system analyst has many important things to do, one of them is to ensure that our products meet the customer's needs, it is very important to go deep into the customer's business needs.
2: I have worked in many positions and I am also a developer. During development, I also enter the data at will and the border test data. However, when submitting the data to others for verification, I must ensure that I have tested the valid data, if effective data is not tested, and some boundary tests are performed, it is an absolute inversion. Every time I check the functional modules developed by the project team, I try to follow the details in the article. This is my personal experience of growth, it also shows some small suggestions that common developers cannot improve in terms of business analysis.
3: it is no longer important for the title party. The question seems exaggerated. I mainly want to remind some developers, especially the developers of information software, why are we always so passive in front of customers that customers need to change their needs? Of course, there are some project management problems or customer reasons, but if we know ourselves and ourselves, the risks of projects will be much lower.
4: software developers have many career directions. system analysts are only one of them, so it is certainly unacceptable. If these two ideas are unacceptable, I think you can choose an architect or a project manager, or a common developer forever.