A | B | C | D | E | F | G | H | I | J | K | L | M | N | O | P | Q | R | S | T | U | V | W | X | Y | Z | AA | |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1 | T | Q number | Examiner | Year | Description | ||||||||||||||||||||||
2 | PA194 | PA181 | PA116 | PA017 | PA152 | PA159 | PA152 | PV157 | PA179 | PV207 | PV203 | PV215 | PV240 | PV241 | PV206 | 6S | Bartek | 2016 | 2016 | ||||||||
3 | PA179 | PA165 | PA195 | PA191 | PV017 | PV214 | PV237 | PV216 | PV166 | PV209 | 8S | Bartek | 2016 | 1. otázka byla na aplikovanou kryptografii. Takže symetrická/asymetrická kryptografie, digitální podpis, hash, certifikační autorita, biometrické systémy. | The 1st question was about applied cryptography. So symmetric/asymmetric cryptography, digital signature, hash, certificate authority, biometric systems. | ||||||||||||
4 | Examiner | 1S | 2S | 3S | 4S | 5S | 6S | 7S | 8S | 1M | 2Ms | 3M | 4M | 5M | 6M | 7M | 1M | Bühnová | 2016 | Teamwork, optimalni mnozsti clenu v tymu, k cemu slouzi Quality Assurance, homogenost vs diverzita clenu v tymu | Teamwork, optimal number of team members, what is the purpose of Quality Assurance, homogeneity vs diversity of team members | ||||||
5 | Walletzký | 24 | 8 | 0 | 0 | 0 | 0 | 0 | 3 | 0 | 0 | 0 | 15 | 3 | 2 | 0 | 1M | Bühnová | 2016 | TOC, CC, Gant... | TOC, CC, Gant... | ||||||
6 | Ráček | 1 | 0 | 4 | 0 | 0 | 0 | 0 | 0 | 16 | 0 | 1 | 0 | 1 | 0 | 0 | 1S | Bühnová | 2016 | Vcelku vpoho ptala se na ekonomicke paradigmata (orientace na produkty/sluzby)... Rozebirali jsme nejake veci z praxe. Spise takova diskuse/polemika nad vecmi nez zkouseni z temat otazky - je hodna. | She asked about economic paradigms (orientation on products/services)... We discussed some things from practice. Such a discussion/controversy over things rather than an examination of the topic of the question - is worthy. | ||||||
7 | Dohnal | 0 | 1 | 0 | 3 | 3 | 6 | 0 | 4 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 4S | Bühnová | 2016 | Bühnová mi povedala nech jej poviem niečo o SOA tak som povedal čo to je, aké to má výhody, prístupy k budovaniu SOA architektúry (top-down, bottom-up). Potom mala nejaké jednoduché otázky k tomu a spýtala sa ma ešte na ITIL, kde som dal definíciu, povedal z akých 5 oblastí sa to skladá a 1 príklad toho čo sa rieši v každej knihe. | Bühnová told me to tell him something about SOA, so I said what it is, what advantages it has, approaches to building SOA architecture (top-down, bottom-up). Then she had some simple questions about it and asked me about ITIL, where I gave a definition, said what 5 areas it consists of and 1 example of what is dealt with in each book. | ||||||
8 | Zlatuška | 0 | 0 | 0 | 0 | 0 | 1 | 1 | 3 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 5S | Bühnová | 2016 | Bühnová mi povedala nech jej poviem niečo o SOA tak som povedal čo to je, aké to má výhody, prístupy k budovaniu SOA architektúry (top-down, bottom-up). Potom mala nejaké jednoduché otázky k tomu a spýtala sa ma ešte na ITIL, kde som dal definíciu, povedal z akých 5 oblastí sa to skladá a 1 príklad toho čo sa rieši v každej knihe. | Bühnová told me to tell him something about SOA, so I said what it is, what advantages it has, approaches to building SOA architecture (top-down, bottom-up). Then she had some simple questions about it and asked me about ITIL, where I gave a definition, said what 5 areas it consists of and 1 example of what is dealt with in each book. | ||||||
9 | Pitner | 0 | 0 | 0 | 1 | 0 | 0 | 1 | 2 | 0 | 0 | 1 | 0 | 0 | 0 | 1 | 4S | Dohnal | 2016 | SoA, zakladne pojmy/rysy, trochu soap vs rest, (wsdl spomenul), url/uri | SoA, basic concepts/features, a bit of soap vs rest, (wsdl mentioned), url/uri | ||||||
10 | Batko | 0 | 0 | 2 | 4 | 2 | 2 | 5 | 1 | 2 | 0 | 1 | 0 | 0 | 0 | 0 | 4S | Dohnal | 2016 | Pan Dohnal mi dal v návaznosti na DP (webová aplikace) SOA, SOAP, WSDL, REST. Obecné principy, největší detail byl ohledně URI u GET, PUT,... | Mr. Dohnal gave me SOA, SOAP, WSDL, REST as a follow-up to DP (web application). General principles, the biggest detail was about URIs for GET, PUT,... | ||||||
11 | Ošlejšek | 0 | 0 | 8 | 1 | 0 | 3 | 1 | 4 | 0 | 0 | 5 | 0 | 0 | 0 | 0 | 0 | 5S | Dohnal | 2016 | Pan Dohnal mi dal distribuovane systemy vs centralizovane. Vydatne navadzal a dost specifikoval co vlastne pozaduje. Bohuzial som tuto temu jaksi "neovladal", takze som pri niektorych otazkach tapal (zjednodusene -> ako sa riesi rozdelenie prace). Bol vsak velmi prijemny. Nasledne mi dal petriho siete ako podotazku a tu som uz nejak laicky podal. Celkovo sa to dalo obkecat bez definicii a vyzeralo to, ze to akceptuje. Posobil neuveritelne pohodovo. Tiez naozaj pocuval co vravim pocas prezentacie a aj listoval zadanim. Mal k nemu dokonca aj otazky. To ma uprimne prekvapilo a zaroven aj potesilo. | Mr. Dohnal gave me distributed systems vs centralized. He followed up profusely and was quite specific about what he actually wanted. Unfortunately, I didn't "master" this topic somehow, so I struggled with some questions (simplified -> how to solve the division of work). However, he was very nice. Next, he gave me a petri net as a sub-question, and I submitted it in a layman's way. All in all, it could be talked about without definition and it seemed that he accepted it. He acted incredibly comfortably. He also really listened to what I was saying during the presentation and flipped through the assignments. He even had questions for him. That honestly surprised me and pleased me at the same time. | |||||
12 | Matyska | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 6S | Dohnal | 2016 | Pan Dohnal mi dal distribuovane systemy vs centralizovane. Vydatne navadzal a dost specifikoval co vlastne pozaduje. Bohuzial som tuto temu jaksi "neovladal", takze som pri niektorych otazkach tapal (zjednodusene -> ako sa riesi rozdelenie prace). Bol vsak velmi prijemny. Nasledne mi dal petriho siete ako podotazku a tu som uz nejak laicky podal. Celkovo sa to dalo obkecat bez definicii a vyzeralo to, ze to akceptuje. Posobil neuveritelne pohodovo. Tiez naozaj pocuval co vravim pocas prezentacie a aj listoval zadanim. Mal k nemu dokonca aj otazky. To ma uprimne prekvapilo a zaroven aj potesilo. | Mr. Dohnal gave me distributed systems vs centralized. He followed up profusely and was quite specific about what he actually wanted. Unfortunately, I didn't "master" this topic somehow, so I struggled with some questions (simplified -> how to solve the division of work). However, he was very nice. Next, he gave me a petri net as a sub-question, and I submitted it in a layman's way. All in all, it could be talked about without definition and it seemed that he accepted it. He acted incredibly comfortably. He also really listened to what I was saying during the presentation and flipped through the assignments. He even had questions for him. That honestly surprised me and pleased me at the same time. | ||||||
13 | Bühnová | 2 | 0 | 2 | 2 | 7 | 0 | 0 | 0 | 5 | 0 | 2 | 1 | 2 | 0 | 0 | 6S | Dohnal | 2016 | Siete - vseobecne, zacal som sam ze co to je, co chcem aby mi zabezpecili a podobne, potom ma naviedol ze mu mam popisat vrstvy OSI, bola to taka prijemna konverzacia, nechal ma nieco povedat, ked ho zaujimalo viac tak sa opytal na nejaky detail, ked som nevedel tak ma naviedol, v podstate zakladne veci, vsetko iba z materialov alebo logicky dedukovatelne... trosku viac sme sa pristavili na smerovani a uz bol koniec... | Networks - in general, I started by myself with what it is, what I want them to secure for me and the like, then he instructed me to describe the OSI layers to him, it was such a pleasant conversation, he let me say something, when he was interested in more, he asked about some detail, when I didn't know, he guided me, basically basic things, everything only from materials or logically deducible... we got a little closer to routing and it was over... | ||||||
14 | Bartek | 0 | 0 | 1 | 0 | 1 | 1 | 1 | 4 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 8S | Dohnal | 2016 | autentizace, autorizace, acl, pak se ptal ještě na ukládání hesel přes co sme došli k hashování (ptal se na vlastnosti), zabrousili jsme i do solení hesel | authentication, authorization, acl, then he also asked about saving passwords, through which we arrived at hashing (he asked about properties), we also honed in on salting passwords | ||||||
15 | Šimková | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 1 | 2 | 3 | 1 | 6S | Novák | 2016 | ISO OSI, popis vrstev, popis IP protokolu, TCP, UDP, jak funguje router. | ISO OSI, description of layers, description of IP protocol, TCP, UDP, how a router works. | ||||||
16 | Matyáš | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 6S | Novák | 2016 | ISO/OSI model som nakreslil. pýtal sa na putovanie správ po vrstvách. Hovoril som na príklad SMTP. IP účel, IPv4 v6 adresy, rozdelenie IPv4 adresy na sieťovú časť a časť označujúcu zariadenie, ako adresy vyzerajú. TCP protokol, účely, ciele, rozdiel medzi TCP/UDP - tu som pustil prvý fail. Najprv som povedal niekoľko rozdielov, ale predseda Matyska (hovoril som, že sa pýta aj predseda| chcel počuť jeden zásadný - congestion control - ktorý mi nejak nešiel na jazyk, ale pritom to viem. Deň predtým som čítal rozdiely medzi IPsec a TCP, ktorý ma úplne pomiatol, takže som zapotil, že TCP sa šifruje pomocou SSL a šiel som dodať, že UDP by šlo riešiť cez IPsec, ale k tomu som sa nedostal, lebo keď som vypustil SSL, tak to okomentovali že "som práve pokazil celý dojem, který sem doted delal" :D :D ufff. Ale tak hneď ako sa Matyska teda pýtal na ten rozdiel, tak mi došlo tým, ako sa pýtal na congestion, ktorý som vysvetlil. Ešte pár detailov k sietiam. | I drew the ISO/OSI model. he asked about messages traveling through the layers. I was talking about the example of SMTP. IP purpose, IPv4 v6 addresses, division of an IPv4 address into a network part and a device part, what addresses look like. TCP protocol, purposes, goals, difference between TCP/UDP - here I played the first file. At first I said a few differences, but Chairman Matyska (I said that the chairman is also asking questions) wanted to hear one fundamental one - congestion control - which somehow didn't fit my language, but I know it. The day before I read the differences between IPsec and TCP, which completely confused me, so I sweated that TCP is encrypted using SSL and I was going to add that UDP could be solved via IPsec, but I didn't get to that, because when I dropped SSL, they commented that "I just messed up the whole impression I was making so far" :D :D ufff. But as soon as Matyska asked about the difference, it occurred to me that he asked about congestion, which I explained. A few more details about the networks. | ||||||
17 | Přenosil | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 8S | Novák | 2016 | Pytal sa na krypto, co je digitalny podpis, z neho sme presli na certifikaty a PKI. Chcel odomna pocut, ze pri certifikatoch je podstatna nie len CA, ale takisto, ci je certifikat platny, co mi najprv nenapadlo, ale postupne sme sa k tomu otazkami v pohode dostali. Nic viac nechcel a bol spokojny. | He asked about crypto, what is a digital signature, from that we moved on to certificates and PKI. He wanted to hear from me that it is not only the CA that is important for certificates, but also whether the certificate is valid, which I didn't think of at first, but gradually we got to it with questions. He wanted nothing more and was satisfied. | |||||||
18 | Švenda | 0 | 1 | 0 | 0 | 0 | 1 | 0 | 5 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 8S | Novák | 2016 | kryptografie, digitální podpis, jak funguje digitální podepsání a ověření, CA | cryptography, digital signature, how digital signing and verification work, CA | ||||||
19 | Novák | 0 | 0 | 0 | 0 | 0 | 2 | 0 | 3 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 8S | Novák | 2016 | Pri skúšaní mi najprv Novák povedal, že ostaneme pri téme mojej diplomky a dostal som 14 - digitálny podpis, certifikáty a PKI. | During the exam, Novák first told me that we would stick to the topic of my diploma and I received 14 - digital signature, certificates and PKI. | ||||||
20 | Summary | 27 | 10 | 17 | 11 | 13 | 16 | 10 | 29 | 24 | 0 | 10 | 17 | 8 | 5 | 4 | 3M | Ošlejšek | 2016 | ITIL (5 stages, SOA, Web service, a bit detail) | ITIL (5 stages, SOA, Web service, and bit detail) | ||||||
21 | 6S | Ošlejšek | 2016 | Zacal otazkou jak probiha smerovani v sitich a na jake vrstve se nachazi. Pote po me chtel do detailu vysvetlit jak funguje Distance Vector a jak Link State plus priklad, nasledne nato presel k IP, co vse je potreba na PC zadat krome IP adresy aby se spravne nacetla sit? Spravna odpoved Gateway a maska podsite, rozebrat co k cemu slouzi, ukazat na prikladech. Dale rozebrat k cemu slouzi NAT a jak funguje. Jak se resi nedostatek IP adres v protokolu IPv4? | He started by asking how routing works in networks and what layers it is on. Then he wanted to explain in detail how Distance Vector works and how Link State works plus an example, then he moved on to IP, what else do you need to enter on the PC apart from the IP address to load the network correctly? Correct answer Gateway and subnet mask, analyze what they are for, show with examples. Let's break down what NAT is for and how it works. How to solve the lack of IP addresses in the IPv4 protocol? | ||||||||||||||||||||||
22 | Didn't examine | 6S | Ošlejšek | 2016 | OSI model - ten jsem dal vpoho. Pote se ale zacal detailne ptat na L1 a L2 vrstvu. Chtel vedet protokoly z obou vrstev, pote jak funguje CSMA/CA, CSMA/CD, Aloha, Token Ring.. Tohle jsem do detailu vubec neznal, takze jsem dost varil z vody a moc jsem nevedel... | OSI model - I used it. But then he started to ask in detail about the L1 and L2 layer. He wanted to keep protocols from both layers, then how CSMA/CA, CSMA/CD, Aloha, Token Ring works.. I didn't know this in detail at all, so I was boiling a lot of water and didn't know much... | |||||||||||||||||||||
23 | Examined | 8S | Ošlejšek | 2016 | vcelku vpoho ptala se na ekonomicke paradigmata (orientace na produkty/sluzby)... Rozebirali jsme nejake veci z praxe. Spise takova diskuse/polemika nad vecmi nez zkouseni z temat otazky - je hodna. | She asked about economic paradigms (orientation on products/services)... We discussed some things from practice. Such a discussion/controversy over things rather than an examination of the topic of the question - is worthy. | |||||||||||||||||||||
24 | Interests in topic | 1M | Ráček | 2016 | pytal sa na PPP, coho je to skratka a ich definicia a potom na project planning a jeho jednotlive casti. | he asked about PPP, what is the abbreviation and their definition, and then about project planning and its individual parts. | |||||||||||||||||||||
25 | 1M | Ráček | 2016 | PPP, co se týče standardů. Srovnání IPMA, PMI, PRINCE2. Rozdíly program, portfolio, proces, projekt. Celkem za C. | PPP in terms of standards. Comparison of IPMA, PMI, PRINCE2. Differences program, portfolio, process, project. Total for C. | ||||||||||||||||||||||
26 | 1M | Ráček | 2016 | PPP, čo to je, expozícia rizík, analýza rizík. Tam sa pýtal na nejaký postup analýzy rizík pomocou akéhosi stromu. To myslím v materiáloch nemáme a nespomenul som si, čo by tým mohol myslieť, teda som trochu očil oči, že fuu a tak teda prešiel na sieťové diagramy, ganntov diagram, milestones, AOA / AON, výhody nevýhody. Zaujímavá informácia, že AOA má výhodu, že sa v ňom dobre zobrazuje milestone práve v tých Node-och, povedal Ráček | PPP, what it is, risk exposure, risk analysis. There he asked about some kind of risk analysis procedure using a kind of tree. I mean, we don't have that in the materials and I didn't remember what the team might think, so I opened my eyes a little, and then I went to network diagrams, Gannt diagram, milestones, AOA / AON, advantages and disadvantages. Interesting information that AOA has the advantage that it displays milestones well in those Nodes, said Ráček | ||||||||||||||||||||||
27 | New programmes (RSSS - Services, cca since 2022) | 1S | Ráček | 2016 | servisní systémy, vztahy Client, Provider, Target, všechno nakreslit. Typy servisních systémů a hlavně příklady něco jiného, než Interim Project. :-D trochu jsem se na tom zasekla. Ale dali mi A. | service systems, relationships Client, Provider, Target, draw everything. Types of service systems and especially examples of something other than Interim Project. :-D I'm a bit stuck on it. But they gave me an A. | |||||||||||||||||||||
28 | PA017 | PA018PV079PV157 | MV013 | PA152 | PA182PV215PV237PV271 | PA179 | PV203PV214 | PV206 | PA194 | PA116 | PA181 | PV207 | PA151PA159PA191 | PV241PV118PV028PV045PV242 | PV240PV216 | 8S | Švenda | 2016 | Alanýza rizik. Aha, řekl jsem si. Nevím jak ostatním, ale mě se to kompletně vykouřilo z hlavy. Začal jsem ale dobře, kde jsem mu popsal Aktiva, Zranitelná místa a prokousával se dál a dál. Chtěl vědět, jak to chápu. Proto se ze mě snažil dostávat i praktické příklady. Ve smyslu, pokud byl bych manažer divadla, jaká jsou pro mě akriva, a jak se je budu snažit ochránit. V koncextu objednávek, jsem řekl že aktivem může být údaj o počtu rezervací, a hrozba, že nám třeba někdo tato číal bude libovolně měnit. Nebylo to to co asi původně chtěl ale pak i s tímto souhlasil. Bavili jsme se i o expozici rizik a o ohodnocení. Jak bych například řešil nízké pravděpodobností riziko ale v velkoufinanční ztrátou. Tady jsem věděl. Pojištění. Pokynul hlavou. Motali jsme se ještě nějakou chvíli v oblasti analýza rizik a potom skončili. | Risk analysis. Ah, I thought. I don't know about others, but I was completely blown away. But I started well, where I described the Assets, Vulnerabilities and went on and on. He wanted to know how I understood it. That's why he tried to get practical examples from me. In the sense that if I were a theater manager, what are the acres for me, and how will I try to protect them. In the context of orders, I said that an asset can be information on the number of reservations, and the threat that, for example, someone will change these numbers at will. It was probably not what he originally wanted, but then he agreed to this. We also talked about risk exposure and valuation. For example, how would I deal with a risk with low probability but with a large financial loss. Here I knew. Insurance. He nodded his head. We dabbled in risk analysis for a while and then we were done. | |||||||
29 | Examiner | 1C | 2C | 3C | 4C | 5C | 6C | 7C | 8C | 1SL | 2SL | 3SL | 4SL | 5SL | 6SL | 7SL | 8S | Švenda | 2016 | Digitální podpis, jak funguje, bezpečnost, proč využíváme symetrické šifrování. Rychlost je tam důležitá, ale to není jediné. Pak jsme přešli k zabezpečení dat na disku, v cloudu a tak obecně. Snažil se ptát kolikrát tak základně, až mě to zmátlo a nevěděl jsem vlastně, co chce slyšet :) Jeho část zabrala větší část zkoušení. | Digital signature, how it works, security, why we use symmetric encryption. Speed is important there, but it's not the only thing. Then we moved on to securing data on disk, in the cloud, and so on in general. He tried to ask so many times so basic that it confused me and I didn't really know what he wanted to hear :) His part took up most of the rehearsal. | ||||||
30 | Ročkai | 2 | 8S | Švenda | 2016 | analyza rizik. Tam som spomenul zakladne pojmy ako hrozba, zranitelne miesta, aktiva, hodnoty, co je riziko. Ze existuje kvalitativna a kvantitativna analyza. Kto ju vykonava, nieco o bezpecnostnej politike. Spominal som o adresovani rizik co s nimi robit ake existuju strategie. Potom sa ma pytal tiez na male a velke firmy, ako casto sa vykonava atd. | risk analysis. There I mentioned basic concepts such as threat, vulnerabilities, assets, values, what is risk. There is qualitative and quantitative analysis. Who executes it, something about the security policy. I mentioned addressing risks, what to do with them, and what strategies exist. Then he also asked me about small and large companies, how often it is done, etc. | ||||||||||||||||||||
31 | Bártek | 2 | 8S | Švenda | 2016 | auntentizácia - teória a využitie v praxi, graf pretnutia false acceptance a false rejection, vyjadrenie acceptance v % v praxi, živosť | authentication - theory and use in practice, graph of false acceptance and false rejection, expression of acceptance in % in practice, liveliness | ||||||||||||||||||||
32 | Batko | 1 | 1S | Walletzký | 2016 | Service Paradigms - Chcel vediet tie 4 zakladne, ale ked som mu odpovedal na prvu (Service is the fundamental basis of exchange), tak povedal, ze unho je to za A, lebo som prvy clovek, co mu na to vedel odpovedat. | Service Paradigms - He wanted to know the 4 basics, but when I answered the first one (Service is the fundamental basis of exchange), he said that it was because of A, because I was the first person who knew how to answer it. | ||||||||||||||||||||
33 | Spurný | 1 | 1 | 1S | Walletzký | 2016 | Walletzky: Service system, mention-use principle. I was lost a bit in describing relationship from the point of mention-use principle among customer-provider-traget. | Walletzky: Service system, mention-use principle. I was lost a bit in describing the relationship from the point of mention-use principle among customer-provider-traget. | |||||||||||||||||||
34 | Walletzký | 1S | Walletzký | 2016 | Service Paradigms (chcel pocut tie 4 - Service is the fundamental basis of exchange, The customer is always a co-creator of the value, All social and economics actors are the resource integrators, Value is always uniquely and phenomenologically determined by the beneficiary) | Service Paradigms (he wanted to hear tie 4 - Service is the fundamental basis of exchange, The customer is always a co-creator of the value, All social and economics actors are the resource integrators, Value is always uniquely and phenomenologically determined by the beneficiary) | |||||||||||||||||||||
35 | Rebok | 1 | 1S | Walletzký | 2016 | Co je servisní systém, trojúhelník CPT. Zajímaly ho podrobně vztahy mention a use, jak se liší mention mezi C-P a P-T, proč mezi C-T není mention, příklady, detaily, víc nic... | What is a service system, CPT triangle. He was interested in details about mention and use relationships, how mention differs between C-P and P-T, why there is no mention between C-T, examples, details, nothing more... | ||||||||||||||||||||
36 | Řehák | 1 | 1S | Walletzký | 2016 | Moc času už nezbylo a tak se mě zeptal na klasický trojúhelník CPT, jaké tam jsou vztahy. Dále pak na rozdíly mezi GDL a SDL s vysvětlením a uvedením příkladu na notebooku. | There wasn't much time left, so he asked me about the classic CPT triangle, what are the relationships there. Next, the differences between GDL and SDL with an explanation and an example on a laptop. | ||||||||||||||||||||
37 | 1S | Walletzký | 2016 | servisné systémy, CPT, duálny systém, spolupracujúci systém, mention a use - zakresliť a na všetko príklady | service systems, CPT, dual system, cooperative system, mention a use - draw and on everything examples | ||||||||||||||||||||||
38 | 1S | Walletzký | 2016 | 2. otázka smerovala na servisný systém, popísať prvky, konkrétne príklady, špeciálne systémy (duálny, kooperujúci). Či môže byť servisný systém súčasťou iného systému. Čo môže byť provider, client, target (človek, technológia ...). Popísať vzťahy MENTION/USE a fungovanie servisného systému. | The 2nd question was directed to the service system, describe the elements, specific examples, special systems (dual, cooperative). Whether the service system can be part of another system. What can be provider, client, target (person, technology...). Describe the MENTION/USE relationships and the functioning of the service system. | ||||||||||||||||||||||
39 | 1S | Walletzký | 2016 | Nejdriv se ptal Walletzky na servisni system, musela jsem nakreslit vztah dodavatele, klienta a cile, kde je tam mention a use a co to presne znamena... obcas se mu nelibila presne moje formulace, ale plus minus jsem to popsala, akorat chtel ode me slyset presne, ze mention mezi poskytovatelem a cilem znamena, ze si poskytovatel naplanuje, co bude delat, coz jsem nevedela. | First he asked Walletzky about the service system, I had to draw the relationship between the supplier, the client and the target, where there is mention and use and what exactly it means... sometimes he didn't exactly like my wording, but plus or minus I described it, as much as he wanted to hear from me exactly, that the mention between the provider and the target means that the provider plans what it will do, which I didn't know. | ||||||||||||||||||||||
40 | 1S | Walletzký | 2016 | Pan Walletzký: produktové a servisní paradigma, value proposition. Trošku jsem se v tom zamotal a trvalo mi, než jsem řekl, co chtěl slyšet... :D | Mr. Walletzký: product and service paradigm, value proposition. I got a little confused and it took me a while to say what he wanted to hear... :D | ||||||||||||||||||||||
41 | 4M | Walletzký | 2016 | Následoval Walletzký a MbC. Mapování pyramidy vitality na pyramidu kultury. A přísahám, že to umím na zpamět, ale tam mi to vypadlo kompletně z hlavy. Zachránila mě moje mnemotechnická pomůcka ISHeMOD :D Pak jsme to nějak dali dohromady. Lezlo to ale ze mě jako z chlupaté deky. Následně jsme pyramidy použili do prostředí divadla. | Walletzký and MbC followed. Mapping the pyramid of vitality onto the pyramid of culture. And I swear I know it by heart, but then it completely slipped my mind. My mnemonic ISHeMOD saved me :D Then we somehow put it together. But it came off me like a furry blanket. Subsequently, we used the pyramids in the theater environment. | ||||||||||||||||||||||
42 | 4M | Walletzký | 2016 | teoria vitality a kde sa uplatnuje. Zacal som hovort o MbC...pri odpovedi, ze nase terajsie dosahovanie cielov by nemalo ovplyvnit dosahovanie cielov v buducnosti sa ma spytal na konkretny priklad...tak som zacal hovorit o tom ze na SVK je vysoka korupcia :D vtedy sa vsetci zacali smiat...tak som spomenul priklad ze ak teraz niekoho podplatime tak v buducnosti nam to moze pokazit meno (a nieco okolo toho) :D walletzky povedal, ze nad tym nikdy neuvazoval takto :D a ze to mozno v buducnosti prepoji teoriu vitality s korupciou :D potom som zacal hovorit jednotlive stupne pyramidy vitality...ku kazdej chcel vediet co sa tam robi a priklady z reality...a vzdy sa ma pytal na male a velke firmy a ze ci to ide uplatnit vsade a preco a stale sa pytal aj na zamestnancov atď. Dost vela detailov chcel vediet | the theory of vitality and where it is applied. I started talking about MbC... when I answered that our current achievement of goals should not affect the achievement of goals in the future, he asked me for a specific example... so I started talking about the fact that there is high corruption at SVK :D then everyone started laughing... so I mentioned the example that if we bribe someone now, it can spoil our name (and something related to it) in the future :D walletzky said that he would never think about it he didn't think like that :D and that maybe in the future I will connect the theory of vitality with corruption :D then I started talking about the individual levels of the pyramid of vitality...everyone wanted to know what was done there and examples from reality...and he always asked me about small and large companies and whether it was going to be applied everywhere and why and he kept asking about employees, etc. He wanted to know quite a lot of details | ||||||||||||||||||||||
43 | 4M | Walletzký | 2016 | 2. otázka byla na teorii vitality, nástroje teorie vitality, teorie omezení a provázání teorie vitality s teorií omezení. | The 2nd question was about the theory of vitality, the tools of the theory of vitality, the theory of limitations and the connection between the theory of vitality and the theory of limitations. | ||||||||||||||||||||||
44 | 4M | Walletzký | 2016 | podobe pyramidy vitality a pyramidy kultury. Tu nastal ale dalsi porod. Cely nateseny som totiz zacal rapotat to previazazanie a hned ma zastavil. Vravel som to totiz zle. Problem bol, ze som to mal naucene z tych materialov SZZ SSME 2015-2016. Do buducna, Stability sa nemapuje na "definiciu, orientaciu a motivaciu". Tu som to teda dost pokazil. Docela ma prekvapuje, ze ma za toto fakt nevyrazil. | forms of the pyramid of vitality and the pyramid of culture. But there was another birth. All excited, I started to mumble about the over-binding and he immediately stopped me. I said it wrong. The problem was that I had learned it from the SZZ SSME 2015-2016 materials. In the future, Stability does not map to "definition, orientation and motivation". So I messed up a lot here. I'm quite surprised that he didn't kick me out for this. | ||||||||||||||||||||||
45 | 4M | Walletzký | 2016 | Strategicke riadenie podla MbC - prisiel mi o nieco strohejsi, obcas ked som trepol tak sa zatvaril ze ho to az zabolelo :D lebo som obcas trosku viac tapal nez u predoslej otazky, povedal som iba par slov ku kazdej casti strategickeho ramca, chcel toho viac a doloval zo mna... nieco som logicky odvodil a nieco som ani nevedel ale nic az take vazne sa nedialo... presli sme na strategicke kontinuum, opat chcel trochu viac podrobnosti nez som si ja pamatal, ale asi nic co nie je v materialoch... | Strategic management according to MbC - he seemed a bit stricter, sometimes when I trembled he pretended that it hurt him :D because sometimes I fumbled a bit more than with the previous question, I only said a few words about each part of the strategic framework, he wanted more and mined me... I deduced something logically and I didn't even know anything but nothing really important happened... we moved on to the strategic continuum, again he wanted a little more details than I remembered, but probably nothing that is not in the materials... | ||||||||||||||||||||||
46 | 7S | Batko | 2017 | Databaze - zaklad - ako to vyzera (tabulky, atributy, zaznamy), kluce (kandidatny, superkluc, primarny) plus relacna algebra (kartezsky sucin, selekcia, projekcia). Ja som tam este kreslil ERD. | Database - foundation - what it looks like (tables, attributes, records), keys (candidate, superkey, primary) plus relational algebra (Cartesian sum, selection, projection). I used to draw the ERD there. | ||||||||||||||||||||||
47 | 1M | Bühnová | 2017 | Project management - WBS, GANT, sitovy diagramy, PERT, CPM, rizika (treba ubytek zdroju - lidi, fyzicke zdroje,...). U gantovyho modelu nemusi vsechny aktivity navazovat prave kvuli rizeni rizik, protoze pocitam, ze aktivita, ktera nenavazuje, tak nezacne v presne danej kvuli tomu, ze predchozi aktivita ma nejasny konec (muze se zpozdit a pak by zdroje dalsi aktivity zbytecne cekali - neco v tom smyslu). | Project management - WBS, GANT, grid diagrams, PERT, CPM, risks (need to reduce resources - people, physical resources,...). In the case of the Gantt model, not all activities have to be connected precisely for the sake of risk management, because I feel that an activity that does not connect will not start exactly because the previous activity has an unclear end (it can be delayed and then the resources would needlessly wait for the next activity - something to that effect). | ||||||||||||||||||||||
48 | New programmes (RSSS - Cybersecurity management, cca since 2022), see above for questions from common core | 1S | Bühnová | 2017 | Service Systems, vztahy provider - client, obecně product dominant logic vs. service dominant logic. Tady to bylo víc v pohodě. Nechala mě obecně mluvit, když jsem šel s něčím víc do hloubky, tak z vlastní vůle. Na začátku chtěla říct, co tvoří servisní systémy, pak jsem nakreslil trojúhelník provider - client - target a mluvil o mention / use. | Service Systems, provider - client relationships, generally product dominant logic vs. service dominant logic. It was more comfortable here. She generally let me talk when I went deeper with something, of my own free will. At the beginning, she wanted to say what constitutes service systems, then I drew the triangle provider - client - target and talked about mention / use. | |||||||||||||||||||||
49 | IV054PV079 | PV079 | PV079 | PV204PV079PA197 | PA151PA159PA191 | PrF:BVV03K, BVV14K, BI301K | 3M | Bühnová | 2017 | ITIL a vztiahnut to na firmu z Interimu. Chcela pocut aj to, kto je v tej firme za jednotlive casti zodpovedny. | ITIL and relate it to the company from Interim. She also wanted to hear who is responsible for individual parts in that company. | ||||||||||||||||
50 | Examiner | 1CB | 2CB | 3CB | 4CB | 5CB | 6CB | 3M | Bühnová | 2017 | #VALUE! | ||||||||||||||||
51 | 5M | Bühnová | 2017 | na závěr marketingový mix (porovnání 4P a odpovídajících C ze 7C). | and finally the marketing mix (comparing the 4Ps and the corresponding Cs from the 7Cs). | ||||||||||||||||||||||
52 | 0 | 5S | Bühnová | 2017 | Bez problémů, pokud se člověk alespoň trochu orientuje. Nechtěla moc detailů, spíše obecný přehled. | No problems, if you at least get your bearings. She didn't want a lot of detail, rather a general overview. | |||||||||||||||||||||
53 | 5S | Dohnal | 2017 | Distribuovane systemy. Presli sme v podstate vsetko z tejto temy a potom sa zameral na skalovatelnost na vysoku dostupnost, pricom to chcel vsetko nad databazami. Jo a este to potom Dohnal prepojil na RAID a k tomu chcel hlavne principy a vyuzitie, kedy pouzijem mirroring a kedy stripping... | Distributed systems. We covered basically everything from this topic and then he focused on scalability and high availability, and he wanted it all over databases. Oh, and then Dohnal connected it to RAID and for that he mainly wanted the principles and usage of when to use mirroring and when to strip... | ||||||||||||||||||||||
54 | 8S | Dohnal | 2017 | otázky vztahoval k diplomce, ptal se na autentizaci a autorizaci (tj jak se tohle bude chovat vzhledem k systému, co jsem navrhovala), rozdíl, jak chránit heslo, jak heslo ukládat, jaké jsou způsoby autentizace, autorizace, proč, zakončil sql injection | he related the questions to the graduate, he asked about authentication and authorization (ie how this will behave in relation to the system I proposed), the difference, how to protect the password, how to store the password, what are the methods of authentication, authorization, why, he finished with sql injection | ||||||||||||||||||||||
55 | 7S | Matyska | 2017 | relační databáze | relational database | ||||||||||||||||||||||
56 | 3S | Ošlejšek | 2017 | Use case diagram, obecne a vsechno kolem, actory, typy vazeb... jak diagramovy tak textovy, docela me zarazil na extendu, poradne nastudovat radsi co to znamena, za jakych pripadech se pouziva, nestaci odpoved ze rozsiruje fukcnost jejiz pouziti je na uvazeni uzivatele. | Use case diagram, in general and everything around, actors, types of connections... both diagrammatic and textual, I was quite taken aback by the extension, it is advisable to study what it means, in what cases it is used, it is not enough to answer that it extends the functionality, but to use them is at the discretion of the user. | ||||||||||||||||||||||
57 | 3S | Ošlejšek | 2017 | stavovy diagram - jednotlivy komponenty ukazany naprikadech. Ptal se hodne,kdy se prechazi se stavu do stavu, na udalosti, akce apod. Potom na determinismus, jak se projevuje, a dedicnost (podstavy - doatani se z libovolneho podstavu mimo rodicovsky stav). aktivity diagram - mluvil jsem dostatecne sam | state diagram - individual components shown in examples. He asked a lot about when they transition from state to state, about events, actions, etc. Then about determinism, how it manifests itself, and heredity (bases - getting from any base outside of the parental state). activity diagram - I've talked enough myself | ||||||||||||||||||||||
58 | 3S | Ošlejšek | 2017 | Use Case diagram. Přiznám se, že jsem to tahal hodně z paty a věděl jenom ty obecnější věci, takže tady mě (právem) hodně vydusil. Začal jsem nakreslením jednoduchého diagramu, pak se mě ptal na typy aktérů (uživatelé, systémy, časované akce). Já si od sebe vzpomněl jen na uživatele, na zbytek mě musel dlouho navádět. Dál chtěl rozvést, jak se dokumentují jednotlivé use cases. To jsem jenom hodně obecně popsal a moc spokojený asi nebyl. Pořád se vyptával víc do hloubky, ale nevěděl jsem, co by chtěl slyšet. Pak se ptal jaký existují druhy vazeb. Řekl jsem generalizaci, pak include a extend. U include a extend šel zase víc do hloubky (k čemu to je, jak se to používá). U extend chtěl slyšet o extension point, což ze mě nedostal. | Use Case diagram. I'll admit that I was dragging my feet a lot and only knew the more general stuff, so he (rightly) suffocated me a lot here. I started by drawing a simple diagram, then he asked me about the types of actors (users, systems, timed actions). I only remembered the user, he had to guide me for a long time about the rest. He further wanted to elaborate on how individual use cases are documented. I just described it in a very general way and I guess he wasn't very satisfied. He kept asking more in depth, but I didn't know what he wanted to hear. Then he asked what types of bonds exist. I said generalize, then include and extend. With include and extend, he again went more in depth (what it is for, how it is used). U extend wanted to hear about extension point, which he didn't get from me. | ||||||||||||||||||||||
59 | 7S | Ošlejšek | 2017 | Databaze - Indexovani - husty, ridky index. Popsal jsem indexovani a pak husty a ridky index, ktery jsem i kreslil (kresleni doporucuju, bere to cas a pak uz se mozna nestihnou zeptat na nejaky podly veci 😄). Pak se ptal, jestli znam jeste jiny indexy, tak jsem rekl, B-stromy a popisoval a kreslil spolu s B+ stromama. Ani jsem myslim nerekl vsechny ty podminky urcujici B+ strom. Potom hodne resil ukladani dat pres B+ stromy, jejich vyhody, nevyhody atd. U toho chtel hlavne slyset, ze arita je podle velikosti bloku na disku. Potom se zeptal Dohnal na pouziti indexu s sql dotazama - ze pro dotaz ...WHERE A:5 > 3 nejde pouzit, protoze to neni cisty vyraz (nebo tak nejak), ale pro WHERE A > 5 uz jde pouzit. | Database - Indexing - dense, sparse index. I described the indexing and then the dense and sparse index, which I also drew (I recommend drawing, it takes time and then they might not have time to ask about some mean things 😄). Then he asked if I knew other indexes, so I said B-trees and described and drew together with B+ trees. I don't even think I said all the conditions determining the B+ tree. Then he thoroughly discussed the storage of data via B+ trees, their advantages, disadvantages, etc. He mainly wanted to hear that the arita is based on the size of the block on the disk. Then Dohnal asked about the use of the index with sql queries - that it cannot be used for the query ...WHERE A:5 > 3, because it is not a pure expression (or something like that), but it can be used for WHERE A > 5. | ||||||||||||||||||||||
60 | 8S | Ošlejšek | 2017 | digitalny podpis, hashovanie, PKI, porovnanie asymetricke a symetricke. Par krat som dost zatapal, hlavne na detailnych otazkach pana Oslejska, obcas mi ich musel Matyska preformulovat. A zadrbal som, ze hashovacia funkcia je "random", za co sa mi budu smiat do konca zivota. | digital signature, hashing, PKI, asymmetrical and symmetrical comparison. A couple of times I was quite confused, especially on Mr. Oslejsko's detailed questions, sometimes Matyska had to reformulate them for me. And I guessed that the hashing function is "random", which will make me laugh for the rest of my life. | ||||||||||||||||||||||
61 | 1M | Ráček | 2017 | sietove diagramy, vela kreslenia. Prvy krat v zivote po mne niekto chcel nieco ine ako F->S, dost komplexne sme to prechadzali a pocitali CP. Potom este doplnujuce otazky na PERT a gantt, inak na pohodu. | network diagrams, lots of drawings. For the first time in my life, someone wanted something other than F->S from me, we went through it quite complexly and calculated CP. Then additional questions on PERT and gantt, otherwise feel free. | ||||||||||||||||||||||
62 | 1M | Ráček | 2017 | Typy modelu zivotniho cyklu, chtel to znat od zacatku na typech projektu kde bych zvolil jaky typ, za jakych okolnosti atd. Pote SCRUM a RUP metodu kde u RUP chtel slyset presne nazvy jednotlivych etap. Rozdil mezi iterativnim a inkrementalnim cyklem a vse kolem tohodle. V teto otazce jsem se dost machal a zdimal, ale Racek pomahal jak mohl a kde jsem se chytal stebla tak do toho tematu presel. Nakonci rekl, ze uz mu to stacilo, ze ma predstavu o znamce, coz me zarazilo protoze jsem se topil jak kocka a citil jsem z jeho tonu ze za F. | Types of the life cycle model, he wanted to know from the beginning about the types of projects where I would choose which type, under what circumstances, etc. Then SCRUM and the RUP method where he wanted to hear the exact names of the individual stages in RUP. He distinguished between an iterative and an incremental cycle and everything around that. In this question, I wavered a lot, but Seagull helped as much as he could, and when I was clutching at straws, he moved on to the topic. Finally he said that he had had enough, that he had an idea of the brand, which surprised me because I was drowning like a cube and I could tell from his tone that he was behind F. | ||||||||||||||||||||||
63 | 3S | Ráček | 2017 | kvalita SW (to co chce z přednášek | SW quality (what he wants from lectures | ||||||||||||||||||||||
64 | 1S | Walletzký | 2017 | 2017 | 2017 | ||||||||||||||||||||||
65 | 2S | Walletzký | 2017 | diamanty, jaké jsou, k čemu, rozdíl mezi see a recognize, jaké tam jsou vazby (nakreslit a vysvětlit) | diamonds, what they are, what they are for, the difference between see and recognize, what connections are there (draw and explain) | ||||||||||||||||||||||
66 | 5M | Walletzký | 2017 | Jako druhý se ptal Walletzký na marketingové mixy a rozdíl mezi produktovým a service-oriented. Chtěl oba porovnat položku po položce a dával mi na vysvětlení příklady, na kterých se to celkem těžce vysvětlovalo. Hodně jsme se zasekli na Price / Cost. Doporučuju si to pořádně nastudovat. | Walletzký was the second to ask about marketing mixes and the difference between product-oriented and service-oriented. He wanted to compare the two item by item and gave me examples that were quite difficult to explain. We got stuck on Price / Cost a lot. I recommend studying it thoroughly. | ||||||||||||||||||||||
67 | 8S | Bartek | 2018 | Biometria, jej typy, ako sa da zneuzit, aka je hlavna nevyhoda, ako sa biometricke systemy brania podvodom, modalita biometrickych systemov a zvysenie bezpecnosti, biometria ako podpora beznych zabezpecovacich metod. (To som vsetko pekne odsypal) | Biometrics, its types, how it can be misused, what is the main disadvantage, how biometric systems are used against fraud, the modality of biometric systems and increased security, biometrics as a support for non-existent security methods. (I poured it all out nicely) | ||||||||||||||||||||||
68 | 4S | Batko | 2018 | Architektury PC, ich vyhody nevyhody, ako by som charakterizoval architekturu a naco su nam vobec | PC architectures, their advantages and disadvantages, how I would characterize the architecture and why we need them at all | ||||||||||||||||||||||
69 | 4S | Batko | 2018 | SOA, zakladne principy, priklad na co sa pouziva, potom co je ESB a na co je to dobre. | SOA, basic principles, an example of what it is used for, then what ESB is and what it is good for. | ||||||||||||||||||||||
70 | 1M | Bühnová | 2018 | Project Management (obecně, diagramy, rizika) | Project Management (general, diagrams, risks) | ||||||||||||||||||||||
71 | 2M | Bühnová | 2018 | BPM, všeobecne plus nakresliť jednoduchý proces ako príklad z diplomky, nevedela som nejaké konkrétne značky, ale bolo jej to dosť jedno, potom sa ma ešte spýtala nech jej vymenujem diagramy, ktoré sú v UML | BPM, in general plus drawing a simple process as an example from the diploma, I didn't know any specific brands, but he didn't care enough, then she asked me to name the diagrams that are in UML | ||||||||||||||||||||||
72 | 5S | Bühnová | 2018 | distribuovane systemy zaklady, ich vyhody nevyhody (spolahlivost, kvalita, bezpecnost), skalovatelnost (horiz./vert.) | distributed systems basics, their advantages disadvantages (reliability, quality, security), scalability (horiz./vert.) | ||||||||||||||||||||||
73 | 4S | Dohnal | 2018 | MVC, SOA - popsat, proč se to dělá, praktická aplikace apod. | MVC, SOA - describe why it is done, practical application, etc. | ||||||||||||||||||||||
74 | 5S | Dohnal | 2018 | distribuovane systemy, vsetko mozne z tejto temy, charakteriskiky, porovnat cetralizovany a distribuovany, data sharding, architektury, skalovatelnost... | distributed systems, everything possible from this topic, characteristics, compare centralized and distributed, data sharding, architectures, scalability... | ||||||||||||||||||||||
75 | 6S | Dohnal | 2018 | siete, iso osi, vsetky vrstvy, potom sa pytal co vsetko dostanem ked sa pripojim k sieti | networks, iso axes, all layers, then he asked what all I get when I connect to the network | ||||||||||||||||||||||
76 | 6S | Dohnal | 2018 | OSI vrstvy, směrování, IPv4, UDP, TCP | OSI layers, routing, IPv4, UDP, TCP | ||||||||||||||||||||||
77 | 8S | Dohnal | 2018 | asymetricka kryptografie, jak funguje, jestli spolu nejak klice souvisi a da se teda pouzit i opacne (narazel na digitalni podpis), potom co je to hasovaci funkce, vlastnosti, co je kolize a proc se nepodpisuje cely soubor,, pak jestli se napr. v tomssl pouziva jen asymetricka nebo i symetricka a proc... proste zaklady otazky navazovaly na to co jsem rikaL. princip defie helman ze je stejny jako v asymetricke kryptografii s klicema | asymmetric cryptography, how it works, if the keys are related to each other and can therefore be used the other way around (he came across a digital signature), then what is the extinguishing function, properties, what is a collision and why is the entire file not signed, then if, for example, in tomssl only asymmetric or symmetric is used and why... just the basics of the questions connected with what I said. the principle of defie helman is the same as in asymmetric cryptography with keys | ||||||||||||||||||||||
78 | 8S | Dohnal | 2018 | autentizace, autorizace, acl, pak se ptal ještě na ukládání hesel přes co sme došli k hashování (ptal se na vlastnosti), zabrousili jsme i do solení hesel | authentication, authorization, acl, then he also asked about saving passwords, through which we arrived at hashing (he asked about properties), we also honed in on salting passwords | ||||||||||||||||||||||
79 | 3M | Pitner | 2018 | TSM, ITIL, cloudy, outsourcing - popsat, víceméně povrchně, výhody, nevýhody, co kdy v reálu zvolit apod. | TSM, ITIL, clouds, outsourcing - describe, more or less superficially, advantages, disadvantages, what to choose in reality, etc. | ||||||||||||||||||||||
80 | 7M | Pitner | 2018 | komunikace (rekl jsem jen nejakou basic teorii a ze feedback je dulezity), active listening (taky staci zaklad, proc je to active - prikyvujes atp.), rizeni konfliktu jsem rekl jen par vet z mbc | communication (I only said some basic theory and that feedback is important), active listening (the basics are also enough, why is it active - you nod, etc.), conflict management I only said a few sentences from mbc | ||||||||||||||||||||||
81 | 8S | Pitner | 2018 | Povedal ze mam popisat autorizaciu a autentizaciu, tak som popisal rozdiely, ake typy autentizacie su, vyhody a nevyhody. Potom povedal ze by sa spytal este nieco ku kryptografii (v duchu si vravim do pice to som sa neucil), ale pozrel na hodinky a poslal ma za dvere. | He said that I should describe authorization and authentication, so I described the differences, what types of authentication there are, advantages and disadvantages. Then he said that he would ask something about cryptography (I tell myself to myself that I didn't study), but he looked at his watch and sent me out the door. | ||||||||||||||||||||||
82 | 1M | Ráček | 2018 | Kvalita SW, trojuholnik kvality, ako by som meral kvalitu, uviest priklad metriky udrzatelnosti kvality + testovanie SW, v ktorej etape sa pouziva aky typ testovania a naco su nam dobre, popisat systemovy test a co obnasa + integracny test ako by som ho implementoval a co by bolo mojim cielom. Ako prebieha nejaka komisionalna kontrola pocas vyvoja z kto sa jej ucastni a na co sa zameriavaju. Cyklometricka zlozitost algoritmu, co to je, kedy sa pouziva | SW quality, the quality triangle, how I would measure quality, give an example of a quality sustainability metric + SW testing, at which stage what type of testing is used and why they are good for us, describe a system test and what it entails + an integration test, how I would implement it and what would be my goal. How does a commission control during development take place, who participates in it and what they focus on. Cyclometric algorithm complexity, what it is, when it is used | ||||||||||||||||||||||
83 | 2M | Ráček | 2018 | BPMN notacia, vsetky typy objektov nakreslit a popisat (Flow, Connecting, Artifacts, Swimlanes, Data) - nic komplikovane, akurat pozor na to, ze sequence flow sipka v BPMN neprenasa data :D Na tom ma nachytal trochu, ale prediskutovali sme to, ze vlastne v ramci jedneho procesu vsetky tie aktivity maju pristup k spolocnym datam, ale priamo po tych sipkach sa ziadne data neprenasaju a bolo to v pohode. | BPMN notation, draw and describe all types of objects (Flow, Connecting, Artifacts, Swimlanes, Data) - nothing complicated, just be careful that the sequence flow arrow in BPMN does not transfer data :D He caught me a bit on that, but we discussed the fact that actually within one process all those activities have access to common data, but no data is transferred directly after those arrows and it was fine. | ||||||||||||||||||||||
84 | 2M | Ráček | 2018 | BPM, povedat co vsetko o tom viem. Hovoril som o roznych leveloch, potom sa pytal na BPMN, rozny typy taskov, bran, artefaktov, popisat swimlanes. Moc som nevedel, nakoniec znechutene povedal Pitnerovi nech sa pyta on. | BPM, tell me everything I know about it. I talked about different levels, then he asked about BPMN, different types of tasks, gates, artifacts, describe swimlanes. I didn't know much, finally disgustedly told Pitner to let him ask. | ||||||||||||||||||||||
85 | 1M | Šimková | 2018 | Gantt, Milníky, nejak to nakresliť na tabuľu, CPM, PERT, PPP | Gantt, Milestones, how to draw it on the board, CPM, PERT, PPP | ||||||||||||||||||||||
86 | 4M | Šimková | 2018 | teória vitality, pyramída vitality, pyramída kultúry a všetko s tým spojené | the theory of vitality, the pyramid of vitality, the pyramid of culture and everything connected with it | ||||||||||||||||||||||
87 | 6M | Šimková | 2018 | ROI, ROA, ROS, zlaté bilančné pravidlo a ich použitie v praxi, Matyska: to isté ale aplikovanie na diplomku | ROI, ROA, ROS, the golden balance rule and their use in practice, Matyska: the same but applying to the diploma | ||||||||||||||||||||||
88 | 1S | Walletzký | 2018 | asymetricka informacia, moralny hazard, informacny gap, aukcie (prvej, druhej ceny) | asymmetric information, moral hazard, information gap, auctions (first, second prizes) | ||||||||||||||||||||||
89 | 1S | Walletzký | 2018 | Service System, Client, Target, Provider, vzťahy, Mention Use + dať príklady z diplomky | Service System, Client, Target, Provider, relationships, Mention Use + give examples from the diploma | ||||||||||||||||||||||
90 | 1S | Walletzký | 2018 | SDL, Servisny system, kooperativny a dualny system, namapovat ich (vymysliet priklady) na moju diplomku. SDL chel uplne presne definicie paradigmatov (exchange v prvom vraj nie ej vymena, ale zamena). (sice najlahsia otazka, ale 6 IQ som mal pred tou komisiou a nevedel som ako sa volam...) | SDL, Service system, cooperative and dual system, map them (invent examples) on my diploma. SDL wanted a very precise definition of paradigms (exchange in the first place is not exchange, but exchange). (admittedly the easiest question, but I had an IQ of 6 before the commission and I didn't know my name...) | ||||||||||||||||||||||
91 | 1S | Walletzký | 2018 | SDL vs. PDL, rozdíly | SDL vs. PDL, differences | ||||||||||||||||||||||
92 | 1S | Walletzký | 2018 | PDL vs. SDL + Service system, čo je dosť ľahká otázka, ale snažil sa zo mňa ťahať konkrétne slová z poučiek | PDL vs. SDL + Service system, which is quite an easy question, but he tried to extract specific words from the tutorials | ||||||||||||||||||||||
93 | 2S | Walletzký | 2018 | diamanty (aspon prve dva SEE a MENTION) vysvetlit pripadne popisat, canvas vysvetlit popisat + nakreslit, rozdiel medzi canvas a lean canvas, asymetricke informace (na vsetko priklad), moral hazard | diamonds (at least the first two SEE and MENTION) explain or describe, canvas explain describe + draw, difference between canvas and lean canvas, asymmetric information (example for everything), moral hazard | ||||||||||||||||||||||
94 | 2S | Walletzký | 2018 | Business Lean Canvas a aplikovanie na diplomku | Business Lean Canvas and application to diploma | ||||||||||||||||||||||
95 | 4M | Walletzký | 2018 | MbC, teorie vitality, pyramida vitality - popis jednotlivých stupňů a napojení na pyramidu kultury, bavili jsme se asi 15 minut, když jsem něco nevěděl tak mě navedl | MbC, theory of vitality, pyramid of vitality - description of individual levels and connection to the pyramid of culture, we talked for about 15 minutes, when I didn't know something, he guided me | ||||||||||||||||||||||
96 | 6M | Walletzký | 2018 | ekonomicke ukazatele (ROI,ROA atd.), zlozenie aktiv a pasiv, na co su, break even point, odpisy, dane - priklad na priamu a nepriamu... | economic indicators (ROI, ROA, etc.), composition of assets and liabilities, what they are for, break even point, depreciation, taxes - example of direct and indirect... | ||||||||||||||||||||||
97 | 8S | Walletzký | 2018 | Digitální podpis, u digitálního podpisu se ptal na kauzu s občankami na slovensku | Digital signature, with regard to digital signature, he asked about the case with female citizens in Slovakia | ||||||||||||||||||||||
98 | 8S | Walletzký | 2018 | Digitální podpis | Digital signature | ||||||||||||||||||||||
99 | 8S | Zlatuška | 2018 | Zlatuška se ptal na bezpečnost, jestli jsem schopen udržet privátní klíč v tajnosti, když jsou zranitelné i procesory (spectre meltdown) | Zlatuska asked about security, if I am able to keep the private key secret when processors are also vulnerable (specter meltdown) | ||||||||||||||||||||||
100 | 7S | Bartek | 2019 | relacna DB, ako sa ukladaju data, pojmy, relacia matematicky, mnoziny matematicky + tie veci vysvetlit vzhladom na tabulky, PK, CK, vztahy, transakcia | relational DB, how data is stored, concepts, relations mathematically, sets mathematically + explain these things with respect to tables, PK, CK, relations, transaction |