| Language of instruction : English |
|
Sequentiality
|
| |
|
No sequentiality
|
| Degree programme | | Study hours | Credits | P2 SBU | P2 SP | 2nd Chance Exam1 | Tolerance2 | Final grade3 | |
 | 3rd year Bachelor of Engineering Technology - Software Systems Engineering Technology | Compulsory | 135 | 5,0 | 135 | 5,0 | Yes | Yes | Numerical |  |
|
| | | Learning outcomes |
- EC
| EC2 - The holder of the degree possesses general scientific and discipline-related engineering-technical insight in the basic concepts, methods, conceptual frameworks and interdependent relations of the specific domain. | | | - DC
| EA-INF 2.1 The student understands why it is necessary to use appropriate design principles and architectures in the design and development of software. | | | | - BC
| The student understands the interactions and technicalities of the different components of an integrated systems and how it influences the process of software engineering. | | | - DC
| EA-INF 2.2 The student has insight into the different networks and network techniques. | | | | - BC
| The student understands the impact of the network on an integrated system, in designing the systems, the software and on the reliability and performance of the final system. | | | - DC
| 2.11 The student has insight into the key aspects of research methodology and project-based working. | | | | - BC
| The student understands the need of project management and team working for the successful realization of a project. | - EC
| EC3 - The holder of the degree is able to recognize problems independently and can take initiative to plan activities and perform accordingly. | | | - DC
| 3.2 The student can plan a technical-scientific project in a structured manner. | | | | - BC
| The student has the ability to plan and execute the various stages of a project. | - EC
| EC4 - The holder of the degree can gather and obtain relevant scientific and/or technical information and/or he/she can measure the necessary information efficiently and conscientiously. Additionally, he/she can make correct references to information. | | | - DC
| 4.1 The student can look up scientific and/or technical information in a goal-oriented manner. | | | | - BC
| The student is fluent in researching, understanding and using the documentation of the used software, higher-level programming languages, APIs and the sort. | - EC
| EC5 - The holder of the degree can analyse unknown, domain-specific problems, subdivide them, structure them logically, determine the preconditions and interpret the data scientifically. | | | - DC
| EA-INF 5.1 The student can for a specific problem or application, analyse in which ways the software can be designed and built and can weigh alternatives based on relevant criteria. | | | | - BC
| The student understands how the data pipeline of an integrated systems functions and is able to explain its behavior. | | | | - BC
| The student can analyse the level of abstraction at which certain responsabilities should be handled of. | - EC
| EC6 - The holder of the degree can select and use adequate solution methods to solve unknown, domain-specific problems and can work methodologically and make solid design choices. | | | - DC
| 6.7 The student is able to make a modular and maintainable design of software. | | | | - BC
| The student is capable of designing a distributed integrated system with well-specified responsabilities for each of the distributed components. | | | | - BC
| The student can solve a problem at different levels of abstraction and with programming languages with different levels of expressivity. | - EC
| EC7 - The holder of the degree can use the selected methods and tools innovatively to systematically implement domain-specific solutions and designs while being aware of practical and economic conditions and company-related implications. | | | - DC
| 7.2 The student can use technical aids such as calculators, measuring devices and software. | | | | - BC
| The student knows how to install and use advanced software such as (cross) compilers, assemblers, remote deployment tools, kernels and Web browsers. | | | - DC
| 7.3 The student can write correct and qualitative code using an appropriate development, testing and maintenance strategy. | | | | - BC
| The student can develop software components in the programming language(s) that are best suited for the required level of abstraction in the concrete component and hardware on which the software component must run. | - EC
| EC8 - The holder of the degree can interpret (incomplete) results, can deal with uncertainties and constraints and can evaluate knowledge and skills critically to adjust own reasoning and course of action accordingly. | | | - DC
| 8.2 The student can reflect critically on a technical-scientific project. | | | | - BC
| The student can analyse the nature of the problem whenever an incident occurs in an integrated system. | | | | - BC
| The student can analyse and improve the performance of an integrated system based on test and measurement results. | - EC
| EC9 - The holder of the degree can communicate with colleagues in oral and in written form (including in a graphical way) about domain-specific aspects in suited language making use of apt terminology. | | | - DC
| 9.1 The student is able to communicate in writing in a correct, structured and appropriate manner in languages relevant to their field of study.
| | | | - BC
| The student should be able to produce documentation for the various phases of the project. | | | - DC
| 9.2 The student can communicate orally in a correct, structured and appropriate way in languages relevant to his field of study. | | | | - BC
| The student should be able do discuss the design choices for their project. | - EC
| EC12 - The holder of the degree can act application-oriented and goal-driven and can act academically and professionally with the necessary perseverance and with eye for realism and efficiency, showing a research-oriented attitude towards lifelong learning. | | | - DC
| 12.3 The student adopts an appropriate engineering attitude (accurate, efficient, safe, result-oriented,...). | | | | - BC
| The student take into account performance, security and reliability when designing a solution. |
|
| | EC = learning outcomes DC = partial outcomes BC = evaluation criteria |
|
|
The student should be familiar with the basic concepts of software engineering and programming.
|
|
|
|
This course focuses on the development of (the software for) a cyberphysical integrated system. This comprises software engineering aspects that are typical for combining a system composed of different components each requiring different layers of abstraction.
The courses starts with an introduction to cyberphysical systems, and continues with software methodolgies for their realization, as well as, the process for design, documentation, and deployment of the system.
Other aspects include:
- Component based architectures, and their coordination
- Distributed system aspects
- Security and compliance aspects
- How to apply networking in an integrated system
- Asynchronous programming concepts
|
|
|
Period 2 Credits 5,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 |
|
|
|
|
|
|
|
|
|
| Other exam | 75 % |
|
| Other | Discussion based on the project work |
|
|
|
|
|
Second examination period
| Evaluation second examination opportunity different from first examination opprt | |
|
|
|
| Compulsory course material |
| |
All material will be distributed through the course website. |
|
|
|
|
|
| Bridging programme Software Systems Engineering Technology - part 1 | Compulsory | 135 | 5,0 | 135 | 5,0 | Yes | Yes | Numerical | |
|
| |
|
|
The student should be familiar with the basic concepts of software engineering and programming.
|
|
|
|
This course focuses on the development of (the software for) a cyberphysical integrated system. This comprises software engineering aspects that are typical for combining a system composed of different components each requiring different layers of abstraction.
The courses starts with an introduction to cyberphysical systems, and continues with software methodolgies for their realization, as well as, the process for design, documentation, and deployment of the system.
Other aspects include:
- Component based architectures, and their coordination
- Distributed system aspects
- Security and compliance aspects
- How to apply networking in an integrated system
- Asynchronous programming concepts
|
|
|
Period 2 Credits 5,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 |
|
|
|
|
|
|
|
|
|
| Other exam | 75 % |
|
| Other | Discussion based on the project work |
|
|
|
|
|
Second examination period
| Evaluation second examination opportunity different from first examination opprt | |
|
|
|
| Compulsory course material |
| |
All material will be distributed through the course website. |
|
|
|
|
|
1 Education, Examination and Legal Position Regulations art.12.2, section 2. |
| 2 Education, Examination and Legal Position Regulations art.16.9, section 2. |
3 Education, Examination and Legal Position Regulations art.15.1, section 3.
|
| Legend |
| SBU : course load | SP : ECTS | N : Dutch | E : English |
|