Japan is developing alarm against overseas software
[Nikkei BP Society] Japanese enterprises fail to have problems with problems with development efforts to Asian software companies. "Japanese carriers are not intentional, this attitude has triggered a lot of questions," Engaged in software development management and quality management research, Musago Industrial College Information System Engineering Materials and Church Lecturer Ring alarm.
And the sonici visited China in September, listening to the difference between Japanese Haibao and China Contractor for software development issues. In a single software development case, when describing the software standard files, when there is no doubt, Japanese happiness felt very relieved, but in the end, it was found that the Chinese engineer understood. "Chinese engineer believes that the main reason is that the documents are incomplete, it is unclear. In Japan, even if the expression is not clear, it is often completed by interrelationships. But this time I still have this kind of habit to China, no reminder And confirmation "(and sonici). "In addition, for the large number of standards for the contractor, some Chinese engineers also feel very surprised. If the standard changes a lot, you must make a clear from the beginning," (and son-Yi).
When this problem occurs, "China's engineers will depend on the struggle, pointing out that the documents of the contractor are unclear, the boundaries of the standard change are unclear," (and soni).
In addition, and son also pointed out: "Many Chinese engineers hope that the software development process can be systematically." And worrying that "do not want software development system in Japan. The people doing this seem very little."
When the software bags such as Asian countries have failed, "there are quite a few Japanese people think that they are caused by cultural differences, thus caught in thinking stalemate" (and son and son). And appeal to "the basic development process should be re-examined".
As a chairman of the 22nd Software Production Quality Management Symposium (held from December 4 to 5, the Committee held by the Japanese Scientific and Technical Alliance). At the subject discussions, "When making product production together with Asia, I hope to find a way to get a long-term supply of remedial" (and soni). (Reporter: Anabao Xiu Xiong)
The article is clearly proposed for two reasons: one is incomplete file, and the condition is unclear. The other is a cultural difference.
Then, in recent years, in recent years, the reasons for the failure of most projects is that the demand is unclear. It is incomplete, the document is incomplete, and sometimes it can be understood, sometimes it can be Understand, I don't know how to understand it for the impression of Chinese programmers. In fact, like domestic projects, most factors are buried when the project is started.
Most of Japan's foreign bags have used waterfall model development processes. Generally speaking, work in demand analysis and detailed design phases is completed in Japan, which may require Chinese programmers to participate in completion. Then the focus of work is transferred to China or the other labor prices is relatively low, and sometimes the day will come to China to complete Coding, UT and Si. The specific work after Si is returned to Japan, and the engineers of Japan do PT and RT work (mainly for the test and acceptance test of the actual environment, the different company practices may be slightly different), this time in China The task of the member is the BUG corresponding to the modification of the BUG discovered by the test phase, and the design changes. After doing a series of tests is the specific application phase, this is basically the end of the project.
In this way, the process is very easy to understand, it is convenient to manage, and the outsourcing is also clear. After the design phase is finished, the document is handed over to China. After the Chinese company is finished, the code and related test documents will be paid. Give the Japanese side. It is very clear when the project is relatively small, and the probability of success is also very large. However, this is not necessarily a good thing in the perspective of system analysis. In most cases, the user is not a way to completely explain that he wants to do something, and there must be many repetitive and superimposed. If the project is relatively large, the records of these change points and the management of records are a very terrible thing. In the recent project, the design party is not the end user, there is no way to make a decision, so many contact tickets. I passed forward, and the project in just six months has nearly a thousand contact tickets. Sometimes I don't know if the contact ticket is in his hand, and all people have an answered answer. Especially in the later stage of the project, the relevant confirmation is not counted. When communicating with Japanese customers, the gap between China and Japanese culture will have a large part of the effect of communication. The first thing to mention is the national emotional problem. Some people in the middle and Japan are some people who despise each other, that is, some Chinese people look down on the Japanese, and some Japanese people look down on Chinese. When discussing specific problems, if this emotion is brought to the desktop, it is likely that the words are too intense, the two needles are pointed to the wheat, and even the interruption of communication, even the interruption of communication, more affected future communication.
Technical Wizard and Quality Wizard. I remember at the friends of Tokyo, I have a dedicated predecessor to talk about China's engineers and Japan's engineers. When the Chinese engineer is based on technology, the Japanese engineer is guided by quality. Chinese programmers pay special attention to the application of technology in the project, but also care about what new technologies that can be learned in the project. In the development, if a new technical problem is solved, many programmers will have a sense of natural accomplishment. This is a good side, in turn, many times, will make "technical gold-plated" problems, and make some problems that can be made very complicated, making control difficulties increase, customers are also difficult to accept these, often will Issue "How to do so long to do so long"; there is a feature that I don't pay attention to the problem that is easy to solve, there has been such a thing in a project:
A string with login, "login" string is erroneously written as "login", but "login" in Japanese is the meaning of saving data into the database, so customers point out that this is a bug, requiring contractor to modify. After the problem is sent to the contractor, the programmer S responsible for modification means that this is easy to modify, and it will be changed in a few minutes. However, after the customer gets the new version, she still discovers this problem, asking the reason, s answers. Customers are very angry and think that this is a very serious quality problem, so the bug control process, from the management, code correction, test, and later Review, from the head to the end. S is not understood: "It is not to change a string, is it so happy?"
Relatively, maybe a lifelong business system, Japanese employees and businesses are tied together, and the Japanese attach great importance to quality, and there is a problem first, if it is not a quality problem, will not affect the company. Image, etc. And what technology has been used in the middle, but it is possible to achieve it.
The Japanese push and the impetuous Chinese people. Perhaps the same reason is the reason for lifelong business, the phenomenon of eating a big pot in Japan is obvious, and the Japanese people are pulling and pushing each other, from above, no one is willing to make a decision, and finally do not have to discuss, after passing After a long marathon meeting, the conclusion that the conclusion is often asked first, and it is done according to the opinions of users. This often waves a lot of time, and it will bring a lot of problems that should be solved in the design phase to the Coding phase, bringing a lot of trouble to the later work. In contrast, some impetuous phenomena of Chinese companies, and more than 80% of things will think is almost enough. The basic function of the software we have developed is achieved, but a lot of small problems is far from the real outstanding product. At present, Japan has also begun to reflect on these issues, and some companies have begun to calmly consider whether software packages to China can save fees and bring better profits. There is a tendency to pay attention to recruiting China's programmers to work directly to Japan, rather than putting the project, which may be high, but it is easy to control more than the quality of the product.
I remember that a few years ago, when I chatted with a software company, I booked the market that the market was in the same bag. When I was eating a cream on the cake, I didn't know if he thought that her cream would be bad. Teeth. It seems that when I have a cake today, as the market is mature, the days of the bones are also coming soon. Is our software company ready? Is our programmer ready?
