As performance improves with the use of ICT technology for all kinds of products, trouble is frequently occurring attributable to the software. Software can contradict the degree of freedom in construction, and the more performance increases, software diversifies and grows in scale, the more it results in low-efficiency and low-quality products, and this causes even more trouble.

In order to prevent trouble from occurring in advance, it is vital to improve reliability. Software development goes through multiple stages from basic design to installation, and reliability is gradually lost along the process. To counter this are efforts to improve the reliability of each stage by referring to previous development examples, patternizing and extracting them to use in conducting formal inspections.

Sometimes diverse programming languages are used for a single software application during large-scale software development, and it can be difficult to inspect the reliability for each language. In contrast, by inspection for each function regardless of the language, the inspection function can be reused to provide a development environment that can deal with multiple programming languages. 

In most cases in software development today, specifications are updated and added during the development process. Conducting development through a new framework using this seed allows appropriate decisions to be made only on the necessary parts, revisions to be added while maintaining quality, and overall high-efficiency software development.

Sponsord research, Collaboration research, Technical consultation