1. Human vs. Computer
2. Business units (users) vs. IT units
3. Current procedures vs. New procedures
4. Usability vs. Control
5. Specification documents vs. Implemented Systems

• Big difference in philosophy and logics.
• The best practice for human process may not be the best solution for computer logics.
• Real life(day-to-day life) vs. virtual world (conceptual)
• People can think, while computers do not think, just process the commands given.
• Business Analysis and Designing, therefore, should be conducted based upon what the computershould do, not upon what the peopleare currently doing.

• Requirements vs. Solutions
• • Business units have requirements, while IT units are to offer solutions
• Differences in language, philosophy and expertise
• Due to the differences, communication can be poor;
• • between the user organization and the system integrator
  • within the user organization; between Business unit and IT units, and also among users, among IT specialists

In case of the replacement of the current system, the analysis of current procedure (As-Is) leads to the extraction of the system requirements for the new procedure of the new system (To-Be) and then to Kaizen.

The users, familiar with the current procedure, are normally reluctant to change the procedure, and tend to resist to the new procedure of the new system.

• Both users and IT specialists tend to look for the convenience and detest controlling mechanism. However, a variety of controlling techniques are required to enhance the reliability of the system. All the Systems are to be properly designed to maintain desirable controls.
• Ease of Use vs. Security.

In some occasions, there can be gaps between the specification documents and the implemented systems

• Even though the appropriate documents are prepared at the beginning, the specification documents are not necessary updated when the system is modified based on the new requirements and facts found during the course of development.
• During the start-up period of operation, there always are some needs for alteration of specification. The systems are often modified without appropriate documentation.

Firstly, the user organization and the system integrator should acknowledge that the gaps exist, and there is no way to remove these gaps completely.

In order to mitigate the impact of each gap;

1. Human vs. Computer
   The project team members must note the difference at the start of the project.
2. Business units vs. IT units
   The system implementation methodology requires means, such as charts, diagrams, maps, etc., understandable for both users and IT specialists.
3. Current procedure vs. New procedure
   The tools, such as simulation, prototype application, pilot model, etc., based on the identification and analysis of the requirements of the new procedure, are essential to enhance the understanding of the new procedure. The tools are to be able to iteratively demonstrate the new procedure to project members and users in an organized manner. These are especially required for the new business.
4. Usability vs. Control
   The project team members needs to have a balanced view both on the ease of operation and the control features.
5. Specification documents vs. programs
   It is beneficial to deploy a methodology, e.g. PEXA ® Methodology, that is designed to associate the system with the documentation. Synchronized documents are essential for future maintenance and improvement.