2019 case study: Difference between revisions
Mr. MacKenty (talk | contribs) |
Mr. MacKenty (talk | contribs) m (Protected "2019 case study" ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite))) |
(No difference)
| |
Revision as of 14:26, 30 May 2018
Case study[1]
Introduction[edit]
This page will help you organize and understand the 2019 case study.
The case study[edit]
Click here for the full pdf case study
Terms worth deeply understanding[edit]
These articles have been written by students. Any article with a green checkmark 
has been approved by a teacher and can be used reliably to study.
- Template for student-defined terms
- Application programming interface (API) Client side random -Zosia K
- Cluster - Tom
- Cluster of servers - Franek
- Commercial software -Max
- Computer aided dispatch (CAD) -Gabriel
- Cookies - Anna
- Custom software - Guilia
- Emergency control centre (ECC) -Felix M
- Emergency management information system (EMIS) - Emre
- Emergency number - Jasper
- Failover - Sheevankit
- Future-proof - Moody
- Global positioning system (GPS) - Zosia B
- HTTP or HTTP/2 -Zosia K
- Load balancing algorithm - Tom
- Multitier architecture - Franek
- Proxy server - Max
- Real-time - Seung Won
- Redundancy - Felix
- Representational state transfer (REST) - Emre
- Scalability / scalable architecture - Gabriel
- Safety-critical - Annie
- Session - Alex B
- Session IP hash - Moody
- Session management -Zosia B
- Socket - Annie
- Source IP hash - Zosia K
- Stateful / stateless / maintaining state - Max
- TCP/IP sockets - Tom
- Transaction processing system (TPS) - Seung Won
- URL rewriting - Felix
- Virtual private network (VPN) - Emre
- Voice over internet protocol (VoIP) - Sheevankit
- Weighted round robin - Moody
- Zero downtime - Zosia B
Previous years case study[edit]
- Click here for 2018 case study wiki-notes
- Click here for 2017 case study wiki-notes
- Click here for the 2018 case study
- Click here for the 2017 case study
- Click here for the 2016 case study