-
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
SLA Optimization Template Example
ID: SUS_SUS2_2_sla-optimization-template
Code: SUS2_2
Context Overview:
Aligning SLAs with sustainability goals ensures that cloud resources are utilized efficiently, reducing waste while still fulfilling business requirements. This alignment promotes a culture of sustainability and enables organizations to optimize their resource consumption to match actual demand.
Template Components:
- Service-Level Objectives (SLOs): Define clear, measurable targets that ensure adequate performance without over-provisioning resources. Example: an SLO of 99.9% uptime for non-critical workloads instead of 99.99% can significantly reduce resource usage.
- Resource Utilization Metrics: Track real-time consumption (CPU, memory, network, storage) to identify usage patterns and forecast peak demand. Rightsize resources based on these insights.
- Automation and Scaling Policies: Automatically scale resources up or down based on usage thresholds and schedule times of known high/low traffic.
- Continuous Improvement Process: Conduct regular reviews to adjust SLOs, refine scaling policies, and implement optimizations as your business needs evolve.
Implementation Example:
Imagine a photo-processing application with predictable spikes on weekends. Configure an Auto Scaling group to add additional instances on Friday afternoons and remove them by Monday mornings. Review and revise the SLAs every quarter to confirm that resource usage aligns with the latest business goals and sustainability metrics.
Outcome:
By setting realistic uptime targets and using on-demand scaling, organizations can precisely match cloud resources to demand, maintaining effective performance while minimizing environmental impact.