ETIS Student Resources¶

ETIS Student Resources help students practice software engineering as professional engineering work in the AI era.

Students are not simply asked to build software.

They are expected to create evidence that their work can be understood, reviewed, governed, operated, improved, and trusted over time.

The model is not the system. The repository is not just code. Engineering work must leave evidence.

What Makes ETIS Student Work Different¶

Traditional student projects often follow this pattern:

Receive assignment
↓
Build software
↓
Submit final artifact
↓
Receive grade

ETIS student work follows a different pattern:

Define intent
↓
Plan work
↓
Engineer context
↓
Use AI responsibly
↓
Build and verify
↓
Preserve evidence
↓
Defend decisions
↓
Improve from feedback

The goal is not only to finish the project.

The goal is to become a trustworthy engineer.

Start Here¶

Student Starter Kit¶

The ETIS Student Starter Kit is a professional engineering environment, not a software platform.

It helps students organize engineering work into clear responsibilities:

docs/      Think
src/       Build
tests/     Verify
data/      Support
scripts/   Automate

Repository-Centered Engineering¶

Students use the repository as an engineering memory system.

The repository should show what the team decided, why it decided it, what evidence supports the work, and what risks remain.

AI Responsibility¶

AI is allowed and encouraged.

Unverified AI dependency is not.

Students are responsible for disclosure, verification, traceability, and ownership.

Professional Portfolio Evidence¶

A strong ETIS repository should become evidence of professional engineering ability, not merely evidence of course completion.

The Student Transformation Model¶

ETIS education is designed to help students mature through a professional engineering progression:

Student
↓
Responsible Engineer
↓
Reviewer
↓
Architect
↓
Release Defender
↓
Operational Thinker
↓
Future Trustworthy Engineer

Each stage requires stronger evidence, better judgment, and greater ownership.

Student Starter Kit Structure¶

The Student Starter Kit separates engineering responsibilities clearly.

Area	Responsibility
`docs/`	Think, decide, explain, preserve evidence
`src/`	Build the system
`tests/`	Verify behavior
`data/`	Support realistic use and evaluation
`scripts/`	Automate repeatable work

The most important area is often docs/.

That is where engineering intent, assumptions, decisions, reviews, risks, and release evidence become visible.

Engineering Evidence Package¶

The starter kit helps students preserve evidence across the full lifecycle.

Student repositories should include evidence such as:

requirements and assumptions
acceptance criteria
planning artifacts
task plans and schedules
team roles and working agreements
architecture descriptions
architecture decisions
AI use logs
AI verification notes
code review evidence
architecture review evidence
test plans
test cases
test evidence
defect logs
quality notes
security and data-handling notes
release readiness evidence
demo scripts
known limitations
operational notes
runbooks
observability plans
postmortem or improvement evidence

This evidence is not paperwork.

It is how engineering work becomes reviewable.

Repository-Centered Engineering¶

In ETIS, the repository is more than a place to store source code.

It is the center of engineering memory.

A strong student repository should answer:

What are we building?
Why are we building it?
What assumptions are we making?
What decisions did we make?
What evidence supports our claims?
What risks remain?
How did we use AI?
How did we verify the work?
Is the system ready to release, demonstrate, or operate?
What should improve next?

If those answers are not visible, the engineering work is incomplete.

AI Use and Verification¶

ETIS students may use AI throughout the engineering lifecycle.

AI may help with:

brainstorming
requirements refinement
design alternatives
code generation
test generation
documentation drafting
defect analysis
review preparation
operational planning

But students remain responsible for the work.

Student AI expectations include:

disclose meaningful AI assistance
verify AI-generated artifacts
document important AI usage
preserve evidence of verification
reject unsupported or incorrect AI output
understand the submitted work
defend the engineering decision

AI proposes.

Engineers verify.

Reviews and Defenses¶

ETIS students should expect their work to be reviewed and challenged.

Students should be prepared to defend:

requirements choices
scope decisions
architecture tradeoffs
AI-assisted work
testing strategy
quality evidence
security assumptions
release readiness
operational risks
known limitations

Engineering work is not complete until it can be defended.

Team Engineering¶

ETIS student work is team-based because professional engineering is team-based.

Strong teams make work visible.

They preserve:

roles
responsibilities
working agreements
communication plans
meeting notes
decisions
risks
blockers
review outcomes
ownership boundaries

Hidden work creates hidden risk.

Visible work creates engineering trust.

Student Accountability Model¶

ETIS students are accountable for more than contribution.

They are accountable for ownership.

Students should be able to explain:

what they personally contributed
what the team produced
what evidence supports the work
what AI helped create
how AI output was verified
what risks remain
what they would improve next

The strongest students do not merely say, “It works.”

They show why the work should be trusted.

Professional Portfolio Value¶

A strong ETIS repository can become professional portfolio evidence.

It can show future employers that a student can:

work in a team
reason about requirements
make architectural decisions
use AI responsibly
test and verify systems
handle defects and quality issues
think about security and operations
prepare release evidence
explain tradeoffs
improve from review

Students should leave the course with evidence of engineering ability.

Not just a grade.

Student Product¶

The primary public student product is:

Product	Purpose
ETIS Student Professional Engineering Guide.pdf	Guidance for using the ETIS starter kit as a professional engineering environment

The website introduces the student model.

The guide provides deeper practical direction.

Student Doctrine¶

ETIS student work is governed by durable principles:

Educational work should resemble professional engineering work.
AI can produce artifacts. Engineers create trust.
The model is not the system.
The repository is an engineering memory system.
Engineering work must leave evidence.
Undisclosed and unverified AI dependency is an engineering risk.
Requirements, decisions, tests, reviews, releases, and operations should be traceable.
Engineering work is not complete until it can be defended.
Tools change. Engineering behaviors endure.
Students should graduate with evidence of engineering ability rather than evidence of course completion.

How to Use Student Resources¶

Students should use ETIS Student Resources to:

Understand the purpose of repository-centered engineering.
Set up a professional engineering environment.
Organize evidence before building too much code.
Use AI responsibly and visibly.
Preserve decisions, tests, reviews, and release evidence.
Prepare to defend engineering work.
Improve the repository as the project matures.

The objective is not to fill folders.

The objective is to make engineering work understandable, reviewable, and trustworthy.

Bottom Line¶

ETIS Student Resources help students move from building software to practicing engineering.

The student who succeeds in ETIS does not merely produce a working project.

The student produces evidence that the work can be trusted.