Development process Steps

That depends on your project manager is what level, if is responsible for customer contact communication, internal supervision and control progress is able to do good internal and external communication, both sides can coordinate well on it. If you want to go deep into project management, then you must be familiar with the whole process of software development projects, what stage to do, how to do, who to do, time, quality, progress three balance. Not a perfect project, because there will always be flaws, not too pursuit of perfection, user satisfaction, moderate quality of the project is good. Some understanding of the software development process to share.

1, first set up the project plan, the original plan is milestone nature.

Can be set by the waterfall model, the milestone is mainly for the requirements review, design review, after code development and unit testing integration testing, deployment is a very important milestone, the average user will expect the system to use the test run time (also known as the user testing phase)

2. Demand Development stage:

How to write good demand is crucial, how to learn to develop the needs of the classic "demand Engineering" the translation of the book, not very thick, but need to understand why do better, this need to practice experience to exercise their own. If there are project members, you can do the requirements together, this stage for business understanding, analysis, how to carry out research and writing, business flow diagram description and the ability to document editing has a lot of requirements. Generally divided into "user demand Specification" and "Requirements specifications", small projects can write a "Demand Analysis report", "User demand Specification" is described in the user's language, so that users and development team to achieve a consistent understanding of the requirements, "Requirements Specification", is the user needs analysis, The ability to form a system that truly provides user-interoperable documentation, which is an important baseline for post-design and code development.
In addition, to understand the needs, to come up with user UI and user communication is also a more important means of demand acquisition, although this belongs to the scope of the design

3. System Design Stage:
The overall architecture of the system, combined with the requirements of the user on the system environment, the development language and the running network hardware, to identify the development tools and so on, the application system relationship to the architectural design, through the requirements phase of the user's analysis of the classification, using a graph to describe the users and subsystems or modules of the global view, and other systems. That is to clarify the boundary problem of the system.
In addition to the high-level architecture design, the design of the network topology diagram, as well as the system deployment diagram. The most important part of the summary design is the sub-system, the module reasonable division. The name of the module will largely become the user's main menu, how to use the user's perspective to get more clear subsystems and modules is very important.

4. Code development and Unit testing phase:

This stage generally needs to improve the waterfall model, similar to the development of the fall, the module is divided into reasonable division, the project master plan of the code development testing phase divided into multiple time periods, each time period includes code development, unit testing and integration testing, this phase also needs to be tracking control requirements changes, if the requirements are changed, Then you need to keep the requirements and design documents back up. The advantage of fall generation development is not to let the code development phase pull process, not to do a timely self-examination, careless to the time of submission, but not the user wants, and may not be what they want.
The important responsibility of the project manager is to control the progress, to identify risks early, and to come up with good prevention and solution measures. Reasonable arrangement of the task of the development team, timely scheduling and convergence of the task, you will feel very artistic, this has to experience. In addition, focus on the situation of the project team, maintain a high level of combat effectiveness, timely detection and can encourage the team to work together towards a goal.

5. Test work:

Testing is a very important part of the project, how to test, how to accurately test, how to effectively test, how to cover the test, time, manpower, experience relate will have a restriction. Advanced testers are able to analyze the various test points of the system, participate in the requirements and design phases, learn early how to test, and write test cases.

6. Document work:

Documents are also important in project development, unless you think the code is the only outcome of the project, then you throw away the document, everything is in your head, and as the team goes, part of the project takes away. Code development In fact also requires documentation, code is the result, code comments are results, module development files are also important results, because the programmer in the development of the logic is how, for the future to check the problem is very useful. Unless your system is designed to be a method, a class, and the code logic is well designed, then the programmer codeing.

7, QA is the quality assurance of the project process:

Some companies. QA and test synthesis a post is called a qa& tester, or is called a QA officer. QA is the whole process of monitoring the project, independent of the project. Supervise the project manager to submit the relevant results in each project milestone, and the warehouse to form a baseline.

In simple terms:

1. Planning Phase: Development plan, Quality plan, test plan
What documents need to be produced and what tools are used?
2. Summary design phase: Requirements Analysis, summary design
What documents need to be produced and what tools are used?
3. Detailed design phase: detailed design, partial coding
What documents need to be produced and what tools are used?
4. Coding test Phase: coding, testing and reporting
What documents need to be produced and what tools are used?
5. Completion stage: Operating manual, user manual, maintenance instructions
What documents need to be produced and what tools are used?

Development process Steps