3Gsim is a load generator for traffic simulation in a WCDMA (WidebandCode Division Multiple Access) network. It is developed at Ericsson AB inLinköping. Tests are run daily and the results are evaluated by testers. Whenerrors or abnormalities are found, the testers write trouble reports and thedescribed problems are handed over to designers whose task is to fix them.In order to save time, Ericsson wished to improve the efficiency.This study has focused on a specific part of the process of the developmentof 3Gsim, namely the process of evaluating test results. The goal has beento investigate if and how the process of evaluating 3Gsim test results can bemade more efficient.The daily work of the testers has been studied at close hand by the author.The testers answered a questionnaire with questions about their work andtheir opinions about the tools being used. The answers were evaluated andfocus was laid on the main problems.It was found that a lot of time is wasted on searching for trouble reports.A big part of the test result evaluation process consists of going throughsummary logs with error print-outs. Unfortunately no mapping betweenerror print-outs and trouble reports is performed. When going through thesummary logs the testers have to determine which errors have already beenreported and which ones that haven’t. Another major problem is the factthat most tests fail. On the webpage where the test results are displayed,this is indicated by a coloured field showing red. This is believed to have anegative effect on the work attitude.A lot of time can be saved by mapping error print-outs to trouble reportsand automatically comparing new error print-outs with old ones. The mappingwill also help preventing the creation of duplicated trouble reports. Thissolution will have the greatest impact on the improvement of the efficiency.Another way to enhance the efficiency is to develop a more advanced colourcoding scheme than the one used today. This coding scheme will help thetesters making the right priorities when processing the test results. Furthermore,these two solutions will have a positive effect on the work attitude. Aprototype implementing the first solution has been created. This prototypegives Ericsson AB the possibility to test the solution idea in practice.

No description available.

<p>Computer errors are a constant problem for software providers. To completely avoid bugs has proven very difficult even though computer software goes through rigorous testing before released. One of the challenges for developers is recreating errors that end-users experience. User-submitted error reports can often be of help for developers to localize and fix bugs. However, the reports often vary in quality depending on the user's experience and the effort they put into writing the report. Instead of relying on manual error reports, some software providers have equipped their software with automated error reporting functionality. These programs are set to collect important information about the computer and the software in the event of a crash. There are pros and cons with both automated and manual error reporting.</p><p>The research that has previously been done in the field of error reporting has mostly focused on the situation where private persons are senders and corporations are receivers. This report addresses the setting where both parties are corporations, which brings several new aspects to the problem. The five main topics this report focuses on are: customer attitude, which data to send, privacy, user interaction and feedback. A study has been conducted at the ERP system provider IFS in Sweden where interviews with employees and customers have been performed. Interviewees in the customer companies have been primarily ERP and application managers. The results of the study show that companies are less concerned than what the literature suggests even though the attitudes differ some depending on line of business. Conclusions are that a high degree of configurability of what is sent in the error reports and the level of user interaction is needed for companies to accept automated error reporting.</p> / <p>Buggar är ett ständigt problem för mjukvarutillverkare. Att helt undvika dessa har visat sig vara mycket svårt trots rigorösa tester innan ny mjukvara släpps. En av utmaningarna för utvecklare är att återskapa felen som uppstår hos användarna. Felrapporter inskickade av användare kan ofta vara till hjälp för utvecklare när de ska lokalisera och åtgärda fel. Men rapporterna kan variera i kvalitet beroende på användarnas erfarenhet och tiden de lägger på att skriva rapporten. Istället för att förlita sig på manuella felrapporter har vissa mjukvarutillverkare utrustat sin programvara med funktionalitet för automatiska felrapporter. Dessa program ska samla in viktig information om datorn och programvaran i händelse av att en krasch uppstår.</p><p>Viss forskning har skett inom området automatiserad felrapportering men fokus har då legat på situationen då privatpersoner är avsändare och företag är mottagare. Denna rapport behandlar läget då båda parter är företag, vilket tillför flera nya aspekter till problemet. De fem huvudfrågorna som den här rapporten fokuserar på är: kunders attityd, vilken data ska skickas, integritet, användarinteraktion och feedback. En studie har utförts hos affärssystemleverantören IFS i Sverige, där intervjuer med anställda och kunder har genomförts. De intervjuade hos kundföretagen har huvudsakligen varit ERP- och applikationsansvariga. Resultaten av studien visar att företagen är mindre oroade än vad litteraturen indikerar även om attityderna skiljer sig något i olika branscher. Slutsatserna är att en hög grad av konfigurerbarhet behövs när det gäller vad som skickas i felrapporter samt vilken grad av interaktion med användaren som behövs. Detta för att kundföretagen ska acceptera automatisk felrapportering.</p>

Computer errors are a constant problem for software providers. To completely avoid bugs has proven very difficult even though computer software goes through rigorous testing before released. One of the challenges for developers is recreating errors that end-users experience. User-submitted error reports can often be of help for developers to localize and fix bugs. However, the reports often vary in quality depending on the user's experience and the effort they put into writing the report. Instead of relying on manual error reports, some software providers have equipped their software with automated error reporting functionality. These programs are set to collect important information about the computer and the software in the event of a crash. There are pros and cons with both automated and manual error reporting. The research that has previously been done in the field of error reporting has mostly focused on the situation where private persons are senders and corporations are receivers. This report addresses the setting where both parties are corporations, which brings several new aspects to the problem. The five main topics this report focuses on are: customer attitude, which data to send, privacy, user interaction and feedback. A study has been conducted at the ERP system provider IFS in Sweden where interviews with employees and customers have been performed. Interviewees in the customer companies have been primarily ERP and application managers. The results of the study show that companies are less concerned than what the literature suggests even though the attitudes differ some depending on line of business. Conclusions are that a high degree of configurability of what is sent in the error reports and the level of user interaction is needed for companies to accept automated error reporting. / Buggar är ett ständigt problem för mjukvarutillverkare. Att helt undvika dessa har visat sig vara mycket svårt trots rigorösa tester innan ny mjukvara släpps. En av utmaningarna för utvecklare är att återskapa felen som uppstår hos användarna. Felrapporter inskickade av användare kan ofta vara till hjälp för utvecklare när de ska lokalisera och åtgärda fel. Men rapporterna kan variera i kvalitet beroende på användarnas erfarenhet och tiden de lägger på att skriva rapporten. Istället för att förlita sig på manuella felrapporter har vissa mjukvarutillverkare utrustat sin programvara med funktionalitet för automatiska felrapporter. Dessa program ska samla in viktig information om datorn och programvaran i händelse av att en krasch uppstår. Viss forskning har skett inom området automatiserad felrapportering men fokus har då legat på situationen då privatpersoner är avsändare och företag är mottagare. Denna rapport behandlar läget då båda parter är företag, vilket tillför flera nya aspekter till problemet. De fem huvudfrågorna som den här rapporten fokuserar på är: kunders attityd, vilken data ska skickas, integritet, användarinteraktion och feedback. En studie har utförts hos affärssystemleverantören IFS i Sverige, där intervjuer med anställda och kunder har genomförts. De intervjuade hos kundföretagen har huvudsakligen varit ERP- och applikationsansvariga. Resultaten av studien visar att företagen är mindre oroade än vad litteraturen indikerar även om attityderna skiljer sig något i olika branscher. Slutsatserna är att en hög grad av konfigurerbarhet behövs när det gäller vad som skickas i felrapporter samt vilken grad av interaktion med användaren som behövs. Detta för att kundföretagen ska acceptera automatisk felrapportering.

The thesis deals with the design and creation of a system for recording and reporting error states of cooling devices on the principle of a compressor heat pump. An important element of the concept of the entire monitoring system is a built-in platform based on the ESP32 microcontroller for evaluating data measured by sensors. Another key element is the communication module, which sends measured data via GPRS in the form of MQTT messages to the service web application. The application receives, evaluates and records measured data. Subsequently are measured data and evaluated error states presented to the user in the form of tables and interactive graphs.

Indiana University-Purdue University Indianapolis (IUPUI) / This qualitative study was successful in utilization of grounded theory methodology to ascertain nurses’ decision-making processes following their awareness of having made a medical error, as well as how and/or if they corrected and reported the error. Significant literature documents the existence of medical errors; however, this unique study interviewed thirty nurses from adult intensive care units seeking to discover through a detailed interview process their individual stories and experiences, which were then analyzed for common themes. Common themes led to the development of a theoretical model of thought processes regarding error reporting when nurses made an error. Within this theoretical model are multiple processes that outline a shared, time-orientated sequence of events nurses encounter before, during, and after an error. One common theme was the error occurred during a busy day when they had been doing something unfamiliar. Each nurse expressed personal anguish at the realization she had made an error, she sought to understand why the error happened and what corrective action was needed. Whether the error was reported on or told about depended on each unit’s expectation and what needed to be done to protect the patient. If there was no perceived patient harm, errors were not reported. Even for reported errors, no one followed-up with the nurses in this study. Nurses were left on their own to reflect on what had happened and to consider what could be done to prevent error recurrence. The overall impact of the process of and the recovery from the error led to learning from the error that persisted throughout her nursing career. Findings from this study illuminate the unique viewpoint of licensed nurses’ experiences with errors and have the potential to influence how the prevention of, notification about and resolution of errors are dealt with in the clinical setting. Further research is needed to answer multiple questions that will contribute to nursing knowledge about error reporting activities and the means to continue to improve error-reporting rates