Practical know-how of the Global Project

Hitoshi Goto

Ukihiko Takagi

In Part16, we discussed how to get along well with foreign vendors. In this part, we will look at the points which you should note when ordering to overseas vendors.

There are vendors who do not easily admit bugs overseas

Even in Japan, the number of companies that conduct source code review (walk-through) seem to be decreasing, but by executing the code review early in the development process, it is possible to realize the status of programmer's habits and compliance with standards, etc. The sorce code review helps to improve the quality of the program.

However, you should understand that there maybe no such cultures outside of Japan, or some vendors do not admit bugs identified in source code review.

Now I will tell you what happened when we had asked an overseas company to develop some customizations in a certain project. When we conducted a source code review, we pointed out that there was an obvious bug, but they told us that they did not accpet it, and they requested to put out the evidence.

After all, we created test data that caused a bug and put out a test report. Then, they finally recognized the bug.

We have heard that some other vendors would respond like that.

It has never been better to specify what review should be conducted　at the contract stage, what review should be conducted and who will respond to the defects found in the review (in the case of domestic, even after the contract making, if stating in the “Project Plan” and adjusting it, there is not propblem.)

However, when Bridge SE (an engineer who works among various overseas vendors and makes various adjustments) was stable in the company, he or she responded to the bug found in the source code review. It is important to create a stable process.

There are also a way to prevent misunderstanding by simplifying the screen design

When it comes to overseas applications including Oracle EBS (e-Business Suite, integrated package for core business made by Oracle Corporation *), you can use screen switching by tabs and the processing content of one screen is simple.
This may ensure maintainability, and when you design an complicated screen, there may be an idea that re-work will occur if the specification is incorrectly transmitted. You may think that if you take the time to make something difficult, you lose the opportunity. * Oracle EBS is a registered trademark of Oracle Corporation and its subsidiaries and affiliates in the United States and other countries.

The same is true for business applications for which we support development, and overseas development vendors tend to request simple screens. That would develop it correctly, and there would be less re-work.

In fact, if the screen design is craftsman-like operability, which is often used in Japanese business applications, developers of foreign vendors are said to be unable to understand the specifications themselves.

In summary, when ordering developments to overseas vendors, it is a key to success to keep in mind a simple and accurate screen design that is clear at the moment of specification transmission.

Not only is the screen itself simple, but let's simply inform what is to be realized without misunderstanding. In that case, in Japanese, it tends to be vague or abstract. Even though we Japanese people intend to write logically, it seems to be a way of "emotional" designation that is left to the developer's discretion from the perspective of foreigners.

Therefore, the point is to write in English from the beginning and in a concise manner with bullet points.

<<Read [Part 16]Read [Part 18]>>

Inquiries about our services and solutions