ETIS Instructor Resources¶
ETIS Instructor Resources provide an educational operating system for teaching trustworthy intelligent systems in the AI era.
They help instructors design, operate, assess, and steward courses where students do more than complete assignments.
Students produce engineering evidence.
Students defend engineering decisions.
Students learn to create trust.
Educational work should resemble professional engineering work.
The ETIS book provides the doctrine.
The Instructor Resources provide the teaching system.
What Makes ETIS Different¶
Traditional software engineering courses often emphasize delivery:
Teach software
↓
Assign project
↓
Grade artifacts
↓
Complete semester
↓
Course ends
ETIS emphasizes engineering accountability:
Teach engineering systems
↓
Require evidence
↓
Review decisions
↓
Defend releases
↓
Preserve educational memory
↓
Improve the next offering
The difference matters.
AI can help students produce more artifacts faster.
ETIS helps instructors teach students how to verify, govern, explain, and own those artifacts.
Start Here¶
Instructor Course Package¶
A complete course operating model for instructors teaching ETIS-based software engineering.
It includes course design, sequencing, assignments, assessment, classroom operations, and stewardship guidance.
Classroom Facilitation Guide¶
Guidance for running ETIS classroom experiences as active engineering environments.
It helps instructors facilitate discussion, team accountability, AI responsibility, review boards, and release defenses.
Instructor Handbook¶
Long-term instructor guidance for preserving institutional memory across repeated ETIS implementations.
It helps instructors improve courses over time instead of rebuilding from scratch.
COMP330 Flagship Implementation Guide¶
A real implementation reference based on Loyola University Chicago COMP330/474.
It shows how ETIS operates in practice while preserving the distinction between ETIS doctrine and one institution’s implementation.
The Six Educational Engines¶
The Instructor Course Package is organized around six educational engines.
Each engine answers a different question an instructor must solve before, during, and after a course.
| Educational Engine | Guiding Question |
|---|---|
| Educational Intent Engine | What will students experience? |
| Educational Sequencing Engine | In what order will students mature? |
| Educational Accountability Engine | How will students progressively prove engineering accountability? |
| Educational Evaluation Engine | How will we know students are becoming trustworthy engineers? |
| Educational Operations Engine | How do instructors run ETIS classroom experiences? |
| Educational Stewardship Engine | What should instructors know while operating ETIS educational systems over time? |
These engines keep ETIS education from becoming a loose collection of lectures, assignments, and rubrics.
They make the course itself an engineered system.
Educational Intent Engine¶
The Educational Intent Engine helps instructors define the educational experience before building the course.
It asks what students should become, not merely what content they should encounter.
Core capabilities include:
- course design guidance
- adoption planning
- course readiness checklists
- learning experience design
- course purpose definition
- educational outcome alignment
- instructor onboarding
This engine prevents the course from becoming a sequence of disconnected topics.
It establishes the course as a transformation system.
Educational Sequencing Engine¶
The Educational Sequencing Engine helps instructors decide how students mature over time.
ETIS learning is staged.
Students should not be expected to demonstrate full engineering maturity immediately.
They progressively inherit responsibility.
Core capabilities include:
- syllabus guidance
- semester sequencing
- quarter sequencing
- module sequencing
- book mapping guidance
- professional training sequence guidance
- phase gate sequencing
- schedule adaptation guidance
This engine helps instructors move students from awareness to accountability.
The sequence matters because maturity is developed, not assigned.
Educational Accountability Engine¶
The Educational Accountability Engine helps instructors design assignments that require evidence, ownership, and reviewability.
ETIS assignments are not just tasks.
They are accountability structures.
Core capabilities include:
- assignment assembly guidance
- assignment sequencing
- phase gate models
- evidence progression
- assessment progression
- engineering accountability checkpoints
- COMP330 phase gate references
- scaling guidance for different course formats
This engine shifts the instructor question from:
Did students complete the assignment?
to:
Did students produce evidence strong enough to defend their engineering decisions?
Educational Evaluation Engine¶
The Educational Evaluation Engine helps instructors assess trustworthiness, not just completion.
ETIS evaluation focuses on the strength of evidence, the quality of reasoning, the reviewability of artifacts, and the maturity of engineering behavior.
Core capabilities include:
- assessment philosophy
- rubric design
- evidence-based assessment
- AI assessment guidance
- engineering defense guidance
- assessment model libraries
- assessment scaling guidance
- COMP330 assessment references
This engine reinforces a critical ETIS doctrine:
Evaluate the strength of the evidence before evaluating the strength of the conclusion.
Grades measure performance.
Maturity signals measure transformation.
Educational Operations Engine¶
The Educational Operations Engine helps instructors run ETIS classrooms as active engineering environments.
The instructor is not merely a lecturer.
The instructor operates as facilitator, reviewer, coach, steward, and engineering leader.
Core capabilities include:
- classroom facilitation
- discussion facilitation
- team facilitation
- AI facilitation
- review board facilitation
- session assembly
- classroom energy management
- facilitation model libraries
- facilitation scaling guidance
- COMP330 facilitation references
This engine helps instructors keep students active, accountable, and engaged in real engineering behaviors.
The classroom becomes an engineering laboratory.
Educational Stewardship Engine¶
The Educational Stewardship Engine helps instructors preserve wisdom across semesters.
ETIS courses should not reset to zero every term.
Each offering should leave evidence for the next instructor, the next course, and the next version of ETIS.
Core capabilities include:
- semester preparation notes
- first weeks guidance
- common student patterns
- engineering maturity signals
- AI transition notes
- difficult conversation guidance
- course correction notes
- institutional adaptation notes
- COMP330 instructor notes references
- teaching philosophy notes
This engine treats educational memory as infrastructure.
Every semester should improve ETIS.
Public Instructor Products¶
The website introduces the instructor system.
The PDFs provide deeper adoption and operating guidance.
| Product | Purpose |
|---|---|
| ETIS Instructor Course Package.pdf | Complete instructor onboarding and course operation |
| ETIS Classroom Facilitation Guide.pdf | Running ETIS classroom experiences |
| ETIS Instructor Handbook.pdf | Long-term instructional stewardship |
| ETIS COMP330 Flagship Implementation Guide.pdf | Real-world implementation reference |
These products are curated educational products.
They are not directory exports.
Instructor Adoption Path¶
A new instructor should adopt ETIS in stages.
Discover the framework
↓
Understand the educational mission
↓
Study the Instructor Course Package
↓
Review the Student Starter Kit
↓
Study the COMP330 flagship implementation
↓
Adapt ETIS to the local course
↓
Operate the course
↓
Capture evidence
↓
Improve the next offering
The objective is not to replicate Loyola University Chicago.
The objective is to inherit ETIS doctrine and adapt it responsibly.
What Instructors Should Expect Students To Produce¶
ETIS courses should produce visible evidence of engineering maturity.
Student repositories should include evidence such as:
- requirements and assumptions
- planning artifacts
- team roles and working agreements
- architecture decisions
- AI use and verification notes
- review records
- test plans and test evidence
- quality and defect records
- security and data-handling notes
- release readiness evidence
- operational notes
- observability plans
- postmortem or improvement evidence
This evidence matters because trustworthy engineering must be reviewable.
If it cannot be reviewed, it cannot be trusted.
Teaching AI Responsibility¶
ETIS does not ask students to avoid AI.
ETIS asks students to use AI responsibly.
Instructor expectations should emphasize:
- disclosure of AI assistance
- verification of AI-generated work
- ownership of submitted artifacts
- traceability from claims to evidence
- awareness of hallucination, overconfidence, and hidden dependency
- engineering judgment over tool fluency
AI usage is not an academic violation.
Undisclosed and unverified AI dependency is an engineering risk.
Review Boards and Release Defense¶
ETIS instructors should normalize review, challenge, and defense.
Students should learn to explain:
- what they built
- why they built it that way
- what evidence supports their claims
- what risks remain
- what tradeoffs they made
- what they would improve next
- whether the system is ready to release, operate, or continue
Engineering work is not complete until it can be defended.
Scaling ETIS Courses¶
ETIS can be adapted to different course sizes, levels, and formats.
The scaling rule is:
Scale complexity, not accountability.
For smaller or earlier courses, reduce project scope.
For larger or advanced courses, increase operational depth.
Do not remove accountability.
Do not remove evidence.
Do not remove reviewability.
Do not remove ownership.
Instructor Doctrine¶
ETIS instructor work is governed by durable principles:
- Educational work should resemble professional engineering work.
- Engineering accountability is the educational outcome, not the side effect.
- Educational systems are engineered.
- Educational systems are also stewarded.
- Educational systems are inherited, not reinvented.
- Every semester should leave evidence for the next instructor.
- Scale complexity, not accountability.
- Scale evaluation mechanisms, not engineering expectations.
- Do not assess AI avoidance. Assess AI responsibility.
- Rubrics should measure trustworthiness, not just task completion.
- Engineering work is not complete until it can be defended.
- Transformation should be observable.
- Engineering maturity leaves evidence.
- Tools change. Engineering behaviors endure.
Public Boundary¶
The Instructor Resources page is a public hub.
It exposes instructor capabilities, products, and adoption pathways.
It does not expose internal freeze registers, continuity packages, raw architecture registers, or unnecessary directory structures.
The internal education architecture remains the source system.
The public instructor experience should remain clear, adoptable, and professionally bounded.
Bottom Line¶
ETIS Instructor Resources help instructors move beyond teaching students to build software.
They help instructors teach students to engineer systems that can be understood, reviewed, governed, operated, improved, and trusted over time.
That is the educational obligation of software engineering in the AI era.