- From: Vijay Sikka <vsikka@nirixa.com>
- Date: Thu, 23 May 2002 20:06:47 -0700
- To: www-qa@w3.org
- Message-ID: <3CEDAE47.1060306@nirixa.com>
From our worldview, Certification as a process is defined as 1. QA or test experts collect compliance requirements and data. This is an iterative/interactive process 2. QA/test experts perform compliance check that criteria defined in the requirements definition are met 3. The requirements definition has been defined by a certifying organization or a standards body or an informal consortium 4. A final report on compliance conformity and/or standards certification is created and approved. 5. Ongoing compliance requirements and changes to requirements definition are maintained by iterative effort. Let me know what you think about it. All views and feedback is welcome. Vijay Sikka ------------- Founder and Principal, Nirixa, Inc. 303 Almaden Boulevard 6th Floor San Jose, CA - 95110 408.998.7844 (main) 408.998.7845 (fax) vsikka@nirixa.com www.nirixa.com Mark Skall wrote: > Karl, > > I just noticed the definition for certification. Again, I think it's > too limiting. The one I would recommend (following up on my proposed > validation definition) is "acknowledgement that a validation was > completed and criteria established by the certifying organization for > issuing a certificate (or branding) has been met." Again, this and > the validation definition are the ones we've used at NIST and we've > published in various places including the Encyclopedia of Software > Engineering. > > Mark > > > > **************************************************************** > Mark Skall > Chief, Software Diagnostics and Conformance Testing Division > Information Technology Laboratory > National Institute of Standards and Technology (NIST) > 100 Bureau Drive, Stop 8970 > Gaithersburg, MD 20899-8970 > > Voice: 301-975-3262 > Fax: 301-590-9174 > Email: skall@nist.gov > **************************************************************** > >
Received on Thursday, 23 May 2002 23:02:18 UTC