My opinion on the process and management of project development

With the increase in working life, we are responsible for a function from the outset, and then to the data dictionary and framework design for a module. To be responsible for the overall system requirements review and architecture design. This all along witnessed the growth of the procedural apes. But when we become an architect, or a project manager, we find that the success of a project involves a variety of problems and risks. Whether the system itself to be compatible with the rapid development of the business form, or due to personnel factors caused by the project delay, or the system code is bloated or difficult to maintain, but also a new face confused. So below, share, project process management I see.   I. Overall project flow     1, requirements review and validation     requirements: PD organizes requirements and puts them into a resource pool of requirements. Determine the functional requirements of this issue, and begin the requirements review, the requirements of the review, to enable technical staff to fully understand the cause and effect of this demand, role, objectives and the entire process. Output: This stage is mainly for PD output related PRD and demo, to preach the demand, and record questions and difficulties.      2, module process documentation     requirements: The closed-loop business process for the entire module is written around the core of this iteration. If you have complex logic, you need to draw a use case diagram, collaboration diagram, and so on.     At the same time, to give the module's non-functional requirements, such as: call volume, daily average increment, the number of visits to wait.     Output: Domain model, development module frame composition, technical frame composition, Division of labor (which module each person is responsible for)      3, detailed design and review         (1) Concept mapping: Extracting some concepts of the iteration of this module.         (2) frame design: The core of this iteration, the expansion of the concept of the module, not only to complete the module of this function as the main theme, but also to consider the future of the system, the module's usability, extensibility.         (3) Database design: Database design should strictly abide by the database paradigm, and also around the system to be extensible.         (4) What interface services need to be called in each session of functional refinement and research.　　　        (5) The mapping and definition of the front and back end transfer objects, and the final review of the front and rear end. Output: Technical frame composition, database association diagram, etc., the unanimous review passed, the formation of a complete document.      4, encoding       (1) Build core framework code around the core of the module (problems can be discussed with each other)       (2) Encoding and feature implementation.       (3) interface annotations, complex logic annotations.      5, testing             Requirements: test phase, according to the code logic, write each case related test cases and unit tests.　　　Change coverage must not be less than 80. Output: test case documentation and unit test TestCase.       6, pre-release preparation and release           Requirements: Check the Code detection tool, the quality can not be less than 35 points, the line of the test coverage must not be less than 60. From the development------------------the release phase, which requires verification and log review.   NOTE: Do a good job of regression testing before pre-hair (test with each iteration of the test case and unit test) to prevent the online functionality from being affected.       7, online problem repair and operations             Requirements: (1) After the release of the issue, the need for urgent changes to deal with, do offline and pre-release verification, published online. At the same time, the causes and consequences of this problem are recorded on Lark.                       (2) Schedule time, daily check your responsible module and overall system operation, found that the problem was thrown in time.          II, code quality and review      requirements: next week after each iteration, Take an afternoon of code quality and review (PMD detects most code quality issues), including whether:      (1) code structure is reasonable and can be better implemented. (Structural angle, method abstraction, JVM stack memory footprint, etc.)       (2) What's not in the code   three, project management project management points are divided into, time control, risk control, fill awareness, results and goal-oriented four points:    Time Control: &nbsp     (1) The entire project process is divided into requirements, design, development, testing, implementation phase. According to the complexity of the requirements, the team's overall ability level, research responsibility to predict the iteration cycle.       (2) Once the time has been fixed, it will be implemented in strict accordance with the output of each stage.      Risk Control:      (1) unforeseen circumstances or progress risk. Need to be exposed in a timely manner to risk causes and risk issues. and to carry out relevant coordination and communication, fill awareness.      Awareness:      (1) Project risk determination, each member has its own strengths, found that the impact of the progress of the problem, included in their ability to help each other speed up, catch up with the project progress.      Results and goal-oriented:      (1) Quality and quantity to complete the requirements and the iteration of the module.       (2) Optimize review and supplement, so that everyone can know the logic of each other's modules and the system-wide logic.       (3) Summary of issues and skills summary.       (4) Consider the development and expansion of the whole system or product from the aspect of the whole system and the business map.      Of course, the reality may be brutal, and time may be urgent. In many cases, we will shelve some of these processes for a variety of reasons. But the norm determines the long-term risk can be controlled, if there is time must be necessary to fill in, this is responsible for others, but also responsible for themselves.