A B C Section/CProcess Keywords Check

LIFECYCLE PROCESESS
4.00 General Requirements
X X X 4.1 Quality Management Systems
X X X 4.2 Risk Management
X X X 4.3 Software safety classification
X X X 4.4 Legacy Software
5.00 Software development process
5.10 Software development planning
X X X 5.1.1 Software Development Plan
X X X 5.1.2 Software Development Plan maintenance
X X X 5.1.3 Software development plan reference to system design and development
X 5.1.4 Software development standard, methods and tools planning
X X 5.1.5 Software integration and integration testing planning
X X X 5.1.6 Software verification planning
X X X 5.1.7 Software risk management planning
X X X 5.1.8 Documentation planning
X X X 5.1.9 Software configuration management planning
X X 5.1.10 Supporting Items to be controlled
X X 5.1.11 Software configuration item controlled before verification
X X 5.1.12 Identification and avoidance of common software defects
X X 5.20 Software requirements analysis
X X X 5.2.1 Define and document software requirements from system requirements
X X X 5.2.2 Software requirements content
X X 5.2.3 Include risk control measures in software requirements
X X X 5.2.4 Re-evaluate medical device risk analysis
X X X 5.2.5 Update requirements
X X X 5.2.6 Verify software requirements task x
5.30 Software architectural design
X X 5.3.1 Transform software requirements into an architecture
X X 5.3.2 Develop an architecture for the interfaces of software items
X X 5.3.3 Specify functional and performance requirements of SOUP item
X X 5.3.4 Specify system hardware and software required by SOUP item
X 5.3.5 Identify segregation necessary for risk control
X X 5.3.6 Verify software architecture
5.40 Software detailed design
X X 5.4.1 Subdivide software into software units
X 5.4.2 Develop detailed design for each software unit
X 5.4.3 Develop detailed design for interfaces
 X 5.4.4 Verify detailed design task
5.50 Software unit implementation
X X X 5.5.1 Implement each software unit
X X 5.5.2 Establish software unit verification process x
X X 5.5.3 Software unit acceptance criteria x
X 5.5.4 Additional software unit acceptance criteria
X X 5.5.5 Software unit verification x
5.60 Software Integration and Integration Testing
X X 5.6.1 Integrate software units x
X X 5.6.2 Verify software integration x
X X 5.6.3 Software integration testing x
X X 5.6.4 Software integration testing content x
X X 5.6.5 Evaluate software integration test procedures x
X X 5.6.6 Conduct regression tests x
X X 5.6.7 Integration test record contents x
X X 5.6.8 Use software problem resolution process
5.70 Software system testing
X X X 5.7.1 Establish tests for software requirements#
X X X 5.7.2 Use software problem resolution process
X X X 5.7.3 Retest after changes
X X X 5.7.4 Evaluate software system testing
X X X 5.7.5 Software system test record contents
5.80 Software release for utilization at a system level
X X X 5.8.1 Ensure software verification is complete
X X X 5.8.2 Document known residual anomalies
X X 5.8.3 Evaluate known residual anomalies
X X X 5.8.4 Document released versions
X X 5.8.5 Document how released software was created
X X 5.8.6 Ensure activities and tasks are complete
X X X 5.8.7 Archive software
X X X 5.8.8 Assure reliable delivery of released software
6.00 Software maintenance process
X X X 6.10 Establish software maintenance plan
6.20 Problem and Modification
6.2.1 Document and evaluate feedback
X X X 6.2.1.1 Monitor feedback
X X X 6.2.1.2 Document and evaluate feedback
X X X 6.2.1.3 Evaluate problem report's affects on safety
X X X 6.2.2 Use software problem resolution process
X X X 6.2.3 Analyze change requests
X X X 6.2.4 Change request approval
X X X 6.2.5 Communicate to users and regulators
6.30 Modification Implementation
X X X 6.3.1 Use established process to implement modification
X X X 6.3.2 Re-release modified software system
SUPPORT
7.00 Software risk management process
7.10 Analysis of software contributing to hazardous situations
X X 7.1.1 Identify software items that could contribute to a hazardous situation
X X 7.1.2 Identify potential causes of contribution to a hazardous situation
X X 7.1.3 Review published SOUP anomaly lists
X X 7.1.4 Document potential causes
7.20 Risk control measures
X X 7.2.1 Define Risk control measures
X X 7.2.2 Risk control measures implemented in software
7.30 Verification of Risk control measures
X X 7.3.1 Verify Risk control measures
7.3.2 empty
X X 7.3.3 Document traceability
7.40 Risk management of software changes
X X X 7.4.1 Analyze changes to medical device software with respect to safety
X X 7.4.2 Analyze impact software changes on existing risk control measures
X X 7.4.3 Perform risk management activities based on analyses
8.00 Software configuration management Process
8.10 Configuration identification
X X X 8.1.1 Establish means to identify configuration items
X X X 8.1.2 Identify SOUP
X X X 8.1.3 Identify system configuration documentation
8.2 Change control
X X X 8.2.1 Approve Change requests
X X X 8.2.2 Implement changes
X X X 8.2.3 Verify changes
X X X 8.2.4 Provide means for traceability of change
8.3 Configuration status accounting
X X X 8.3.1 Configuration status accounting task
9.00 Software problem resolution Process
X X X 9.10 Prepare problem reports
X X X 9.20 Investigate the problem
X X X 9.30 Advise relevant parties
X X X 9.40 Use change control process
X X X 9.50 Maintain records
X X X 9.60 Analyze problems for trends
X X X 9.70 Verify software problem resolution
X X X 9.80 Test documentation contents
Artefact/Reference/Document

SW Dev Plan

SW Dev Plan
SW Dev Plan or Test Concept
SW Dev Plan

SW Dev Plan

SW Dev Plan
Test report (verification/validaition?)

Test report (verification/validaition?)