Institutional Adoption¶
Institutional Adoption helps universities, departments, and educators bring ETIS into their educational environments without reinventing software engineering education from scratch.
ETIS is designed to be inherited, adapted, operated, and stewarded over time.
It is not designed to be copied mechanically.
Institutions should inherit ETIS doctrine, not ETIS implementations.
The objective is not standardization.
The objective is trustworthy adaptation.
Who This Is For¶
Institutional Adoption is intended for:
- universities
- departments
- colleges
- professional training programs
- academic leaders
- instructors
- curriculum designers
- educational innovators
Any organization that teaches software engineering in the AI era can adopt ETIS principles.
Why Institutional Adoption Exists¶
Software engineering education is changing.
AI has fundamentally altered how students create artifacts.
The educational challenge is no longer:
How do we teach students to produce software?
The educational challenge is now:
How do we teach students to create trustworthy systems while using increasingly capable AI?
ETIS helps institutions answer that question.
What Institutions Adopt¶
Institutions do not adopt a course.
Institutions adopt an educational framework.
The ETIS Educational Ecosystem provides:
- educational philosophy
- educational doctrine
- instructor operating systems
- professional student engineering environments
- implementation examples
- adoption guidance
- long-term stewardship models
This allows institutions to adapt ETIS without rebuilding educational systems from scratch.
ETIS Adoption Model¶
Institutional adoption should follow a deliberate progression.
Learn ETIS
↓
Study Educational Products
↓
Study the Flagship Implementation
↓
Adapt to the Local Environment
↓
Operate the Course
↓
Collect Educational Evidence
↓
Improve the Implementation
↓
Steward Future Offerings
The process is evolutionary rather than prescriptive.
Adoption Principles¶
ETIS adoption is governed by several principles.
Preserve Doctrine¶
Do not rewrite ETIS principles.
Adapt implementations.
Preserve doctrine.
Adapt Locally¶
Every institution is different.
Adapt to:
- semester length
- quarter systems
- class size
- student maturity
- institutional policies
- AI policies
- instructor experience
- project complexity
Preserve Accountability¶
Do not simplify accountability when adapting ETIS.
Instead:
Scale complexity, not accountability.
Reduce project scope if necessary.
Do not remove evidence.
Do not remove reviewability.
Do not remove ownership.
Preserve Evidence¶
Educational evidence should survive beyond a single semester.
Evidence should help future instructors improve future offerings.
Educational memory is educational infrastructure.
What Institutions Should Not Copy¶
Institutions should not mechanically copy:
- Loyola schedules
- Loyola assignments
- Loyola calendars
- Loyola dates
- Loyola grading percentages
- Loyola logistics
- Loyola terminology where unnecessary
These are implementation details.
They are not ETIS doctrine.
What Institutions Should Inherit¶
Institutions should inherit:
- repository-centered engineering
- evidence-centered engineering
- AI responsibility
- engineering accountability
- engineering review
- engineering defense
- educational stewardship
- educational memory
- transformation models
These are durable ETIS principles.
Adoption Building Blocks¶
Institutions can adopt ETIS incrementally.
Stage 1: Educational Philosophy¶
Introduce ETIS doctrine.
Students begin thinking like engineers instead of assignment completers.
Stage 2: Repository-Centered Engineering¶
Introduce repository-centered evidence.
Students learn to preserve engineering memory.
Stage 3: AI Responsibility¶
Introduce AI disclosure, verification, and ownership.
Students learn to govern AI-assisted work.
Stage 4: Engineering Accountability¶
Introduce engineering evidence requirements.
Students learn that engineering work must be reviewable.
Stage 5: Engineering Defense¶
Introduce review boards, release readiness, and engineering defense activities.
Students learn to explain decisions.
Stage 6: Stewardship¶
Preserve lessons for future semesters.
Educational systems begin improving themselves.
Institutional Decision Areas¶
Institutions should make decisions in several areas.
Academic Structure¶
Determine:
- semester or quarter model
- course duration
- meeting cadence
- project duration
Student Structure¶
Determine:
- undergraduate or graduate audiences
- team sizes
- leadership models
- project complexity
AI Structure¶
Determine:
- AI policies
- AI disclosure expectations
- AI verification expectations
Assessment Structure¶
Determine:
- evidence expectations
- review expectations
- defense expectations
- maturity expectations
Operational Structure¶
Determine:
- repository expectations
- tooling expectations
- instructional support
The framework stays stable.
The implementation adapts.
Recommended Adoption Path¶
A department adopting ETIS should progress through these steps.
- Read the ETIS book.
- Study the Educational Ecosystem.
- Study Instructor Resources.
- Study Student Resources.
- Study the COMP330 Flagship Implementation.
- Build a pilot implementation.
- Run one offering.
- Collect evidence.
- Improve the next offering.
- Steward the implementation over time.
Do not attempt to perfect ETIS before operating it.
Educational systems improve through use.
Public Adoption Products¶
The Educational Ecosystem provides several public products that support adoption.
| Product | Purpose |
|---|---|
| ETIS Educational Ecosystem Guide.pdf | Educational architecture and product overview |
| ETIS Instructor Course Package.pdf | Instructor operating system |
| ETIS Classroom Facilitation Guide.pdf | Classroom operations |
| ETIS Instructor Notes Handbook.pdf | Long-term stewardship |
| ETIS Student Professional Engineering Guide.pdf | Professional student engineering behaviors |
| ETIS COMP330 Flagship Implementation Guide.pdf | Real-world implementation reference |
Together, these products provide a complete adoption system.
Why ETIS Is Sustainable¶
Many educational innovations disappear because they depend upon a single instructor.
ETIS was intentionally designed to survive beyond one person, one institution, or one course.
Its sustainability comes from:
- doctrine
- products
- evidence
- stewardship
- continuity
- adaptation
The goal is long-term educational durability.
Institutional Doctrine¶
Institutional adoption is governed by durable principles:
- Educational work should resemble professional engineering work.
- Educational systems are engineered.
- Educational systems are also stewarded.
- Educational systems are inherited, not reinvented.
- Educational memory is educational infrastructure.
- Every semester should leave evidence for the next instructor.
- Scale complexity, not accountability.
- Scale evaluation mechanisms, not engineering expectations.
- Tools change. Engineering behaviors endure.
- Educational laboratories are where educational frameworks become trustworthy.
Bottom Line¶
Institutional Adoption helps organizations responsibly inherit ETIS.
The goal is not to reproduce Loyola University Chicago.
The goal is to build sustainable educational systems that teach future engineers how to create trustworthy intelligent systems in the AI era.