web-programming-project/mail.txt at main · sorooshaghaei/web-programming-project · GitHub

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
Dear students,


Here you can find last lecture 10 and import document for Friday.

This Friday you will present your full-stack project. Please read the instructions carefully.


What you MUST prepare

Each team must:

Prepare a presentation (5–7 slides, max 6 minutes)
Prepare a working deployed application
Be ready for a live demonstration
Print 1 copy per team of the provided document:
 Project WEB_Prog (attached)
Bring it to the defense.


Printed Document (IMPORTANT)

One printed copy per team
Fill in Names, Student IDs, Roles.
You will use this document during the presentation it will aslo help you to prepare yourselves and check if you have done everything is required.


How the defense will work


Your presentation will be interactive and controlled by me.

You will NOT just present slides.

I will ask you to:

show specific features
perform actions live
explain your technical choices
Structure of the defense (6 minutes)

You should be ready to:

1. Very short introduction

Explain:

what your system does
what problem it solves
2. Live Demonstration (MAIN PART)

You will be asked to immediately show:

Login
Create an event
Create a participant
Register a participant to an event
Try duplicate registration (must be blocked)
Filter events
Show role-based behavior (admin vs viewer)
3. Technical Questions

Be ready to explain:

your architecture
your database design
your API
differences between Django and Node.js
frontend logic (React, hooks, state handling)
deployment choices
 Important rules

All team members must be able to answer questions
You must understand the entire project, not only your part
The demo must be real and working (not screenshots)
Not acceptable

No live demo
Only slides without system
Reading from slides
Missing key features:
authentication
CRUD
many-to-many relationship
What I evaluate

Does your system work end-to-end?
Do you understand what you built?
Can you explain your decisions clearly?
Can you demonstrate it live without issues?


Final advice

Prepare like this:

Practice the demo (it should take < 3 minutes)
Make sure everything works in production
Be ready to answer “why?” for every decision
If your system works and you understand it — you will do well.


If your project is not fully complete — do not panic.


You can still achieve a good result if you:


1. Focus on one part of the system and present it well

(for example: backend logic, frontend, or authentication)

2. Clearly explain what is implemented vs not implemented

3. Demonstrate that you understand your code and decisions


It is better to show:

a working partial system with clear explanations than a broken full system you cannot explain


You are evaluated not only on completeness, but also on: understanding, reasoning, ability to explain your work

Stay calm, be clear, and show what you do know.


Good luck!


My best regards,

Alla Jammine