In the past few days, I was busy with a project, the time was tight, and the requirements were also high, so I stopped watching the "System Analyst Tutorial".
In tensions, I always want to use the content of the practical system analyst. The development process of this system has not changed in the development process of previous projects. My personal development process is almost the same. It is also a first write code, then organizes the information, but I think I am more thinking than the previous ideas. .
For example, although now in the case of the specific function of the system, I am also writing code, but I mainly written the code in the interface, my purpose is only one, that is, the functional idea of the system is to users through the programming interface Expressed, then obtain further feedback from users, the feedback is used as the next basis. In this process, if it is before, I may consider the data processing of the background. This kind of thinking comes from the study of prototype development.
When dividing the system function module, I will first give me a preliminary program according to the department manager, listen out all objects, first identify the relationship between the object, then analyze the process of data according to the relationship, then analyze the data Process, analyze the function module, then analyze 4 different operating levels according to function modules. Although the logical relationships of every step made are not very strict, I feel that my idea is still very clear, this idea comes to the "data-centered" concept in system analysis.
The above is a little experience, and there is also a lot of indifferent places. I hope that my friends have advice!
