Chapter 358 GB 8567

Chapter 358 GB 8567
This technology is different from instant messaging. It does not require both parties involved in the communication to be online at the same time. It is free for both the sender and the receiver.

Maybe it is less immediacy-oriented, but in real life, instant communication is not needed all the time. This real letter-like method is more in line with people's daily habits and needs.

At least when things are not so urgent, you only need to write a letter and send it over, and the other party will always receive it, instead of having to call first, agree on a time, and then wait for the long and tortuous dialing process.

In fact, FTP can also achieve this effect to some extent, but FTP does not have a complete set of email management mechanisms. Needless to say, the in-depth things, just to achieve visibility only to specific objects, the whole process is already extremely cumbersome and unsafe.

This undoubtedly greatly improves the practicality and convenience of computer communication in the current environment, and greatly lowers the threshold of computer communication.

For people who have already enjoyed the convenience of data communications, this improved, more convenient and easy-to-use means of communication is undoubtedly good news.

"Chief Engineer Gao, this is a great idea. It's just like real mail. You put the letter into the oil barrel, and the recipient will receive it soon. There is no need to intervene. For the user, everything is transparent."

Gao Zhendong smiled and said, "Yes, so I named it electronic mail, the English name is e-mail."

"E-mail, this name is so appropriate." Director Li heard the hidden meaning in Gao Zhendong's words, let foreigners use our things too! But at this time, this can only be heard, and it will not be good for anyone to say it casually.

Chief Engineer Chi is more focused on the technology: "In this way, we only need to compile the files we want to send into a letter, and we can send the content we want to send to the other party, and neither party needs to squat by the computer and wait."

Gao Zhendong smiled and said, "No, no, Chief Engineer Chi, this email program has a function that allows you to add any binary data file as an attachment. You can edit your information any way you want, even existing information. Just write the email and add it as an attachment. You don't have to edit the file again."

Chief Engineer Chi was delighted: "Good fellow, Chief Gao, you not only realized electronic letters, but also electronic packages!"

Chief Engineer Chi’s summary was very accurate. Many people did not realize later that the attachment in an e-mail is not just a letter. It is more like a package. Unlike a letter that can only contain words and drawings, a package can contain anything.

Gao Zhendong said: "Anyway, I just felt that this function was very necessary, so I built it in. I have a test plan here, please ask the comrades in the institute to continue all the tests, I will be lazy, and I will mainly talk and not do anything in the future."

Chief Engineer Gao is very generous! This sentence came to everyone's mind.

If Chief Engineer Gao did not take the initiative to "slack off", it would be difficult for the comrades present to have their names written in the achievement summary report.

Now that Mr. Gao has done this, everyone can go up and enter a command and watch the output nearby.

Chief Engineer Chi took it from Gao Zhendong and said, "I'll do it myself, haha."

He watched Gao Zhendong and Director Li perform the experiment just now and felt that it was just scratching the surface and was not satisfying. Now that he has the chance, he will do it himself!

Gao Zhendong stayed in the computing center until noon before he finished testing all the projects.

Facing the people in the computing office who were looking expectant, Gao Zhendong took out a set of materials that he had prepared in advance.

"Director Li, Chief Engineer Chi, as you have just seen, this email protocol and basic program have all the functions, but it is not easy to use and has some deficiencies in function combination and function expansion. I don't have the time to do it myself. I have prepared a complete list of functions and requirements for an email program. You can complete the program according to this information."

Director Li looked like he knew something good was going to happen. As expected, Chief Engineer Gao only focused on the core, and left the trivial things to the Computing Institute to pick up.

"Well, don't worry, we will definitely get this done."

Gao Zhendong smiled and said, "Actually, the trouble with this thing is that it requires one or more mail servers and a relatively well-secured communication line. My suggestion is that you can communicate with the Postal and Communications Commission, and also the Defense Work Committee, as they have special needs. You can sit down and develop one or a batch of mail systems to meet the needs of all parties."

Director Li understood what he meant. After the protocol and software are completed, the main issue is actually the environment. There is no way around it with the Postal and Communications Commission. As for the Defense Work Committee, it goes without saying that they have special needs.

"This is a good suggestion from Chief Engineer Gao. It will solve the deployment and use problems of this system in one go. We will report it to the ministry and invite the 17th Ministry of Machinery, our ministry, as well as the Defense Work Committee and the Postal and Communications Committee to work together to complete this task."

Leader of the 17th Ministry of Machinery: Ahem, ahem, what do you want me to do? I am so embarrassed. Hi~~~~
Chief Engineer Chi was not focusing on this matter. He was looking at the complete plan sent by Gao Zhendong in an email.

In the plan, he feels that the functions themselves are all natural and not surprising. After watching "Seeing Words as Meeting People", these expansions or things that increase human-computer convenience are no longer his focus.

What made his eyes light up was the material itself - its organization, framework, and structure.

Buying the casket and returning the pearl was originally a derogatory term, but here, what Chief Engineer Chi wants is the "casket"!
While pondering the materials, he said, "Chief Engineer Gao, I think your materials are very interesting. The organizational form and framework are really instructive for us."

Gao Zhendong took a look and understood that he was interested in this.

This document is actually a software requirement description. Gao Zhendong was too lazy to write anything deeper.

The description was written in accordance with the GB 8567 standard used by Gao Zhendong in his previous life, but not in accordance with the requirements of GB/T 8567-2006 "Computer Software Documentation Specification", but in accordance with the "Software Requirements Specification" in the GB 8567-88 "Computer Software Product Development Documentation Guide" which it replaced.

The original 8567 version of 88 was a mandatory standard, but when it came to the 2006 version, it was found that it was meaningless to make it mandatory, so it was changed to a recommended standard.

As for why we use the replaced ones instead of the new ones, the main reason is that the software requirement specification in 2006 was split into too many contents and was completely unsystematic. If it wanted to be systematic, it would become long and boring, or extremely complicated.

When facing small projects, it is actually not as easy to use as the one in 88. When facing large projects, hehe, it is actually just like that. There are too many documents and the supervisor is cursing.

There is no doubt that whether it is the 88 version or the 2006 version, for Chief Engineer Chi, it is like discovering a new continent. This thing is so easy to use!
Gao Zhendong asked: "Are you talking about the format of this document?"

Chief Engineer Chi nodded and said, "Yes, yes, this Software Requirements Specification is very instructive for our work. We are currently compiling software and have no idea what documents are needed to support each step. Each topic is diverse and depends entirely on the compilers' own abilities. The whole process is very chaotic. I'll refine yours and it will be a good standard document for the requirements stage." Chief Engineer Chi has a good eye and can see the usefulness and significance of this thing at a glance.

Gao Zhendong thought about it and thought, this is true. Where can there be a guiding document for the entire life cycle of software development? They must be crossing the river by feeling the stones. As for which stone they touch and whether it is suitable, it depends on their technical ability and a little luck.

Well, this matter can be dealt with.

Thinking of this, Gao Zhendong laughed and said, "Chief Engineer Chi has a sharp eye. I just made a set of things and you found it. Hahahaha."

"Trap"? Lao Chi was smart. When he heard what Gao Zhendong said, he knew that things were far from as simple as he thought at the beginning.

"Chief Engineer Gao, from what you said, this document is not just one copy, but a complete set that can cover many tasks in the software compilation process?"

Gao Zhendong nodded: "Yes, I did develop a set of standards for documents used throughout the software development life cycle."

Life cycle? Mr. Gao’s words are very advanced. I have learned it.

No, what’s the life cycle? Listen to what I heard, it’s the standard!
Standards are a new thing these days and are very advanced.

The first national standard GB1 "Requirements for standard format, first page, continuation page and cover", which is known as the "standard of standards", was promulgated only recently in 1958, less than two years ago.

At this time, standardization work is either not present in the work schedule of most units or is put at the back of the list. Some of them have technical reasons, while others simply do not have the energy to take care of it.

In a nutshell: standards, and the Institute of Computing has not made many of them.

Chief Engineer Chi was immediately excited: "Boss Gao, why don't you write them out so that we can work together to push them to the level of national standards? This way, software programmers across the country will have a reliable basis to work with."

Before DJS-59 and DJS-60D were widely used, this thing was actually meaningful but not very significant, because the software at that time was actually used to solve whatever problems were encountered. It was small in scale, single in function, and clear in direction. The entire software development process that followed was just that for this type of work.

However, with the popularity of DJS-59 and 60D, this issue has slowly come to light.

This is a good thing. Doing it in advance will allow software programmers to get into the state in advance, form work ideas and habits in advance, and avoid a lot of detours.

Gao Zhendong nodded: "Okay, I'll take some time when I get back and put them into text in the near future, and then you organize people to proofread and revise them, and we'll report them."

He planned to take out the entire GB 8567-88 "Guidelines for the Preparation of Computer Software Product Development Documents". What's the point of just a "Software Requirements Specification"? If I'm going to do it, I'll do the whole set!

As for GB/T 8567-2006, forget it. The conceptual span is too wide and the step is too big, which may easily lead to something wrong.

Director Li looked at the discussion between Chief Engineer Chi and Gao Zhendong with a very satisfied look on his face. It must be Old Chi who had dug up a new thing from Chief Gao. No, he had to report it to the department immediately along with the email.

The festival is coming soon, so this is a good thing, not too big or too small.

Gao Zhendong had lunch at the computing center and returned to his office during the afternoon workday.

As soon as I walked in and was about to start work, the phone rang.

The person who answered the phone was Chief Engineer Feng from the Institute of Communications.

Chief Engineer Feng started half jokingly and half complaining: "Hey, my Chief Engineer Gao, you come up with something new, why don't you take care of us? Email, email, it's mainly email. Our Institute of Communications is just the right place for us, and we have as many software programmers as the Institute of Computing."

Ever since they took on the project of "Telegraph Digital Communication Machine", they have been working hard. The technical part of this project has been solved by Gao Zhendong, but the organizational and management content is more time-consuming. They have been working on this problem, so they have not troubled Gao Zhendong much recently, and naturally it is impossible for them to know about Gao Zhendong's job movements.

So as soon as I heard his words, I knew that he had done his homework in advance and knew that Gao Zhendong had been promoted to chief engineer.

Everyone is competing for good research topics, especially Gao Zhendong's research topics, which are basically high-quality topics.

So his words did not mean to blame Gao Zhendong, but rather to remind him indirectly, Chief Engineer Gao, we are also strong and can do things.

Gao Zhendong smiled and said, "Don't worry, Mr. Feng. There is always work to be done. I have also asked the Computing Institute to borrow your expertise and strength."

Come on, I have a lot of things to do here. And regarding this matter, it was only after I informed the Institute of Computing that they brought you in.

Chief Engineer Feng achieved his goal and decided to quit while he was ahead: "Boss Gao, don't worry about the email. We will definitely put all our efforts into it and work with the computing institute to make this system a success."

Chief Engineer Feng was talking about the work arrangements of the email system on the phone, and was also showing their capabilities to Gao Zhendong. "Chief Gao, if there is any good news, please think of us first."

Listening to his words, Gao Zhendong also remembered today's matter about GB 8567-88. It was a good opportunity to bring them in as well. The content of 8567 was only a few dozen pages, but because it was so new, it would take quite a lot of time to successfully complete the proofreading and revision.

After all, if you don’t even understand it, there is no point in proofreading and revising it. It takes time to learn.

The reason for bringing in the Institute of Communications is that, first, they have more manpower, second, they are also professional counterparts, third, the authority of the standard is more endorsed, fourth, they will naturally spare no effort to promote it, and fifth,
Thinking of this, Gao Zhendong smiled and said, "Boss Feng, you should prepare some software personnel during this period. There is something we can do together later."

 Well, that's all for today. I'll resume updating three times tomorrow.
  
 
(End of this chapter)