Systems development methods and usability in Norway: An industrial perspective

This is the post-print version of the Article. The official published version can be accessed from the link below - Copyright @ 2007 Springer Berlin HeidelbergThis paper investigates the relationship between traditional systems development methodologies and usability, through a survey of 78 Norwegian IT companies. Building on previous research we proposed two hypotheses; (1) that software companies will generally pay lip service to usability, but do not prioritize it in industrial projects, and (2) that systems development methods and usability are perceived as not being integrated. We find support for both hypotheses. Thus, the use of systems development methods is fairly stable, confirming earlier research. Most companies do not use a formal method, and of those who do, the majority use their own method. Generally, the use of methods is rather pragmatic: Companies that do not use formal methods report that they use elements from such methods. Further, companies that use their own method import elements from standardised methods into their own

Software development methods and usability: Perspectives from a survey in the software industry in Norway

This paper investigates the relationship between traditional software development methodologies and usability. The point of departure is the assumption that two important disciplines in software development, one of software development methods (SDMs) and one of usability work, are not integrated in industrial software projects. Building on previous research we investigate two questions; (1) Will software companies generally acknowledge the importance of usability, but not prioritise it in industrial projects? and (2) To what degree are software development methods and usability perceived by practitioners as being integrated? To this end a survey in the Norwegian IT industry was conducted. From a sample of 259 companies we received responses from 78 companies. In response to our first research question, our findings show that although there is a positive bias towards usability, the importance of usability testing is perceived to be much less than that of usability requirements. Given the strong time and cost pressures associated with the software industry, we believe that these results highlight that there is a gap between intention and reality. Regarding our second research question our survey revealed that companies perceive usability and software development methods to be integrated. This is in contrast to earlier research, which, somewhat pessimistically, has argued for the existence of two different cultures, one of software development and one of usability. The findings give hope for the future, in particular because the general use of system development methods are pragmatic and adaptable

Inter-organizational learning in drifting environments - Experiences from a multi-firm software development project

This paper examines conditions under which organizations can acquire and profitably utilise knowledge generated in joint product development ventures. Past research states that such learning depends on relationships between knowledge accumulation at the level of joint venture and the evolution of knowledge structures in the wider organizational environment. An important argument of this paper is that such relationships might drift abruptly due to unforeseen events taking place during project operation, creating new challenges and opportunities for learning. Drawing upon previous research on project-based learning, the paper proposes a model of interorganizational learning aimed to help managers and researchers visualising links between drift and learning in distributed project contexts. The paper illustrates and assesses the empirical relevance of the analytical framework through a case study of a multi-firm product development project in the European software industry.

Selection of third party software in Off-The-Shelf-based software development: an interview study with industrial practitioners

The success of software development using third party components highly depends on the ability to select a suitable component for the intended application. The evidence shows that there is limited knowledge about current industrial OTS selection practices. As a result, there is often a gap between theory and practice, and the proposed methods for supporting selection are rarely adopted in the industrial practice. This paper's goal is to investigate the actual industrial practice of component selection in order to provide an initial empirical basis that allows the reconciliation of research and industrial endeavors. The study consisted of semi-structured interviews with 23 employees from 20 different software-intensive companies that mostly develop web information system applications. It provides qualitative information that help to further understand these practices, and emphasize some aspects that have been overlooked by researchers. For instance, although the literature claims that component repositories are important for locating reusable components; these are hardly used in industrial practice. Instead, other resources that have not received considerable attention are used with this aim. Practices and potential market niches for software-intensive companies have been also identified. The results are valuable from both the research and the industrial perspectives as they provide a basis for formulating well-substantiated hypotheses and more effective improvement strategies.Peer ReviewedPostprint (author's final draft

Understanding the perception of very small software companies towards the adoption of process standards

This paper is concerned with understanding the issues that affect the adoption of software process standards by Very Small Entities (VSEs), there needs from process standards and there willingness to engage with the new ISO/IEC 29110 standard in particular. In order to achieve this goal, a series of industry data collection studies were undertaken with a collection of VSEs. A twin track approach of a qualitative data collection (interviews and focus groups) and quantitative data collection (questionnaire), with data analysis being completed separately and finally results merged, using the coding mechanisms of grounded theory. This paper serves as a roadmap for both researchers wishing to understand the issues of process standards adoption by very small companies and also for the software process standards community

OSS integration issues and community support: an integrator perspective

The reuse and integration of Open Source Software (OSS) components provided by OSS communities is becoming an economical and strategic need for today’s organizations. The integration of OSS components provides many benefits, but also risks and challenges. One of the most important risks is the lack of effective and timely OSS community support for dealing with possible integration problems. For gaining an understanding of the common problems that organizations face when integrating OSS components, and the role played by OSS communities, we performed an exploratory study on 25 OSS integration projects from different European organizations. The results show that the main way of reducing integration problems was the use of OSS components from well-established communities; therefore very few integration problems were identified. In most of the cases these problems were successfully solved with the support from the OSS community and/or colleagues. In addition, contrary to the common belief that understanding code from someone else is a hard and undesirable task, some integrators consider OSS code even more understandable than their own code.Peer ReviewedPostprint (author's final draft

European Information System for Organic Markets (EISFOM QLK5-2002-02400): WP 2: “Data collection and processing systems (DCPS) for the conventional markets” and WP 3: “Data collection and processing systems for organic markets” = Deliverable D2

European markets for organic products are developing fast. In Europe, as other parts of the world, more and more farm land is being converted to organic production. In order to adjust production and consumption levels, detailed market information is needed, especially where decisions with a long-term impact need to be taken, for example on converting specific land or livestock enterprises requiring high levels of investment in glasshouses, housing, processing facilities etc. Since public subsidies (regional / national / European) are heavily involved in these investments, valid, accurate and up-to-date information is essential not only for farmers and growers, but also for policy-makers, consultants, processing industry etc. EU-research projects such as OFCAP (FAIR3-CT96-1794) and OMIaRD (QLK5-2000-01124) have shown that regional or national data gathering takes place in many countries, but often only very basic data are reported, such as certified organic holdings, land areas and livestock numbers. Important market data, e.g. the amount of production, consumption, international trade or producer and consumer prices, do not exist in most European countries. In some European countries there are only rough estimates of the levels of production and consumption. There is no standardization and data are seldom comparable. Furthermore, detailed information on specific commodities is missing. Hence, investment decisions are taken under conditions of great uncertainty. Likewise, if politicians want to support organic agriculture, they do not know whether it would be better to support production or consumption or to address problems in the marketing channel. The EU concerted action EISfOM (QLK5-2002-02400) (European Information System for Organic Markets) is attempting to take the first steps in solving these problems. The aim of this concerted action is to build up a framework for reporting valid and reliable data for relevant production and market sectors of the European organic sector in order to meet the needs of policy-makers, farmers, processors, wholesalers and other actors involved in organic markets. In order to reach this aim, this action was split into several workpackages. This report describes the approach and results of workpackages 2 and 3. In this first chapter the objective and general approach of these work packages are described. Chapters 2 and 3 provide an overview of international statistics and data collection systems within the food supply chain at the public and the private level. Chapter 4 describes national statistics and data collection systems within the food supply chain. In Chapter 5, an analysis and appraisal is made of the results with regard to organic data collection and processing systems (DCPSs) and their integration into existing common DCPSs. Chapter 6 draws several general conclusions. Two substantial annexes complete the report, one with the country reports on the situation of data collection and processing in all investigated countries and the other with the first and the second stage questionnaires covering the different data collection levels

What influences the speed of prototyping? An empirical investigation of twenty software startups

It is essential for startups to quickly experiment business ideas by building tangible prototypes and collecting user feedback on them. As prototyping is an inevitable part of learning for early stage software startups, how fast startups can learn depends on how fast they can prototype. Despite of the importance, there is a lack of research about prototyping in software startups. In this study, we aimed at understanding what are factors influencing different types of prototyping activities. We conducted a multiple case study on twenty European software startups. The results are two folds, firstly we propose a prototype-centric learning model in early stage software startups. Secondly, we identify factors occur as barriers but also facilitators for prototyping in early stage software startups. The factors are grouped into (1) artifacts, (2) team competence, (3) collaboration, (4) customer and (5) process dimensions. To speed up a startups progress at the early stage, it is important to incorporate the learning objective into a well-defined collaborative approach of prototypingComment: This is the author's version of the work. Copyright owner's version can be accessed at doi.org/10.1007/978-3-319-57633-6_2, XP2017, Cologne, German