Software development process I understand

1. Customer Manager: understand the general direction of customers, such as industry and consumer groups, as a bridge between technology and demand.

2. Design Department ① cut the image --- work with the website prototype Creation

② Page prototype --- Dreamweaver

The output is a page prototype with a menu description. It is best to use axure for design. Submit each design change to the GIT repository (the prototype directory in the project ).

The prototype designer is busy at this time because he wants to record a lot of things, draw on paper, and communicate with the customer in a timely manner. Finally, convert the pictures on the paper into HTML and add interaction effects in subsequent iterations.

3 Development Department:

① Learn the basic concepts in a timely manner based on the prototype provided by the design department. Such as shopping cart, unpaid order, paid order, return, logistics and other information. The functional modules are roughly divided.

② Functional modules for feasibility analysis, at the same time do E-R diagram design, determine the site "draft" (the reason forFeasibility AnalysisAndERTUThey are arranged together because they are an internal implementation logic iteration process ).

Cut down functions that cannot be implemented at all; record the functions that deviate from the product trunk in later versions for iteration; send the feasibility analysis report to the design department and the customer manager by email.

③ Clarify the communication tools, database design tools, program frameworks, version management, and time management among developers.

④ Divide functional blocks and assign them to specific persons. Through redmine. Quick completionMain CodeRequires codeVery robust.

⑤ Project team members can subdivide the modules allocated to themselves based on the actual needs of the project to manage the time.

⑥ Perform waterfall iterative development on the main code.

4 Test & maintenance:

① Optimize the code quality and user experience. Follow the principle of open and closed.

② Reusable core code componentization for future use in new projects.

PS: Why do I write so much?

Because I wrote a letter to boss about how to make the meeting more effective, boss said that he would come back to discuss with us on a business trip. This is a preparation.

Suggestions for meeting:
1. The meeting time should be agreed in advance, so that our friends can arrange their work in advance and come to the meeting time to make an appointment on time.
2. Several specific questions should be prepared before the meeting, and specific discussions should be conducted during the meeting. The person who makes the meeting record should inform everyone in advance to prepare questions.
3. You should think positively during the meeting, but do not argue. You can use notes to record the areas of inconsistent thinking. After the discussion on the subject is completed, you can submit it in time.
4. After the meeting, the Conference recorder should send emails to the participants, regardless of whether the solution is finalized. (Mail is used because it can be retained for a long time and has a clear subject)

Software development process I understand