Reliability factors in business software: volatility, requirements and end-users

Many business-oriented software applications are subject to frequent changes in requirements. This paper shows that, ceteris paribus, increases in the volatility of system requirements decrease the reliability of software. Further, systems that exhibit high volatility during the development phase are likely to have lower reliability during their operational phase. In addition to the typically higher volatility of requirements, end-users who specify the requirements of business-oriented systems are usually less technically oriented than people who specify the requirements of compilers, radar tracking systems or medical equipment. Hence, the characteristics of software reliability problems for business-oriented systems are likely to differ significantly from those of more technically oriented systems.

End User Perspective to ERP Implementation

Toiminnanohjausjärjestelmät ovat oleellinen osa yrityksien liiketoimintaa. Järjestelmän päivittäminen uudempaan versioon tai kokonaan uuden järjestelmän käyttöönotto saattavat yrityksen ydintoiminnot ja prosessit hyvin haavoittuvaiseen asemaan. Järjestelmien kokonaisvaltaisuus yhdessä reaaliaikaisen käyttöönoton kanssa tekevät näistä projekteista erityisen haasteellisia. Tämä pro gradu -tutkielman tapaustutkimuskohteena toimi Andritz Oy. Tapaustutkimuksen tavoitteena oli arvioida kesäkuussa 2005 suoritettua toiminnanohjausjärjestelmän käyttöönottoa ja sitä kuinka hyvin tässä onnistuttiin. Tutkimus toteutettiin loppukäyttäjännäkökulmasta. Loppukäyttäjä omalla työllään voi vaikuttaa miten hyvin järjestelmästä tavoitellut hyödyt pystytään lunastamaan. Tutkimus on laadullinen tapaustutkimus. Tutkimuksessa kiinnitetään huomiota erityisestiprojektitiimin, johdon ja käyttäjien eroaviin näkemyksiin käyttöönoton onnistumisesta.

Are Evaluation of ICTs Investment Using Decision Support Systems:Case Applications from Distributor's and End User's Perspective Group Decision

The evaluation of investments in advanced technology is one of the most important decision making tasks. The importance is even more pronounced considering the huge budget concerning the strategic, economic and analytic justification in order to shorten design and development time. Choosing the most appropriate technology requires an accurate and reliable system that can lead the decision makers to obtain such a complicated task. Currently, several Information and Communication Technologies (ICTs) manufacturers that design global products are seeking local firms to act as their sales and services representatives (called distributors) to the end user. At the same time, the end user or customer is also searching for the best possible deal for their investment in ICT's projects. Therefore, the objective of this research is to present a holistic decision support system to assist the decision maker in Small and Medium Enterprises (SMEs) - working either as individual decision makers or in a group - in the evaluation of the investment to become an ICT's distributor or an ICT's end user. The model is composed of the Delphi/MAH (Maximising Agreement Heuristic) Analysis, a well-known quantitative method in Group Support System (GSS), which is applied to gather the average ranking data from amongst Decision Makers (DMs). After that the Analytic Network Process (ANP) analysis is brought in to analyse holistically: it performs quantitative and qualitative analysis simultaneously. The illustrative data are obtained from industrial entrepreneurs by using the Group Support System (GSS) laboratory facilities at Lappeenranta University of Technology, Finland and in Thailand. The result of the research, which is currently implemented in Thailand, can provide benefits to the industry in the evaluation of becoming an ICT's distributor or an ICT's end user, particularly in the assessment of the Enterprise Resource Planning (ERP) programme. After the model is put to test with an in-depth collaboration with industrial entrepreneurs in Finland and Thailand, the sensitivity analysis is also performed to validate the robustness of the model. The contribution of this research is in developing a new approach and the Delphi/MAH software to obtain an analysis of the value of becoming an ERP distributor or end user that is flexible and applicable to entrepreneurs, who are looking for the most appropriate investment to become an ERP distributor or end user. The main advantage of this research over others is that the model can deliver the value of becoming an ERP distributor or end user in a single number which makes it easier for DMs to choose the most appropriate ERP vendor. The associated advantage is that the model can include qualitative data as well as quantitative data, as the results from using quantitative data alone can be misleading and inadequate. There is a need to utilise quantitative and qualitative analysis together, as can be seen from the case studies.

Assessment of critical competences required in managing end-user driven businesses in a global forest products compa

Työn pääasiallisena tavoitteena on selvittää ydinosaamista, jota tarvitaan kansainvälisen metsäteollisuusyrityksen loppukäyttäjävetoisessa liiketoiminnassa. Lisäksi tavoitteena on laatia kompetenssimalli, jota voidaan käyttää mm. rekrytoinnissa, koulutuksen ja työnkierron suunnittelussa. Tarkoituksena on tarkastella sekä tällä hetkellä että tulevaisuudessa tarvittavia ydinosaamisia. Työ keskittyy myyntihenkilöiden kompetenssien kuvaamiseen. Kirjallisuuden ja asiantuntijoiden haastattelujen avulla on selvitetty. kompetensseihin liittyviä asioita ja käsitteitä, kuten organisaation oppiminen, innovaatiot sekä asiakaslähtöisyys. Tämän jälkeen on kartoitettu case-yrityksen kartonkiyksikön myyntihenkilökunnan kompetensseja. Kompetenssikartoitus on tehty teemahaastattelujen avulla sekä lisäksi on käytetty työn aikana laadittua kompetenssimatriisia. Saatuja tuloksia on verrattu yhden asiakkaan näkemyksiin. Tulosten mukaan kolme tärkeintä tämän hetken kompetenssia ovat: holistinen näkemys asioista, suhteiden rakentaminen ja kielitaito. Tulevaisuuden tärkeimpiä kompetensseja puolestaan ovat: asiakaslähtöisyys, sähköinen kaupankäynti ja suhteiden rakentaminen. Lopuksi on käsitelty yleisiä metsäteollisuuden tulevaisuuden haasteita sekä annettu joitain kehitysideoita kompetenssien kehittämistä varten.

Personal Liberty in Psychiatric Care - Towards Service User Involvement

This study explores personal liberty in psychiatric care from a service user involvement perspective. The data were collected in four phases during the period 2000-2006 in psychiatric settings in Finland. Firstly, patient satisfaction and factors associated with user involvement were studied (n = 313). Secondly, patients’ experiences of deprivation of their liberty were explored (n = 51). Thirdly, an overview on patients’ options for lodging complaints was conducted, and all complaints (n = 4645) lodged in Finland from 2000 to 2004 were examined. Fourthly, the effects of different patient education methods on inpatients’ experiences of deprivation of liberty were tested (n = 311). It emerged that patients were quite satisfied, but reported dissatisfaction in restrictions, compulsory care and information dissemination. Patients experienced restrictions on leaving the ward and on communication, confiscation of property and coercive measures as deprivation of liberty. Patients’ experienced these interventions to be negative. In Finland, the patient complaint process is complicated and not easily accessible. In general, patient complaints increased considerably in Finland during the study period. In psychiatric care the number of complaints was quite stable and complaints led more seldom to consequences. An Internet-based patient education system was equivalent with traditional education and treatment as usual in supporting personal liberty during hospital care. This dissertation provides new information about the realization of patients' rights in psychiatric care. In order to improve patients' involvement, systematic methods to increase personal liberty during care need to be developed, the procedures for patients lodging complaints should be simplified, and patients' access to information needs to be ensured using multiple methods.

Evaluating End-User Training Effectiveness in ERP System Implementation

Today’s business world demands more and more internal and external integration and transparency among companies at all fields. Integrated ERP (enterprise resource planning) systems offer a possibility to improve business practices and procedures by providing a unified view on the business including all functions and departments. Due to the obvious benefits, the popularity of integrated ERP systems keeps growing. The implementation of ERP systems has however proven risky. The implementation projects tend to be long, extensive, and costly – and often they end up in a failure. Due to the significant task and role changes ERP implementation brings to almost everybody in the company, training has been identified as one of the most critical success factors of an ERP implementation. To ensure that the training is conducted in the most effective and successful manner, the training outcomes should be evaluated. So far, training evaluation has however gained only limited attention at most companies investing in different training programs. Uponor corporation has initiated a large ERP implementation and process harmonization program in 2004. Thousands of end-users have been trained during this project so far, and the work still continues until the project is completed in 2010. In this thesis, the evaluation of end-user training in Uponor’s ERP program is brought further from the current state of performing the basic participant satisfaction survey in the end of each class. The results show that in order to reach reliable training effectiveness evaluation results, not only the reaction towards training but also transfer of skills and attitudes and the final results of the training program should be evaluated.

Virtual communities : a virtual treasure trove for end-user developers

End-user development is a very common but often largely overlooked phenomenon in information systems research and practice. End-user development means that regular people, the end-users of software, and not professional developers are doing software development. A large number of people are directly or indirectly impacted by the results of these non-professional development activities. The numbers of users performing end-user development activities are difficult to ascertain precisely. But it is very large, and still growing. Computer adoption is growing towards 100% and many new types of computational devices are continually introduced. In addition, other devices not previously programmable are becoming so. This means that, at this very moment, hundreds of millions of people are likely struggling with development problems. Furthermore, software itself is continually being adapted for more flexibility, enabling users to change the behaviour of their software themselves. New software and services are helping to transform users from consumers to producers. Much of this is now found on-line. The problem for the end-user developer is that little of this development is supported by anyone. Often organisations do not notice end-user development and consequently neither provide support for it, nor are equipped to be able to do so. Many end-user developers do not belong to any organisation at all. Also, the end-user development process may be aggravating the problem. End-users are usually not really committed to the development process, which tends to be more iterative and ad hoc. This means support becomes a distant third behind getting the job done and figuring out the development issues to get the job done. Sometimes the software itself may exacerbate the issue by simplifying the development process, deemphasising the difficulty of the task being undertaken. On-line support could be the lifeline the end-user developer needs. Going online one can find all the knowledge one could ever need. However, that does still not help the end-user apply this information or knowledge in practice. A virtual community, through its ability to adopt the end-user’s specific context, could surmount this final obstacle. This thesis explores the concept of end-user development and how it could be supported through on-line sources, in particular virtual communities, which it is argued here, seem to fit the end-user developer’s needs very well. The experiences of real end-user developers and prior literature were used in this process. Emphasis has been on those end-user developers, e.g. small business owners, who may have literally nowhere to turn to for support. Adopting the viewpoint of the end-user developer, the thesis examines the question of how an end-user could use a virtual community effectively, improving the results of the support process. Assuming the common situation where the demand for support outstrips the supply.

An Empirical Study of Fault Localization for End-User Programmers

End users develop more software than any other group of programmers, using software authoring devices such as e-mail filtering editors, by-demonstration macro builders, and spreadsheet environments. Despite this, there has been little research on finding ways to help these programmers with the dependability of their software. We have been addressing this problem in several ways, one of which includes supporting end-user debugging activities through fault localization techniques. This paper presents the results of an empirical study conducted in an end-user programming environment to examine the impact of two separate factors in fault localization techniques that affect technique effectiveness. Our results shed new insights into fault localization techniques for end-user programmers and the factors that affect them, with significant implications for the evaluation of those techniques.

Helping End-User Programmers “Engineer” Dependable Software

Not long ago, most software was written by professional programmers, who could be presumed to have an interest in software engineering methodologies and in tools and techniques for improving software dependability. Today, however, a great deal of software is written not by professionals but by end-users, who create applications such as multimedia simulations, dynamic web pages, and spreadsheets. Applications such as these are often used to guide important decisions or aid in important tasks, and it is important that they be sufficiently dependable, but evidence shows that they frequently are not. For example, studies have shown that a large percentage of the spreadsheets created by end-users contain faults, and stories abound of spreadsheet faults that have led to multi-million dollar losses. Despite such evidence, until recently, relatively little research had been done to help end-users create more dependable software.

Using Source-Code Analysis to Help End-user Programmers Create Dependable Software

Not long ago, most software was written by professional programmers, who could be presumed to have an interest in software engineering methodologies and in tools and techniques for improving software dependability. Today, however, a great deal of software is written not by professionals but by end-users, who create applications such as multimedia simulations, dynamic web pages, and spreadsheets. Applications such as these are often used to guide important decisions or aid in important tasks, and it is important that they be sufficiently dependable, but evidence shows that they frequently are not. For example, studies have shown that a large percentage of the spreadsheets created by end-users contain faults. Despite such evidence, until recently, relatively little research had been done to help end-users create more dependable software. We have been working to address this problem by finding ways to provide at least some of the benefits of formal software engineering techniques to end-user programmers. In this talk, focusing on the spreadsheet application paradigm, I present several of our approaches, focusing on methodologies that utilize source-code-analysis techniques to help end-users build more dependable spreadsheets. Behind the scenes, our methodologies use static analyses such as dataflow analysis and slicing, together with dynamic analyses such as execution monitoring, to support user tasks such as validation and fault localization. I show how, to accommodate the user base of spreadsheet languages, an interface to these methodologies can be provided in a manner that does not require an understanding of the theory behind the analyses, yet supports the interactive, incremental process by which spreadsheets are created. Finally, I present empirical results gathered in the use of our methodologies that highlight several costs and benefits trade-offs, and many opportunities for future work.

Analysis and Transformation of Pipe-like Web Mashups for End User Programmers

Mashups are becoming increasingly popular as end users are able to easily access, manipulate, and compose data from several web sources. To support end users, communities are forming around mashup development environments that facilitate sharing code and knowledge. We have observed, however, that end user mashups tend to suffer from several deficiencies, such as inoperable components or references to invalid data sources, and that those deficiencies are often propagated through the rampant reuse in these end user communities. In this work, we identify and specify ten code smells indicative of deficiencies we observed in a sample of 8,051 pipe-like web mashups developed by thousands of end users in the popular Yahoo! Pipes environment. We show through an empirical study that end users generally prefer pipes that lack those smells, and then present eleven specialized refactorings that we designed to target and remove the smells. Our refactorings reduce the complexity of pipes, increase their abstraction, update broken sources of data and dated components, and standardize pipes to fit the community development patterns. Our assessment on the sample of mashups shows that smells are present in 81% of the pipes, and that the proposed refactorings can reduce that number to 16%, illustrating the potential of refactoring to support thousands of end users developing pipe-like mashups.