The stakeholders for requirements elicitation need to be identified at an early stage and their knowledge is the basis for what is to become a Requirements specification. Just because a stakeholder holds a lot of expertise and knowledge it does not mean that the stakeholder can communicate the knowledge in a clear way. Validation of knowledge means that knowledge is valued and recognized in a structured way. People and organizations can evolve by exchanging knowledge, experience and skills.  The purpose of this study is to increase the understanding of knowledge management between requirement elicitation and external stakeholders.

The importance of internal communication within companies has increased in recent years. However, there are still a number of companies that are not adapted to the modern world and the new modes of communication the Internet provides. This study evaluates the internal communication of a medium sized company by holding semistructured interviews with the employees. The goal of the interviews was to develop a requirement specification. This requirement specification was later used as the basis to analyze possible aids for the internal communication of the company.

Prioritisation of software requirements is a critical part of the development of software. Whichrequirements and in which order they will be developed is one of the main tasks that requirementprioritisation supports.There are different ways that a requirement prioritisation can be used, for example alone or in agroup and with different methods.The purpose of this report is to map out how you can carry out a requirement prioritisation alonewith different types of prioritisation methods and how you solve the problems that can arise whenprioritisting requirements. This is done by documenting the use of three different types of methodsthat can be execute alone. The methods are "100-dollar test", "Ranking" and "Top-tenrequirements".To be able to prioritise requirements, you need to establish which requirements you shall prioritise.The paper retrieves this information by interviewing stakeholders in the system and analysing theresult of the interviews and the execution of the requirement prioritisation.Three problems arose during that work and I present solutions on these problems. The problemswere 1) equivalent requirements when using the "100-dollar test", 2) low differentiation gradebetween the prioritised requirements in the "100-dollar test" and 3) that the requirements that wereprioritised weren't classified before the prioritisation, which leads to inaccuracies in the resultingprioritisation.The solution to the problems that the paper presents is to increase the amount of distributable unitsin the "100-dollar test" to 1000 per requirement, suggestions of classes of the requirements andthe combination of the methods "100-dollar test" and "ranking" to bypass the equivalentrequirements.The report is written in Swedish.Nyckelord: GoTRIS, requirements retrieval, requirements analysis, Viktoria Swedish ICT,requirements prioritisation, requirements, 100-dollar test, ranking, top 10 requirements..

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.

A degree project has been carried out at Motion Control, Västerås. The degreeproject ?Grafisk Skärm för Inbyggda System? have developed a first prototype of anembedded system with a display, a graphical user interface with touchscreen andpossibilities to communicate with external units.The work initiated with surveys of critical components. A technical specification forthe desired end product was developed. With the technical specification as support,design specifications for hardware and firmware were developed.After the specifications were done, a circuit diagram was developed and a circuitboard was made.

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.

This report was written as a result of a Bachelor Degree Project at the School of Technology and Society at University of Skövde, first semester 2007. The assigner was Tibrokök in Tibro, Sweden. The commission was originally to design a sliding door concept for kitchen. Later it was expanded to also include bathrooms.During the feasibility study of the project Internet was used as an information source. Kitchen brochures and magazines were ordered from different companies to give inspiration and ideas.

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.

This project aims at investigating if the use of UML as a support to small-scale development ofan embedded system is relevant. The investigation is conducted by using UML during the initialphase of the development ofTelfafill, a filling machine by the company ?Telfafill AB?. The aimof the development of Telfafill is to separate the user interface from the control unit. In additionto this main objective, Telfafill AB would like possible changes to, and additions of,functionality of the filling machine to be investigated.Within the boundaries of this project, the development of Telfafill reached a full requirementspecification of the proposed system, and contact was made with potential external developers.No prototype construction had been started when the project ended.

The building and plant sectors represent a large part of Sweden?s energy use. Putting energy requirements in public procurement as a tool for reducing energy consumption in the building and plant sectors is therefor an opportunity that operators can take advantage of. The aim of this thesis was to map the energy requirements in procurement that operators in the public sector use today in building and plant projects. The analysis was made with respect to if the energy requirements corresponded to the parts with large energy use in building and plant projects and also in which way energy requirements in procurement are written in the contract.

This Master Thesis has been carried out in cooperation with Ursus Medical AB (URSUS) which markets, assembles and sells the Rotex Screw Needle Biopsy Instrument ®. The instrument is delivered with an instrument holder. Customers had expressed dissatisfaction over that they needed to use two hands during a biopsy procedure, which resulted in a project to develop a new instrument holder.The project aim was to create concepts for how the new instrument holder should be designed, with focus on the mechanics. The new instrument holder would build on the existing basic principle that the screw needle and the cannula were screwed into the tissue. The thesis work would result in a technical solution and a functional prototype of the chosen concept.To achieve this, a generic product development processes were used and began with a comprehensive literature review.

This exam paper has been a collaboration between the writers and SYSteam Utvecklingspartner in Huskvarna. The assignment was about finding a need for a mobile application, making a requirement specification document with design documents and parallel to this constructing a prototype. The assignment is summarized in the following questions:? How can companies in the forest industry benefit from mobile information technology?? How can a user centered perspective be used in the process of making the requirement specification document and the design documents?? How do guidelines for usability apply to a mobile application?Three visits to companies in the forest industry were made to find a need for mobile information technology solutions. After a small analysis of the different companies? problems and conditions the decision was to use Tenhults Impregneringsverk AB in the case study.We used the FA/SIM method in our job of finding the organization needs for change and the principles of User Centered Design in the work of constructing a prototype.The result of our work is a requirement specification with design documents and a prototype.

The company LightLift Esystems AB manufactures patented motorized lift systems for the illumination of halls with high ceilings. The company wants a new design for singular heavy lights in order to be more competitive.This project consists of the development of the new design under the requirements and specifications imposed by the company. The new design must support lights up to 300kg and keep the overall dimensions as low as possible without modifying the driving unit.This document contains all the designing steps followed to reach the final solution as well as the material selection, manufacturing process and assembly of all the parts that form it.The solution obtained shows to be very competitive with other alternative products, since this new design triples their maximum load capacity while the dimensions are very similar.In this context, the optical appearance was also very important to the company and so it was another main objective of this project. From an aesthetical point of view, the final solution proves to be very compact and versatile since it can either be hidden behind a false ceiling or covered by a plastic case that gives the design a very nice look.Finally, the solution achieved fulfils all the requirements and specification previously imposed. It is reliable, compact, cheap to manufacture, easy to assembly and it has a good optical appearance. .

At present Getinge can offer a new generation of trolleys that they produced in 2011. The trolley used to Getinge various autoclaves and has the primary task to help the user/sterilization personnel to transport shelves or baskets, with or without cargo, from a packing table to the autoclave. The purpose of this thesis has been to develop a primary solution how the docking process between Getinge trolleys and autoclaves can be improved. The work has in most part followed Fredy Olsson principle and primary construction method. The work has included product research, study visit and development of a Requirements specification, to satisfy Getinge, their clients and circumvention products requirements.