Today, I have to sort out the work and sort out the documents. I found a better one while surfing the Internet. I wrote it down here, and it will be used when I have to write in the future.
Author: wei wu
Link: https://www.zhihu.com/question/499257000/answer/2227213141
Source: Zhihu
The copyright belongs to the author. For commercial reprint, please contact the author for authorization, for non-commercial reprint, please indicate the source.
1 Hold a demand analysis meeting : the product manager will talk about the demand, and the relevant development engineers will understand the demand first, and then the meeting will end.
2 Engineers analyze the requirements , as does the front end. See how to achieve the requirements, what framework to choose, etc. The point is to find out unreasonable requirements, and then communicate with the product manager how to change the requirements (usually it is not easy to achieve, and the product manager may not understand, such as requiring the background color of the webpage to be the same as the color of the user's mobile phone case)
3 After analyzing the requirements, start to formally enter the development process , make development plans , when to complete what functions, etc. Front-end engineers should pay attention to the work plan of UI designers and coordinate with each other. Also pay attention to the interface development plan of the back-end engineer, and cooperate with the joint debugging time
4 Front-end engineers are developing abstract functions (those that do not require UI diagrams), while waiting for UI diagrams, back-end interface documents and joint debugging notifications. UI images are generally blue lake or sketch, photoshop files, and some companies cut the images to the UI, so it may be necessary to communicate with the UI about the effects and how to cut the images
5 After getting the picture from the UI, you can start to do interface development , write html, css, interface interaction (mouse event, touch screen event, etc.)
6 The backend has an interface, and the related functions of the interface can be jointly debugged
7 Self-test : run the project by yourself, check whether the development is completed and meet the required effect according to the requirements and UI diagram
8 Testing : Cooperate with the backend to output the testing code. This step sometimes also communicates with the backend in step 2
9 Modify the BUG : Change it after receiving the BUG, and then continue to test
10 Go-live : The test results verify that the project has been able to run stably, and output the go-live code. Similar to step 8, the requirements need to be communicated with the backend. For example, interface address modification or something
11 Maintenance : After the project goes online, if a BUG is found, it must be modified, and then go through the 7-10 process