Acceptance Criteria
For RISQ Artifacts
The purpose of RISQ is to provide reference information on software
quality. The methods, tools and techniques described in RISQ artifacts
represent accepted practice or new technology. The reference
information must meet certain criteria reflecting professional
standards for publication. Any requirement may be waived at the
discretion of the RISQ administrator and any submission may be
rejected also at the discretion of the RISQ administrator. All
artifacts must be related to high integrity software.
- Requirements. HHRF/ RISQ must ensure that its credibility is
sustained when it makes available information about technology. HHRF/RISQ
must ensure that it does not appear to be endorsing commercial products,
while at the same time assuring equal opportunity for technology to be
exposed to industry. The RISQ will enforce acceptance criteria for each
entity's artifact. A preliminary set of criteria are identified for document
and tool artifacts. Acceptance criteria will eventually be developed for
all artifact types. The RISQ/CHISSA project manager will review recommendations
from the RISQ administrator and has final authority for accepting or rejecting
submissions for this facility.
- Document Artifact. A document submitted to RISQ must have had
a technical peer review (e.g., a review process for a published journal
article; or a refereed conference paper) and must be associated with the
RISQ taxonomy (i.e., it must address one or more topics identified in the
taxonomy). The document may describe a software development or assurance
method, a software tool associated with the method, an experiment of the
method. It may contain case studies of using the method, or may provide
a tutorial for using the method. Documents may also be surveys of a specific
subject area (e.g., software safety, testing).
- Tool Artifact. A software tool may implement a software development
or assurance (verification, testing, any diagnostic) method or a new approach
or algorithm to solve a specific problem. It must be associated with the
taxonomy of the RISQ (i.e., it must address one or more topics identified
in the taxonomy.) Current acceptance criteria are:
- The tool must be supported by a technical paper that has had a technical
peer review (e.g., refereed conference ). The paper must describe the tool
and the technology on which it is based. Normally, both the tool artifact
and the supporting technical paper document artifact should be submitted
to the HHRF/ RISQ.
- The submitter of the tool must supply evidence that the tool will completely
execute in its demonstration mode.
- The demonstration consists of a tutorial accompanying each demonstrated
function of the tool (see tool installation instructions.) The submitter
must provide on-line user documentation separate from the demonstration.
- In general, tool demonstrations normally execute on the submitter's
server.
- The submitter is responsible for modifying the tool to be able to execute
under control of the RISQ, which executes via the WWW.
Return to RISQ.