Gridcheck, LLC
Document Owner: Gridcheck Executive Leadership
Effective: August 2026
Review Frequency: Annual
Last Reviewed: August 2026
Next Scheduled Review: August 2027
1. Purpose
The purpose of this Software Development Life Cycle (SDLC) is to define Gridcheck’s approach to planning, developing, testing, deploying, maintaining, and retiring software in a manner that promotes security, reliability, and service quality.
Gridcheck follows a structured development process designed to ensure that new features, enhancements, bug fixes, and security updates are implemented in a controlled and repeatable manner.
2. Scope
This SDLC applies to:
- Gridcheck SaaS applications
- Supporting APIs and services
- AWS-hosted production and staging environments
- Application frameworks and third-party software libraries
- Security-related enhancements
- Bug fixes and maintenance releases
3. Roles and Responsibilities
Gridcheck executive leadership provides oversight of the software development process.
Authorized technical personnel are responsible for:
- Requirements analysis
- Software development
- Security review
- Testing
- Deployment
- Ongoing maintenance
Development activities are planned and tracked using Gridcheck’s issue management system (Redmine).
4. Planning and Requirements
Software enhancements, maintenance requests, customer feedback, security improvements, and bug reports are documented and prioritized within Redmine.
Development priorities are established based upon:
- Customer requirements
- Security considerations
- Operational impact
- Product roadmap
- Business priorities
5. Design
Prior to implementation, proposed changes are evaluated to determine:
- Functional requirements
- Security implications
- Performance impact
- Compatibility with existing systems
- Required third-party dependencies
Major architectural changes are reviewed before implementation.
6. Development
Software development is performed using controlled source code repositories and established development practices.
During development, Gridcheck seeks to:
- Follow secure coding practices
- Minimize unnecessary system complexity
- Utilize supported software components
- Review third-party libraries and dependencies during major releases
- Protect sensitive information from inclusion within application code
7. Testing
Where applicable, software changes are deployed to a staging environment prior to production.
Testing may include:
- Functional testing
- Regression testing
- Security validation
- User acceptance testing (when appropriate)
- Performance verification
Testing is intended to verify that changes perform as expected while minimizing unintended effects on existing functionality.
8. Change Management and Release
Production releases follow Gridcheck’s documented Change Management and Patch Management processes.
Prior to production deployment:
- Changes are reviewed
- Impact is evaluated
- Required approvals are obtained
- Validation is completed
Emergency changes follow documented emergency change procedures, including post-implementation review and documentation.
9. Security
Security is considered throughout the software development lifecycle.
Development activities include consideration of:
- Authentication
- Authorization
- Data protection
- Encryption
- Dependency management
- Security updates
- Vulnerability remediation
Critical security issues receive priority handling under Gridcheck’s Patch Management Policy.
10. Deployment
Software releases are deployed in a controlled manner designed to minimize customer impact.
Where practical:
- Releases are scheduled during lower-usage periods
- Production deployments are validated
- Rollback procedures are considered when appropriate
Gridcheck operates as a multi-tenant SaaS platform. Customers automatically receive production updates and security improvements.
11. Maintenance
Following deployment, Gridcheck continues to:
- Monitor application performance
- Correct software defects
- Deploy security updates
- Maintain supported software components
- Improve platform functionality
Product planning and future enhancements are managed through Gridcheck’s internal development roadmap and Redmine issue tracking system.
12. Related Policies
This SDLC should be read in conjunction with Gridcheck’s:
- Information Security Policy
- Change Management Policy
- Patch Management Policy
- Disaster Recovery Plan
- Business Continuity Plan
- Privacy Statement
13. Review
This Software Development Life Cycle document is reviewed annually and following significant changes to Gridcheck’s development practices.