generated from isaqb-org/advanced-template
-
Notifications
You must be signed in to change notification settings - Fork 5
Home
Alexander Heusingfeld edited this page Sep 9, 2024
·
5 revisions
Welcome to the curriculum-flex wiki!
Consider overlaps/links/integration with other curricula https://github.com/isaqb-org/curriculum-flex/issues/36
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.
- What is the core of FLEX, what are CAN-be extensions, and what are integration points to other CPSA-A curricula.
- 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
- Architecture Styles
- Microservice Taxonomy
- 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
- What qualitative Questions to ask to decide on integration methods
- Resilience vs. High Availability
- Observability options
- Continuous Deployment
- PaaS, CaaS, FaaS
- Developer Experience
- Zero Downtime (Canary & Blue-Green)
- Service Level Objectives
- MTBF vs. MTTR
- Incident Management
- Disaster Recovery
- Chaos Engineering