-
Planning and Strategy
-
Requirements
-
- Customer Feedback Report
- Capacity Planning Report
- Stakeholder Input Record Example
- List of Customer Journeys
- Reverse Engineering: Legacy Inventory Management System
- Task Analysis: Customer Support Ticketing System
- Requirements Workshop: Employee Onboarding System
- Mind Mapping Session: Mobile Travel Planning App
- SWOT Analysis: New Food Delivery App
- Storyboarding Session: Mobile Health & Fitness App
- User Story Mapping Session: Online Grocery Shopping Platform
- Focus Group: Requirements Gathering for Fitness Tracking App
- Prototyping Session Example: E-Commerce Website
- Document Analysis Example: Hospital Management System Requirements
- Observation Session: Warehouse Operations
- Survey: E-Learning Platform Requirements
- Workshop Session Example: Requirements Gathering for Mobile Banking App
- Interview Session Example: Requirements Gathering for CRM System
- Event Storming Session: Retail Order Management System
- Generate Requirements from Meeting Transcripts
- Requirements Definition Process Example
- ISO/IEC/IEEE 29148 Systems and Software Requirements Specification (SRS) Example Template
- Show all articles ( 7 ) Collapse Articles
-
- Customer Requirement Document (CRD)
- Customer Journey Map
- Internal Stakeholder Requirement Document (ISRD)
- Internal System Use Case Example: CI/CD System
- User Stories & Acceptance Criteria
- Technical Specification Document Example
- BDD Scenarios Example for User Login
- Non-Functional Requirements Example
- Functional Requirements Specification Example
- Use Case Example: User Login
-
-
Communication
-
Design
- Functional Specification for Inventory Management Workload
- Technical Specification for Inventory Management System
-
- Overview of Design Diagrams
- High-Level System Diagram Standards
- User-Flow Diagram Standards
- System Flow Diagram Standards
- Data-Flow Diagram (DFD) Standards
- Sequence Diagram Standards
- State Diagram Standards
- Flowchart Standards
- Component Diagram Standards
- Network Diagram Standards
- Deployment Diagram Standards
- Entity-Relationship Diagram (ERD) Standards
- Block Diagram Standards
-
Operations
-
-
- Creating a Visualization Dashboard Guide
- Business Outcome Metrics Dashboard Guide
- Trace Analysis Dashboard
- Dependency Health Dashboard
- Guidelines for Creating a Telemetry Dashboard
- Guidelines for Creating a User Behavior Dashboard
- Improvement Tracking Dashboard
- Customer Status Page Overview
- Executive Summary Dashboard Overview
- Operations KPI Dashboard Example
- Stakeholder-Specific Dashboard Example
- Business Metrics Dashboard Example
- System Health Dashboard Example
- Guide for Creating a Dependency Map
-
-
-
- Event Management Policy Example
- Incident Management Policy
- Problem Management Policy
- Example Training Materials for Escalation
- Runbook Example: Incident Management with Escalation Paths
- Escalation Path Document Example
- Incident Report Example: Failed Deployment Investigation
- Incident Playbook Example: Investigating Failed Deployments
- Contingency Plan for Service Disruptions
-
-
-
Testing
-
Development
Sustainability Compliance Checklist: Aligning Cloud Resources
ID: SUS_SUS2_sustainability_compliance_checklist
Code: SUS2_5
1. **Assess Current Resource Utilization**: Conduct an analysis to identify current resource usage patterns. Look for underutilized or over-provisioned resources that can be rightsized to match actual demand.
2. **Implement Auto-Scaling Mechanisms**: Leverage AWS auto-scaling capabilities to automatically adjust capacity based on demand. Ensure that workloads can dynamically scale up during peak times and scale down when not needed, thereby optimizing resource consumption.
3. **Utilize AWS Cost and Usage Reports**: Regularly review AWS Cost and Usage Reports to gain insights into resource utilization. Use this data to make informed decisions on resource allocation and right-sizing.
4. **Adopt Serverless Architectures**: Where feasible, transition to serverless computing such as AWS Lambda. Serverless architectures can help eliminate idle resources and only use power when needed, aligning resource consumption with actual operational demand.
5. **Establish Resource Tagging Standards**: Create and enforce a resource tagging strategy that categorizes resources based on workload, team, environment, and usage level. This will facilitate ongoing monitoring and management of resources to ensure they align with demand.
6. **Monitor and Optimize with CloudWatch**: Utilize AWS CloudWatch to set up alarms and dashboards that provide real-time insights into resource utilization. Regular monitoring allows for quick adjustments when resource use deviates from demand.
7. **Conduct Regular Reviews**: Schedule periodic reviews of resource allocation strategy against team usage and operational needs. Engage stakeholders to assess if current configurations still meet business objectives, adjusting as necessary for efficiency and sustainability.
8. **Encourage Resource Sharing**: Foster a culture of resource sharing among teams where feasible. This can help to minimize redundant resources and facilitate better overall utilization.
By following this checklist, teams can ensure that their cloud resources are effectively aligned with operational demands, minimizing waste and promoting sustainability within their cloud infrastructure.