1. |
- Borg, Markus, et al.
(author)
-
Conflict management in student groups - a teacher’s perspective in higher education
- 2011
-
In: Högre utbildning. - 2000-7558. ; 1:2, s. 111-124
-
Journal article (peer-reviewed)abstract
- Students working in groups is a commonly used method of instruction in higher education, popularized by the introduction of problem based learning. As a result, management of small groups of people has become an important skill for teachers. The objective of our study is to investigate why conflicts arise in student groups at the Faculty of Engineering at Lund University and how teachers manage them. We have conducted an exploratory interdepartmental interview study on teachers' views on this matter, interviewing ten university teachers with different levels of seniority. Our results show that conflicts frequently arise in group work, most commonly caused by different levels of ambition among students. We also found that teachers prefer to work proactively against conflicts and stress the student’s responsibility. Finally, we show that teachers at our faculty tend to avoid the more drastic conflict resolution strategies suggested by previous research. The outcome of our study could be used as input to future guidelines on conflict management in student groups.
|
|
2. |
- Holmén Notander, Jesper, et al.
(author)
-
A Model-Based Framework for Flexible Safety-Critical Software Development - A Design Study
- 2013
-
In: Proceedings of the ACM Symposium on Applied Computing/SAC '13. - 9781450316569 ; , s. 1137-1144
-
Conference paper (peer-reviewed)abstract
- This paper presents the findings from a design study of a model-based framework for safety-critical software development, called SimPal. The objective of the study was to better understand the necessary properties of such a framework and to learn more about the challenges of realizing it. Our research approach can be labeled as design research, which means that we try to answer our research questions by developing an artifact, in our case SimPal, and analyzing our experiences from the design of the artifact. In the paper we present what we identify as the necessary quality characteristics, using the ISO25010 quality in use quality model, of a framework like SimPal. These characteristics are then used to evaluate the SimPal framework in combination with a simple design case where we design a soft safety controller. We show that our approach has potential considering safety-critical software development. Although, there are some concerns about its run-time performance, from our results we conclude that the ideas behind the SimPal framework are sound but more work is required to investigate how they can be realized. In the future more effort should be spent on increasing performance and adding more features to the framework.
|
|
3. |
- Holmén Notander, Jesper, et al.
(author)
-
Challenges in Flexible Safety-Critical Software Development -- An Industrial Qualitative Survey
- 2013
-
In: Lecture Notes in Computer Science/Product-Focused Software Process Improvement. - Berlin, Heidelberg : Springer Berlin Heidelberg. - 1611-3349 .- 0302-9743. - 9783642392580 ; 7983, s. 283-297
-
Conference paper (peer-reviewed)abstract
- Context. Development of safety-critical systems is mostly governed by process-heavy paradigms, while increasing demands on flexibility and agility also reach this domain. Objectives. We wanted to explore in more detail the industrial needs and challenges when facing this trend. Method. We launched a qualitative survey, interviewing engineers from four companies in four different industry domains. Results. The survey identifies human factors (skills, experience, and attitudes) being key in safety-critical systems development, as well as good documentation. Certification cost is related to change frequency, which is limiting flexibility. Component reuse and iterative processes were found to increase adaptability to changing customer needs. Conclusions. We conclude that agile development and flexibility may co-exist with safety-critical software development, although there are specific challenges to address.
|
|
4. |
- Lindholm, Christin, et al.
(author)
-
A case study on software risk analysis and planning in medical device development
- 2014
-
In: Software Quality Journal. - : Springer Science and Business Media LLC. - 0963-9314 .- 1573-1367. ; 22:3, s. 469-497
-
Journal article (peer-reviewed)abstract
- Software failures in medical devices can lead to catastrophic situations. Therefore, it is crucial to handle software-related risks when developing medical devices, and there is a need for further analysis of how this type of risk management should be conducted. The objective of this paper is to collect and summarise experiences from conducting risk management with an organisation developing medical devices. Specific focus is put on the first steps of the risk management process, i.e. risk identification, risk analysis, and risk planning. The research is conducted as action research, with the aim of analysing and giving input to the organisation’s introduction of a software risk management process. First, the method was defined based on already available methods and then used. The defined method focuses on user risks, based on scenarios describing the expected use of the medical device in its target environment. During the use of the method, different stakeholders, including intended users, were involved. Results from the case study show that there are challenging problems in the risk management process with respect to definition of the system boundary and system context, the use of scenarios as input to the risk identification, estimation of detectability during risk analysis, and action proposals during risk planning. It can be concluded that the risk management method has potential to be used in the development organisation, although future research is needed with respect to, for example, context limitation and how to allow for flexible updates of the product.
|
|
5. |
- Lindholm, Christin, et al.
(author)
-
A Case Study on Software Risk Analysis in Medical Device Development
- 2012
-
In: Software Quality. Process Automation in Software Development/Lecture Notes in Business Information Processing. - Berlin, Heidelberg : Springer Berlin Heidelberg. - 1865-1348. - 9783642272127 ; 94, s. 143-158
-
Conference paper (peer-reviewed)abstract
- Software failures in medical devices can lead to catastrophic situations. Therefore is it crucial to handle software related risks when developing medical devices. This paper presents the experiences gained from an ongoing case study with a medical device development organisation. This part of the study focuses on the two first steps of the risk management process, i.e. risk identification and risk analysis. The research is conducted as action research, with the aim of analysing and giving input to the organisation’s introduction of a software risk management process. The risk identification activities focus on user risks based on scenarios describing the expected use of the medical device in its target environment. Challenging problems have been found in the risk management process with respect to definition of the system boundary and system context, the use of scenarios as input to the risk identification and estimation of detectability used during risk assessment.
|
|
6. |
- Lindholm, Christin, et al.
(author)
-
Software risk analysis in medical device development
- 2011
-
In: Proceedings of the 37th EUROMICRO Conference on Software Engineering and Advanced Applications. - 9780769544885 ; , s. 362-365
-
Conference paper (peer-reviewed)abstract
- The purpose of risk management in the development of safety-critical software is to eliminate or reduce harmful behaviour. In health-care it is essential to manage risk related to software due to its increased use in medical devices and other computer systems. This paper presents some of the experiences gained from an ongoing case study at a large hospital in Sweden. The study focuses on identification and analysis of risks using scenarios and how effective this approach is. The research is conducted as action research, with the aim of analysing and giving input to the organisation’s new software risk management process.
|
|