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 will often fall into the unclear queen on a certain issue. (93 years, my paper guides the teacher's discretion, I have affected the understanding of software development in the next few years - the future computer is getting faster and faster, write a few lines of code less write code is not critical, the most important thing is the whole; It's wrong, some part has a good time, and it is also useful) System analysts must have ideas for users. 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 is not deviated. 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 in management work, and I have exposed a lot 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 become a standard 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 systems "," 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 "against Microsoft Hegemony
"The slogan, many people call the emergence of China's" Silicon Valley ". Microsoft's success is not the success of the technology, more is the success of business operations. China IT tree is growing high, depending on the soil he rooted The present thing is that this soil is really barren! If we press our current ideas and law, it is not a big tree, don't count on it. Quot; Microsoft, "Silicon Valley" so fruitful fruit . If our software technology is behind the United States ten years, our hardware manufacturing technology is behind the United States for 20 years, and our management is backward in the United States for at least 30 years. The ultimate decision of development is just our death - poor management level. The reason for the formation of poor management level has a deep background and a multi-faceted reason. Systematic analysis work is to solve a problem, the goal is to convert a demand for computer application into actual physical implementation, which is complicated in the actual surface. In the system analysis process, pay attention to the following issues, which may be helpful in system analysis design work. 1) What is the purpose of the system you have finished? Note that it is not a functional requirement, but purpose. That is why we want to build, why do you want modern construction. When considering the purpose of the system, I focus on the ultimate goal of the system, because a system is impossible to perfect, and there is some room for the system. 2) What are the participation of the system you have finished, what is the original intention of all aspects? Those people may play an important role in system construction, what kind of attitude would be taken? How much influence do you have? One of the failures in China's IT industry is that people "too young" must have leadership support, otherwise they will end. Don't think that you have much influence on them, even if you have, it is necessary to think that decision makers will affect them. In China, a technician, do you have a few a few? I am very sad about saying this here. Whoever plays an important role in the system and clarifies their attitude, this is very important. 3) Does your system have a clear evaluation criteria? It is best to consider from all aspects of participation. I don't know if this is wrong, before the construction of the system, the programmer for you, there must be at least two different evaluations for your leaders. 4) What is your system design idea? Whether it can be recognized by all aspects. If it is high, the leadership, the best way to use the programs, is recognized, that is, let them recognize their own ideas. (I try to do this, but don't do it, system analysts have to learn to be smashed, tolerated) 5) Do you know the personnel involved in system design and development? Where is their special length, is it willing to cooperate with you, why? Do you have enough influence on them? The software has developed to a certain level, not programming, not mathematics, but management. 6) Is your system development plan perfect? Does your plan have a clear stage? What should I do at any stage? How to evaluate this situation? 7) Are you familiar with the system development methods and tools used? Is your partner familiar? In fact, it is not every kind of tool to use, and it is not necessarily to master. Remind one sentence, when you do the program, you can do not rely on a programmer, you have no trust in before the programmer, because from this programmer will be larger. I am not in use in the company.
