- Case-studies
- Java framework change
case-studies
Case-studies
60+ companies of the TOP200 companies listed on the Tokyo Stock Exchange chose us.
Idemitsu Kosan, Nissan, Japan Airlines, SoftBank, Kyocera, TOTO, Murata Manufacturing, Japan Petroleum Exploration(JAPEX), Unitika, Nitori, Toppan, Ricoh, Nitto Denko, Token, DAIDO LIFE INSURANCE, Mizuho Research & Technologies, Okasan Information Systems, Kanden Systems, JAL Information Technology(JIT), ITEC HANKYU HANSHIN, Nishitetsu Information System, KIRIN BUSINESS SYSTEM, JFE Systems, KOBELCO SYSTEMS, Toray Systems Center, Bridgestone Software, Tec Information Systems, NEC Group, NTT Group, T.D.I, PERSOL P&T, Unisystem, etc.
Customer Testimonial (presentations)
PERSOL P&T
Japan Petroleum Exploration(JAPEX)
Japan Airlines
Nissan Motor
JAL Information Technology(JIT)
What often happens during Java framework change / Java upgrade
Java framework change
- As the time and budget of system migration is limited, bugs often occur in the re-development process due to missing functionalities and insufficient testing. Users have to test and take the responsibility of quality.
- The maintainability of Java source generated by most Java framework conversion tools is poor. Without testing tools, a large amount of testing hours is required, after which quality problems still remain.
Java upgrade
- Java upgrade involves not only version differences but also differences in existing and new browser, DB, AP server, and other problems.
- Most of conversion tools can’t cover some detailed problems.
- Most migration companies don’t run functional test and leave the test to users.
Because users do not know the weak points of the migration, many potential quality problems can’t be identified, even although they spend a lot of time for testing .
Our features of Java framework change / Java upgrade
Java framework change
- Use AI tools to analyze Java programs and convert with high maintainability, perform test with coverage of each migration technical point.
- Based on proven expertise and conversion tool we have accumulated from 50+ projects, our conversion rate can reach almost 100%.
- Migrate to Java’s mainstream framework Spring MVC with the same maintainability as a new development or migrate to a Java framework required by customer.
- Java upgrade, OS change, AP server change, DB change are done along with framework change.
- Use in-house developed AI testing tool to automatically operate migrated system, compare existing and new systems, and monitor the test coverage of each technical point.
Make sure comparison test is done efficiently according to business scenarios.
Java upgrade
- Based on proven expertise we have accumulated from 60+ projects, our tool can be used in different system environments and achieve almost 100% conversion rate.
- When manual correction is unavoidable, we will run unit test for the manually corrected portion. Even if there’s no manual modification, the tool can detect bug-prone spots and we run unit comparison test.
- Run comparison test on business scenarios and compare and verify each technical point.
The maintainability of migrated source
Maintenance problems won’t happen in Java upgrade. Even if it’s Java framework change, we can achieve high maintainability.
Struts ⇒ Spring MVC
Comparison before and after automated conversion
WACs ⇒ Spring MVC
Comparison before and after automated conversion
Seasar2 ⇒ Spring MVC
Comparison before and after automated conversion
System Reform Schedule
Migration Cases
A Java system of an auto company
- Development process
- Inventory, migration design, specification documentation, source migration – system test, user acceptance test support, go-live
- System reform information
- Java1.3 → Java6
WACs(JavaEE) → NSF(Struts1)
SQC → Pro*C
WAS V4 → JBoss 5.0.1
DB2 7.2 → Oracle11
AIX5 → RedHat Linux 5.4
WindowsXP/7 → No change - Current system scale
- Java/JSP：2,397KL、SQC：484.7KL
- Development period
- 10 months
Three Java systems from an airline
- Development process
- Inventory, migration design, UI design – migration test, system test & user acceptance test support
- System reform information
- Java1.2/1.3/1.4 → Java6
WACs4.0 → Struts2.2 + Spring3.0
AIX C → Linux C
AIX Perl&Shell → Linux Perl&Shell
DB2 8.1 → DB2 9.7
AIX5.2 → RedHat Linux 6
WindowsXP → WindowsXP/Vista/7 - Current system scale
- Java/JSP：1,535KL、SQC：86.8KL
- Development period
- 10 months
A membership website system
- Development process
- Inventory, migration design, source code migration – migration test, system test & user acceptance test support
- System reform information
- Java7 → Java8
Seasar2 → Macchinetta(SpringMVC4.3）
PostgreSQL9.5.6 → No change
Tomcat7.0 → Tomcat9.0
Linux6.4 → RHEL7.4
Windows7 → Windows10 - Current system scale
- Java/JSP：125.6KL
- Development period
- 6 months
A membership management system
- Development process
- Inventory, migration design, source code migration – migration test, system test & user acceptance test support
- System reform information
- Java4 → Java6
WAS V5.1 → WAS V8.5
Struts 1.0/1.1 → Struts 1.3.10
AIX Shell → Linux Shell
DB2 V8 → No change
AIX 5 → RedHat Linux 6.4
Windows7 → No change - Current system scale
- Java：686.4KL、AIX Shell：27KL
- Development period
- 8 months
A management system
- Development process
- Inventory, migration design, source code migration – migration test, system test & user acceptance test support
- System reform information
- Java6 → Java8
Struts1 → SpringMVC4.3
Oracle11g → Oracle12c
JBoss EAP5.1.1 → JBoss EAP7
Red Hat Linux 5.5 → Red Hat Linux 7
Windows7 → No change - Current system scale
- Java/JSP：70.5KL
- Development period
- 5 months