A, the project manager and the company's decision-making communication to determine whether the demand is not sufficient manpower and feasibility to achieve, as well as the existing product dependencies.
B, the company's decision-making and marketing/planning Department of Communication, the process will be very adequate, and is repeated, long-term, it is committed to the user's perspective on the needs of the refinement and decomposition.
C. The marketing department needs to communicate with the project manager on the details to determine if the requirement is feasible to achieve.
D,e,j, this is the entire product architecture design process, is divided into the UI architecture design and the program architecture design two parts. First the architect needs to agree with the project manager and then design. This design must be easy to work on, maintain and expand, and be able to withstand the pressure of a certain amount of prototype development. The UI architect splits the product according to the interface logic, and knows what needs to be placed on each interface. After a democratic discussion with all developers, the program architect formulates a bottom-to-top program hierarchy (such as class, library, and so on) and divides functional modules (such as home page, content list, background management, help system, and so on). The UI architect and the program architect need to agree on functional division, file naming rules, and so on, and constantly refine their thinking in development.
F, the artist uses Photoshop and other tools to design the interface, and complete the picture cutting work.
G, web designers are responsible for writing static templates. If there is a shortage of manpower, this position can be drawn from the developer of the program.
K, art and web designers need to do some coordination. Some art design thinking and can not be perfectly reflected in the Web page, it is necessary to constantly run-in and correction, to achieve both sides are satisfied with the results. In contrast, the artwork does not require much change, so a one-way arrow is indicated here.
h, the underlying logic (such as the design of classes, methods, libraries), and the collation of related documents. If you have the energy to carry out small-scale testing, to ensure that future development work smoothly.
I, when the underlying interface and related documents are completed, the modular splicing will be more relaxed, this process will complete the basic module to the external function of the construction work.
L, this is where program developers pay the most exchange cost. Many of the underlying modules need to be changed during the stitching process, such as adding or subtracting parameters, modifying the name of the class, property, method, moving the class, properties, methods, and so on. At the same time, the external implementation needs to be adjusted with the change and optimization of the underlying module.
M, after the product is formed, will be delivered to the testing department for testing. The test Department returns a report that is sent to the project manager and the program developer. In a small-scale development team, the project manager can act as a quality assurance role, provided that he has a certain degree of understanding of the project's development process, otherwise a dedicated quality assurance person should be assigned to handle the bug list.
N, the report returned by the Test department could have been sent to all program developers, but unfortunately, the testers only deal with the interface, they focus only on the results, not on the principle of implementation. As a result, the bug list usually needs to be handed over to the developer responsible for the interface logic and then distributed to the individual members for correction. In small-scale development teams where the interface logic and underlying logic may be implemented by the same group of people, they need a bugzilla to work together on these bugs. We also recommend that testers use the same set of bugzilla systems to submit bug reports.
Finally summarizes several points: first, the purpose of the detailed division of labor is to reduce the exchange costs. Second, the actual situation will make the development work complicated, so the process model should be able to adapt to the prototype development work. Third, documentation and standardized specifications are extremely important, it can make the development process of the factory, improve the quality of code and maintainability.
Transferred from: http://blog.csdn.net/hello_simon/article/details/19993343
(GO) Web development process