How to become a good system analyst
Deng Lei (from 51cmm)
System analysts based on system analysts are generated from excellent programmers, and a solid programming base is a basis for the future system analysis in the future. There is no thorough analysis of the system itself, it is difficult to understand some of these difficulties. But not equal to a good programmer can become a good system analyst. Reasonable knowledge structure. Language ability, text expression ability, comprehensiveness of technology, etc. are the basic requirements for system analysts. For example, C / S and 3-layer development, if it is familiar with Netscape products, it is necessary to understand, such as Microsoft and other products, and to understand their history, development ideas, technical advantages and disadvantages, to cope with various poor chasing. Summary question. But more importantly, this is the premise you use custom technical requirements. System Analyst's Thought Global Concept is the concept that system analysts must have. If the system analyst is designed too much attention to details, it is often trapped in a quagmire on a certain issue. (93 years, my aphrographic guidelines have affected the understanding of software development in the next few years --- In the future, the computational opportunity is getting faster and faster, and write a few lines of code less write code. The most important thing is the whole; I was wrong at the beginning, some part was better, and it was also useful) System analysts had to have user thinking. System analysts should have the ability to play themselves into users, to understand what they want to deliver, think what they think, thus understanding the user's ideas and picking out a reasonable part. In this sense, system analysts can get meaningful insights to guide his development group members. The system analyst has a clear understanding of the project outcome, and guarantees that the project does not deviate from the direction. System analysts must have ideas that rooted in technology, higher than technology thinking. Pure programmers often consider the final result. When a new technology appears in the market, they are relatively small for delivery on time, and strongly hope that their plan can be built in new technology. on. Therefore, the system analyst's ideas and actions should be like a user, and it is also possible to stand in the height of technology, becoming a true user, the spokesperson between programmers. The predictive ability of task difficulty system analysts must have fast task difficulty prediction capabilities and the ability to quickly determine the composition and task division of the development group. (I will return this to my thoughts, not the ability) insects will naturally go out of wings, but their thoughts require long-term infiltration. To do this, you need a lot of thinking and learning. Design is much more important than programming. The development of the software industry, the emergence of various development tools, the programming is not a problem, and the programmer's work is aware of the existing things that others are piled up. System analysts must clearly understand that most programmers have not learned how to understand a system overall, some don't even understand programming (this is not said that they don't write code). Visual development tools plus five-flowered control, programmers can steal. (This is not exaggerated, I have been managing the management of several years, exposed to a large number of programmers) based on technology, and jump out of the framework. Jump out of the framework based on the problem of user demand. System analyst's key to trust. The most important quality of system analysts is to achieve trust, which is the key to the excellent system analyst. Mature is the most important. Mature can provide correct support for the entire project group, understand how technology can solve user needs. System analysts are prepared in various document modes, including future software variables, field naming rules. I recommend the basis for the rules set by PB, and by changing the standards suitable for their utility. Unified document management. Unified analysis software. For example, Rose (UML is too standardized, the domestic software management level is not used, but only as much as possible, your own understanding of the systematic analysis is good) The method is the show, and there is not much to say in the specific method.
I got a few books from U $ A, used for the use of object-oriented system development, "object-oriented analysis", "project management" is very good, recommend everyone to see. I have sent a glimpse of "I have a computer in China." I heard that some people (habitual). In fact, BBS was originally vented, and there was a rare article here. Since the "Venus" landed in Shenzhen, everyone is more eye-catching from the macro look at China IT industry. China IT this small tree is really not easy to grow today. Some people put forward the slogan of "opposing Microsoft Hegemony", many people call for the emergence of China's "Silicon Valley". Microsoft's success is not the success of technology, more is the success of business operations. China IT This tree can grow high, depending on the soil he rooted. The current fact is that this soil is really barren! If we don't have a big tree according to our current ideas, it is not a big tree, don't expect to knot. Quot; Microsoft, "Silicon Valley" is a fruitful fruit. If our software technology is behind the United States, our hardware The manufacturing technology is behind the United States for 20 years, our management level is in the United States for at least 30 years. The final decision of development rate is precisely our dead point - poor management level. The reason for the formation of poor management level has a deep management Background and multiple reasons. Systematic analysis work is to solve a problem, the goal is to transform a demand for computer application into actual physical implementation, which is complex in the actual surface. In system analysis process Note that the following questions may be the system analysis of the system, which may be helpful 1) What is the purpose of the system you have finished? Note that it is not a functional requirement, but the purpose. That is to build, why do you want modern construction. Consider When the system is the purpose, I focus on the ultimate goal of the system, because a system is not perfect, there is some room for the system. 2) What are the participation in the system you have finished, what is the original intention? Those people may play an important role in system construction. What kind of attitude they will do? How much affects them? One of the failures of China IT industry is "Tai Young", must have leadership, otherwise Don't think that you have much influence on them, even if you have, you should think that decision makers will affect them. In China, a technician, you are old? I am very sad. Who is in the system It plays an important role and clarify their attitude, this is critical. 3) Do you have a clear evaluation criterion? Best of the participation of all aspects of participation. I don't know if this is wrong, in the system construction Previously, for your programmers, there must be at least two different evaluations for your leaders. 4) What is your system design idea? Can you get all recognitions. If you are, the leadership, the programmer is used Boots, the best way to get recognition is to let them recognize their own ideas. (I try to do this, but doing bad, system analysts must learn to be smashed, tolerated) 5) You are designed and developed in the system Does the person know? Where is their specialties, is it willing to cooperate with you? Why? Do you have enough influence? Software has to develop to a certain degree, not programming, not mathematics, but management.
