-
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
Auto Scaling Policy Example
ID: SUS_SUS2_1_auto-scaling-policy
Code: SUS2_1
Efficiently aligning cloud resources to demand is crucial for achieving sustainability goals. By optimizing the geographic placement of workloads, organizations can minimize latency, reduce energy consumption, and lower the total network resources required for their operations. This practice not only enhances performance but also contributes to a more sustainable cloud environment.
Below is an example of an auto scaling policy in AWS that demonstrates how to dynamically adjust compute resources based on user traffic:
- Amazon EC2 Auto Scaling Group: Defines the minimum, maximum, and desired number of instances.
- Scaling Policies: Triggers based on CloudWatch metrics, such as CPU utilization or custom metrics for request rates, adjusting the number of instances up or down.
- Geographic Placement: Ensures that the scaling group is deployed in regions closest to end users, minimizing latency and reducing energy consumption.
- Lifecycle Hooks: Allows you to control scenarios such as gracefully draining connections before terminating instances, enhancing system reliability and maintaining sustainability targets.
This approach ensures that you deploy the right number of instances at any given time, thereby reducing resource waste and contributing to an overall sustainable cloud ecosystem. By automatically scaling resources up or down based on real-time demand, you optimize usage, save on costs, and remain agile for unexpected traffic spikes or drops.