-
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
Cloud Resource Inventory Example
ID: SUS_SUS2_cloud_resource_inventory
Code: SUS2_4
1. **Inventory Assets:** Maintain a comprehensive inventory of all cloud resources utilized within your workload. Document details such as resource type (e.g., EC2 instances, S3 buckets), configurations, performance metrics, and cost associated with each resource.
2. **Utilization Monitoring:** Implement monitoring tools (such as AWS CloudWatch, Cost Explorer, or AWS Trusted Advisor) to analyze the actual usage of each resource against its expected demand. Pay attention to idle or underutilized resources, for instance, EC2 instances with low CPU utilization or S3 buckets with minimal access.
3. **Demand Forecasting:** Utilize historical usage data and predictive analytics to forecast resource demand. Tools like AWS Budgets and AWS Cost Explorer can assist in analyzing trends and identifying peaks and troughs in resource usage.
4. **Decommissioning Strategy:** For resources identified as unused or underused based on monitoring and forecasting, develop a decommissioning strategy. This may include:
– Scheduling decommissioning activities during low-impact times.
– Informing stakeholders of the changes to avoid disruption.
– Safeguarding necessary data before deleting resources.
5. **Regular Audits:** Schedule regular audits of your cloud resource inventory to continually reassess usage against demand and ensure that any new resources added to the architecture are also evaluated for necessity.
6. **Automation and Scaling:** Leverage AWS features such as Auto Scaling to automatically adjust the number of active instances based on current demand, ensuring that resources align dynamically as needs change.
By following these steps and maintaining an ongoing cycle of monitoring, evaluating, and adjusting, you can effectively align your cloud resources to your demand, reducing waste, lowering costs, and contributing to a more sustainable cloud environment.