...
An evaluation report can have only one software candidate but multiple building blocks against which the software candidate is tested.
That means creating an evaluation report requires to select certain BB and accordingly the entry form adapts according to the requirements in the BB specifications.
An evaluation report as the following phases of submission (will be reflected in Jira issues)
Drafted: Open to be edited
Submitted: Ready to be reviewed by GovStack Staff
Reviewed: Review finished and ready to be published
Published: Published and cannot be changed
An evaluation report as always one version of software and one version of the BB specs
If the version changes or something needs changing, a new evaluation report needs to be submitted → creating a history
A evaluation report consists of (example: Compliance Evaluation: Template )
Meta information
Manual entry on Deployment and Requirement Specification Compliance
Test Harness Report for Interface Compliance
The categorization (Failed, Level 1, Level 2) according to Compliance Concept can be either defined automatically or done by the GovStack Staff in Review Process
The form should be automatically created and filled with all required and optional requirements for each BB.
Questions from Dominica to Nico
...