Home

Welcome to the curriculum-flex wiki!

(Proposal for) New Chapter structure

The following structure shall help us to group the Learning Goals of the FLEX curriculum. The structure does not define the order in which courses have to be structured.

0. Introduction to Flexible Systems

• What is the core of FLEX, what are CAN-be extensions, and what are integration points to other CPSA-A curricula.

1. Chapter 1: WHY approach Flexible Systems

• How to find out the long-term quality goals for the system you build
• Quality Goals that later on justify architectural decisions
• Quality Scenarios as executable (architecture) tests (Fitness functions)
• Principles
  • Focus on Customer Value
  • Build for Replacement: The difference between service implementation and service functionality
  • Interfaces, Interactions, Information: Integration Points are relationships between humans
  • Establish Feedback Loops: Build-Measure-Learn
  • Start with the end in mind: What operations model can your organisation handle?
  • Quality vs. Quantity: Prioritize SLOs/Error Budget against Feature Development

2. Chapter 2: Modularization of Systems of Systems

• Architecture Styles
• Microservice Taxonomy

3. Chapter 3: Software and their Organisations

• Conway's Law
• DDD Context Maps to explain AS-IS vs. TO-BE to stakeholders (Stakeholder Management)
• Interoperation between organization and software systems
• Team-organisation, Socio-technical Architectures, and Team Topologies
• Technology Mgmt vs. Technology Diversity/ Overwhelm

4. Chapter 4: Integration Methods & Protocols

• What qualitative Questions to ask to decide on integration methods
• Resilience vs. High Availability

5. Chapter 5: Deployment & Runtime/ Platform Methods

• Observability options
• Continuous Deployment
• PaaS, CaaS, FaaS
• Developer Experience
• Zero Downtime (Canary & Blue-Green)

6. Chapter 6: Service Operation Models

• Service Level Objectives
• MTBF vs. MTTR
• Incident Management
• Disaster Recovery
• Chaos Engineering