| Language of instruction : English |
|
Sequentiality
|
| |
|
No sequentiality
|
| Degree programme | | Study hours | Credits | P2 SBU | P2 SP | 2nd Chance Exam1 | Tolerance2 | Final grade3 | |
 | Master of Software Systems Engineering Technology | 2-yearly optional (next academic year) | 108 | 4,0 | 108 | 4,0 | Yes | Yes | Numerical |  |
|
| | | Learning outcomes |
- EC
| EC1 – The Master of Software Engineering Technology can communicate adequately, cooperate effectively, and take into account the economic, ethical, social and/or international context and (s)he is aware of the impact on the environment in all aspects of his/her professional thought-process and agency. (S)he displays an appropriate engineering attitude, including continuous attention to the development of his/her professional competencies --. [people, data literacy and essential software skills]. | | | - DC
| DC-M12 - shows a suitable engineering attitude. | - EC
| EC2 - The Master of Software Engineering Technology masters the necessary sets of knowledge and skills regarding the design of integrated, resilient software systems and can creatively conceive, plan and implement them as an integrated part of a series of methodologically ordered actions within multidisciplinary projects with a significant research and/or innovation component. [systems thinking] | | | - DC
| DC-M1 - has knowledge of the basic concepts, structures and coherence. | | | - DC
| DC-M2 - has insight in the basic concepts and methods. | | | - DC
| DC-M4 - can gather, measure or obtain information and refer to it correctly. | | | - DC
| DC-M5 - can analyze problems, logically structure and interpret them. | | | - DC
| DC-M6 - can select methods and make calculated choices to solve problems or design solutions. | | | - DC
| DC-M8 - can evaluate knowledge and skills critically to adjust own reasoning and course of action accordingly.
| - EC
| EC3 - The Master of Software Engineering Technology has advanced knowledge and understanding of the principles and applications of software engineering, including software development processes, software architectures and the software life cycle, and can apply them, with an understanding of current technological developments, in complex and practice-oriented problem domains. [software engineering] | | | - DC
| DC-M5 - can analyze problems, logically structure and interpret them. | | | - DC
| DC-M8 - can evaluate knowledge and skills critically to adjust own reasoning and course of action accordingly.
| - EC
| EC4 - The Master of Software Engineering Technology has advanced knowledge and understanding of principles and applications of contemporary wireless and mobile communication networks, and in this domain, (s)he can autonomously initiate, plan, critically analyse and solve problems in a well-founded manner with an eye for data acquisition and implementation, and with the help of simulation techniques or advanced tools. [connected] | | | - DC
| DC-M1 - has knowledge of the basic concepts, structures and coherence.
| | | - DC
| DC-M2 - has insight in the basic concepts and methods.
| | | - DC
| DC-M4 - can gather, measure or obtain information and refer to it correctly. | | | - DC
| DC-M5 - can analyze problems, logically structure and interpret them. | | | - DC
| DC-M6 - can select methods and make calculated choices to solve problems or design solutions.
| | | - DC
| DC-M8 - can evaluate knowledge and skills critically to adjust own reasoning and course of action accordingly.
| - EC
| EC6 - The Master of Software Engineering Technology masters the necessary sets of specialised knowledge and skills regarding generic abstraction techniques such as virtualization and containerization in order to utilise the underlying hardware and software systems in a secure, protected, and efficient way. [virtual world] | | | - DC
| DC-M4 - can gather, measure or obtain information and refer to it correctly.
| | | - DC
| DC-M5 - can analyze problems, logically structure and interpret them.
|
|
| | EC = learning outcomes DC = partial outcomes BC = evaluation criteria |
|
|
This course gives an insight in the overal efficiency of programs by not only focussing on the efficiency, both in time and in space, of individual components but also in how it is influenced by the communication between different modules on a single computer or through the netwerk taking into account diverse factors such as cost of virtualisation, connectivitity, latency, network protocols and architectures and translations between different technologies, stacks and/or frameworks.
|
|
|
Period 2 Credits 4,00
| Evaluation method | |
|
| Written evaluaton during teaching periode | 25 % |
|
| Transfer of partial marks within the academic year | ✔ |
|
| Conditions transfer of partial marks within the academic year | at least 12/20 |
|
|
|
|
|
|
|
|
|
|
|
| Written exam | 75 % |
|
| Transfer of partial marks within the academic year | ✔ |
|
| Conditions transfer of partial marks within the academic year | at least 10/20 |
|
|
|
|
|
|
|
|
|
|
|
Second examination period
| Evaluation second examination opportunity different from first examination opprt | |
|
|
|
| Compulsory course material |
| |
All study material will be made available through Toledo |
|
|
|
|
|
1 examination regulations art.1.3, section 4. |
| 2 examination regulations art.4.7, section 2. |
3 examination regulations art.2.2, section 3.
|
| Legend |
| SBU : course load | SP : ECTS | N : Dutch | E : English |
|