ETIS COMP330 Flagship Implementation¶
The Loyola University Chicago COMP330/474 implementation is the flagship ETIS educational implementation and feedback system.
It shows how ETIS operates in a real software engineering course.
It also shows how an educational framework improves when it is tested through real students, real teams, real projects, real constraints, and real evidence.
Educational laboratories are where educational frameworks become trustworthy.
Purpose¶
The flagship implementation demonstrates how ETIS can be taught, operated, reviewed, and improved inside an academic software engineering course.
It is not the definition of ETIS.
It is proof that ETIS can work in practice.
The distinction matters:
ETIS Doctrine
↓
Educational Ecosystem
↓
Flagship Implementation
↓
Evidence and Feedback
↓
ETIS Improvement
Implementation Context¶
The flagship implementation is based on:
| Area | Detail |
|---|---|
| Institution | Loyola University Chicago |
| Courses | COMP330 — Software Engineering; COMP474 — Software Engineering |
| Instructor and ETIS Steward | William T. O’Connell |
| Course Model | 15-week semester |
| Enrollment Model | Mixed undergraduate and graduate enrollment |
| Team Model | Teams of approximately 5–6 students |
| Graduate Student Model | Graduate students intentionally distributed across teams, often as team leads |
| Project Model | One team project across the full semester |
| Engineering Model | Two-cycle ETIS engineering model |
| Review Model | Six engineering phase gates |
| Tooling Model | GitHub-supported repository-centered engineering |
| AI Model | AI encouraged throughout the lifecycle and governed through ETIS principles |
Professional Provenance¶
The flagship implementation is informed by approximately four decades of software engineering experience, including IBM Distinguished Engineer and IBM CTO for Quality and Delivery Excellence experience across hundreds of organizations and client engagements.
That provenance matters because ETIS is not only an academic framework.
It carries professional engineering lessons into the classroom.
The implementation asks students to experience software engineering as disciplined, reviewable, evidence-centered work.
Core Thesis¶
COMP330/474 is a bi-directional educational laboratory.
ETIS informs the course.
The course informs ETIS.
The learners transform.
The course operationalizes ETIS doctrine.
The classroom tests ETIS educational assumptions.
The student repositories leave evidence.
The semester generates feedback.
The framework improves.
What the Implementation Proves¶
The flagship implementation demonstrates that students can practice professional engineering behaviors in an academic course when the course is designed around evidence, review, and accountability.
It proves that students can:
- work in engineering teams
- use AI responsibly
- maintain repository-centered evidence
- make and defend requirements decisions
- reason about architecture
- perform reviews
- produce test evidence
- evaluate quality
- consider security and operations
- defend release readiness
- reflect on improvement
The implementation does not prove that every institution should copy Loyola’s course structure.
It proves that ETIS doctrine can be implemented in a real educational environment.
Two-Cycle Engineering Model¶
The flagship implementation uses a two-cycle engineering model.
Cycle 1
Can it work?
Cycle 2
Can it survive?
Cycle 1 emphasizes initial system construction, requirements clarity, architecture direction, working functionality, and early evidence.
Cycle 2 emphasizes maturity, quality, verification, release readiness, operational thinking, and defense.
This model helps students understand that software engineering does not end when the first working version appears.
A working demo is not operational proof.
Six Engineering Phase Gates¶
The flagship course uses six engineering phase gates to distribute accountability across the semester.
Phase gates prevent the course from collapsing into end-of-semester compression.
They create recurring moments where students must show evidence, receive challenge, and improve the work.
Phase gates support:
- requirements accountability
- planning accountability
- architecture accountability
- AI responsibility
- testing and quality accountability
- release readiness
- operational thinking
- team ownership
The goal is not ceremony.
The goal is visible engineering maturity.
Repository-Centered Engineering¶
GitHub is used because it is free, familiar, widely used, and supports repository-centered engineering.
But ETIS is not defined by GitHub.
The repository is used as an engineering memory system.
Students preserve evidence such as:
- requirements
- assumptions
- plans
- team roles
- architecture decisions
- AI use logs
- AI verification notes
- reviews
- test evidence
- defects
- release notes
- operational notes
- postmortems or improvement records
The tool can change.
The engineering behavior must endure.
AI-Supported, Evidence-Governed Work¶
AI is encouraged throughout the entire lifecycle.
Students may use AI for ideation, drafting, code support, testing, documentation, review preparation, and operational reasoning.
But AI use must be governed.
Students are expected to:
- disclose meaningful AI assistance
- verify AI-generated artifacts
- preserve evidence of verification
- understand the work they submit
- defend AI-supported decisions
- avoid hidden dependency
AI usage is not an academic violation.
Undisclosed and unverified AI dependency is an engineering risk.
Graduate Student Leadership¶
Graduate students are intentionally distributed across teams.
This creates a stronger team-learning model and gives graduate students opportunities to practice leadership, coordination, review, and technical judgment.
The role is not simply to do more work.
The role is to help the team mature.
Graduate student leadership supports:
- team accountability
- project planning
- technical decision-making
- peer mentoring
- review readiness
- release defense preparation
- professional communication
Professional Portfolio Evidence¶
The flagship implementation encourages students to build projects that may continue for one to two years as professional portfolio evidence.
That matters because ETIS education should produce durable evidence of engineering ability.
A strong repository can show future employers that students can:
- work in teams
- reason about requirements
- make design decisions
- use AI responsibly
- verify system behavior
- respond to review
- prepare release evidence
- think operationally
- improve from feedback
Students should leave with more than a grade.
They should leave with evidence.
Educational Feedback System¶
The flagship implementation is also a feedback system for ETIS itself.
Each semester can reveal:
- where students struggle
- where instructors need better guidance
- where assignments need clearer sequencing
- where AI policy needs refinement
- where assessment needs better evidence
- where repository structures need improvement
- where ETIS doctrine needs clearer teaching pathways
The course does not merely consume ETIS.
The course improves ETIS.
What Other Institutions Should Learn¶
Institutions should study the flagship implementation to understand how ETIS can be operationalized.
They should not mechanically copy it.
Local adoption should consider:
- academic calendar
- course level
- student background
- class size
- tooling environment
- institutional policy
- AI expectations
- assessment model
- project scale
- instructor capacity
The right question is not:
How do we copy COMP330?
The right question is:
How do we implement ETIS doctrine responsibly in our environment?
Public Implementation Product¶
The primary public implementation product is:
| Product | Purpose |
|---|---|
| ETIS COMP330 Flagship Implementation Guide.pdf | A real-world implementation reference for instructors, departments, universities, and institutional adopters |
The website introduces the implementation model.
The guide provides deeper implementation detail.
Implementation Boundary¶
The Loyola implementation is an adoption example.
It is not the ETIS architecture.
It is proof, not doctrine.
Educational products teach ETIS.
Adoption examples prove ETIS.
This boundary protects ETIS from becoming overfit to one course, one university, one semester model, or one instructor.
Bottom Line¶
The COMP330/474 flagship implementation shows ETIS operating in the real world.
It proves that students can learn software engineering as professional, evidence-centered, AI-responsible engineering work.
It also proves something larger:
A course can become more than a course.
It can become an educational laboratory where the framework, the instructor, the students, and the engineering evidence improve each other over time.