This Knowledge Base contains a set of useful documents we used during the service validation and testing process.
| Document | Purpose | Owner|||
|---|---|---|---|---|
| Acceptance Criteria (example) | Input to the service assessment (by Service Operation Manager, CSI manager) | Marcin Wolski | ||
| User Support Survey | Evaluating service support (by users) | Aleksandra Radulovic | ||
| System Usability Scale [ source: Brooke, J. "SUS: a "quick and dirty" usability scale". In P. W. Jordan, B. Thomas, B. A. Weerdmeester, & A. L. McClelland. Usability Evaluation in Industry. London: Taylor and Francis, 1996 ] | SUS give us global view of subjective assessments of usability. | Szymon Kupiński | ||
Test Plan description (applicable to any evaluation, test or audit that involves a group of participants) (Slight update upon the DS4.1.1 TA feedback) | Subjects that need to be discussed, defined and agreed between the requester and evaluators before the assessment is commenced | Branko Marovic | ||
| Input to the security audit (pen testing and security code audit) | Getting the input to start the audit | Gerard Frankowski Branko Mažar | ||
| Input to the quality code review (DOES NOT EXIST) | Getting the input to start the audit | Patryk Promiński Simone Visconti | ||
| Pre-assessment survey (it is already on the public site) | Grabbing the preliminary information about the service candidate to production | Szymon Kupiński | ||
| Automatic quality code review | A brief summary of the automated source code analyze procedure | |||
| User view on a software quality | A simple questionnaire to gather the user point of view about a software and its perception of quality | Service and Architecture documentation (DOES NOT EXISTS) | Getting the input to start the documentation / operational audit (installation guide, upgrade guide, deployment etc.) | Tobias Appel Dalibor Kirchmayer |