2019 case study: Difference between revisions
Mr. MacKenty (talk | contribs) |
Mr. MacKenty (talk | contribs) |
||
| (8 intermediate revisions by 2 users not shown) | |||
| Line 7: | Line 7: | ||
== The case study == | == The case study == | ||
[[Media:2019 case study.pdf| Click here for the full pdf case study]] | [[Media:2019 case study.pdf | Click here for the full pdf case study]] | ||
== Terms worth deeply understanding == | == Terms worth deeply understanding == | ||
| Line 13: | Line 13: | ||
* [[Template for student-defined terms]] | * [[Template for student-defined terms]] | ||
* [[Application programming interface (API) Client side random]] | * [[Application programming interface (API) Client side random]] -Zosia K | ||
* [[Cluster]] | * [[Cluster]] - Tom | ||
* [[Cluster of servers]] | * [[Cluster of servers]] - Franek | ||
* [[Commercial software]] | * [[Commercial software]] -Max | ||
* [[Computer aided dispatch (CAD)]] | * [[Computer aided dispatch (CAD)]] -Gabriel | ||
* [[Cookies]] | * [[Cookies]] - Sid | ||
* [[Custom software]] | * [[Custom software]] - Guilia | ||
* [[Emergency control centre (ECC)]] | * [[Emergency control centre (ECC)]] -Felix M | ||
* [[Emergency management information system (EMIS) Emergency number]] | * [[Emergency management information system (EMIS)]] - Emre | ||
* [[Failover]] | * [[Emergency number]] - Jasper | ||
* [[Future-proof]] | * [[Failover]] - Sheevankit | ||
* [[Global positioning system (GPS)]] | * [[Future-proof]] - Moody | ||
* [[HTTP or HTTP/2]] | * [[Global positioning system (GPS)]] - Zosia B | ||
* [[Load balancing algorithm]] | * [[HTTP or HTTP/2]] -Zosia K | ||
* [[Multitier architecture]] | * [[Load balancing algorithm]] - Tom | ||
* [[Proxy server]] | * [[Multitier architecture]] - Franek | ||
* [[Real-time]] | * [[Proxy server]] - Max | ||
* [[Redundancy]] | * [[Real-time]] - Seung Won | ||
* [[Representational state transfer (REST)]] | * [[Redundancy]] [[file:approved.png|25px|Approved]] | ||
* [[Scalability / scalable architecture]] | * [[Representational state transfer (REST)]] - Emre | ||
* [[Safety-critical]] | * [[Scalability / scalable architecture]] - Gabriel | ||
* [[Session]] | * [[Safety-critical]] - Lea | ||
* [[Session IP hash]] | * [[Session]] - Sid | ||
* [[Session management]] | * [[Session IP hash]] - Moody | ||
* [[Socket]] | * [[Session management]] -Zosia B | ||
* [[Source IP hash]] | * [[Socket]] - Lea | ||
* [[Stateful / stateless / maintaining state]] | * [[Source IP hash]] - Zosia K | ||
* [[TCP/IP sockets]] | * [[Stateful / stateless / maintaining state]] - Max | ||
* [[Transaction processing system (TPS)]] | * [[TCP/IP sockets]] - Tom | ||
* [[URL rewriting]] | * [[Transaction processing system (TPS)]] - Seung Won | ||
* [[Virtual private network (VPN)]] | * [[URL rewriting]] - Felix | ||
* [[Voice over internet protocol (VoIP)]] | * [[Virtual private network (VPN)]] - Emre | ||
* [[Weighted round robin]] | * [[Voice over internet protocol (VoIP)]] - Sheevankit | ||
* [[Zero downtime]] | * [[Weighted round robin]] - Moody | ||
* [[Zero downtime]] - Zosia B | |||
== Previous years case study == | == Previous years case study == | ||
* [[2018 case study|Click here for 2018 case study wiki-notes]] | * [[2018 case study|Click here for 2018 case study wiki-notes]] | ||
* [[2017 case study|Click here for 2017 case study wiki-notes]] | * [[2017 case study|Click here for 2017 case study wiki-notes]] | ||
* [[Media:2018 case study.pdf|Click here for the 2018 case study]] | |||
* [[Media:2017 case study.pdf|Click here for the 2017 case study]] | * [[Media:2017 case study.pdf|Click here for the 2017 case study]] | ||
<!-- | <!-- | ||
Latest revision as of 07:23, 6 April 2019
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 - Sid
- 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
- Representational state transfer (REST) - Emre
- Scalability / scalable architecture - Gabriel
- Safety-critical - Lea
- Session - Sid
- Session IP hash - Moody
- Session management -Zosia B
- Socket - Lea
- 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