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
Sustainability Checklist Example
PostedMarch 29, 2025
UpdatedMarch 29, 2025
ByKevin McCaffrey
ID: SUS_SUS3_2_sustainability-checklist
Code: SUS3_2
Removing unused components and refactoring under-utilized ones is an effective way to minimize waste in your architecture. This practice not only decreases energy consumption but also leads to more efficient resource utilization and cost savings.
Checklist for Sustainable Software and Architecture Patterns
- Identify and Remove Unused Components: Regularly audit your architecture to find orphaned instances, zombie resources, or dormant services. Decommission them to avoid unnecessary power usage and costs.
- Refactor Under-Utilized Components: Consolidate or repurpose resources that are seldom used. Consider adopting auto-scaling solutions or pay-as-you-go services to match capacity with demand.
- Adopt Serverless Architectures: Break down monolithic applications into serverless functions where possible. This reduces operational overhead and ensures you only run code when needed, lowering overall energy usage.
- Implement Caching and Content Delivery: Utilize caching strategies and Content Delivery Networks (CDNs) to reduce the load on origin servers, boosting efficiency and cutting energy consumption.
- Optimize Data Storage: Archive or compress infrequently accessed data. Periodically review storage usage to minimize wastage and limit hardware footprint.
- Use Efficient Data Processing Frameworks: Choose streamlined data processing libraries and frameworks that consume fewer resources, ensuring more sustainability throughout the data pipeline.
- Embrace Automation and Monitoring: Implement automated scripts and monitoring tools. This helps track performance, detect inefficiencies, and trigger optimizations in real time.
By regularly reviewing and updating this checklist, you can keep your application portfolio lean and energy efficient, contributing to broader sustainability goals.
Table of Contents