The understanding of the front and back separation mode of website development

Before and after the separation of the development model, originally felt nothing strange, in the recent participation in a large project, let me have a deeper understanding.

The development pattern of the front and back end separation: System Analysis phase, the department and front-end developers agreed on the page on the required logical variables, into the functional development phase, front-end developers to the front page structure, style, behavior layer code writing, and according to the agreed variables, logic rules, to complete different situations show different performance. The backend developer, by convention, gives these variables meaning and provides the data needed for the backend interaction.

I used to play the MVC Development Framework in PHP, but not in such a large project practice, so the process exposed some problems, it also shows that there is a certain gap between the reality and the ideal.

The following is a record of the problems encountered in the project:

A. Lack of understanding of interactive whiteboard, such as: implementation of Ajax to achieve large amount of data interaction, no timely suggestions for improvement

B. The agreed-upon phased output is very fragile, and there are times when new things and changes appear in the development process, which leads to a tangle of the back-and-end collaborative development.

C. The project process, due to the early stage and the demand side, the designer, the Department of Communication is not enough, leading to the development process to find a lot of consideration of the insufficiently comprehensive place

D. In the process of project development, the ratio of the resources in the development of the front and back end is quite disparity, in the late frequent demand change, the front-end has been in: barely cope with the state

Visible, the above mentioned above, many are communication and collaboration on the issue, the following is a summary of the initial experience, I hope that the front-end development engineers for reference:

communication: before the project development, as far as possible proactive and system analyst and interaction designer to communicate more, to determine the interface between the interactive and server-side exchange of data interfaces, methods, formats, etc., so that the front and back end of the agreement more plump. Because the fuller she is, the less tangled she will be in the back.

A. Forward design, participate in the early interactive design of the discussion, to understand the design, backward development, to understand what the backend development engineer is concerned about, do not want to care about what is worried about, learn to stand on the other side of the angle to see the problem

B. You must confirm the various error scenarios in the interactive whiteboard and the completeness of the error prompts, requiring the background developer to complement the backend error scenarios that the interaction designer is not aware of, and ask the interaction designer to give the corresponding hint copy

C. Clear interactive effect, which is to be implemented through Ajax, and with the developer agreed to the data interface, manner, format, etc., and to confirm the failure of data interaction, whether there is a copy hint, if not, the initiative to find interactive designers to supplement this kind of scene of the copy tips

cooperation: The function development process, needs to establish a common debugging environment, facilitates the front and back end schoolmate coordinated development.

A. Some data interface APIs and data formats may be identified in development. You can have an interface document. If you all know that you are familiar with the business rules, you can identify them individually in development. In any case, the interface document is required. It records the abstraction of the business at the system level. Interface details can be perfected in development.

B. There are always some files that are modified by the front and back end developers. These sensitive files, both before and after modification, should be known to the backend developers. And to develop the habit of update before edit. If there is a conflict, it is best to resolve it together or to inform it in time. Avoid conflict again.

C, the project in the end of the resource ratio should be appropriate, 1:10 of the resource ratio to push the front and back end of the development model is still relatively difficult, personally think 1:3 is relatively moderate ratio.

Due to the resource ratio of the front and back end, the system analysis stage is not detailed and so on, in some large-scale projects, the separation and development model for some adjustment, said that some of it is not, but this should be the most consistent with the current situation of the development of the front and back end of the model, with the development of the vision to look ahead, the front is growing, There should be a satisfactory answer to the questionnaire!

In the functional development phase, because the project is relatively large, the general decomposition function, so it is difficult to provide a relatively stable function of the front and back end of the common debugging environment, plus the resource ratio is too wide disparity, so the proposed functional development is not stable this stage, the front-end development resources to assist the development of the role of entry, By the backend developer's reference frame the data type and the interface provide the data and the nesting page logic, when the function development is relatively stable, the front end developer carries on the acceptance to the nested foreground content, at this time, the debug work of the front and back end development can operate concurrently.