Milestone map
Milestone map
2 milestones
Do the course work in public
1–2 weeks (10 hrs/week)
Take Databases: Modeling and Theory for free and do data models (ER diagrams and normalised tables) for three real systems. Keep everything in one public repo or notebook as you go. Certificates cost money. Audit is free; you never need the certificate here.
Proof required
Link your public repo or notebook with data models (ER diagrams and normalised tables) for three real systems, and a screenshot or log showing the self-check passed.
What gets checked
- Each model fits a real system you name.
- Tables are in third normal form or the reason is given.
- Keys and relations are correct.
Common mistakes
- Copying posted answers: verifiers read the history.
- Skipping the self-check, then asking for review too early.
Powstik Guide
A public repo or notebook with data models (ER diagrams and normalised tables) for three real systems.
Steps
- Make a public repo or notebook first.
- Do one unit at a time and commit after each.
- Run the self-check: Check your models against the normal forms in the notes.
- Write a short README: what is here and how to run it.
- Ask three people who know the topic to check it.
Template
README Course: Databases: Modeling and Theory (Stanford on edX) What is here: How to run it: Self-check result: What was hardest:
What gets sent back
- No history, just one big upload.
- Self-check not shown.
- Code that does not run from the README.
Resources
Foundationstart here
Depthgo deeper
What a verifier looks for
- Each model fits a real system you name.
- Tables are in third normal form or the reason is given.
- Keys and relations are correct.
- Ask one question about a choice in the code; the answer should be clear.
You'll sign in first, then come straight back here.
Design the database for a real app
1–3 weeks (5–8 hrs/week)
Use what you learned. Make a schema for an app you use or build, with sample data and five queries it must answer. Keep it small enough to finish in about two weeks.
Proof required
Link a schema for an app you use or build, with sample data and five queries it must answer, with a README that says how to run or read it.
What gets checked
- The schema answers all five queries.
- Sample data loads with no errors.
- Design choices are explained.
Common mistakes
- A project too big to finish.
- A demo that only works on your machine.
Powstik Guide
A schema for an app you use or build, with sample data and five queries it must answer.
Steps
- Write one line: what it does and for whom.
- Build the smallest version that works.
- Test it on someone else's machine or with someone else reading it.
- Write the README.
- Ask three people to check it.
Template
README What it does: Who it is for: How to run it: What I would do next:
What gets sent back
- Does not run from the README.
- Not clearly the person's own work.
- Claims more than it does.
Resources
Foundationstart here
Depthgo deeper
What a verifier looks for
- The schema answers all five queries.
- Sample data loads with no errors.
- Design choices are explained.
- Check that the work is the person's own.
You'll sign in first, then come straight back here.