Network Security Internet Technology Development Database Servers Mobile Phone Android Software Apple Software Computer Software News IT Information

In addition to Weibo, there is also WeChat

Please pay attention

WeChat public account

Shulou

Software integration strategy story serialization-the adverse impact on the project is so great.

2025-02-23 Update From: SLTechnology News&Howtos shulou NAV: SLTechnology News&Howtos > Internet Technology >

Share

Shulou(Shulou.com)06/03 Report--

2. The adverse impact on the project is so great.

Lao Liu, the project manager, told Xiaochuan that when this round of integration is done, let's have a chat. Xiaochuan was a little nervous. But think about it, I have worked very hard, and there is nothing to worry about. In fact, the key is the quality of programmer submission. I can take this opportunity to communicate with the leader.

Monday morning. Lao Liu first said some words of thanks for Xiaochuan's hard work. Xiaochuan was very relieved to hear this. Then, Lao Liu showed Xiaochuan a huge picture with his notebook and told him that this was the task plan of the project. It's so complicated. Xiaochuan was stunned. Seeing this, Lao Liu turned to the whiteboard and drew a simple picture for Xiaochuan on the whiteboard. As shown in figure 1.

"Xiaochuan, I want you to know how important your work is to this project. look at this picture. This is a typical example. Development tasks B, C, D must be completed after development task An is completed. a string of tasks like this determines at least how long it will take for the project to be completed. Can you understand that?"

"Yes."

"but now, after task An is completed, tasks B, C and D cannot start immediately. Not even if the manpower for tasks B, C and D is already in place. You know the details."

"well, after task An is completed, we can't integrate until the next round of integration. The integration itself also takes time, waiting for the end of the integration, and the corresponding changes to task An are in the baseline. Only then can you see the results of task An and task B can begin." Xiaochuan is familiar with it.

"how long do we have to wait now?" Lao Liu asked.

"well, that depends on how long it takes for me to integrate. The one that just ended is a whole week. Oh, it's not just integration time. Also take into account the time waiting for integration. If it happens to be done on Monday morning, there is little need to wait. If it happens to be done on Tuesday, or too late, on Monday afternoon, it will take two weeks. In other words, it takes an average of a week to wait for the integration to enter, and then a week to complete the integration. "

Xiaochuan finished, lost in thought. In the past, I just thought my work was very hard, but unexpectedly, the whole project was looking at me, expecting me to be faster and faster.

"I know it's hard for you, Xiaochuan," Liu said. "now you know how much I expect you to do a better job. Do you have any good ideas?"

Xiaochuan: "I think the key is the quality of the code submitted by developers." if they make sure that the code can be compiled and passed before committing, there will be no build problems during integration. What wastes time now is building over and over again during integration. "

Lao Liu: "you mean that most of the time is spent on repeated builds, rather than on merging previous versions?"

Xiaochuan: "Yes, it is." For example, in this integration, everyone's submissions will be processed at 1: 00 p.m. on Monday. You know, everyone's code changes are all on their respective task branches. The so-called commit is to tell me to merge his branch into the integrated branch when it comes to integration. In the process of my merger, I may encounter a version merge conflict, so I will coordinate and find a solution to whoever submitted it. At the end of the day, I e-mailed all the programmers who had not yet been submitted and told them to stand by to resolve the conflict. In this way, by 9: 00 p. M., all the version merge conflicts were resolved. And the rest of the time, it will be spent on repeated construction. "

Lao Liu: "good." it seems that it takes time to build repeatedly. Then your idea is that if all the versions submitted by programmers can be built, you don't need to build them here? "

"that's right. In that case, maybe tasks B, C and D can begin on Tuesday morning." Xiaochuan is very confident.

"if the programmer's submission is all right, are you sure you'll be fine when you build it?" Lao Liu slowed down and said one word at a time.

"of course, but." Xiaochuan realized something, as if the logic here seems simple and clear, but in fact it is not strict reasoning.

"well, I see you have some ideas, which is good. Think again. Investigate more and find out why it needs to be built over and over again. Let's talk to everyone. In short, please help me think of a way to shorten the time between the completion of Task An and Task B.

This article is excerpted from the book "Software Integration Strategy".

Dong Yue.

Published by Electronic Industry Press.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.

Views: 0

*The comments in the above article only represent the author's personal views and do not represent the views and positions of this website. If you have more insights, please feel free to contribute and share.

Share To

Internet Technology

Wechat

© 2024 shulou.com SLNews company. All rights reserved.

12
Report