Some graduates or non-IT industry people want to know a real development process and share my personal experience with me for reference only. It is not a factual standard covering the whole industry. The boss or Party A is a real initiator of the demand and a dreamer of the basic idea. The product is responsible for specialized demand sorting or effective evaluation and refinement, and the design is the upstream of the front-end, the front end is the downstream of the design. The purpose of the design is to professionally process the macro thinking results of the product, because according to the general habits, the final result of the product is a prototype diagram, and the prototype diagram can be understood as a design sketch, for real users, this sketch is too simple or does not meet the operational habits of use, so the designer needs to perform professional processing, such as color matching, layout separation, sometimes there is also a part of interaction work, setting the user interaction with the page booking process, someone asked, Do you not need to design it? The front-end can not write pages directly, but it also requires designers to make a picture. Because there is a concept of cost risk control here, because in the early stage, especially in design, subjective feelings are greater than rational thinking, the results are different every day, therefore, designers need to digest the misunderstandings brought about by this part of subjective feelings. In the end, in some scenarios, it is easier for designers to change diagrams than to change codes. The designer's result is a PSD file. It is the result of multiple layers stacked together, and the front-end work result HTML page is the effect of many layers, organic process of HTML organization. The front-end sends the converted HTML to the downstream server development engineer, or the backend development. This html contains some interactive JS files. In general, the front-end is a leading position. Some companies also enlarge their front-end responsibilities and are responsible for the development of the entire front-end view layer page. Such good and bad information has already been discussed in the previous article. In the past, the basic process was to lead or Party A to propose the requirements, analyze the requirements of the product, draw a prototype Diagram Based on the requirements, and then generate a design draft based on the prototype diagram. After the design draft Team reviews, the team submits the static pages to the front-end, and then submits the static pages to the design review. Then, the team submits the static pages to the developers for Dynamic Data addition. After adding the product, release the test environment. After the product test lead reviews the environment, directly release the product environment. Or perform version iteration.
This is the entire design, development, and deployment process. According to the previous section, the soul in all the previous procedures is the original requirement. However, as the objective conditions change, the thinking and understanding may be different, so documents are generated, document is the soul of the entire process. The product is the creator of the documents in the entire process. Because the product is the most open to original requirements and has a more profound or professional understanding of the requirements, he will have a document. This document needs to be delivered to the design for reference during the design process. Another document read by the front-end. Interaction designers generate interaction documents. Generally, companies that do not have Interaction designers are interaction documents from products. Some interactions are not complex, so there are no documents, just emails. Sometimes, if you don't want to send this email, you may find it the simplest original thing. If you don't have any files or emails, you won't be able to perform a back-to-back test. The product document indicates the page flow or data trend. The interactive document describes complex page interactions or various interactions between user forms and users. The other two are the requirement documents issued by architects or project managers. The requirement documents are the historical background of the entire project, software and hardware requirements for system development, or version information. The other is the interface document provided by the server engineer, which includes some request types, the number and key name of parameters passed, and the parameter name conventions returned by the server, these documents are the soul of development and the standards or basis for future testing backtracing. Http://www.cnblogs.com/daoshi/p/3751922.htmlcreate the front and back of a website (origin, domain name, cloud platform, filing, CDN, etc.) (1)
Frontend development QQ group: 159758989. chatting is prohibited. If you are not happy, do not enter ~!
Our general frontend Development Process
