# Software Readiness Level

Software Readiness Levels (SRLs) are used to articulate the current status of a project in its development cycle. 

Defining a robust and repeatable process will ensure the progression of solution development can be thoroughly validated before going into production. 

SRLs are key to articulating expected requirements or phases of development requested in a 'call to tender'. For example; a tender request may articulate progression of a project from SRL 4 to an SRL 6. This outlines typical expectations for the tender and demonstrates to the community the expected artefacts/value to be delivered. 

These SRLs and breakdowns below are typical of core node development, they may only be partly suitable for other types of development but they provide a useful guide nevertheless.

<table><thead><tr><th width="170">Stage</th><th width="70">SRL</th><th width="263">Description</th><th>Typical Artefact</th></tr></thead><tbody><tr><td>Research</td><td>1</td><td>Idea Formulated</td><td>Outline Problem Statement</td></tr><tr><td></td><td></td><td>Basic Research </td><td>Research Paper</td></tr><tr><td>Innovation</td><td>2</td><td>CPS Produced</td><td><p>CPS or Technical </p><p>Report</p></td></tr><tr><td></td><td></td><td>Initial Delta-Q Analysis</td><td>Analysis Report</td></tr><tr><td></td><td></td><td>First CIP or Technical Report Produced</td><td>CIP</td></tr><tr><td>Feasibility</td><td>3</td><td>Outline Feasibility Demonstrated</td><td>Report</td></tr><tr><td></td><td></td><td>Initial Software Demonstrators</td><td>Software Demonstrators</td></tr><tr><td></td><td></td><td>CIP Updated</td><td>Revised CIP</td></tr><tr><td>Design</td><td>4</td><td>Outline Design Study</td><td>Outline Design Report</td></tr><tr><td></td><td></td><td>Feasibility Study Completed (Functionality)</td><td>Feasability Study</td></tr><tr><td></td><td></td><td>Quantitative Timing Analysis Completed</td><td>Detailed Timing Analysis</td></tr><tr><td></td><td></td><td>Detailed Software Prototypes Produced</td><td>Software Prototypes</td></tr><tr><td>Initial Implementation</td><td>5</td><td>Detailed Design Completed</td><td>Detailed Design Produced</td></tr><tr><td></td><td></td><td>Code Investigation Completed</td><td>Report on Code Investigation</td></tr><tr><td></td><td></td><td>Design Reviewed</td><td>Technical Workshop(s)</td></tr><tr><td></td><td></td><td>Implementation Plan Produced</td><td>Implementation Plan</td></tr><tr><td></td><td></td><td>Initial Implementation</td><td>Software Deliverables</td></tr><tr><td>Main Implementation</td><td>6</td><td>Code Completed</td><td>Software Deliverable</td></tr><tr><td></td><td></td><td>Functionality Tests Completed</td><td>Test Results</td></tr><tr><td></td><td></td><td>Security Review Completed</td><td>Security Audit Report</td></tr><tr><td></td><td></td><td>Performance Tests Completed as Necessary</td><td>Performance Reports</td></tr><tr><td>Integration</td><td>7</td><td>Integration Into Node</td><td>Integrated Node (Preview Release)</td></tr><tr><td></td><td></td><td>Integration Functionality Tests Completed</td><td>Test Results</td></tr><tr><td></td><td></td><td>Node Deployed to Preview Test Environment</td><td>Explorers shows deployment</td></tr><tr><td></td><td></td><td>Performance Tests Completed</td><td>Preformance Reports</td></tr><tr><td>Deployment</td><td>8</td><td>Mainnet-ready node Released</td><td>Intergrated Node (Mainnet Release)</td></tr><tr><td></td><td></td><td>Node Deployed to Preproduction Test Environment</td><td>Explorers show deployment</td></tr><tr><td></td><td></td><td>Node Deployed to Mainnet</td><td>(Possible hard fork)</td></tr><tr><td>Completion</td><td>9</td><td>Post-deployment snags fixed</td><td>Snagging Report</td></tr><tr><td></td><td></td><td>Live Performance Evaluation Completed</td><td>Performance Reporting</td></tr><tr><td></td><td></td><td>Residual Issues Identified</td><td>Final Report</td></tr></tbody></table>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://committees.docs.intersectmbo.org/intersect-technical-steering-committee/technical-roadmap/project-cards-explained/software-readiness-level.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.