The project behind this thesis empirically explored the possibility of mobile handheld devices and use situations of the hospital arena by building prototypes and have them evaluated by real users in realistic settings. The main aspects of discussion are: what characterizes work that is suitable in this context; how well does the technology support the user’s work ―input of data, output of data, navigation, ease of handling, and general usability of device; and what the ideal mobile device in a hospital would be.

This thesis focuses on the effect of nursing staff's redundant work routines on error and quality of care in one Critical Access Hospital in rural Wisconsin, USA. Methods were based on participatory design and an ethnographic approach, and included individual interviews and observation-based interviews. Introduction of a computerized information system was scheduled for the case study site and this thesis makes pre-implementation suggestions regarding staff training, interface features desired by the future users, and removal or restructuring of certain redundancies. The contribution of this thesis to information systems research is a classification system for determining the degree of redundancy (productive, gray-zone, and unproductive) present in the task chains of specific work routines, and a second classification system for determining to what extent modifying or removing an unproductive redundancy returns value. The degree to which an unproductive redundancy may be modified or removed is weighted against the difficulty of changing the work routines associated with that redundancy as well as the expected impact on other routines.

This thesis concerns the safety in user interfaces. In particular it concerns the user interfaces in systems in which safety is critical. I have studied such systems in the maritime industry, where we for instance may find them on the bridges of ships. Computer systems get more and more important in the daily routines of humans, and it is important that this does not go unnoticed. Designers of computer systems need to take human factors into consideration when designing their systems. These considerations might be especially important in complex systems, as these are often safety critical. The bridges on ships are likely to include complex systems for the operator to handle, as they often involve multiple screens, or other factors that increase the complexity of a system. Such factors might include being able to pay attention to several incidents at once. When dealing with complex systems, it is important that the operator knows how to handle the system, and also how to react when an incident occurs. These are factors that need to be considered by the designer when making the system and theories on how to do this are described in the thesis. I have also described standards which consider this, like the ISO 11064 standard, or the Atomos regulation and the ISO 17894 which considers this for the maritime industry in particular. Parts of the industry have made an effort to develop tools to be used to improve the safety. I have studied some of these efforts and presented them in the thesis. Furthermore, I have developed a survey to study how the individual members and different parts of the industry feel and behave towards safety. The survey gave an insight into reality of how safety is being handled in the industry as a whole. In particular it pointed to the main problem of the maritime industry, that the industry is very heterogeneous, and also that the different parts of the industry are in competition with each other. Most of the respondents had not heard about the Atomos regulation or the ISO 17894 standards, efforts that could have been used as a tool to improve the level of safety. The questionnaire also showed that while most of the respondents are satisfied with the level of safety in their organization, they are not satisfied with the level of safety in the overall industry. The thesis consists of six parts. Part I deals with the introduction and general theory from research methods and psychology. Part II deals with usability and related standards. These include ISO 11064, theory on usability and a description of an accident due to poorly designed user interface. Part III describes relevant background from the maritime industry, which involves the ISO 17894 standard, the Atomos regulation and e-navigation, an example of a newly made effort. Part IV gives a description of the development of my questionnaire, and also provides the results and conclusions made from them. Part V provides the conclusions and suggestions for future work, while part VI contains appendices.

Exception handling suffers from a fluke in its evolution. Some time in the 1970's, a researcher called Goodenough introduced the exception handling mechanism, known today as the tcode{try...catch} construct. At about the same time, two fellows called Parnas and Würges published a paper about "undesired events". This paper appears forgotten. The funny thing is, Parnas and Würges effectively described how to emph{use} exception handling mechanisms. There is a need to respond to this undesired event. Exception handling suffers from lack of design guidelines and a number of inconsistencies with the object-oriented paradigm, among other things. The thesis' main contribution is creating a library of exception challenges and the evaluation of safety facades, an approach that introduce an architecture and guidelines for designing exception handling. Through qualitative evaluation, this thesis shows how safety facades form an interesting new approach to exception handling.

When proponents of open source software are asked to explain the success of their movement they typically point to the quality of the software produced, which is in turn attributed to the rather unconventional development model of releasing unfinished versions of the software and having users look over the code and report and fix bugs. This thesis investigates the open source quality assurance model from a knowledge management perspective – based on the assumption that debugging involves a high degree of knowledge work. By doing interpretive case studies of two open source projects – using direct observation, e-mail archives, and bug-trackers as data sources – I present descriptive accounts of the day to day quality practices in open source development. The analysis shows that conceptualizing and classifying bugs is a complex process involving sense-making and subjective considerations; that the peer-review process in open source projects has a lot in common with traditional field-testing; and that communication tools and mediums are used interchangeably, but with certain preferences depending on subject matter. I conclude that perhaps the success of the open source development model is not due to its novelty compared to traditional software engineering, but because open source developers have recognized that debugging is a knowledge-intensive process. Keywords: Open Source, Software Quality, Knowledge Management

As our reliance on software has increased, robustness has become an important subject. Software that is not robust enough may lead to frustration, or loss of time or value. Software architecture forms the main structures of applications. Having focus on the quality of an applications architecture may increase the robustness of the application. This thesis tries to find a suitable architectural process for achieving robustness. I report on the findings from ten interviews with software architects from the software industry, around the theme robustness. Interview results are used in order to form a definition of robustness which is wider than the definitions I found in literature. The thesis's main contribution is a proposed process for designing and analyzing robust software architectures that make use of elements from existing methods. The proposed process is grounded on results from interviews, personal experience, and evaluation of existing methods in literature.

Agile software development have in recent years been widely accepted in industry, as well as being the target of much research. XP has been the main focus, while there exist relatively few studies of other Agile methods such as Scrum. This thesis describe an ethnographic study of a Scrum team in a project. The goal is to give a rich description of the use and application of Scrum. Special attention is given to the implications of differences in implementation from theory. Another focus is to reveal the dynamics of teamwork within the project. The main findings are that Scrum was easy to implement, and worked well, but is challenging when used to increase predictability. With regard to teamwork, Scrum supported a shared mental, communication and adaptability. The leadership function is however complex, and requires good interpersonal skills. Keywords: Agile, Scrum, Teamwork, Implementation, Software development, Software engineering

This master thesis is a case study on software reuse within a subset of systems at the Norwegian Directorate of Taxes, Skattedirektoratet (SKD). The systems chosen for our research are the GLD systems; legacy systems which dates back to the late 1980's and early 1990's. Because of historical reasons, these systems are copied and created over and over again in an annual cycle. There are redundancies in code and data between the annual versions, but also across the different GLD systems. The consequence of this is systems with reduced maintainability and possible inconsistencies in code and data. Our objectives with this case study is to determine both the current level of software reuse within a subset of the GLD systems, and the emphasis on reuse in SKD's development process. After determining the status of as-is, we will continue with an investigation of the potential for software reuse within the context of SKD, and how they can achieve systematic software reuse. The contributions of this thesis can be divided into four main themes: * T1: Review of state-of-the-art literature on software reuse * T2: Investigation of reuse level within selected GLD systems * T3: Investigation of SKD's development process * T4: Investigation of opportunities for systematic reuse in SKD The main contributions are: * C1: Review of literature in the field of software reuse * C2: Measurement of the reuse maturity level within the selected GLD systems. * C3: Survey of the software development process and reuse aspects at SKD * C3.1: Results from SKD * C3.2: Results from SKD combined with results from previous surveys on software developers attitude toward software reuse by NTNU * C4: Process which assures reuse Keywords: Systematic software reuse, Reuse maturity, Software development, Software engineering

This thesis looks into the literature in the fields of informal learning, mobile learning and mobile games. A demonstrator is build to test the effect of informal learning and the use of collaborative games in a learning context.

N/A