SystemsArchitect.io

• 1.0 / 6U Introduction
  • Project Timeline example

• 1.1 / User Story
• 1.2 / User Roles
• 1.3 / User Qualities

• 1.4 / User Interface
• 1.5 / User Screens
• 1.6 / User Growth

• 2.1.1 / Functional Document
• 2.1.2 / App Features
• 2.1.3 / UX Flow/Research
• 2.1.4 / Business Diagram Types
• 2.1.4 / Business Architect Expectations

• Build Checklist
• Components
• Design Patterns
• Query Examples

• ⭐️ 150+ Solutions Architect metrics
• 2.2.5 / Initial Estimates
• 2.2.6 / Network Estimates
• 2.2.7 / Compute Estimates
• 2.2.8 / Storage Estimates
• 2.2.9 / Cost Estimates
• 2.2.10 / Provider limits

• 2.3.1 / Org Requirements
• 2.3.2 / Data Access Workflow
• 2.3.3 / System Design Funnel
• 2.3.4 / Architect Diagram Types
• 2.3.5 / UCROPS Workflow
• 2.3.6 / Data models (Rideshare example)
• 2.3.7 / Best Practices
• 2.3.8 / DevOps

• Daily Active Users (DAU)
• Actions Per User (APU)
• Daily User Actions (DUA)
• Requests Per Second (RPS)
• DB/Storage
• Media Storage
• Bandwidth Consumed
• Available Bandwidth

• All Components
• APIs/Data Models
• Auth/Login
• Best Practices
• Caching
• Compute
• Database
• DevOps
• ETL Choices
• Events/Messaging
• Load Balancer
• Logging/Metrics
• Machine Learning
• Media Streaming
• Migration Services
• Network
• Search
• Security
• Storage

• 3.1.1 / Focus
• 3.1.2 / Tech Review Process
• 3.1.3 / Success tips

• 3.2.0 / Pre-Presentation checklist
• 3.2.1 / Presentation Demeanor
• 3.2.2 / Review of 6Us, Functional Docs
• 3.2.3 / Review potential technical solutions

• 3.2.4 / Soliciting feedback
• 3.2.5 / Wrapping it Up
• 3.3.1 / Problems: Why the Systems Review Fails

4. Resolve

• 4.1 / Resolving Disagreements
• 4.2 / UX/Design disagreements
• 4.3 / Steps to Resolution

5. Realize

• 5.1 / Project Timeline: Realize

6. Reassess

• 6.1 / Post-Launch Checklist
• 6.2/ Site Reliability