Search for the Right Document
-
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
< All Topics
Print
Component Utilization Matrix Example
PostedMarch 29, 2025
UpdatedMarch 29, 2025
ByKevin McCaffrey
ID: SUS_SUS3_2_component-utilization-matrix
Code: SUS3_2
Removing unused components and refactoring under-utilized ones is crucial for minimizing waste in your architecture. By highlighting usage trends and associated costs, you can take strategic action to eliminate or repurpose unnecessary resources, enhancing sustainability and reducing energy consumption.
| Component | Utilization Status | Suggested Action | Potential Sustainability Impact |
|---|---|---|---|
| EC2 Instance A | Under-utilized (25% CPU usage) | Consolidate or switch to a smaller instance size Implement scale-in policy for off-peak hours |
Reduces overall energy consumption by aligning capacity with actual usage |
| EC2 Instance B | Redundant (no usage in past 30 days) | Decommission or repurpose Remove from load balancer |
Eliminates unnecessary power draw and operational overhead |
| RDS Database | Appropriately scaled | Continue monitoring Consider auto-scaling if usage patterns change |
Maintains optimal resource usage with minimal energy consumption |
By regularly reviewing this matrix, you align your system design with sustainability best practices. Metrics from AWS CloudWatch or similar tooling can be automated to identify when components are underutilized, ensuring proactive management and continuous improvement of your overall energy footprint.
Table of Contents