The project you describe seems a lot for just "basic networking", at least to do it well.
In general, you select the devices for their features and performance capabilities. For instance, a core device is generally a bit more "powerful" then distribution or access devices, devices supporting servers are also generally a bit more powerful than those supporting users.
You mention WiFi, well those might want PoE ports, but then the question is, what are PoE wattage needs. You also mention WiFi 6, for those you may want mGig ports.
You mention a requirement for designing a 3 layer hierarchy, but for a network as small as your seems to be, a single chassis device, or stackable switch, might be suitable, especially with current gen devices for this size network, likely no more than a "collapsed core" network would be needed.
Knowing ALL your port needs is necessary. You mention user port needs (60 + 10 + 80 + 10 + 36 + 15 = 211? [possibly handled by 5 x 48 port line cards or switches]), but port counts for (later posted): WiFi WAP ports, CCTV ports, server ports, or other needed ports? Physical placement is important, due to 100m copper Ethernet distance limitation.)
Basically, you need much, much more information about what's expected for your network to support to begin to select actual devices (and in the real world, something like the budget, often has much say in what you might select).
What about fault tolerance?
No doubt this project is basically to learn concepts, but then conceptionally, all you would really need is any L3 switch for core or distribution or access (the latter might also use just L2 switches).
I.e. I cannot see how you can justify any specific switch model without much more detail for the requirements. Without such requirement details, one L3 x number of ports switch/line-card is the same as any other.
Unfortunately, likely the above isn't very helpful, but whoever set the project requirements should also set the corresponding expectations what's expected.
To me, even "We are to design a server room that will accommodate 3 departments." is unclear. Generally, server rooms aren't designed for departments, although depending on interior funding accounting, a department might "own" its server(s) and/or a cabinet rack(s). Again, much more details are needed.
BTW, in the real world, you try to take into account possible future changes. I've seen user floor plans changed to accommodate more users. Running physical cabling is very (labor) expensive. Knowing that, you might run more cables out to the floor or server room, then initially needed, so they might be easily connected to in the future.
If all the above makes designing a network, "complex", that's because it is. Lots to take into account to do it well. Again, I wouldn't expect a student project to fully address all of this, but again, that's why it needs to be clear what exactly the project is, what's the information being provided, and what's the expected deliverable.
