Standardized product development process

Understand product and design, participate in demand, interaction, and visual meetings, and understand product design and project members. Understand the devices and platforms for the product. Understand product compatibility requirements and whether responsive design is used. Understand the technologies used by the product (WEB, desktop, APP, template language, and hybrid mode ).

Development preparation

Understand product and design

Participate in requirement, interaction, and visual meetings to learn about product design and project members.

Understand the devices and platforms for the product.

Understand product compatibility requirements and whether responsive design is used.

Understand the technologies used by the product (WEB, desktop, APP, template language, and hybrid mode ).

Raise questions and opinions

Raise questions and opinions in interactions or visual meetings based on technical requirements.

Raise possible problems (technical implementation problems, performance problems, etc.), negotiate solutions (such as Elegant degradation), and reach consensus.

Propose application scenarios of existing new technologies in products to assist in product innovation.

Technical Research and Training

Whether technical research is required to identify possible risks.

Conducts technical research, generates technical demos, displays demos, and feedbacks the survey results.

For technical research, consult experienced front-end engineers or front-end technical teams.

If you have insufficient experience or new employees, you can apply for training.

You can submit difficult technical issues to NEC, which will help you solve the problem.

Understand NEC, especially code specifications and technical demos.

Budget manpower and time

Budget manpower and time based on project time requirements and workload.

Budget development cycle and phased output.

Remind the demander to create a project in the project management platform and add project members, create SVN and set member permissions.

Development process

Responsibilities and tasks

Determine the person in charge of a page engineer, who will be responsible for overall planning, allocation and coordination of the entire page development work and primary development responsibilities.

Confirm that the interaction prototype or visual effect has been finalized before development.

If parallel mode is adopted (both visual design and page development), the interaction prototype is finalized (after the visual effect is finalized, the page engineer adds details) to start allocation.

Distribute by page type. the same type of page is assigned to the same person.

Everyone needs to understand the public elements of the page (the same or similar parts of multiple pages). one public element is assigned to only one person, and each person completes the "extract and strip" process while completing their own pages ", you may need to understand the "classification method specification ".

Because the image cannot be merged and resolved using SVN, you need to allocate the image as a whole.

Create a subdivided development task on the project management platform, and fill in the task details and time. if there is a relationship between tasks, set the association or subordination.

Page development

Create a front-end Directory, including the "page development" directory (such as js, css, html, and img) and "extract and strip" directory (such as demo ).

Use the NEC framework to create front-end files, such as css/*. css, html/*. html, demo/grid.html, demo/module.html, and demo/unit.html.

Use the NEC code library and plug-ins to efficiently develop pages.

Maintain good communication with interaction, visual and other front-end engineers or back-end engineers.

Feedback questions and suggestions in a timely manner: confirmation of results questions, supplement to missing states, recommendations for Elegant degradation, and descriptions of behavior structures.

If the parallel mode is adopted (both page development and JS development), the final interaction prototype shall prevail. JS development engineers can develop the business logic layer in parallel, after the page is developed, the UI layer is embedded.

Extract and strip

The layout (grid), module, and component (unit) of the page are extracted to the corresponding HTML file.

To avoid repeated work, you can view the page elements at a glance. when adding elements, you first need to check whether the directory has been implemented or has similar implementations, but only need to expand it.

The HTML files in the "extract and strip" directory and the HTML files in the "page development" directory must be maintained simultaneously.

Development and output

Joint debugging for self-testing

Update, merge, resolve conflicts, and submit.

Perform comprehensive multi-device and compatibility tests on your code.

If you find any problem with the code written by others during the self-testing process, give feedback in a timely manner.

Submit for acceptance

When there is a phase output, the page engineer submits the page to the designer for effect acceptance.

The results acceptance mainly checks the visual effect conformity (size, position, color, cut graph, etc ).

If necessary, you can submit it to experienced front-end engineers or front-end technical teams for code acceptance.

Code acceptance mainly checks compatibility, HTML specifications, and CSS specifications.

Handover instructions

After the acceptance is completed, inform and hand it to the subsequent development engineers for template-layer development and behavior logic development. the engineers on the page should explain what they may need to pay attention to or explain the code.

If your work needs to be handed over to others, you also need to clarify the overall architecture deployment and Code explanation.

Summary and sharing

The sharing content may include: architecture thoughts, collaboration experiences, use of NEC experiences, device features, new technology applications, research presentations, problems encountered and solutions.

Sharing objects are not limited to interaction, vision, front-end, and all interested people.

You can submit the technical demo in the summary to NEC. we will release it to the code library to help you accumulate these technologies and share them with others.

Change maintenance

In principle, development and changes are not allowed without any change in demand or design.

The reasons for the change should be understood before the change, and subsequent development engineers should be notified in a timely manner after the change.

If the version number of a static resource is not automatically updated, you may need to manually update the version number.

Change and maintenance use all the procedures in this specification, that is, you may need to repeat the previous procedures.