Search

The article explores an issue on a more technical end of design research which is conducted in industrial design programs in leading art and design universities, technical universities and software research programs in Europe. It presents a collection of papers that represents some of the best pieces of ongoing work in that field. The research aims to provide readers a map that would be helpful to understand the papers in terms relevant to a person with background in the social sciences. The writers have established a device, an artwork or an environment which is used as a kind of physical hypothesis to determine whether their theoretical work made sense.

The purpose of writing this Three Year Vision paper is threefold. Firstly, it briefly recaps the progress Semat has made thus far; secondly, it lays out the future directions for people working actively within the Semat community; thirdly, it provides the background for seeking funding support from agencies, such as the European Community and the like. Funding support is necessary to sustain the ongoing activities of Semat and its growth into a broader community effort, as most people working within Semat are volunteers. As such, the paper may be both too much and too little for the wider supporter base. However, we intend to make our work fully transparent, hence, we publish it widely. We seek feedback and comments from supporters and signatories in order to improve the vision. In this context, other companion papers are being written to better address the specific needs for the practitioners, the industry and the academia. [ABSTRACT FROM AUTHOR]

Requirements engineering has been recognized as a fundamental phase of the software engineering process. Nevertheless, the elicitation and analysis of requirements are often left aside in favor of architecture-driven software development. This tendency, however, can lead to issues that may affect the success of a project. This paper presents our experience gained in the elicitation and analysis of requirements in a large-scale security-oriented European research project, which was originally conceived as an architecture-driven project. In particular, we illustrate the challenges that can be faced in large-scale research projects and consider the applicability of existing best practices and off-the-shelf methodologies with respect to the needs of such projects. We then discuss how those practices and methods can be integrated into the requirements engineering process and possibly improved to address the identified challenges. Finally, we summarize the lessons learned from our experience and the benefits that a proper requirements analysis can bring to a project. [ABSTRACT FROM AUTHOR]