Skip to main content
QMSQMS
QMS
  • Welcome to your QMS
  • Quality Manual
  • Procedures
    • GP-001 Control of documents
    • GP-002 Quality planning
    • GP-003 Audits
    • GP-004 Vigilance system
    • GP-005 Human Resources and Training
    • GP-006 Non-conformity, Corrective and Preventive actions
    • GP-007 Post-market surveillance
    • GP-008 Product requirements
    • GP-009 Sales
    • GP-010 Purchases and suppliers evaluation
    • GP-011 Provision of service
    • GP-012 Design, Redesign and Development
      • Deprecated
      • Templates
        • T-012-001 Requirements
        • T-012-003 Test run
        • T-012-004 Software version release
        • T-012-005 Design change control
        • T-012-006 _Product name_ life cycle plan and report_YYYY_nnn
        • T-012-007 Formative evaluation plan_YYYY_nnn
        • T-012-008 Formative evaluation report_YYYY_nnn
        • T-012-009 Validation and testing of machine learning models_YYYY_nnn
        • T-012-010 Device backup verification_YYYY_nnn
        • T-012-012 Customers product version control_YYYY_nnn
        • T-012-013 Design stage review
        • T-012-014 Summative evaluation plan_YYYY_nnn
        • T-012-015 Summative evaluation report YYYY_nnn
        • T-012-016 Software usability test guide
        • T-012-017 Integration test review
        • T-012-018 Test plan
        • T-012-019 SOUP
        • T-012-020 Predetermined Change Control Plan
        • T-012-021 Product Design Phase 1 Checklist
        • T-012-022 Software Design Phase 2 Checklist
        • T-012-023 Software Development Plan
        • T-012-024 Software Candidate Release Phase 3 Checklist
        • T-012-025 Software Verification Phase 4 Checklist
        • T-012-026 Product Validation Phase 5 Checklist
        • T-012-027 Version delivery description
        • T-012-028 Software Requirement Specification
        • T-012-029 Software Architecture Description
        • T-012-030 Software Configuration Management Plan
        • T-012-031 Product Requirements Specification
        • T-012-032 SOUP Name
        • T-012-033 Software Tests Plan
        • T-012-034 Software Test Description
        • T-012-035 Software Test Run
        • T-012-036 Software development plan
      • Specific procedures
    • GP-013 Risk management
    • GP-014 Feedback and complaints
    • GP-015 Clinical evaluation
    • GP-016 Traceability and identification
    • GP-017 Technical assistance service
    • GP-018 Infrastructure and facilities
    • GP-019 Software validation plan
    • GP-020 QMS Data analysis
    • GP-021 Communications
    • GP-022 Document translation
    • GP-023 Change control management
    • GP-024 Cybersecurity
    • GP-025 Usability and Human Factors Engineering
    • GP-027 Corporate Governance
    • GP-050 Data Protection
    • GP-051 Security violations
    • GP-052 Data Privacy Impact Assessment (DPIA)
    • GP-100 Business Continuity (BCP) and Disaster Recovery plans (DRP)
    • GP-101 Information security
    • GP-200 Remote Data Acquisition in Clinical Investigations
    • GP-026 Market-specific product requirements
    • GP-110 Esquema Nacional de Seguridad
  • Records
  • Legit.Health Plus Version 1.1.0.0
  • Legit.Health Plus Version 1.1.0.1
  • Licenses and accreditations
  • External documentation
  • Procedures
  • GP-012 Design, Redesign and Development
  • Templates
  • T-012-024 Software Candidate Release Phase 3 Checklist

T-012-024 Software Candidate Release Phase 3 Checklist

Actors​

NameTitleMeaningApproved Date & Time

Change history​

RevisionSummaryDate

Process overview​

The purpose of the Software Design Checklist review is to ensure the outputs of Phase 3 satisfy the criteria listed in the next section.

Project information​

  • Project title:
  • Project manager (name and function):

Planning​

PhaseObjectDone
Phase 1 Product Design ReviewEstablish input data
Phase 2 Software Design ReviewSRs, Architectural Design and UI Prototypes
Phase 3 Software Candidate ReleaseCoding, integration and test plan
Phase 4 Software Verification ReviewSoftware version verified and residual anomalies
Phase 5 Product Validation ReviewValidation activities, Technical Documentation and DHF

Previous reserves​

Instructions

If there were any reserves or outstanding issues identified during Phase 2, list them here. Include a brief description of each reserve, the actions required to address them, and assign an owner and targeted completion date. See T-012-022 Software Design Phase 2 Checklist for an example.

N°Documents / Purpose / Actions to implementOwnerTargeted DateSatisfying

Version identifier​

  • Version:
  • Version type: Major/minor/patch
  • Git tag:
  • Version objectives:
  • Changelog:

List of implemented software requirements​

KeySummarySoftware item

Software requirements​

List the expected records and observations

ItemSatisfyingCommentReserves

Test plan​

  • Regression test type:
  • Test planification:

Reserves​

N°Documents / Purpose / Actions to implementOwnerTargeted Date

Conclusions​

Instructions

Summarize the outcome of the review for this phase, clearly stating whether the project milestone can proceed. Include the following elements:

  • A brief assessment of whether the reviewed outputs (e.g., software requirements, traceability, test plan, documentation) are available, complete, and relevant.
  • A statement confirming whether all identified software criteria for the release have been met.
  • Indicate whether any reserves exist and whether they impact the approval of the phase.
  • Explicitly confirm whether the release candidate has been accepted for the next phase (e.g., verification).

Be factual and concise. Use present-tense language and avoid vague expressions.

Previous
T-012-023 Software Development Plan
Next
T-012-025 Software Verification Phase 4 Checklist
  • Actors
  • Change history
  • Process overview
  • Project information
  • Planning
  • Previous reserves
  • Version identifier
    • List of implemented software requirements
  • Software requirements
  • Test plan
  • Reserves
  • Conclusions
All the information contained in this QMS is confidential. The recipient agrees not to transmit or reproduce the information, neither by himself nor by third parties, through whichever means, without obtaining the prior written permission of Legit.Health (AI LABS GROUP S.L.)