Browse Prior Art Database

Method for Systems to Recommend Readiness for Certification

IP.com Disclosure Number: IPCOM000200629D
Publication Date: 2010-Oct-21
Document File: 2 page(s) / 21K

Publishing Venue

The IP.com Prior Art Database

Abstract

Disclosed is a software product certification method which allows a system seeking certification to identify for itself when, over the course of its normal mode of operation, it meets the functional and interoperability requirements for certification. The method incorporates a testing manifest within the software system which stores functional and interoperability requirements for certification as well as a system’s performance results. The method improves the certification process for both software vendors and customers.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 51% of the total text.

Page 01 of 2

Method for Systems to Recommend Readiness for Certification

Product certification presents a number of difficulties and burdens to product manufacturers. For example, to obtain Internet Protocol version 6 (IPv6) certification, a pre-release version of the hardware and system software must be shipped to a certification center and undergo a battery of tests by an independent party, with no guarantee of success. In other cases, certification for a new system to run a particular application or Operating System (OS) requires that the vendor looking to be qualified exhaustively run the test suite. The testing vendor submits results to the certification body once it attains a favorable result. This creates heavy physical hardware and labor costs for products that oftentimes are already operating with narrow profit margins. To improve efficiency and reduce costs, vendors need methods that require less persistent care and feeding in order to certify hardware.

The disclosed solution is a method that allows the system itself to identify when it has met the functional and interoperability requirements for certification over the course of its normal mode of operation. One or more systems can generate alerts as to the system's certification readiness without any explicit personnel or infrastructure support. The system can go through either normal internal product testing or field operation testing while tracking which functions, Application Programming Interfaces (APIs), and criteria required by the test suite have been run; the system also tracks their results.

In a preferred embodiment, the testing system stores within its software a manifest and understanding of all the required server states and conformance/interoperability requirements, along with corresponding behaviors which would indicate the equivalency of passing various conformance tests.

For example, a conformance test might require the implementation of a specific subset of a standard programmatic interface, such as the Intelligent Platform Management Interface (IPMI). As such, a typical test suite attempts to execute each of these commands (typically with little motivation to observe the actual functional correctness of the command) in order to ensure that the system under testing supports the proper commands.

In a best mode of operation, the server to be certified instead monitors over its lifetime the commands which have been executed. If, during the natural span of its life-cycle, the server happens to execute each of the commands required to meet this com...