Systems Thinking
Learn a practical way to frame messy situations, trace behavior over time, and choose interventions with a clearer view of consequences.
ExerciseBoundary framing exercise
Key ideasSystem boundary / System context / Stocks and flows
Field guide 01 / Systems engineering
Systems Engineering Foundations
Learn to see relationships, define boundaries, manage interfaces, and connect engineering evidence—one practical lesson at a time.
0% complete
Reading order
Start with the whole. Then add complexity.
Each lesson stands alone, but the sequence builds a useful vocabulary before adding new kinds of complexity.
The course
Four foundations
Modular Design Systems
Learn why decomposition is a design decision, how cohesion and coupling expose change risk, and where modularity creates tradeoffs.
ExerciseChange-impact architecture comparison
Key ideasDecomposition / Cohesion / Coupling
Model-Based Systems Engineering
Learn what MBSE is—and is not—through a tool-agnostic model of an emergency-notification system.
ExerciseDocument-versus-model comparison
Key ideasModel purpose / Abstraction / View and viewpoint
Systems of Systems Engineering
Learn why a System of Systems is not merely a very large system and practice analyzing a regional emergency-response capability.
ExerciseGovernance comparison
Key ideasConstituent independence / Evolutionary development / Governance types
Working skills
What you will practice
Frame the system
Draw a useful boundary, identify stakeholders, and trace feedback rather than analyzing isolated parts.
Design for change
Use cohesion, coupling, interfaces, and event-driven communication to make modular tradeoffs explicit.
Connect evidence
Relate needs, requirements, architecture, analysis, and verification through traceability and viewpoints.
Coordinate autonomy
Reason about governance, interoperability, emergence, and cascading risk across independent systems.
Lesson format
Read it. Work with it. Test it.
- LearnBeginner-focused explanations use cited standards, handbooks, and foundational literature.
- ExploreKeyboard-operable diagrams and small simulations make relationships visible.
- ApplyWorked examples and misconception checks turn definitions into decisions.
- AssessTen-question checks give immediate explanations and can be retried without penalty.
On the syllabus
Notes for future lessons
These topics are in the notebook. They will be published as the examples, exercises, and references are ready.
Requirements Engineering
Turn stakeholder needs into clear, traceable, verifiable requirements.
System Architecture
Develop, compare, and communicate structural and behavioral architecture decisions.
Verification and Validation
Build evidence that the system was built correctly and fulfills its intended use.
Trade Studies and Decision Analysis
Compare alternatives transparently under competing objectives and uncertainty.
Risk and Opportunity Management
Identify, analyze, treat, and monitor uncertainty across the life cycle.
Interface Management
Define, control, verify, and evolve cross-boundary agreements.
Digital Engineering
Connect authoritative data, models, workflows, and evidence across engineering work.
Digital Threads and Digital Twins
Distinguish connected life-cycle information from operational representations of specific assets.
System Life-Cycle Processes
Tailor technical and management processes to the system, organization, and life-cycle model.
Human Systems Integration
Design human roles, work, training, safety, and technology as one system.
Reliability and Resilience
Reason about failure, recovery, adaptation, and sustained capability.
Configuration Management
Keep product definitions, baselines, changes, and evidence coherent over time.
Technical Measurement
Use measures and indicators to understand progress, performance, and uncertainty.
Systems Engineering for AI-Enabled Systems
Engineer data, models, human oversight, change, and assurance as an integrated capability.