Search for the Right Document
Design Standards Change Request Log Example
Date Created: November 7, 2024
Maintained By: Standards Governance Committee
Request ID: CR-001
- Date Submitted: November 6, 2024
- Submitted By: John Smith
- Team: DevOps
- Standard Affected: Security Practices
- Description of Request: Request to modify password complexity requirements for internal admin tools.
- Reason for Change: To reduce user frustration while maintaining security standards.
- Status: Under Review
- Date Reviewed: November 8, 2024
- Reviewed By: Sarah Lee
- Decision: Pending
- Comments/Notes: Awaiting security assessment.
Request ID: CR-002
- Date Submitted: November 7, 2024
- Submitted By: Emily Davis
- Team: Backend
- Standard Affected: API Rate Limiting
- Description of Request: Increase rate limits for partner APIs from 100 to 200 requests per minute.
- Reason for Change: To address increased demand from key partners.
- Status: Approved
- Date Reviewed: November 10, 2024
- Reviewed By: Tom Harris
- Decision: Approved
- Comments/Notes: Approved for the next deployment.
Request ID: CR-003
- Date Submitted: November 7, 2024
- Submitted By: Michael Brown
- Team: Frontend
- Standard Affected: UI Design Guidelines
- Description of Request: Exception request to use a custom color scheme for a new client-specific project.
- Reason for Change: To meet client branding requirements.
- Status: Under Review
- Date Reviewed: November 12, 2024
- Reviewed By: Jane Carter
- Decision: Pending
- Comments/Notes: Design review scheduled.
Request ID: CR-004
- Date Submitted: November 8, 2024
- Submitted By: Lisa Turner
- Team: Mobile
- Standard Affected: Coding Standards
- Description of Request: Add guidelines for using Swift concurrency features.
- Reason for Change: To leverage new language features for better performance.
- Status: Under Review
- Date Reviewed: November 14, 2024
- Reviewed By: Alex Johnson
- Decision: Pending
- Comments/Notes: Reviewing potential impact on legacy code.
Request ID: CR-005
- Date Submitted: November 9, 2024
- Submitted By: David Clark
- Team: QA
- Standard Affected: Testing Frameworks
- Description of Request: Change default testing framework from Framework A to Framework B.
- Reason for Change: Framework B offers better integration with CI/CD pipelines.
- Status: Denied
- Date Reviewed: November 11, 2024
- Reviewed By: Sarah Lee
- Decision: Denied
- Comments/Notes: Framework B lacks certain features critical to testing.
Status Definitions:
- Under Review: The request is currently being evaluated.
- Approved: The request has been approved and will be implemented.
- Denied: The request has been denied, with reasons documented in the Comments/Notes.
Note: This log should be kept up-to-date, and all teams should have access for transparency and efficient communication.
End of Document