| Credits: 5,0 | | Study load hours: 135 | Period: semester 1 (0sp) semester 2 (5sp)  |
| Language of instruction: English | | Exam contract: not possible |
|
|
|
The main focus of this course is creating awareness of the importance of taking into account the entire ecosystem surrounding the software system, i.e. not only the traditional stakeholders such as the client commissioning the software, the product owner, the business analyst, the developer and the end user; but also competition, regulatory agencies, research institutions, society and community, environment, ...
Within this context, user-centered design plays an essential role. Given the application-oriented profile of the master in Engineering Technology, this is explored in depth by means of a realistic use case with end users in a group project. The project will be developed incrementally throughout the semester.
Some of the topics of user-centered design covered are (in a non-binding list):
Principles and techniques of user-centered design (e.g., observational techniques, user profiling, contextual design, etc.).
Related methods such as user experience design and universal design.
Estimating and applying prototyping techniques.
Informal and formal techniques to evaluate user interfaces.
These topics are approached both practically and more conceptually. The theoretical sessions also present general principles and theories of systems thinking. Because of the impact of regulations on a software system, there is also a (brief) section on legal as well as ethical aspects.
Guest lectures may present real life cases with a discussion of the impact on direct and indirect stakeholders and on society and the global system as a whole
Because of the focus on user-centered design, this course unit is complementary with the course 'Engineering Interactive Software'.
A distinct part of this course is the Life Long Learning (LLL) portfolio: the goal is to raise awareness of the fact the learning doesn't stop when graduating and that being a professional entails more than just doing your own job. Therefore this part of system thinking encourages students to actively participate in the organisation, to develop their talents and to educate themselves. This can be done by supporting lessons, participating in councils, forums, innovation camps or information days, organizing activities, carrying out extra assignments in a civic setting, attending seminars and many other programme-related activities that shape the student's engineering attitude. The student must hand in an portfolio of approximately 30 hours that gives evidence of his efforts in this aspect in which the students reflects on each of these activities.
|
|
| Compulsory course material |
| |
All compulsary study materials consisting of slides, papers and/or chapters from books will be made available through the electronic learning environment, as will all additional course materials, either directly or through references. |
|
|
| Recommended reading |
| |
Research Methods in Human-Computer Interaction,Jonathan Lazar, Jinjuan Feng, Harry Hochheiser,2nd,Elsevier Science & Technology,9780128053904 |
|
|
| Mandatory software |
| |
Software used will either be freeware or previously purchased software (e.g. text editor for reports, ...) |
|
|
|
|
|
|
|
|
|
Application Lecture ✔
|
|
|
|
|
|
|
|
Case study ✔
|
|
|
|
Group work ✔
|
|
|
|
Porfolio ✔
|
|
|
|
Semester 2 (5,00sp)
| Evaluation method | |
|
| Written evaluation during teaching period | 50 % |
|
| Transfer of partial marks within the academic year | Yes, no resit exam |
|
|
|
|
|
|
|
|
| Written exam | 50 % |
|
| Transfer of partial marks within the academic year | Yes, with condition |
|
| Conditions transfer of partial marks within the academic year | For the exam at least 10/20.
For the portfolio a PASS. |
|
|
|
|
|
|
|
|
|
|
|
|
| Use of study material during evaluation | ✔ |
|
| Explanation (English) | When applicable, a limited list of material allowed during the exam (e.g. summaries or specific papers) is communicated, at the latest during the last lecture. |
|
|
|
| Evaluation conditions (participation and/or pass) | ✔ |
|
| Conditions | The student must obtain a pass for the LLL-portfolio. |
|
|
|
| Consequences | In case of a FAIL on the LLL-portfolio, the overall grade of the course is FAIL. In case of a PASS, the weighted grade of the project + exam counts for the entire course. |
|
|
|
| Additional information | For specific guidelines and possible consequences regarding the usage of AI, consult Toledo.
The LLL-portfolio is evaluated with a PASS/FAIL. In case of a FAIL, the overall grade of the course is FAIL. In case of a PASS, the weighted grade of the project + examen counts for the entire course.
|
|
Second examination period
| Evaluation second examination opportunity different from first examination opprt | |
|
|
Learning outcomes | EC = learning outcomes DC = partial outcomes BC = evaluation criteria |
Master of Teaching in Sciences and Technology
|
- EC
| 5.1 The Educational Master in Science and Technology as a domain expert: the Educational Master communicates appropriately with all stakeholders in professional contexts, collaborates effectively within a multidisciplinary STEM team, uses modern (digital) tools, and takes into account economic, ethical, societal, and international contexts, while being aware of environmental impact. | - EC
| 5.2 The Educational Master in Science and Technology as a domain expert: the Educational Master has specialised knowledge of and insight into subject didactics and is able to creatively design, plan, and implement these within an educational context, particularly as part of a methodologically structured and project-based sequence within a multidisciplinary STEM project with a strong research and/or innovation component. | - EC
| 5.3 The Educational Master in Science and Technology as a domain expert: the Educational Master has advanced or specialised knowledge of the principles, structure, and technologies of various industrial processes and techniques relevant to subject didactics, and is able to independently identify, critically analyse, and methodically solve complex, multidisciplinary, unfamiliar, practice-oriented design or optimisation problems, taking into account application, material selection, automation, safety, environment, and sustainability, while recognising practical constraints and current technological developments. |
|
|
|
Master of Software Systems Engineering Technology
|
- EC
| EC1 – The Master of Software Engineering Technology can communicate adequately, cooperate effectively, and take into account the sustainable, 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-M8 - can evaluate knowledge and skills critically to adjust own reasoning and course of action accordingly. | | | | - BC
| can reflect on accomplishments and adjust future progress based on own insights and feedback moments with the teaching team. | | | - DC
| DC-M9 - can communicate in oral and in written (also graphical) form. | | | | - BC
| can present, demonstrate and defend the work completed orally (in discussion form) .
can document and report progress a nd final results in writing, using correct subject terminology.
can communicate and present the project results to a cl ient (non-expert). | | | - DC
| DC-M10 - can function constructively and responsibly as member of a (multidisciplinary) team. | | | | - BC
| is capable of going through the design process as a team.
participates in the group discussions on cases of systems thi nking, presented by the teaching team or by guest speakers from industry and is in this respectful for the other members' opinio ns. | | | - DC
| DC-M11 - acts socially responsible and within an international framework. | | | | - BC
| is aware of the impact of software projects on all levels of society and takes this into account in discussions and reports. | | | - DC
| DC-M12 - shows a suitable engineering attitude. | | | | - BC
| works iteratively, incrementally as well as result-oriented.
assembles a portfolio of Life Long Learning activities. | - 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. | | | | - BC
| knows the essential philosophical views on systems thinking.
possesses the knowledge of the material provided on the de sign process of systems.
knows the legal issues involved in software engineering (IP rights and software licensing). | | | - DC
| DC-M2 - has insight in the basic concepts and methods. | | | | - BC
| is able to apply systems thinking skills and tools.
understands the material and demonstrates an understanding of the d esign process of systems through application in a project. | | | - DC
| DC-M4 - can gather, measure or obtain information and refer to it correctly. | | | | - BC
| does further research based on the material provided to gather all required information. | | | - DC
| DC-M5 - can analyze problems, logically structure and interpret them. | | | | - BC
| can analyze and interpret the impact of a proposed software project on the end user and on the system as a whole. | | | - DC
| DC-M6 - can select methods and make calculated choices to solve problems or design solutions. | | | | - BC
| can apply appropriate techniques and design principles of systems thinking. | | | - DC
| DC-M8 - can evaluate knowledge and skills critically to adjust own reasoning and course of action accordingly. | | | | - BC
| is able to reflect on the level of the acquired systems thinking competencies, in general and/or in the context of a specific pr oject.
can adjust artifacts depending on feedback moments with the client.
can adjust artifacts depending on f eedback moments with the educational team. | - 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-M1 - has knowledge of the basic concepts, structures and coherence. | | | | - BC
| has knowledge of the entire software development process and the steps that are involved, especially in the context of user-centered. | | | - DC
| DC-M2 - has insight in the basic concepts and methods. | | | | - BC
| has an understanding of all the basic concepts of user-centered software development.
has an understanding of what methods are applied to accomplish the various steps of the design and development process. | | | - DC
| DC-M3 - can recognize problems, plan activities and perform accordingly. | | | | - BC
| schedules activities and actions necessary for project implementation in a timely manner. | | | - DC
| DC-M5 - can analyze problems, logically structure and interpret them. | | | | - BC
| can analyze and interpret the needs and requirements of the proposed use case. | | | - DC
| DC-M6 - can select methods and make calculated choices to solve problems or design solutions. | | | | - BC
| can apply appropriate techniques and design principles based on project requirements. | | | - DC
| DC-M7 - can use selected methods and tools to implement solutions and designs. | | | | - BC
| is able to develop the necessary artifacts based on the material provided and feedback moments. | | | - DC
| DC-M8 - can evaluate knowledge and skills critically to adjust own reasoning and course of action accordingly. | | | | - BC
| can adjust artifacts depending on feedback moments with the client.
can adjust artifacts depending on feedback moments with the educational team. |
|
|
|
|
| Included in these programmes | Tolerance3 |
|
Master of Software Systems Engineering Technology
|
N
|
|
Master of Teaching in Sciences and Technology - Engineering and Technology choice for subject didactics engineering & technology
|
N
|
|
|
1 Education, Examination and Legal Position Regulations art.12.2, section 2. |
| 2 Education, Examination and Legal Position Regulations art.15.1, section 3. |
3 Education, Examination and Legal Position Regulations art.16.9, section 2.
|
|
|