Chapter 362 Half of a Family
Although the telegraph data communication machine developed by the Communications Institute uses DJS-60D as the control computer, this thing cannot be exported now, but the software can still be used on DJS-59.
The Oceanic Convention countries may not be able to enter, but the Economic Assistance Council countries and some other scattered countries can still try.
As for email, it looks similar to a telegraph data communication machine, but in fact it is quite different. At this stage, it is more used for communication between agency staff, and it is quite easy to use. The habit of sending e-mails among foreigners at work is actually a result of the popularization of e-mail relatively early and was gradually developed.
The leader of the National Defense Working Committee finished introducing these two things, and also said that there is no need for confidentiality of these two softwares. Feel free to sell them as much as you can, and sell them wherever you can.
Even if necessary, DJS-59 can be made with a special firmware program just for this function.
This ability is still available in computing units.
Several other departments are very interested in this matter.
For foreign affairs, it is a means to expand influence, especially such high-tech products. Although it is very weak, but as the old saying goes, if you don't accumulate small steps, you can't reach a thousand miles, and if you don't accumulate small streams, you can't reach the river. The road must be walked step by step, and there are not so many things that can be accomplished overnight.
Well, except for wall hangings like Gao Zhendong.
For the Ministry of Foreign Commerce, it is even simpler, just sell it for a small amount of money to pay off the debt!
Especially after knowing the concept of "selling software", I became even more interested in the fact that selling one or two small tapes can earn a relatively large amount of foreign exchange.
A few people made a decision on the spot. Once this thing is sold, it will be added to the list immediately without having to hold a demonstration meeting.
The leader of the Ministry of Foreign Commerce also made a joke: "Old While nodding, I thought to myself, you don't have to ask, I have already arranged it.
——
Gao Zhendong spent a day to correct the things that should be changed in GB8567. This thing only has dozens of pages, so it is not troublesome to change.
Then two phone calls were made, and two chief engineers from the Computing Institute and the Institute of Communications were invited.
When the two chief engineers met, it was quite subtle. Well, if it weren't for you, I would have it all to myself.
However, this kind of healthy competition is not a bad thing. Gao Zhendong pretended not to see it. You fight yourselves. I will sit firmly on the Diaoyutai and I will never be in the air force.
While Gao Zhendong was slandering the fisherman in his heart, he took out the "Software Development Document Preparation Guide" that he had modified, divided it into two halves, and handed it to the two of them. The two of them ignored the cockfight and quickly took it and opened it.
GB8567 is a standard that covers the entire process of computer software development from feasibility study report to project development summary report. It has a total of 14 documentation instructions and defines the entire life cycle of the software.
The chapter organization is based on the entire process of the software life cycle, written from front to back. It is very easy for developers to understand and master.
This is the biggest difference between 88 and 2006. In 2006, some things were expanded, split and reorganized. There are a total of 25 software development documents.
The details are detailed, but when it comes to the organizational order of the files, it is not an exaggeration to say that it is disorganized.
Generally speaking, the 88 version is very suitable for the waterfall development model, while the 2006 version is quite difficult to describe. It seems to be more agile development, but it is not so agile. In short, it stands out.
In Gao Zhendong’s view, if you want to develop project-based software, it is more appropriate to use version 88 as the general outline. If you want to develop software that continues to iterate quickly, it is more appropriate to use things removed from 2006.
In fact, it is a good idea to integrate 2006 into the documentation of various stages of 88. However, given the current environmental conditions, this step is a bit large, and it is easy for developers to fall into the dilemma of documenting for the sake of documentation.
For developers at this time, they can probably manage a project well by using 88 to operate like a fool and following the standards to implement the documents.
As for the 2006 version, it takes some effort. The 2006 version is more advanced and some things are more detailed, but the system is not as systematic as the 88 version. A person who does not have a relatively formed project management thinking, Looking at a lot of stuff in 2006, the probability of being confused is not low.
This is the reason why Gao Zhendong did not choose the 2006 version. The original development process was already messy for software developers at this time. Adding a messy 2006 version would be tantamount to making developers unclear about their ideas. , adding insult to injury.
As the same saying goes, the more advanced the technology, the better, but the more appropriate. Just like when Gao Zhendong was reading online articles in his previous life, a certain author complained that he used an antique-level X220 small black book to write his book. The small yellow croaker costs 165 yuan to postage. Anyway, if you can type and look up information, it will be no problem. On the contrary, that The keyboard is easier to use than almost any new laptop, which makes sense.
Sure enough, this standard directly opened up their software development for Mr. Chi and Mr. Feng, two big guys with both technical skills and management experience. new door.
“Feasibility study, development plan, demand specification, data requirements, outline design, detailed design, data design. Mr. Gao, you have broken the entire process of software compilation into pieces. It’s been determined through documentation. With this, you won’t have to worry about delaying work even if you change people midway.”
Chief Engineer Chi is from the Institute of Computing and is closer to software development, so the content he got is the first 7 documents, which are also the first 7 processes of software development. The only difference from 88 is that there is no concept of database at this time. So Gao Zhendong changed database design to data design.
Otherwise, we have to explain the database. Now that this concept has not been formed, it is a bit too early, so the database will be left behind.
As soon as Mr. Chi got it, he glanced at the chapter names and realized the usefulness of this standard. This is to teach software developers step by step how to be orderly and organized from beginning to end. , Complete the compilation and development of a software from top to bottom, from coarse to fine.
If the previous software development method relied on the personal ability and inspiration of software personnel, then if it is implemented according to the standards of General Engineer Gao, software development can be regarded as an industrialized assembly line. Did it.
Although it may lack some spirituality, application software does not have so much spirituality. The main thing is to complete the function. As for spirituality, it only needs to be possessed by a few people.
"Okay, okay," Chief Engineer Chi kept mumbling while looking at it.
At this end, the Institute of Communications is, after all, a subordinate research institute of a huge organization that actually operates. They will also be exposed to more things of a management nature and a process nature. In this regard, they are better than all computing Advantageous.
So what Chief Engineer Feng got here is the last seven documents in GB8567.
“Tsk, tsk, tsk, Mr. Gao, you are no longer software development, you have taken data management, process management, and users into consideration.”
This is not the case, user manual, Operation manuals, module development files, test plans, test reports, monthly progress reports, and project summaries are all here. For Mr. Feng, who has never been exposed to systematic development and software project management, he feels like everything he sees. It's fresh and every document I see is useful.
The user manual and operation manual were just that. The module development files and test contents were completely novel to him. It didn't mean that they didn't do testing, but the software test plan and test report were blank.
Seeing that both of them understood it, Gao Zhendong said: "These things are my summary of the current stage of software development. Basically, they can sustain a software from beginning to end, no matter how big or small it is. , and it can also standardize the disordered state of software development in various industries."
He pointed to the half-and-half standards in their hands: "With the popularization of DJS-59 and 60D, many of them should be able to do it. The organization develops its own application software. With this, firstly, it can manage the software development process; secondly, it can basically ensure that the development intention is clear and guide users to use it; thirdly, it can also better manage the entire software development process. It will leave traces of development experience and lessons, and it will not cause the phenomenon of people leaving the project.”
Chief Engineer Chi said with a smile: “Mr. Gao’s standards are so timely. To be honest, I thought of the first purpose, but I didn’t expect the second and third ones.”
General Engineer Feng secretly said, “Chief Engineer Chi is right. I’ve seen both the first and second ones.” After it came out, I didn’t fully consider the third one.”
Um? What do you mean? You can see one more than me, right?
Chief Engineer Chi stretched out his hand: "I've just finished the first half, and I'm covering the second half in my hand. What's so exciting about an open-book exam? Come on, come on, show me the second half too. Look.”
Mr. Feng smiled and exchanged the second half with him. He also wanted to see the first half.
After the two chief engineers exchanged views, Lao Feng quit.
"Chief Engineer Chi, how about we exchange part of the content? We don't have any software development process here, which is not conducive to training our comrades who work on software. It won't be easy for me to do business when I go back."< br>
Lao Feng is a very thief, and at the same time his thinking is very clear.
Since it is called software development standards, everyone’s focus must be on the software development process. The content that is naturally focused on is the development, and other content is subconsciously not so valued.
Just like in a water conservancy design institute, the major majors must be hydrology and hydraulic engineering. Other mechanical and electrical, metalwork, etc. are not as outstanding as major majors, and it is not as easy to move up as major majors.
Chief Engineer Chi shook his head and said with a smile: "Hey, Mr. Feng, you are wrong. How can you be picky and picky about your work? Hasn't it already been allocated by Mr. Gao? The only difference in revolution is the division of labor. There is no hierarchy, just follow the plan.”
(End of this chapter)