ETIS Instructor Resources¶
An educational operating system for teaching trustworthy engineering in the AI era
ETIS Instructor Resources help instructors design, operate, assess, and steward courses in which 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 Framework Reference Work, Engineering Trustworthy Intelligent Systems, provides the comprehensive full-lifecycle engineering doctrine.
The ETIS Professional Computing Series develops enduring professional capabilities through longer-form computing works aligned with that framework.
The Education Papers provide focused professional readings.
The Instructor Resources provide the teaching system.
The ETIS Engineering Platform provides a professional reference and implementation environment through staged lifecycle guidance, reusable templates, LMU/COICP examples, governance assets, and Project Workspace patterns. Course implementations may use their own team repositories as the authoritative location for project-specific engineering evidence.
Start Here¶
| Resource | Purpose |
|---|---|
| ETIS Books | Full-length framework and professional computing works for curriculum design and professional formation |
| From Data Structures to Engineering Judgment | Use data structures and algorithms as a technical vehicle for developing engineering judgment; especially relevant to foundational and intermediate computing courses |
| Instructor Course Package | Course design, sequencing, assignments, assessment, operations, and stewardship |
| Classroom Facilitation Guide | Discussion, team accountability, AI responsibility, review boards, and release defenses |
| Instructor Handbook | Long-term instructional memory, patterns, judgment, and improvement |
| COMP 330 Flagship Implementation Guide | Real implementation reference without confusing one course with ETIS doctrine |
| ETIS Education Papers | Professional student readings for orientation, teamwork, AI use, portfolios, and careers |
| Platform Overview | Learn how the Platform supports ETIS courses |
| Launch the Engineering Platform ↗ | Enter the working ETIS implementation environment |
Explore Educational Products →
Explore the ETIS Education Papers →
Explore the Platform Overview →
Launch the Engineering Platform ↗
What Makes ETIS Different¶
Traditional course pattern:
Teach software
↓
Assign project
↓
Grade artifacts
↓
Complete semester
↓
Course ends
ETIS pattern:
Teach engineering systems
↓
Establish professional expectations
↓
Require evidence
↓
Review decisions
↓
Defend releases
↓
Preserve educational memory
↓
Improve the next offering
AI can help students produce more artifacts faster.
ETIS helps instructors teach students how to verify, govern, explain, and own those artifacts.
Using ETIS Books in Curriculum¶
ETIS Books serve two complementary instructional roles.
The ETIS Framework Reference Work gives instructors the comprehensive engineering model: how trustworthy software and intelligent systems are framed, designed, constructed, verified, released, operated, governed, and stewarded over time. It can serve as a reference work, course foundation, or source for lifecycle-specific readings.
The ETIS Professional Computing Series develops durable professional capabilities through sustained computing topics aligned with the framework. Its inaugural title, From Data Structures to Engineering Judgment, uses data structures and algorithms as the technical teaching vehicle for engineering judgment rather than treating the subject as an end in itself.
That book is particularly relevant to data structures and intermediate computing courses. It is not intended to become a required text for every ETIS course or implementation.
Explore the ETIS Professional Computing Series →
Explore From Data Structures to Engineering Judgment →
Education Papers as Professional Readings¶
The five Education Papers can serve as a structured orientation sequence:
| Paper | Instructional Use |
|---|---|
| COMP-WP-001 | Establish why software engineering matters more in the AI era |
| COMP-WP-002 | Connect course evidence to portfolios and interviews |
| COMP-WP-003 | Establish team roles, shared ownership, review, and professional conflict |
| COMP-WP-004 | Define responsible AI-assisted engineering behavior |
| COMP-WP-005 | Connect the course to long-term judgment, growth, and professional trust |
These papers are not replacements for lectures or course materials. They provide shared language and professional orientation.
The Six Educational Engines¶
| Educational Engine | Guiding Question |
|---|---|
| Educational Intent Engine | What will students experience and become? |
| 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 preserve and improve 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¶
This engine defines the educational experience before the course is assembled.
Core capabilities include:
- course-purpose definition;
- student transformation goals;
- learning-experience design;
- outcome alignment;
- instructor onboarding;
- course-readiness review;
- adoption planning.
The central question is not merely what students will cover.
It is what they will become capable of doing responsibly.
Educational Sequencing Engine¶
ETIS learning is staged.
Students progressively inherit responsibility.
Core capabilities include:
- syllabus and module sequencing;
- semester or quarter adaptation;
- book and publication mapping;
- phase-gate sequencing;
- assignment progression;
- professional training sequence;
- schedule adaptation.
Maturity is developed, not assigned.
Educational Accountability Engine¶
ETIS assignments are accountability structures.
Core capabilities include:
- assignment assembly and sequencing;
- phase-gate models;
- evidence progression;
- accountability checkpoints;
- review and defense requirements;
- scaling guidance.
The instructor question shifts from:
Did students complete the assignment?
to:
Did students produce evidence strong enough to defend their engineering decisions?
Educational Evaluation Engine¶
ETIS evaluation focuses on evidence quality, reasoning, reviewability, and professional maturity.
Core capabilities include:
- assessment philosophy;
- rubric design;
- evidence-based assessment;
- AI-responsibility assessment;
- engineering-defense guidance;
- maturity signals;
- scaling guidance.
Evaluate the strength of the evidence before evaluating the strength of the conclusion.
Grades measure performance.
Maturity signals reveal transformation.
Educational Operations Engine¶
The instructor operates as facilitator, reviewer, coach, steward, and engineering leader.
Core capabilities include:
- classroom and discussion facilitation;
- team facilitation;
- AI facilitation;
- review-board facilitation;
- session assembly;
- classroom energy management;
- intervention and escalation;
- professional communication.
The classroom becomes an engineering laboratory.
Educational Stewardship Engine¶
ETIS courses should not reset to zero every term.
Core capabilities include:
- preparation notes;
- early-semester guidance;
- recurring student patterns;
- engineering maturity signals;
- AI transition notes;
- difficult-conversation guidance;
- course-correction records;
- institutional adaptation notes;
- end-of-term learning;
- continuity for future instructors.
Educational memory is infrastructure.
Every offering should improve the next one.
Engineering Platform as a Reference and Implementation Environment¶
The Engineering Platform can support:
- project startup and lifecycle orientation;
- staged engineering work;
- requirements, architecture, and decision-record patterns;
- responsible AI-use and verification practices;
- review and phase-gate preparation;
- testing and release-readiness practices;
- operational thinking and stewardship.
The Platform should be adapted to the course rather than treated as a rigid compliance system.
A course may use the Platform Project Workspace directly or establish a separate course-specific repository model. When a course-specific repository is designated, that repository remains the authoritative location for project-specific engineering evidence.
The Engineering Platform provides lifecycle guidance, templates, examples, and professional reference patterns. The Engineering Education Suite complements that reference environment with phase-gate readiness, student engineering-judgment development, and formal instructor review. Together they reinforce a consistent repository-centered engineering workflow without requiring every course to use the same repository implementation.
Explore the Platform Overview →
Launch the Engineering Platform ↗
Browse the ETIS Engineering Platform Starter Kit Repository ↗
Instructor Role in the Engineering Education Suite¶
The ETIS Engineering Education Suite gives instructors a coordinated environment for student readiness, developmental engineering review, and formal phase-gate evaluation while preserving clear authority boundaries.
ETIS Preflight is student-facing. It uses phase-aware analytical checks to help teams determine whether expected evidence is present and basically ready for formal review.
ETIS Engineering Studio is also student-facing, but its role is developmental rather than checklist-oriented. Student teams can create repeated frozen evidence snapshots and engage independently with a controlled multidisciplinary review board. Instructors can see the longitudinal review activity and dialogue, helping them understand where teams are learning, struggling, or repeatedly encountering unresolved engineering concerns.
ETIS Engineering Review Center is the instructor-facing formal review environment. At each gate, the designated Git tag establishes the formal evidence snapshot. The Review Center provides rubric-aligned evidence, reviewer findings, confidence, summaries, longitudinal context, and evidence lineage back to the repository sources that support the analysis.
The same controlled reviewer perspectives appear in Studio and the formal review environment, but their mandate changes:
- in Studio they mentor, coach, question, and challenge;
- in the Review Center they perform formal evidence-centered phase-gate analysis.
Developmental Studio conversations do not silently become evidence in the formal gate review. The tagged submission must stand on its own.
The instructor remains responsible for interpreting evidence, applying the rubric, resolving ambiguity, and making the academic decision.
Explore the Engineering Education Suite →
What Students Should Produce¶
Student repositories should preserve 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 evidence;
- defects and quality records;
- security and data-handling notes;
- release-readiness evidence;
- operational notes;
- observability plans;
- postmortem and improvement evidence.
If the work cannot be reviewed, it cannot be trusted.
Teaching AI Responsibility¶
ETIS does not ask students to avoid AI.
It asks students to use AI professionally.
Instructor expectations should emphasize:
- disclosure;
- verification;
- ownership;
- traceability;
- awareness of hallucination and overconfidence;
- data and authorization boundaries;
- engineering judgment over tool fluency.
AI use is not an academic violation.
Undisclosed and unverified AI dependency is an engineering risk.
Read COMP-WP-004 — Using AI Professionally →
Review Boards and Release 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¶
Scale complexity, not accountability.
For earlier or smaller courses, reduce project scope.
For advanced courses, increase lifecycle and operational depth.
Do not remove evidence, reviewability, ownership, or professional defense.
Instructor Adoption Path¶
Discover the Framework Reference Work
↓
Review ETIS Books and Professional Formation Resources
↓
Understand the Educational Mission
↓
Read the Education Papers
↓
Study the Instructor Products
↓
Explore the Engineering Platform
↓
Study the 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.
Instructor Doctrine¶
- Educational work should resemble professional engineering work.
- Engineering accountability is the educational outcome, not a side effect.
- Educational systems are engineered and stewarded.
- Every offering should leave evidence for the next instructor.
- Scale complexity, not accountability.
- Do not assess AI avoidance; assess AI responsibility.
- Rubrics should measure trustworthiness, not merely 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.
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.