A reasonable game development process should be like this


This article shares the development process specification, the purpose is to improve product quality, optimize the development process, for your reference.

Norms are dead, people are alive, hope that their own norms, do not be beaten in the face.

Next, it will be disassembled one by one from the above six stages.

1 Requirement Review
As technicians, they must have participated in the requirements review meeting. I wonder if they have encountered such a situation?

The product manager read through the PRD document and the participants were indifferent.

As soon as the product manager talked about a demand point, there was a heated discussion among the participants and they were all proving that they were right.

The participants were not clear about the goal of the demand, discussed the demand point with divergent thinking, and finally deviated from the direction.

If you encounter the above problems, you must not be fully prepared before you participate in the requirements review. When the problem comes, what needs to be prepared in advance?

Before review

Don’t listen to the product students say that the demand is followed up by the big boss, very important, very urgent and so on. Just ask three questions about the product:

What problems have been solved?

What indicators have been improved?

What is the commercial value?

These three issues should be clarified before the review.

After the product manager issues the prototype and the first draft of PRD, the developer should have 1-2 days (the specific time depends on the size of the project) to get familiar with the documents. Any questions can be fed back to the development manager, who will collect them and then feed them back to the product manager. The product manager will answer the questions one by one.

After getting familiar with the documentation, the developer and the development manager need to work together to determine:

Technology selection (front end / back end framework, log middleware, message middleware, database…)

Technical architecture (how components work together and how to deploy)

Prediction of technical difficulties (identify existing technical difficulties and determine solutions)

Performance bottleneck prediction (identify possible performance bottlenecks and determine Countermeasures)

Interaction between upstream and downstream systems (specify the location in the process, specify the time of interface document provision and interface joint debugging)

Functional module division (task splitting and allocation)

After the technical scheme is determined, the technical design documents need to be output, including: overall design, outline design, detailed design, interface design, etc.

Under review

Developers must take part in it. If there are unclear requirements, they should put forward them on the spot. At the same time, developers also need to think about whether the product requirements are reasonable, and they can put forward their own product opinions appropriately.

There are at least two general reviews (first draft and final draft).

After review

After the review, if it is necessary to update the technical documents, please update them in time.

The development manager should first consider the existing resources of the team and the priority of the project, and then evaluate and schedule according to the technical design documents.

The schedule template is as follows:

2 technical review
Before review

Developers must pay attention to technical design!

Developers must pay attention to technical design!

Developers must pay attention to technical design!

Say important things three times!

What is the main content of technical review?

System diagram, module diagram, flow chart design, drawing tools according to their own preferences.

Interface design, need to consider the compatibility of the interface, scalability, parameter naming to comply with the parameter naming specification.

Database design, need to comply with database design specifications, and record data table change documents.

Detailed design, need to consider the public class, public method, method definition, comply with the project framework directory specification.

Under review

Developers and development managers must participate. When it comes to overall design and outline design, architects need to be invited to participate. When it comes to database adjustment, DBAs need to be invited to participate.

There are at least two general reviews (first draft and final draft).

After review

After the review, if you need to update the scheduling document, please update the game in time.

After the schedule is determined, reply to the schedule by email, and use the standardized reply to the schedule email template.

Step by step, according to the plan.

3. Demand development

In the coding process, developers need to abide by the coding specifications of the team and strictly follow the technical solutions in the design documents. In addition to ensuring the correctness of the code logic, they also need to consider the code encapsulation, maintainability and scalability. When the technical solutions need to be adjusted in the coding stage, they need to inform the development manager in time and implement them after approval, When it comes to introducing new frameworks and technologies, the development manager also needs to be informed in advance.

Code review

Developers need to control the frequency and granularity of code submission. Within 24 hours after each code submission, they need to actively contact the code reviewer to complete the inspection, and the development manager is responsible for checking whether the implementation is in place.

What is the main purpose of code review?

Normative inspection (whether it conforms to code specification, submission remarks specification, etc.)

Robustness check (whether to fall into dead loop, resources not released, etc.)

Security check (whether there is SQL injection, XSS*F. CSRF, ultra vires, file upload, etc.)

Performance check (whether there are frequent connections to DB without cache and whether connection pool is required)

Joint debugging

The developers actively promote the joint debugging work, and inform the technical manager in time for coordination if they encounter obstacles.

Self test

After the joint debugging, developers need to complete the self-test at the same time, and send the standardized self-test report to the test team.

For example: wwwsangpi.com for projects with performance requirements, developers are required to conduct performance tests and issue standardized performance test reports.

Raise test

After the completion of the self-test, apply for the test by e-mail, and use the standardized application e-mail template.

Developers deploy to the test environment according to the release mode provided by the company’s operation and maintenance.

4 follow up test
Test case review

Developers must participate to avoid inconsistent understanding of requirements between testing and development.

Bug repair

Developers should pay attention to the bug list in time to quickly repair the iterative release. If there is a risk of delay in the test progress, they need to inform the development manager in time.

5 follow up online
The developers first confirm that all bugs are closed, and the product personnel pass the acceptance in the test environment. Then they need to actively promote the relevant teams to sort out the online dependence and order, determine the rollback plan, and finally deploy to the online environment according to the release method provided by the company’s operation and maintenance.

After the online environment deployment is completed, the product personnel and testers are informed by e-mail, and the standardized e-mail template is used. At the same time, the testers and product personnel are actively promoted to complete the online verification, and the development manager is informed as soon as there is a problem on the line.

6. Online problem review
There are no bugs in the test environment and formal environment, but bugs appear after a period of time. What kind of institutional constraints are used to solve this problem?

When the problem occurs, the developer repairs it in time, and it’s over after the repair. That’s not enough.

It is recommended to use the following template for re listing.

You can count how many specifications are used. At this time, some friends will say that there are too many specifications. What’s the difference between them and factory workers? We programmers are creative. We like cutting-edge and challenging work. We are unrestrained and love freedom

To solve this problem, first of all, I don’t deny that developers are creative, but not all programmers are creative. In real work scenarios, most programmers don’t do creative work, and there is no need to do creative work, so they must follow the standard process.

Team management and cooperation between teams must be standardized and strictly implemented.

That’s all for reference.

Recommended Today

VBS obtains the operating system and its version number

VBS obtains the operating system and its version number ? 1 2 3 4 5 6 7 8 9 10 11 12 ‘************************************** ‘*by r05e ‘* operating system and its version number ‘************************************** strComputer = “.” Set objWMIService = GetObject(“winmgmts:” _  & “{impersonationLevel=impersonate}!\\” & strComputer & “\root\cimv2”) Set colOperatingSystems = objWMIService.ExecQuery _  (“Select * from […]