MDevSPICE Software Configuration Management Process

Overview

Document and evidence the software configuration management process per IEC 62304 and MDevSPICE: identification, change control, build and release, configuration status accounting.

Getting Started

Add your source materials to the project workspace, then activate the MDevSPICE Software Configuration Management Process skill. The agent will guide you through the process step by step.

Example Conversation

Below is an example of how a typical MDevSPICE Software configuration management process session unfolds. The agent confirms scope and drafts content aligned to MDevSPICE and IEC 62304.

You: We need to prepare our MDevSPICE Software configuration management process document. Can you draft it based on our current procedures and evidence?

Agent: I’ll draft the Software configuration management process content. Do you have existing materials in the workspace (e.g. process lists, quality procedures, design history file references) I should use, or should I create a structure from the MDevSPICE reference?

You: We have a procedure index and our DHF structure. Use those and the MDevSPICE process model reference.

Agent: I’ve loaded the MDevSPICE process model (IEC 62304 process areas). I’ll map your procedures and evidence to each process area and produce the Software configuration management process with coverage table and evidence references.

Sample Output Excerpt

Below is a representative excerpt from an MDevSPICE Software configuration management process document.

Scope and structure

This document covers [organisation]’s MDevSPICE Software configuration management process. It is aligned to the MDevSPICE process reference model and IEC 62304 (software development, maintenance, risk management, configuration management, problem resolution).

Process / evidence (example)

Extension and validation

This skill does not include custom validation tools. Elaboration is guided by the workflow in the skill and the MDevSPICE / IEC 62304 references. You can add extension tools later (e.g. to check process coverage or regulatory mapping) by editing the skill’s extension.ts.