Products

Morris Medical Monday: Work Item Type "Software System Test"

By morrisd

Welcome back to Morris Medical Monday: a weekly series for medical device development companies (and companies who are related to such companies), providing some useful information about Polarion solutions and Polarion extensions.

Today we will continue on the subject of Polarion’s MedPack extension, and have a look into MedPack’s Software System Test type Work Item.


Software System Test


Description


A system test description according to clause 5.7.1 of the IEC 62304:2006. Any issue of this type either describes the test completely or links to test procedure descriptions or code to perform the test. It must be linked to the software system(s) and software item(s) covered by the test as well as the software requirement(s) that is tested. System tests must only be performed in case of a class B or class C project.

Workflow Steps


The Software System Test Work Item uses the standard Full Workflow.

FullWorkflow_Overview

Traceability & Impact


A Software System Test Work Item must be traceable to a Software Requirement Work Item and has an impact on an Anomaly.
For more information on traceability and impacts, see the Traceability wiki page.

Attributes


Work Item Attributes


The following custom fields must be filled out before verification can be requested:













































Attribute Name Type Description
Input stimuli Text Establish tests for software requirements: Input value (as required by IEC 62304:2006->5.7.1).
Expected outcomes Text Establish tests for software requirements: Expected outcomes (as required by IEC 62304:2006->5.7.1).
Pass/Fail criteria Text Establish tests for software requirements: Pass/Fail criteria (as required by IEC 62304:2006->5.7.1).
Procedure used Enum Establish tests for software requirements: Procedure used.
This enumeration has to be filled out from the administrator. The procedure has to be explained in Integration Test Plan. (as required byIEC 62304:2006->5.7.1).
Tester Text (as required by IEC 62304:2006->5.7.5c/9.8g).
Relevant test tool(s) used Text (as required by IEC 62304:2006->9.8e).
Test parameters to ensure repeatability Text (as required by IEC 62304:2006->5.7.5 NOTE/9.8d).

Preset values for the “Procedure used” enumeration


























































Name Description
Blackbox test using equivalence classes A blackbox test is performed, test values are determined using equivalence classes.
Blackbox test, boundary based A blackbox test is performed, test values are determined using boundaries of equivalence classes.
Blackbox test using decision tables A blackbox test is performed, test values are determined using decision tables.
Stress test A stress test ist performed, making the system crash and see how well it recovers.
Long term test A long term test is performed to check for long-time performance, memory leaks etc.
Error based test The system is fed with unexpected input values.
Load test A load test is performed to check the system’s behaviour under heavy load.
Volume test The system is fed with a huge amount of input data.
Inspection A group of usability experts perform a usability inspection on the system.
Usability lab The system is tested in a usability lab.
Questionnaire Users are given a questionnaire.
Interview Users are interviewed about their experience with the system.

Verification/Evaluation Attributes


The following custom fields must be filled out before verification/evaluation can be finshed and the work item can be closed:

























Attribute Name Type Description
Reviewer Text Person(s) to perform, performing or have performed a review.
Review summary Text Short summary of the review. Attachments should be used for additional information.
Last review date Date Hidden field automatically set when review has been finshed. Intended to be used for sorting and statistical analysis.

Evaluation Checklist


The following checklist must be filled out before evaluation can be finshed and the work item can be closed:













Checklist entry Description
Test passed (as required by IEC 62304:2006->5.7.4d).

Possible Resolutions


The following table shows the possible resolution values when the work item is closed:





















Resolution Name Description
Done The software system test has been executed and successfully evaluated.
Obsolete The software system test has become obsolete and is no longer needed.
Discarded The work item entry has been discarded. No further attention is needed.

For more information about Polarion’s MedPack visit our Extension Portal using following link:

http://extensions.polarion.com/extensions/31-polarion-alm-medpack-iec-62304. I hope you liked this article and you will visit our Blog again when there is another Morris Medical Monday article



Webinar Banner: Improve Software Verification and Validation in Regulated Environments


 

Banner photo: Flicker/Samuel Mann

Morris Daniel

Leave a Reply

This article first appeared on the Siemens Digital Industries Software blog at https://blogs.stage.sw.siemens.com/polarion/morris-medical-monday-work-item-type-software-system-test/