Communication is different from software projects in the Internet industry.

I have recently learned some differences between the Internet industry in software development projects and the communication industry.

First, the two have different requirements on the capture method. In the communication industry, the initial requirements are determined by standardization organizations such as 3GPP, however, the requirements of communication products in various versions are determined by the carrier's proposal to the communication enterprise. Product Manager and System Architect play an important role in determining requirements. The difference is that because the products in the Internet industry are very close to end users, users can use the online feedback system to propose their own needs. product managers (product designer, the name of the Internet industry) determine whether the product is ultimately a development requirement based on the amount of feedback required and the status of competing products. Although both industries have the concept of a Project Manager, the role and management level are very different.

Second, there is a big difference in the project evaluation process of the two industries. Most versions of communication products involve the development of multiple communication sub-devices. Therefore, there are two major steps to focus on: 1, the system architect designs the system as needed and forms the system architecture documents and interface documents between various communication sub-devices, each communication sub-device development team carries out subsequent software development based on the output documents in step 1. The two steps also show that there are two phases for evaluating the project development time. In the first phase, all departments provide an evaluation time according to feature's rough technical documents. The evaluation time requirements of the system engineering department in this phase are relatively accurate, but the evaluation by the Development Department can be very rough. The second stage is that after the system engineering department completes the design work and outputs relevant documents, the Development Department should re-evaluate the development time according to the document. Because the information at this time is more detailed than the previous stage, therefore, the evaluation accuracy is higher, and the evaluation time is used as the project development plan.

Back in the Internet industry, project evaluation is more intuitive because the coupling between systems is not as strong as that of communication products, and there may be no system design work at the architect level. However, due to the lack of Architects, the evaluation of the project is completely completed by developers, and the project risk is often higher when the levels of developers are uneven. A communications company like Motorola is able to achieve project development as scheduled and has nothing to do with high-level architects.

Thirdly, the role and importance of design review in two industries are also different. In the communication industry, after completing the system design, the system engineering department will review various documents of the system design. In addition to the System Architect of the System Engineering Department, the reviewer also includes the Development architect from the communication sub-Device Development Department. This review process helps to ensure that the system design scheme can finally be implemented by the Development Department. When the development department starts development, there must be a summary design review and finalCodeReview, which is mandatory for the release of high-quality products.

In contrast, in the Internet industry, because the product is very short from the user, and the product can be quickly repaired online after a defect occurs, the requirement on the product defect rate is naturally not that high, the result is that the development team has a poor normative understanding of software development, making it more like a "hands-on workshop". In terms of quality assurance, it cannot use a "systematic methodology ".

Another thing I would like to share with you is that development engineers in the two industries have different work habits in the face of unclear requirements. In the communications industry, development engineers usually seek help directly from the System Engineering Department (System Architect) if they are faced with problems such as unclear requirements. Then, the System Architect communicates with the product manager to the customer to clarify and reply to the Development Engineer. However, in the Internet industry, development engineers work with product managers directly (because there is no System Architect level ), in addition, the lack of product manager experience makes the proposed requirements unclear, and even technically difficult to implement. In this case, the development engineer takes responsibility for helping the product manager clarify the requirements and persuade the product manager to change the requirements if necessary.

This article is from Li Yun's blog and must be kept at: http://blog.csdn.net/hzliyun/article/details/9028263.