The aim of this thesis was to evaluate the music downloading service Musikwebb regarding its indexing and retrieval effectiveness. This was done by performing various kinds of search in the system. The outcome of these searches were then analysed according to the criteria specificity, precision, recall, exclusivity and authority control. The study showed that Musikwebb had several flaws regarding its retrieval effectiveness. The most prominent cases were the criteria exclusivity and specificity.

For this essay we used pattern theory from interface design and applied it in an analysis of touch games. In order to make full use of the patterns, we selected five of them and adapted these slightly with the help of game related patterns to be useful for the framework of this essay. The selection of games were the top eight games on the App Store?s ?What?s Hot?. The results showed, among other things, that the games had a clear focus on getting a pleasant apperance, and they did it relatively well.

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.

The maintenance phase within software projects is typically very expensive in terms of resources. The activities of this phase are largely focused around some form of modification of program code. This leads one to consider if there are alternative methods of code production that results in code that allows for less costly modifications. This thesis has its basis in a subset of those concepts which research has shown to provide more flexible code. Once this subset is established, connections are made between the concepts within the subset and claims of benefits provided by the use of Test Driven Development (TDD) methodology.

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.

Can the Danish "Aftalesystemet", a system with the intention to simplify the use of services within health care, be used in Sweden? This project has investigated the possibility by installing and testing the system and explored its functions to detect any eventual problems. Analyses were made of the system's graphical part and the underlying code to see in greater detail how the communication between units occurred, since no actual documentation of it existed. Discussions with the Developers took place regarding how the current system works and how further development should continue. In order to test the system, a completely virtual environment was used.

This essay focuses on the term usability while conducting a user centred system design. Usabilitymeans to what extent a user can use a product to achieve effectiveness, efficiency and satisfaction.Development using a user centered system design means that knowledge about the end-users andit?s opinions becomes a crucial part of the development process. The question of this essay is if usinguser centred system design will lead to good usability.We used methods from a user centered system design point of view while developing an applicationfor a Swedish bookstore company called Bokia AB. This included user and task analysis following by aclose relationship between the Developers and end-users by using sketches and showing themprototypes of the system while collecting feedback.After concluding our case study we determined that using methods from user centered systemdesign could be used as a great tool to further improve the usability and to improve an applicationssuccess chances..

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.

According to statistics, requirements management is identified as a major source of error to failed IT-projects. Moreover communication is identified as a factor affecting the require-ments management and can lead to deficiencies in the requirements. The requirements analyst is responsible for managing the requirements from the different stakeholders, act as a com-munication accommodator and to translate abstract requirements expressed by users to more specific requirements that Developers can implement. The purpose of this thesis is to study the role of the requirements analyst to investigate the problems that may arise in working with requirements management.  To achieve the purpose we have performed a requirements management process in which we ourselves took the role as the requirements analysts. The requirements management process consisted of three phases: gather requirements, document requirements and validate require-ments.

The purpose of this report is to analyze the advantages of using programme software to monitor masshauling instead of using the conventional method. A comparsion between different programs will also be conducted in an attempt to determine the most affordable. This report is written for NCC Construction AB to help them choose a software most fitting for future projects.The report is based upon literature such as information taken from the Developers website, existing reports with similar context, interviews with sellers of the software and interviews with people working in the building sector.The result of this report shows that there are several advantages with investing in a software that helps the management of a project and that it is something that should be taken under consideration instead of the existing method. Topcon is a clear favorite following the inquiries comparisons as done, when they deliver a complete system and not only a supplement to the current approach. Scanlaser are just in the beginning of its development, and is so far only out with an early version of the software, while Topcon has been brought further in development and therefore has more features in the program.

Through analysis of the work of scheduling the doctors at the hospitals of Sundsvall,Gävle and Karolinska in Stockholm this thesis presents some conclusion about howand why a computer system would benefit these very tasks. The reason for doing thisis mainly to save money through more efficient scheduling, but also to minimizeerrors and maximize comfort for scheduler and doctor alike.Scheduling consists of collecting doctors? requests, assessing the need of staff,distribute the available doctors and make sure all tasks are covered throughout thescheduled period of time. The work is often very complex and involves manyvariables ranging from competence to personal whishes and economical constraints.Solving these problems takes a lot of time and energy which could be better spentcuring patients.The conclusion of this thesis is that there is reason to develop such a system to savetime and optimize resources. A description of the system is found in numerous lists ofroles, tasks and prototype sketches which combined shape the content andfunctionality.

Healthcare in Sweden are in need of a drastic change to meet the requirements of highly developed societies, and information technology is seen as an essential part to get there. However, the Swedish healthcare have to challenge their traditional innovation approaches as well. For example, it has become more common to engage patients in the innovation process through web-based platforms. We have been focusing on an approach called co-creation by studying a workshop, in which potential users and other stakeholders are cooperating creatively to come up with innovative solutions in order to improve healthcare practice. Our findings suggests that co-creation may increase the mutual understanding between different stakeholders, for example healthcare professionals and IT Developers, enable horizontal learning through and outside the organization and also to raise concepts and actions that are responding to healthcare needs.

The Thesis purpose is in the context of system development validate the Scrum Methodology. Projects concerning information technology are difficult to manage and tend to fail in quality, time or costs. Scrum presents a new view of the system development. Better cooperation between customers and Developers, continuous follow-up on daily basis and extensive communication in the development team are all characteristics of Scrum. Scrum is described as a new paradigm by its founders but has been criticized by experts of system development too.

The objective of this thesis is to examine the capital structure of Swedish small and medium sized enterprises (SMEs). Accounting data from Swedish game Developers, combined with the result from a survey, is used to examine their financial conditions and capital structure decisions. We find that non-debt tax shield, firm size, growth opportunities and age are, to various extents, the determinants of capital structure in the game industry, while effective tax rate and asset structure have marginal effects. Our study also implicates that most of the existing capital structure theories can explain SMEs leverage decisions to some extent; however, some adaptation is needed to fit these theories into the SME context. Additionally, we find the existence of a financial gap in the game industry which might need efforts from both demand side and supply side to eliminate..