Both Software Engineering and Machine Learning have become recognized disciplines. In this article I analyse the combination of the two: engineering of machine learning applications. I believe the systematic way of working for machine learning applications is at certain points different from traditional (rule-based) software engineering. The question I set out to investigate is “How does software engineering change when we develop machine learning applications”?. This question is not an easy to answer and turns out to be a rather new, with few publications. This article collects what I have found until now.
LINK
Testen van software is een speerpunt in onze opleiding Software Engineering. In de propedeusefase wordt de testgedreven software-ontwikkeling geoefend. De student wordt aangeleerd software met testen at te leveren. Als onderdeel van de toetsing werd een performance-assessment ontwikkeld, dat de mogelijkheid biedt modelleren, programmeren en testen integraal te toetsen. Studenten blijken deze nieuwe toetsvorm positief te waarderen. In het kader van competentiegericht onderwijs is dit performance-assessment een waardevolle toevoeging.
DOCUMENT
The pace of introduction of new technology and thus continuous change in skill needs at workplaces, especially for the engineers, has increased. While digitization induced changes in manufacturing, construction and supply chain sectors may not be felt the same in every sector, this will be hard to escape. Both young and experienced engineers will experience the change, and the need to continuously assess and close the skills gap will arise. How will we, the continuing engineering educators and administrators will respond to it? Prepared for engineering educators and administrators, this workshop will shed light on the future of continuing engineering education as we go through exponentially shortened time frames of technological revolution and in very recent time, in an unprecedented COVID-19 pandemic. S. Chakrabarti, P. Caratozzolo, E. Sjoer and B. Norgaard.
DOCUMENT
In the fall of 1999, we started, the Integrated Product Development- Collaborative Engineering ( IPD-CE) project as a first pilot. We experimented with modern communication technology in order to find useful tools for facilitating the cooperative work and the contacts of all the participants. Teams have been formed with engineering students from Lehigh University in the US, the Fontys University in Eindhoven, The Netherlands and from the Otto-von-Guericke University in Magdeburg, Germany. In the fall of 2000 we continued and also cooperated with the Finnish Oulu Polytechnic. It turned out that group cohesion stayed low (students did not meet in real life), and that Internet is not mature enough yet for desktop video conferencing. Chatting and email were in these projects by far the most important communication media. We also found out that the use of a Computer Support for Cooperative Work (CSCW) server is a possibility for information interchange. The server can also be used as an electronic project archive. Points to optimise are: 1. We didn't fully match the complete assignments of the groups; 2. We allowed the groups to divide the work in such parts that those were developed and prototyped almost locally; 3. We haven't guided the fall 2000 teams strong enough along our learning curve and experiences from previous groups. 4. We didn't stick strong enough to the, by the groups developed, protocols for email and chat sessions. 5. We should facilitate video conferencing via V-span during the project to enhance the group performance and commitment.
DOCUMENT
In the fall of 1999, an international integrated product development pilot project based on collaborative engineering was started with team members in two international teams from the United States, The Netherlands and Germany. Team members interacted using various Internet capabilities, including, but not limited to, ICQ (means: I SEEK YOU, an internet feature which immediately detects when somebody comes "on line"), web phones, file servers, chat rooms and Email along with video conferencing. For this study a control group with all members located in the USA only also worked on the same project.
DOCUMENT
From the article: This paper describes the external IT security analysis of an international corporate organization, containing a technical and a social perspective, resulting in a proposed repeatable approach and lessons learned for applying this approach. Part of the security analysis was the utilization of a social engineering experiment, as this could be used to discover employee related risks. This approach was based on multiple signals that indicated a low IT security awareness level among employees as well as the results of a preliminary technical analysis. To carry out the social engineering experiment, two techniques were used. The first technique was to send phishing emails to both the system administrators and other employees of the company. The second technique comprised the infiltration of the office itself to test the physical security, after which two probes were left behind. The social engineering experiment proved that general IT security awareness among employees was very low. The results allowed the research team to infiltrate the network and have the possibility to disable or hamper crucial processes. Social engineering experiments can play an important role in conducting security analyses, by showing security vulnerabilities and raising awareness within a company. Therefore, further research should focus on the standardization of social engineering experiments to be used in security analyses and further development of the approach itself. This paper provides a detailed description of the used methods and the reasoning behind them as a stepping stone for future research on this subject. van Liempd, D., Sjouw, A., Smakman, M., & Smit, K. (2019). Social Engineering As An Approach For Probing Organizations To Improve It Security: A Case Study At A Large International Firm In The Transport Industry. 119-126. https://doi.org/10.33965/es2019_201904l015
MULTIFILE
Dames en heren, het is mij een grote eer dat u met zo velen gekomen bent om te luisteren naar mijn openbare les in het kader van mijn benoeming tot lector product design & engineering. Ik begrijp best dat u gekomen bent, want product design & engineering is belangrijk. Zonder product design & engineering was u hier tenslotte niet eens geweest. De auto, trein of bus waarmee u hier gekomen bent, zijn mede tot stand gekomen dankzij product design & engineering. Dat u mij ook achter in de zaal kunt horen, heeft u te danken aan ditzelfde vakgebied. En dat u aan het eind van deze openbare les mogelijk pijn in uw rug heeft door een oncomfortabele zit is er ook een gevolg van. Kortom: product design & engineering is een belangrijk vakgebied waarmee we in ons dagelijks bestaan voortdurend geconfronteerd worden, aangenaam of niet. Mijn voordracht valt in drieën uiteen. Eerst sta ik stil bij de titel: Van vuistbijl tot mobieltje. Aan de hand van deze objecten illustreer ik de historische achtergronden van het vakgebied product design & engineering. Daarna ga ik dieper in op het begrip ontwerpen. Het derde deel van mijn openbare les gaat over de ambitieuze plannen van de kenniskring product design & engineering. Ik sluit mijn openbare les af met het mobieltje, maar hoe blijft nog even een verrassing.
DOCUMENT
The current set of research methods on ictresearchmethods.nl contains only one research method that refers to machine learning: the “Data analytics” method in the “Lab” strategy. This does not reflect the way of working in ML projects, where Data Analytics is not a method to answer one question but the main goal of the project. For ML projects, the Data Analytics method should be divided in several smaller steps, each becoming a method of its own. In other words, we should treat the Data Analytics (or more appropriate ML engineering) process in the same way the software engineering process is treated in the framework. In the remainder of this post I will briefly discuss each of the existing research methods and how they apply to ML projects. The methods are organized by strategy. In the discussion I will give pointers to relevant tools or literature for ML projects.
LINK
This chapter discusses several aspects related to engineering methods in wind turbine design codes. Current engineering models for rotor aerodynamics topic are built around the Blade Element Momentum (BEM) theory. The Blade Element Momentum theory in itself is very basic, e.g., it is derived for two-dimensional, stationary, homogenous, and non-yawed conditions. For this reason, several engineering models have been developed which overcome these simplifications and which act as add-ons to the basic BEM theory. This chapter describes the BEM theory, the most important engineering add-ons, and an assessment of BEM with engineering add-ons with results from higher fidelity models and measurements.
LINK
This paper describes a model for education in innovative engineering. The kernel of this model is, that students from different departments of the faculty of Applied Science and Technology are placed in industry for a period of eighteen months after two-and-a-half year of theoretical studies. During this period students work in multi-disciplinary projects on different themes. Students will grow to fully equal employees in industry. Therefore it is important that besides students, teachers and company employees will participate in the projects. Also the involvement of other level students (University and high school) is recommended. The most important characteristics of the model can be summarized in innovative, interdisciplinary and international orientation.
DOCUMENT
