Achievements and Strengths
Verification Technology
A Unique Method Containing our Experience and Know-how to Ensure High Quality
Realizing Standardized Verification through a Defined Workflow Including Work Procedures and Deliverables
Verification, which tends to be left to individuals, is performed according to our own company standards. We have defined the verification workflow and included work procedures, deliverables, and samples to offer the VeriServe Standard Method (VSMethod). All VeriServe employees possess thorough knowledge about the VSMethod, allowing them to provide high-quality service. In addition, with the VSMethod serving as the foundation, it becomes possible to also apply it to verification targets and individual cases in a suitable manner. This means that we provide you with an optimal level of verification.
System Test Categories for Purpose-Based Testing Analysis and systemization of the causes of failures,
leveraging VeriServe's results to date, and efficient fault identification.
At VeriServe, system verification, which often relies on the experience and skills of each engineer, was categorized by failures that easily occur and their causes based on past data analysis. This resulted in the establishment of our System Test Categories, which altogether consist of 11 categories. We conduct reliable and efficient system tests that are applicable to your product characteristics.
| 1. Volume Test | Used to confirm that everything is working properly even when requested to test software that involves high-capacity data processing, high-volume data processing, and various types of data processing. |
|---|---|
| 2. Storage Test | Used to confirm that the test target operates correctly even when resources to be used are likely to be insufficient or in a situation where resources are insufficient. |
| 3. High-frequency Test | Used to confirm that the system operates correctly even when a large number of processing requests that exceed processing capacity within the unit time are required for the test target. |
| 4. Cumulative Operating Test | Used to confirm that the system works correctly even if the test target is repeatedly required long periods for processing |
| 5. Configuration Test | Used to confirm that the test target operates correctly when elements that make up the system in the same environment as the test target are deleted, replaced, or changed in some way, or when another element is added to the same environment. |
| 6. Compatibility Test | Used to confirm that the components that make up the system in the environment operate correctly when the test target is added, deleted, replaced, or changed in some way for the environment. |
| 7. Data Compatibility Test | Used to confirm that the system operates correctly when processing data in a format that can be used for the test target. |
| 8. Non-functional Test | Used to confirm if potential failures can be dealt with, such as whether the impact at the time of the failure is localized, non-fatal, or how much can be recovered when a failure occurs. |
| 9. Usability Test | Used to evaluate the visibility and operability of the test target’s user interface. |
| 10. Security Test | Used to confirm that measures are appropriately in place to prevent unjust actions targeting the test subject. |
| 11. Document Test | Used to evaluate the technical accuracy of documents (manuals) provided to users. |