Requirements engineering is a widespread topic in the research field of informatics. However, there is little research regarding lack of requirements documentation and how it is perceived. The same applies for how requirements engineering in retrospect can be implemented. This is a debated issue on blogs and forums but it has not been reflected in the research area.Therefore, this study concerns research questions regarding how the developers, testers and requirements analyst experience the lack of requirements documentation and how requirements engineering in retrospect can be implemented.To answer these questions, data collection has been conducted through qualitative interviews with individuals affected by this problem in their everyday work.This study has provided an explanation of how the problem is perceived and what the consequences are, both direct and indirect. The impacts are divided into three categories and are presented as, emotional consequences, system implications and consequences regarding re source consumption.

Abstract          Background: End of life is difficult to establish in patients with dementia and many patients die due to complications related to the disease. To document that care are palliative in this group of patients is not common among nurses and physicians. This may depend on that the palliative course is extended and not similar to the palliative course common among patients with cancer. Aim: To describe how the registered staff in nursing homes document the care of persons with dementia in a late palliative phase. Method: A retrospective record study with a deductive approach.

The exclusion of visually impaired from the information flow presented to us through signs was what led me into this project. With a growing amount of information being presented to us on signs and digital information surface the need of communicating this information in a way that could be read by visually impaired is evident. Looking into different ways of communication, my goal was to create something that filled the need of the visually impaired without branding them as disabled. Having a close relative with bad eyesight is became evident on how much it limited her in her everyday life, not being able to navigate herself without the support of her husband. Through interviews with her and others with varying diagnoses I reached an insight in their situation. To my surprise they still favored a visual form of communication before an auditory or tactile form, because it?s easy to survey and quick to interpret.

Stenebergs sockerbruk is a large log-timber construction, purpose built as a sugar refinery in 1739 and is one of Sweden's oldest industrial buildings constructed entirely out of wood. Despite receiving the status of a listed building (in Swedish: Byggnadsminne) in 1977, there exists today a surprisingly low amount of documentation of the building itself. In order to enhance the existing and lacking building documentation, this case study aims to shed light on the building's log-timber built frame, focusing on how it was constructed, how the long lengths of its walls were handled and what type of joinery and tools were used. A thorough investigation of the building is conducted on site, followed by gathering of information which is then presented through text and illustrations. The findings indicate the orientation of timbers, location of joints and scarfs as well as tool marks which together contribute to the forming of a basis of understanding of the building's construction..

In visual programming the developer specifies her code, using visual tools. Within the range of visual programming languages lay icon-based languages, form-based languages, and diagram languages.Mediator is a multimedia authoring tool that allows the user to create interactive CD-ROM presentations, dynamic HTML pages and Flash projects, without any coding or scripting. The user can create interactivity in her project, using event driven and icon-based visual programming, through a ?drag and drop? user interface. This report intends to determine some of the qualifications of a tool of this kind, as well as its limitations.The report is based on a case study, in which a smaller software application was to be updated using Mediator 9.

This master?s degree project concerns the combination of a multi dwelling passive house with solar energy for the generation of electricity and domestic hot water (DHW). Different alternatives with either solar thermal systems or photovoltaic (PV) systems are compared with two reference alternatives producing DHW from electricity or district heating. The economical comparison uses a life cycle cost (LCC) perspective based on the present value of expenditures for investment, energy and annual operating and maintenance.The energy yields from the solar energy systems were calculated by hand and with simulation software. Calculation and dimensioning of PV systems were carried out with a software called PVSYST.

Requirements engineering is a widespread topic in the research field of informatics. However, there is little research regarding lack of requirements documentation and how it is perceived. The same applies for how requirements engineering in retrospect can be implemented. This is a debated issue on blogs and forums but it has not been reflected in the research area.Therefore, this study concerns research questions regarding how the developers, testers and requirements analyst experience the lack of requirements documentation and how requirements engineering in retrospect can be implemented.To answer these questions, data collection has been conducted through qualitative interviews with individuals affected by this problem in their everyday work.This study has provided an explanation of how the problem is perceived and what the consequences are, both direct and indirect. The impacts are divided into three categories and are presented as, emotional consequences, system implications and consequences regarding re source consumption.

Requirements engineering is a widespread topic in the research field of informatics. However, there is little research regarding lack of requirements documentation and how it is perceived. The same applies for how requirements engineering in retrospect can be implemented. This is a debated issue on blogs and forums but it has not been reflected in the research area.Therefore, this study concerns research questions regarding how the developers, testers and requirements analyst experience the lack of requirements documentation and how requirements engineering in retrospect can be implemented.To answer these questions, data collection has been conducted through qualitative interviews with individuals affected by this problem in their everyday work.This study has provided an explanation of how the problem is perceived and what the consequences are, both direct and indirect. The impacts are divided into three categories and are presented as, emotional consequences, system implications and consequences regarding re source consumption.

Vårterminen 2006.

In today?s IT world where software is constructed in a rapid pace, testing has become a crucial area to master when testing has to be done at a greater speed. To still be able to handle the demands of high quality software, companies have to spend more resources on testing and introduce test automation. By automating test cases the testers can gain time which they can spend on doing more complex testing and thereby increase the quality of the software.In this thesis we have helped Extenda AB, who delivers systems to retail companies, to introduce test automation in one of their customer specific projects. This has been done using their own in-house ?capture/replay? tool ECP (Extenda Cashier Player).We have also derived a process that explains how Extenda can introduce test automation on other customer projects.

In February 2002 the European commission put forward a proposal for a new directive on The patentability of computer-implemented inventions, but which during my work on this essay has not been decided on yet. The directive has divided the decision-makers in the union, the commission and parliament, into two different positions regarding by which range computer-implemented inventions should be patentable. The parliament has amended the commissions proposal in a substantial way and the legal process has caused a heated debate both within the unions administration and among various interest groups both in favour of and against a patent on computer-implemented inventions. The loudest protests have come from a group that feels threatened by a possible software patent: Open Source. In this study I examine both the arguments by the decision-makers and by the lobbying for and against the proposal.

This Degree project summarizes how it is to work in the CAD program Revit Architecture. This was done because AQ Arkitekter in Eskilstuna is interested in how Revit works. Especially compared to AutoCad which is the software they are using today. Will their work become more efficient with the new software?The starting point was to find out how it is to work with Revit when you only used AutoCAD Architecture before.

The purpose of this essey is through empirical methods investigate usability factors on Video On Demand applications for the Internet. More specificly we will focus on a application called Voddler. The purpose is to identify usability problems that exist in Voddler, and present the reader with suggestions on possible solutions. This could be used as guidelines to how to design for usability in this kind of system. We will use an online survey to investigate Voddler usability and use this data as a basis for our analysis.

This Degree project summarizes how it is to work in the CAD program Revit Architecture. This was done because AQ Arkitekter in Eskilstuna is interested in how Revit works. Especially compared to AutoCad which is the software they are using today. Will their work become more efficient with the new software?The starting point was to find out how it is to work with Revit when you only used AutoCAD Architecture before.

Background: Insufficient nutritional support is associated with prolonged hospitalisation, impaired wound healing and impaired survival for patients in intensive care. In severe sepsis and septic chock, calculation of nutritional need is complicated since the metabolism is affected by decease. Aim: The aim of the study was to investigate nutritional support and to examine the quality of nursing documentation of nutritional status and nutritional support in patient records in severe sepsis and septic chock.  Method: The study was conducted as a retrospective investigation where 64 patient records were studied. The quality of documentation was examined in 10 patient records using an examinational model.Findings: Calculation of average nutritional support showed insufficient supply particularly in the two first days of intensive care. During the next five days nutritional supply was higher but individual variation was seen, why a clear picture of nutritional support is hard to detect.