This is the third article I’ve been involved with getting started

Everybody is good, a brief introduction of me, I am a front small white, has just entered the company internship, here to explain I learned that the company’s overall business process and each post, before this I a set of processes for the overall project is not very clear, very simple, as an intern for a period of time have a certain understanding, to share what I know to everyone here.

The following is my flow chart, if there is wrong, please give some advice, but do not point/dog head

Graph TD project approval --> communication requirements --> project evaluation --> Plan formulation --> design prototype --> architect design overall architecture --> UI design design drawing -->DBA design database --> operation and maintenance start service --> backend setup background write interface --> Front-end page write link interface --> Test --> O&M periodic maintenance --> delivery project

First, the project

Generally by the product manager or project manager (this is the two positions, but may be a person) after project after project or boss, received after the project, they will first evaluate your company can do, can do is contact party a, communication needs, and then a meeting in the company, to evaluate the need how long can do it, comb demand, And give the quotation to Party A. If Party A agrees, the next step will be made.

Second, make a plan

After the product manager determines the requirements, a detailed prototype diagram is drawn up and explained to everyone at the meeting. The project manager arranges people to do it to see who is familiar with this aspect of the business. The next step is to start the work of each position.

Third, the operation of each post

1. Architects

The architect is responsible for the design of the overall system architecture, from the requirements to the design of every detail should be considered, grasp the entire project, make the design of the project as efficient as possible, easy development, easy maintenance, simple upgrade. Good to meet the performance, scalability, integration, security, o&M, high availability, easy to deploy, easy to update. After identifying non-functional requirements, technology selection, technical architecture risk identification and technical implementation workload assessment are also required.

Generally speaking, it is to make which module is more economical to use what language, and later convenient maintenance and update.

2.DBA database design

Mainly responsible for the full lifecycle management of the business database from design, testing to deployment and delivery. The core goal of the DBA is to ensure the stability, security, integrity, and high performance of the database management system.

3. The UI design

Through communication with customers and the front end, the design staff can design the design drawing suitable for customers’ needs through their own experience. Good UI design is not only to make the product personalized and tasteful, but also to make the operation of the product comfortable, simple and free, fully reflecting the positioning and characteristics of the product.

4. The back end

The back-end mainly builds the support service container of the back-end, and the interface design mainly carries out the corresponding functional interface design for different industries. Usually, a platform has multiple sets of interfaces, and its main responsibilities are platform design, interface design and function realization.

5. The front end

The product UI design draft is realized into website products, covering the user PC terminal, mobile terminal web pages, small programs, APPS, and so on, as well as the link background transfer interface, and the front end is mainly displayed in front of the user.

Test 6.

Testing is an important part of the whole product life cycle. For the most part, it’s functional testing. At a more advanced level, there’s security testing, which looks at customer requirements, keeps track of Bug changes, and constantly tests to improve the product.

7. Ops

Operation and maintenance (O&M), in essence, is the operation and maintenance of each stage of the life cycle of the network, server and service. Mainly deployment projects and late operation and maintenance.

Iv. Project delivery

After the work in these positions, the project will be released, and the project will be delivered after the customer has confirmed that there is no problem. In the later period, the customer can carry out operation (this is also a post).

In live.

This is a process from taking projects to delivering them. In fact, there are many subdivisions in the above positions. Every post has its responsibilities, and every post is indispensable.