Zhong Xin Tech-Zhong Xin Tech

1. Develop the project plan first. The initial plan is milestone. 2, requirements development stage: how to write good requirements is very critical, do software call 1wugrilled 1133s7444. How to learn to develop requirements can go to see the classic "requirements engineering" this translation book, not very thick, but need to be able to understand why it is better to do that, this needs practical experience to exercise their own. If there are project members, they can work together on requirements. In this stage, there are many requirements for business understanding, analysis, how to carry out research, text expression, business flowchart description and document editing ability. Generally divided into the user requirements specification and the requirements specifications, can write a small project the demand analysis report, the user requirements specification is described in the user's language, let the user and development team for requirements agreed understanding of the requirements specifications, is the analysis of user needs, form a system to have the function, This is the document that really provides user interaction, which is an important baseline for later design and code development. In addition, to understand the requirements, the user UI and user communication is also an important means of requirements acquisition, although this belongs to the category of design 3. System design phase: < p > system overall architecture, combined with the user on the system environment, development language, and operation of network hardware requirements, determine the development tools, etc., to the architectural design of application system relations, on the analysis of user classification, through the requirements phase graph way to describe users and a global view of the subsystems or modules, as well as the relationship with other systems. That is, figuring out the boundaries of the system. In the summary design, in addition to the high-level architecture design, the network topology diagram and the system deployment diagram also need to be designed. Summary design is more important is the subsystem, module for reasonable division. The name of the module will largely become the main menu for the user, and it is important to get a clear view of the subsystem and module from the user's perspective. This stage generally need to improve a waterfall model, similar to drop generation development, divide the modules in a reasonable manner, the project master schedule of code development testing phase is divided into several periods, each time period include code development, unit testing and integration testing, this stage need to tracking control of requirement changes, if demand is subject to change, So get the requirements document, the design document back up to date. The advantage of downgeneration development is not to let the code development phase of the process, not timely self-inspection, accidentally when the time to submit, but not what users want, or perhaps not what you want. The important responsibility of the project manager is to control the schedule, to identify risks early, and to come up with good preventive and solution measures. Properly arrange the tasks of the development team, timely task arrangement and cohesion, you will feel very artistic, this should be realized by yourself. In addition, pay attention to the situation of the project team members, maintain high combat effectiveness, timely find and can encourage the team to move towards a goal. Senior testers can analyze the test points of the system, participate in the requirements and design stages, understand how to test in advance, and write test cases. Documentation is also an important part of a project. Unless you think that the code is the only result of the project, then you can get rid of the documentation. It's all in your head, and when the team leaves, you take a piece of the project with you. Code development actually also needs documents, code is the outcome, code comments is the outcome, module development file is also an important outcome, because the programmer in the development of the logic is how, for the future query problem is very useful. Unless your system is designed to the extent that methods, classes, and code logic are designed, then programmers should CODEING. 8. QA is the quality assurance for the project process. Some companies combine QA and test work into one position called QA& Testers, or just QA people. QA is the supervision of the whole project process, independent of the project. Supervise the project manager to submit relevant results at each project milestone to form a baseline.