arXiv subjects

Kurt Schneider

Publications and source records attributed to Kurt Schneider.

40 records · Page 3Linked to original sources

arXiv2017

What Works Better? A Study of Classifying Requirements

Classifying requirements into functional requirements (FR) and non-functional ones (NFR) is an important task in requirements engineering. However, automated classification of requirements written in natural language is not straightforward, due to the variability of natural language and the absence of a controlled vocabulary. This paper investigates how automated classification of requirements into FR and NFR can be improved and how well several machine learning approaches work in this context. We contribute an approach for preprocessing requirements that standardizes and normalizes requirements before applying classification algorithms. Further, we report on how well several existing machine learning methods perform for automated classification of NFRs into sub-categories such as usability, availability, or performance. Our study is performed on 625 requirements provided by the OpenScience tera-PROMISE repository. We found that our preprocessing improved the performance of an existing classification method. We further found significant differences in the performance of approaches such as Latent Dirichlet Allocation, Biterm Topic Modeling, or Naive Bayes for the sub-classification of NFRs.

cs.SE↗

arXiv2014

Orchestration of Global Software Engineering Projects

Global software engineering has become a fact in many companies due to real necessity in practice. In contrast to co-located projects global projects face a number of additional software engineering challenges. Among them quality management has become much more difficult and schedule and budget overruns can be observed more often. Compared to co-located projects global software engineering is even more challenging due to the need for integration of different cultures, different languages, and different time zones - across companies, and across countries. The diversity of development locations on several levels seriously endangers an effective and goal-oriented progress of projects. In this position paper we discuss reasons for global development, sketch settings for distribution and views of orchestration of dislocated companies in a global project that can be seen as a "virtual project environment". We also present a collection of questions, which we consider relevant for global software engineering. The questions motivate further discussion to derive a research agenda in global software engineering.

cs.SE↗

arXiv2014

Supporting acceptance testing in distributed software projects with integrated feedback systems: Experiences and requirements

During acceptance testing customers assess whether a system meets their expectations and often identify issues that should be improved. These findings have to be communicated to the developers a task we observed to be error prone, especially in distributed teams. Here, it is normally not possible to have developer representatives from every site attend the test. Developers who were not present might misunderstand insufficiently documented findings. This hinders fixing the issues and endangers customer satisfaction. Integrated feedback systems promise to mitigate this problem. They allow to easily capture findings and their context. Correctly applied, this technique could improve feedback, while reducing customer effort. This paper collects our experiences from comparing acceptance testing with and without feedback systems in a distributed project. Our results indicate that this technique can improve acceptance testing if certain requirements are met. We identify key requirements feedback systems should meet to support acceptance testing.

cs.SE↗

arXiv2012

FLOW-Methode - Methodenbeschreibung zur Anwendung von FLOW

Information of many kinds is flowing in software projects and organizations. Requirements have to flow from the customer to the developers. Testers need to know the requirements as well. Boundary conditions and design decisions have to be at the right place at the right time. Information flow analysis with FLOW facilitates modeling of mode and route of the flow of information and experience independent of the development methodology. Experience often acts as a control factor, because experienced developers can process and route information more efficiently. Therefore, experience needs to be at the right place at the right time, too. However, most valuable experiences never get documented. Since information and experience is flowing in agile as well as in traditional environments, the FLOW method does not distinguish between agile and traditional, but only between how the flows are shaped. ---- In Softwareprojekten fließen vielerlei Informationen. Anforderungen müssen vom Kunden zu den Entwicklern gelangen. Auch Tester müssen die Anforderungen kennen. Randbedingungen und Entwurfsentscheidungen müssen zur rechten Zeit am rechten Ort sein. Die Informationsflussanalyse mit FLOW ermöglicht es, unabhängig von der Entwicklungsmethode zu modellieren, wie und auf welchem Wege Informationen und Erfahrungen fließen. Erfahrungen spielen dabei oft die Rolle von Steuergrößen, denn erfahrene Mitarbeiter können Informationen kompetenter bearbeiten und weiterleiten. Auch die Erfahrungen müssen in geeigneter Form zur rechten Zeit am rechten Ort sein. Viele Erfahrungen werden aber nie dokumentiert. Da Informationen und Erfahrungen sowohl in agilen als auch in traditionellen Umgebungen fließen müssen, wird in FLOW ein Modell aufgebaut, das nicht nach agil, traditionell oder anderen Bezeichnungen unterscheidet, sondern einzig danach, wie die Flüsse gestaltet sind.

cs.SE↗