Chapter 362 Half of the Family

Although the telegraph data communication machine developed by the Institute of Communications uses DJS-60D as the control computer, this thing cannot be exported now, but the software can still be used on DJS-59.

It may not be possible to break into the Oceania Convention countries, but we can still try for the Economic Assistance Council countries and some other scattered countries.

As for e-mail, it looks similar to telegraph data communication machine, but it is actually quite different. At this stage, it is more used for communication between staff members of institutions, and it is quite useful. The habit of foreigners to send e-mails at work is actually because e-mail was popularized earlier and it was gradually developed.

The leader of the Defense Work Committee introduced these two things and also said that there is no need to keep these two software confidential. You can sell them as much as you can and sell them wherever you can.

If necessary, the DJS-59 can even be specially hardened for this function only.

Units such as the computing center still have this capability.

Several other departments are very interested in this matter.

For foreign affairs, it is a means to expand influence, especially this kind of high-tech products. Although it is very weak, but as the old saying goes, a journey of a thousand miles begins with a single step, and a river is formed by the accumulation of small streams. The road must be taken step by step, and there are not so many things that can be achieved overnight.

Well, except for the wall-hanging one like Gao Zhendong's.

For the Ministry of Foreign Trade, it is even simpler, just sell small amounts of money to pay off debts!
Especially after learning the concept of "selling software", I became more interested in the fact that I could earn a relatively large amount of foreign exchange by selling one or two small tapes.

Several people decided on the spot that this thing would be sold and added to the list immediately without having to hold a discussion meeting.

The leader of the Ministry of Foreign Trade even made a joke: "Old X, you have to take good care of this precious treasure of the 17th Ministry of Machinery, and make sure nothing unexpected happens."

The leader of the Defense Work Committee nodded and thought to himself, do you even need me to tell you? I have already arranged it.
-
Gao Zhendong spent one day to modify the necessary parts in GB 1. It was only a few dozen pages long and was not difficult to modify.

Then two phone calls were made to invite the two chief engineers from the Computing Institute and the Institute of Communications.

When the two chief engineers met, there was a subtle rivalry between them. Well, if it weren't for you, I would have kept it all for myself.

However, this kind of healthy competition is not a bad thing. Gao Zhendong pretended not to see it. You guys fight your own battles, and I will sit back and wait, and I will never come up empty-handed.

While Gao Zhendong was cursing at the fisherman in his heart, he took out his revised "Guide to Software Development Document Preparation", divided it into two halves, and handed them to the two men. The two men no longer cared about the cockfighting and hurriedly took it and opened it.

GB 8567 is a standard covering the entire process of computer software development, from feasibility study report to project development summary report. It contains 14 document preparation instructions and defines the entire life cycle of the software.

The chapters are organized from front to back according to the entire process of the software life cycle, which makes it very easy for developers to understand and master.

This is the biggest difference between 88 and 2006. 2006 expanded some things, split and reorganized some things, and there are a total of 25 software development documents.

It is detailed, but when it comes to the organization of the files, it is not an exaggeration to say that it is disorganized.

In general, the 88 version is very suitable for the waterfall development model, while the 2006 version is a bit hard to describe. It seems to be more inclined to agile development, but not too agile. In short, there is a twist.

In Gao Zhendong's opinion, if you want to develop project-based software, then it is more appropriate to use version 88 as the general outline. If you want to develop software that is continuously and rapidly iterated, then it is more appropriate to use things taken out of 2006.

In fact, integrating 2006 into the documentation of various stages of 88 is a good approach. However, given the current environmental conditions, this step is a bit too big and can easily put developers in the dilemma of documentation for the sake of documentation.

For developers at this time, they can probably manage a project well by using 88 to do fool-proof operations and implementing the documents according to the standards.

As for the 2006 version, you will need to spend some time to think about it. The 2006 version is more advanced and some things are more detailed, but it is not as systematic as the 88 version. A person who does not have a relatively formed project management mindset will most likely be confused when looking at all the things in 2006.

This is why Gao Zhendong did not choose the 2006 version. The development process was already chaotic enough for software developers at that time. Adding the messy 2006 would only make the developers' already unclear thinking even worse.

As I said, the more advanced the technology is, the better it is. It is like when Gao Zhendong was reading online articles in his previous life, a failed author complained that he used an antique X220 small black notebook to write his book. The small yellow fish cost 165 yuan and included shipping. Anyway, it was fine as long as it could be used for typing and looking up information. On the contrary, the keyboard was better than almost all new laptops. How can this be justified?

Sure enough, this standard opened a new door for software development for Chief Engineer Chi and Chief Engineer Feng, two big guys who have both technical skills and management experience.

"Feasibility study, development plan, requirements specification, data requirements, outline design, detailed design, data design. Mr. Gao, you have broken down the entire process of software compilation and documented it. With this, even if you change people in the middle of the process, you don't have to worry about delaying the work."

Chief Engineer Chi was from the Computing Institute, which was closer to software development, so he got the first 7 documents, which were also the first 7 processes of software development. The only difference from 88 was that there was no concept of database at that time, so Gao Zhendong changed database design to data design.

Otherwise, we still have to explain the database issue, which is a bit ahead of the times now when this concept has not yet been formed, so we will put the database issue aside.

As soon as Chief Engineer Chi got the book and glanced at the chapter names, he immediately realized the usefulness of this standard. It teaches software developers step by step how to complete the compilation and development of a software in an orderly, organized, top-down, and rough-to-fine manner from beginning to end.

If the previous software development method relied on the personal abilities and inspiration of software personnel, then if Chief Engineer Gao's standards were implemented, software development could be treated as an industrial assembly line.

Although it may be less spiritual, but where does the application software come from? Completing the function is the main thing. As for spirituality, it is enough for a small number of people to have it.

"Okay, okay," Chief Engineer Chi kept muttering to himself as he looked at it.

On the other hand, the Institute of Communications is, after all, a subordinate research institute of a large actual operating organization. They will also be exposed to more management and process-related things. In this respect, they have an advantage over all computing institutions.

So what Chief Engineer Feng got here are the last 8567 documents in GB 7.

"Tsk tsk tsk, Mr. Gao, this is no longer software development. You're taking data management, process management, and users into consideration."

Yes, the user manual, operation manual, module development file, test plan, test report, monthly progress report, and project summary are all included here. For Mr. Feng, who has never been exposed to systematic development and software project management, each one of them feels new and each document feels useful.

The user manual and operation manual were fine, but the module development files and testing contents were completely new to him. It was not that they did not do testing, but that the software testing plan and test report were blank.

Seeing that both of them understood, Gao Zhendong said, "These things are my summary of the current software development. Basically, they can support a software from start to finish, no matter how big or small it is. They can also standardize the disordered state of software development in various industries."

He pointed to the half of the standard in the hands of the two people and said: "With the popularization of DJS-59 and 60D, many people should organize the development of their own application software. With this, first, we can manage the software development process well, second, we can basically ensure the clear development intention and guide users to use it, and third, we can also leave a better record of the entire software development process, leaving development experience and lessons, and at the same time, it will not cause the project to be paralyzed when people leave."

Chief Engineer Chi smiled and said, "Boss Gao's standard is really timely. To be honest, I thought of the first purpose, but I didn't think of the second and third."

Chief Engineer Feng secretly challenged: "Chief Engineer Chi, you're right. I saw the first and second ones, but I didn't think through the third one."

Hmm? What do you mean? You figured out one more thing than I did, right?
Chief Engineer Chi stretched out his hand and said, "I have just finished explaining the first half. You are covering the second half with your hand. What is there to be proud of in an open-book exam? Come on, show me the second half as well."

Mr. Feng smiled and exchanged the second half with him, as he also wanted to see the first half.

After the two chief engineers took turns looking at it, Old Feng quit.

"Chief Engineer Chi, how about we exchange some of the content? We don't have any software development process here, which is not conducive to the training of our comrades who are engaged in software development. It will be difficult for me to report back when I go back."

Lao Feng is very cunning, but his thinking is also very clear.

Since it is called software development standards, everyone's focus must be on the software development process. The natural focus is on development, and other content seems to be less important subconsciously.

It is just like in a water conservancy design institute, the major major is definitely hydrology and hydraulic engineering. Other fields such as mechanical and electrical engineering, metal structure engineering, etc. are not as outstanding as the major majors, and it is not as easy to move up as in the major majors.

Chief Engineer Chi shook his head and said with a smile: "Hey, Mr. Feng, you are wrong. How can you be picky when doing your work? Mr. Gao has already allocated it. In revolution, there is only division of labor, not high or low. Just follow the plan."

(End of this chapter)