Industrial experiences of organizing a hackathon to assess a device-centric cloud ecosystem The author of this thesis was the second author. He performed the research design, including data collection protocol and interview questions, together with the first author. He acted as the interviewer in all interviews with the other authors. The author of this thesis contributed to the main body of analysis and documenting the results. All the authors contributed in the writing and reviewing the paper.

An increasing number of organizations are interested in binding requirements and testing more closely together. Based on a series of practitioner interviews conducted in five Finnish organizations, this paper presents a set of good practices that can be applied to create a stronger link between requirements engineering and testing. These practices include early tester participation particularly in requirements reviews, setting up traceability policies, taking feature requests from testers into account, and linking testing personnel with requirement owners. Due to reported hardships in implementing complete test traceability to requirements, communication links between testers and requirement owners are suggested in order to overcome the deficiencies of document links.

No abstract

No abstract

No abstract

No abstract

Marketing experts emphasize that the creation of superior customer value is a key element for companies' success. Understanding how to create value for customers, however, is not trivial in practice. The purpose of this paper is to analyze the role of requirements engineering (RE) in customer value creation. The paper describes experiences gained from six Finnish companies that develop software-intensive products and services for global markets. In practice, the focus of RE activities is mainly on product features. Customer value creation is, however, more than developing a competitive set of product features. It is important for companies to understand customers' processes and develop solutions that support these processes. To enable practitioners to change the focus from feature development to customer value creation, we propose a set of RE practices.

No abstract