ETIS Educational Products¶
Reusable educational products that operationalize the ETIS Educational Ecosystem
The ETIS Educational Ecosystem produces a collection of public educational products that transform ETIS from educational doctrine into deployable educational systems.
These products support instructors, students, institutions, and adopters while preserving a clear separation between public educational experiences and internal educational architecture.
Why Educational Products Exist¶
The ETIS book teaches the doctrine.
The Educational Ecosystem teaches educators how to teach the doctrine.
Educational Products operationalize that ecosystem into reusable implementation assets.
These products are designed to:
- accelerate ETIS adoption
- support instructional stewardship
- provide reusable educational systems
- promote evidence-centered learning
- create consistent educational experiences
- establish reference implementations
Educational Architecture¶
ETIS Educational Ecosystem Guide
Educational architecture, learning models, adoption pathways, and ecosystem design.
Download PDF Open PDFInstructor Products¶
ETIS Instructor Course Package
Complete instructor onboarding, course implementation, and educational operation guidance.
Download PDF Open PDFETIS Classroom Facilitation Guide
Classroom execution, facilitation strategies, and instructional operations.
Download PDF Open PDFETIS Instructor Handbook
Long-term instructional stewardship, observations, and operational guidance.
Download PDF Open PDFStudent Products¶
ETIS Student Professional Engineering Guide
Professional engineering behaviors, AI responsibility, and evidence-centered work.
Download PDF Open PDFFlagship Implementation¶
ETIS COMP330 Flagship Implementation Guide
Loyola University Chicago reference implementation and educational laboratory.
Download PDF Open PDFBottom Line¶
The ETIS Educational Products transform educational theory into reusable educational systems.
The ecosystem defines the architecture.
The products operationalize the architecture.
The implementations prove the architecture.