MFC releases update of Didge android app. Get your update on
Google Play
Ctrlk
Book a meetingGo to websiteLogin to Didge
For the complete documentation index, see llms.txt. This page is also available as Markdown.

Software Development

Software Development & Change Request Management Policy

Purpose

To ensure that software developed and deployed within MFC Safe adheres to best practices in security, quality, and operational stability through structured development and change management processes.

Scope

This policy applies to all MFC Safe developers, QA engineers, and DevOps professionals responsible for building and deploying platform services, including APIs, web applications, and backend microservices.

Policy Statement

MFC Safe mandates disciplined software engineering practices, including:

  • Secure Coding Standards: All code must adhere to OWASP Top 10 principles. Development teams will conduct static analysis scans and threat modeling as part of design.

  • CI/CD Workflows: All services are deployed through automated CI/CD pipelines. Pipelines include:

    • Code linting and style checks

    • Unit and integration tests

    • Static code analysis

    • Build and packaging steps

    • Deployment to staging and production with audit trails

  • Version Control: All code changes must be committed to Git and submitted via Pull Requests.

  • Peer Review: All Pull Requests require review and approval by at least one other developer. Code reviews must assess logic, documentation, and potential vulnerabilities.

  • Release Management:

    • Features are released via tagged semantic versioning.

    • Releases to production require sign-off from QA and product teams.

    • Release notes are automatically generated and archived.

  • Rollback Procedures:

    • All deployments include rollback scripts and version pinning.

    • Emergency rollbacks must be logged and communicated within 30 minutes of execution.

  • Change Control:

    • Material changes must be scheduled during release windows.

    • All change requests are logged in the change management system and assessed for business impact and security risk.

  • Audit Trail:

    • All merges, deployments, and change requests are logged and retained for no less than 12 months.

Enforcement

Violations of this policy may result in deployment freeze and require incident response review. All development and deployment activities are monitored for conformance to this policy.

PreviousOperational
NextService Level Agreement

Last updated

Was this helpful?