About System Verification Theory Research Council
In 1983, having attentively recognized the significance of verification work, we started our system verification services. The scope of verification has been varying with the kind of services for application packages, peripherals and SI systems etc.
In due course of accumulation of the experiences and achievements in verification work, we have come to establish a characteristic verification style which was good enough to deal with the individual need of our users. Critically speaking, however, this verification style being sometimes localized because of delay in work standardization, it had often relied upon the personal experience and skill of verification engineers in charge.
For that reason, it had been getting more and more necessary for us to seek after systematically organized system verification methods, before we initiated an in-house board called System Verification Theory Research Council.
The principal operations of the Council consist of activities to integrate the system verification standardization with its theory, and to work over the methods and guidelines by holding a monthly conference to discuss about the procedures and consequences concerned.
Also, in order for us to come up with the truly efficient method of a noteworthy accomplishment in the world, we have decided to solicit such distinguished academic researchers to cooperate with us,
as follows:
In collaboration with
Prof. Hitoshi Kume (professor emeritus at Tokyo University, Veriserve Executive Advisor)
Prof. Yoshinori Iizuka (professor at Tokyo University)
Prof. Takeshi Nakajo (professor at Chuo University)
Dr. Yasuharu Nishi (assistant professor at the University of Electro-Communications)
Chronicle of the Research Council
Year |
Objective |
Achievement |
|---|---|---|
1994 |
Study of Test · Consensus of Understanding |
Study of Examples. |
1995 |
Study of Test · Consensus of Understanding |
Study of Examples, Compilation of Definitions of System Test Category. |
1996 |
Format of Test |
Compilation of Definitions of System Test Category, Compilation of Test Procedures of System Test. |
1997 |
Framework of Test |
Compilation of Test Procedures of System Test, "Test Procedures β". |
1998 |
Approach to Test |
Compilation of Test Procedures of System Test, "Test Procedures First Edition". |
1999 |
Know-How of Test |
Reconstruction of Test Procedures of System Test ( Constitution Test, Reconstruction of Compatibility Test, Reconstruction of Trouble Shooting Test ). |
2000 |
Integration of Test Design |
Completion of "Design Method of System Test according to the Functions of Software". |
2001 |
Compilation of Standards for Test Panning |
Project for "Estimation of Test", "Appropriateness of Test". |
2002 |
Collection of Test Know-How |
Project for "Appropriateness of Test", "Security Test", "Collection of Test Know-How", "Design Method of Functional Test". |
Themes of Verification Theory as Proposed "IMPOTANT" for Further Study
1.Theorization of Security Test
To work by concentrating on "Security Test for Operative Systems".
2.Collection of Test Know-How
To facilitate the use of methodically centered verification theory by collecting, and organizing, as a common property, the working knowledge of the technical employees. And also to facilitate the rapid training of verification technical staffs.
3.Compilation of Evaluation Criteria for Test Appropriateness
To study about judgment criteria for the accuracy of test design, and the termination of test.
4.Standardization of Combination Test
To establish, with emphasis on mountable devices, a test design method for combination test.
System test categories
Name of category |
Description of category |
|---|---|
Volume test |
To verify that the system operates correctly when large volumes, numbers, and kinds of data are processed on the test object. |
Storage test |
To verify that the test object operates correctly when the system is short of resources or about to run short of resources. |
High frequency test |
To verify that the system operates correctly when a large number of processes that may exceed the throughput limit per unit of time are requested of the test object. |
Repeated operation test |
To verify that the system operates correctly when time consuming processes are repeatedly requested of the test object. |
Configuration test |
To verify that the test object operates correctly when an element constituting the system in the same environment as the test object is deleted, replaced, an attribute is changed, or when another element is added to the same environment. |
Compatibility test |
To verify that the elements constituting the system in the same environment as the test object operate correctly when the test object is added to an environment or when the test object is deleted, replaced, or its attribute is changed. |
Data compatibility test |
To verify that the system operates correctly when data in a format that can be used by the test object are processed. |
Test of response to a failure |
To verify that the system responds to a failure when it occurs, including whether the effect is confined to the local area, whether it will be fatal, and to what extent the effect of the failure can be recovered. |
Usability test |
To evaluate the visibility and operationality of the user interface of the test object. |
Security test |
To verify that appropriate measures are taken to prevent security breaches of the test object. |
Document test |
To evaluate the technical correctness of the document (manual) provided to the user. |
©VERISERVE Corporation. All Rights Reserved.