Back to Course
Docs / Assessments

Assessments

Complete Assessment Package

Course: Blockchain, Crypto Economy & NFTs Academic Year: 2024/2025 Created: December 2024

Overview

This directory contains all assessment materials for the BSc Blockchain, Crypto Economy & NFTs course, including:

Directory Structure

assessments/
├── projects/
│   ├── PROJECT_GUIDE.md              (Main project guidelines)
│   └── templates/
│       ├── M1_Proposal_Template.md
│       ├── M2_Design_Template.md
│       ├── M3_Implementation_Checklist.md
│       ├── M4_Security_Checklist.md
│       └── M6_Final_Submission_Checklist.md
├── rubrics/
│   └── RUBRICS.md                    (All grading criteria)
├── quizzes/
│   ├── QUIZ_1_Blockchain_Foundations.md
│   ├── QUIZ_2_Ethereum_Basics.md
│   ├── QUIZ_3_Tokens_NFTs.md
│   ├── QUIZ_4_NFT_Applications_Tokenomics.md
│   ├── QUIZ_5_DeFi.md
│   └── QUIZ_6_Advanced_Regulation.md
└── README.md                         (This file)

Course Grading Breakdown

Component Weight Description
Semester Project 70% Six milestones (M1-M6) with cumulative deliverables
Lab Assignments 15% 12 hands-on labs throughout semester
Quizzes 10% 6 quizzes covering lecture material
Participation 5% Attendance, engagement, peer review
Total 100%

1. Semester Project (70% of grade)

Project Tracks

Students choose ONE of four project tracks:

  1. Token Economy Track: ERC-20 token with governance features
  2. NFT Platform Track: NFT collection with utility (ticketing, membership)
  3. DeFi Protocol Track: Simplified lending pool or swap mechanism
  4. Supply Chain Track: Provenance tracking system

Project Milestones

Milestone Due Week Weight Deliverable
M0: Team Formation Week 2 0% Team registration (mandatory)
M1: Project Proposal Week 4 5% 2-3 page proposal document
M2: Contract Design Week 6 10% Technical design + interfaces
M3: Core Implementation Week 8 20% Functional contracts + tests
M4: Testing & Security Week 10 15% 80%+ coverage + security analysis
M5: Frontend Integration Week 11 20% Working frontend application
M6: Final Submission Week 12 30% Complete package + presentation
Total 100%

Key Documents

Minimum Requirements

2. Grading Rubrics (RUBRICS.md)

A. Project Rubric (70% of course grade)

Detailed rubrics for each milestone component:

M1 Proposal (5%):

M2 Design (10%):

M3 Implementation (20%):

M4 Security (15%):

M5 Frontend (20%):

M6 Final (30%):

B. Lab Assignment Rubric (15%)

C. Quiz Rubric (10%)

D. Participation Rubric (5%)

3. Quizzes (10% of grade)

Quiz Schedule

Quiz Lectures Topics Covered Timing
Quiz 1 L01-L08 Blockchain foundations, cryptography, consensus Week 3
Quiz 2 L09-L16 Ethereum basics, smart contracts, Solidity Week 5
Quiz 3 L17-L24 Tokens, ERC standards, NFT basics Week 7
Quiz 4 L25-L32 NFT applications, tokenomics Week 9
Quiz 5 L33-L40 DeFi protocols, AMMs, lending Week 11
Quiz 6 L41-L48 Advanced topics, regulation, future trends Week 13

Quiz Format

Each quiz contains:

Quiz Content

All quizzes include:

4. Project Milestone Templates

M1: Project Proposal Template

Purpose: Initial project planning and approval

Sections:

  1. Problem statement (30%)
  2. Proposed solution (40%)
  3. Technical approach (20%)
  4. Team & timeline (10%)
  5. Success criteria

Deliverable: 2-3 page PDF proposal

M2: Contract Design Template

Purpose: Detailed technical architecture before coding

Sections:

  1. Architecture overview (25%)
  2. Contract interfaces (30%)
  3. Data structures & storage (15%)
  4. Security considerations (25%)
  5. Gas optimization strategy (10%)
  6. Testing strategy (10%)
  7. Standards compliance (10%)
  8. Dependencies & libraries (5%)

Deliverable: Technical design document + Solidity interfaces

M3: Implementation Checklist

Purpose: Track core development progress

Sections:

  1. Smart contract implementation (40%)
  2. Testing (20%)
  3. Deployment (15%)
  4. Repository organization (15%)
  5. Documentation (10%)
  6. Functionality assessment
  7. Security self-check

Deliverable: Functional contracts + tests + GitHub repo

M4: Security Checklist

Purpose: Comprehensive testing and security analysis

Sections:

  1. Test coverage (40%) - must achieve 80%+
  2. Unit tests (20%)
  3. Integration tests (15%)
  4. Security analysis (35%)
- Automated tools (Slither, Mythril) - Manual review (reentrancy, access control, etc.)
  1. Gas optimization (10%)
  2. Edge cases & stress testing (10%)
  3. Bug fixes from M3 (10%)

Deliverable: Test suite + security analysis report

M6: Final Submission Checklist

Purpose: Complete project package with all deliverables

Sections:

  1. Code & deployment (35%)
- Smart contracts (40%) - Frontend application (30%) - Testnet deployment (30%)
  1. Documentation (20%)
- Whitepaper 8-12 pages (50%) - README.md (30%) - Code documentation (20%)
  1. Presentation (15%)
- 15-minute presentation - Live demo (5-7 min) - Q&A preparation
  1. Demo video (10%) - 5-10 minutes
  2. Code quality (20%)
  3. Final deliverables checklist
  4. Project reflection

Deliverable: Everything - code, docs, whitepaper, presentation, video

5. Using These Materials

For Instructors

Setup (Week 1):

  1. Review PROJECT_GUIDE.md and adjust deadlines as needed
  2. Set up Moodle with quiz templates
  3. Share PROJECT_GUIDE.md with students
  4. Announce team formation deadline (M0)

Milestone Grading:

  1. Use templates as submission guides
  2. Refer to RUBRICS.md for grading criteria
  3. Provide feedback sections at end of each template
  4. Track progress through milestones

Quiz Administration:

  1. Import quiz questions into Moodle or exam platform
  2. Use provided answer keys for grading
  3. 30-minute time limit per quiz
  4. Administer every 8 lectures (approximately every 2 weeks)

Final Presentations (Week 12):

  1. Schedule 15 minutes per team (10 min presentation + 5 min Q&A)
  2. Require live demo or backup video
  3. Use M6 grading rubric for evaluation
  4. Collect peer review feedback from students

For Students

Project Planning:

  1. Read PROJECT_GUIDE.md carefully
  2. Choose project track by Week 2
  3. Use milestone templates to guide your work
  4. Submit all templates as documentation

Test Preparation:

  1. Review quiz files to understand format and topics
  2. Model answers show expected depth
  3. Practice writing concise short answers
  4. Focus study on lectures covered by each quiz

Milestone Submissions:

  1. Use templates as checklists
  2. Complete all sections thoroughly
  3. Self-assess before submission
  4. Keep all templates in your /docs folder

6. Assessment Philosophy

Learning Outcomes Alignment

This assessment structure ensures students:

  1. Understand blockchain fundamentals (Quizzes 1-2)
  2. Master smart contract development (Labs + M3)
  3. Apply security best practices (M4)
  4. Build complete dApps (M5-M6)
  5. Understand crypto economics (Quizzes 3-4, Project tracks)
  6. Navigate DeFi protocols (Quiz 5)
  7. Recognize regulatory landscape (Quiz 6)
  8. Communicate technical concepts (Whitepaper + Presentation)

Progressive Complexity

Projects build knowledge incrementally:

Scaffolding

Templates provide structure while allowing creativity:

7. Technical Requirements

Smart Contracts

Frontend

Deployment

Repository

8. Key Dates (Template)

Adjust these dates based on your semester schedule:

Week Milestone/Quiz Deliverable Weight
1 Course Intro - -
2 M0: Team Formation Team registration 0%
3 Quiz 1 Blockchain Foundations 1.67%
4 M1: Proposal Project proposal 5%
5 Quiz 2 Ethereum Basics 1.67%
6 M2: Design Technical design 10%
7 Quiz 3 Tokens & NFTs 1.67%
8 M3: Implementation Functional contracts 20%
9 Quiz 4 NFT Apps & Tokenomics 1.67%
10 M4: Security Tests + security analysis 15%
11 M5: Frontend + Quiz 5 Frontend + DeFi Quiz 20% + 1.67%
12 M6: Final + Presentation Complete project 30%
13 Quiz 6 Advanced & Regulation 1.67%

Labs distributed throughout weeks 1-12 (15% total).

9. Common Questions

Q: Can teams change their project track after M1?

A: Yes, until M2 submission with instructor approval. After M2, track changes are not allowed.

Q: What if a team member doesn't contribute?

A: Document contribution issues early. Contact instructor by Week 6. Individual grades can be adjusted based on documented evidence.

Q: Can we use AI coding assistants (GitHub Copilot, ChatGPT)?

A: Yes, but you must understand all generated code and be able to explain it. You're responsible for all code security and correctness.

Q: What if our deployed contracts have a bug?

A: Document known issues in your whitepaper. Minor bugs are acceptable if documented and understood. Critical security bugs will impact grade.

Q: Can we build on existing open-source projects?

A: Yes, with proper attribution. You must add significant original functionality. Copying without attribution is plagiarism.

Q: What happens if live demo fails during presentation?

A: Have a backup demo video ready. You can use the video if live demo encounters technical issues. Practice beforehand to minimize risk.

Q: How are quizzes administered?

A: Online via Moodle, 30 minutes, closed book. Must be taken during scheduled time window. No retakes except documented emergencies.

Q: Is mainnet deployment required?

A: No. Testnet deployment only. Do NOT deploy to mainnet without professional audit. This is a prototype/learning project.

10. Support Resources

For Help

Learning Resources

Development Tools

11. Academic Integrity

Allowed

Prohibited

Violations: First offense = 0 on assignment. Second offense = F in course.

12. Accessibility

Students with documented disabilities should contact the Office of Disability Services and inform the instructor within the first two weeks to arrange accommodations.

13. Version History

Version Date Changes
1.0 Dec 2024 Initial release with all assessment materials

14. License

These assessment materials are provided for educational use in the BSc Blockchain, Crypto Economy & NFTs course. Instructors may adapt as needed for their specific course context.

Contact

For questions about these materials:

Last Updated: December 2024

(c) Joerg Osterrieder 2025

Back to Home | Syllabus