Time filter

Source Type

Riegel N.,Fraunhofer Institute for Experimental Software Engineering
2012 20th IEEE International Requirements Engineering Conference, RE 2012 - Proceedings | Year: 2012

Requirements engineers in business-process-driven software development are faced with the challenge of letting stakeholders determine which requirements are actually relevant for early business success and should be considered first or even at all during the elicitation and analysis activities. In the area of requirements engineering (RE) and release planning, prioritization is an established strategy for achieving this goal. Available prioritization approaches, however, do not consider all idiosyncrasies of business-process- driven software development. This lack of appropriate prioritization leads to effort often being spent on (RE) activities of minor importance. To support the requirements engineer in overcoming this problem, the idea of applying different models during prioritization is introduced, which shall bring it to a more reliable basis. Through this notion it is expected to reduce unnecessary (RE) activities by focusing on the most important requirements. © 2012 IEEE.

John I.,Fraunhofer Institute for Experimental Software Engineering
IEEE Software | Year: 2010

Product line scoping is the process of determining which of an organization's products, features, and domains would find systematic reuse economically useful. Scoping is generally the first phase in product line engineering. For a decade, it has been recognized as its own discipline in product line engineering. Scoping, also called product line planning, is based on expert knowledge and information; in meetings and workshops, individuals must interactively elicit information on the features, products, and further plans in the expert's product line domain. But often, these domain experts don't have the time to really reproduce and formulate all the knowledge needed for scoping. They should be heavily integrated into the scoping knowledge elicitation process, but they're only minimally available. The CAVE (Commonality and Variability Extraction) approach and its industrial applications offer a solution to the problem of domain experts' availability. CAVE supports scoping and product line engineering in a development organization by systematically eliciting the needed information from user documentation of existing systems. This article describes the approach and its embedding in scoping, as well as results and lessons learned from three industrial applications of the approach. © 2010 IEEE.

Tanveer B.,Fraunhofer Institute for Experimental Software Engineering
Lecture Notes in Business Information Processing | Year: 2016

Unlike traditional software development approaches, Agile embraces change. The resulting dynamism of requirements makes it challenging to estimate effort accurately. Current practice relies on expertjudgment that can be biased, labor intensive and inaccurate. Therefore, a systematic yet lightweight effort estimation methodology is needed to support expert judgment and improve its effectiveness. Such an approach will utilize the quantification of the impact of a requirement on software artifacts potentially affected by it. It will further introduce an explicit consideration of effort drivers that contribute to effort overhead. The aim is to synthesize research from three often orthogonal areas of research: (1) change impact analysis, (2) effort estimation (model and expert driven) and (3) software visualization. Hence, resulting in a hybrid methodology with tool support that incorporates expert knowledge, change impact analysis and enables an explicit consideration of cost drivers by experts to improve the effectiveness of effort estimation process. © The Author(s) 2016.

Adler R.,Fraunhofer Institute for Experimental Software Engineering
SAE Technical Papers | Year: 2013

A safety concept describes a plan for implementing safety. A bad safety concept compromises the achievement of safety or leads to unnecessarily high costs for implementing and proving safety. However, safety standards and research approaches do not provide any means for developing a good safety concept or for assessing the quality of a safety concept. Consequently, real-world safety concepts often lack information or have low quality. To overcome this practical problem, we systematically derive which fundamental information should be contained in a safety concept and introduce quality attributes for a safety concept. We also evaluate state-of-the-art approaches for developing a safety concept. Copyright © 2013 SAE International.

Gotzhein R.,University of Kaiserslautern | Kuhn T.,Fraunhofer Institute for Experimental Software Engineering
Computer Networks | Year: 2011

In this paper, we present Black Burst Synchronization (BBS), a modular protocol for multi-hop tick and time synchronization in wireless ad hoc networks, located at MAC level. For the successful operation of BBS, it is crucial that collisions of synchronization messages that are sent (almost) simultaneously by two or more nodes are non-destructive. This is achieved by collision-protected bit encodings with black bursts, periods of transmission energy of defined length on the medium, starting at determined points in time. Under reasonable assumptions, BBS provides low and bounded tick and clock offsets, guarantees a very small and constant convergence delay, has low and bounded complexity regarding computation, storage, time, and structure, and is robust against topology changes at runtime. This makes it a candidate for user level applications such as data fusion and networked control systems, and especially for system level tasks such as duty cycling and multi-hop medium slotting. To validate its predicted behavior, we have implemented and deployed BBS on MICAz motes. © 2011 Elsevier B.V. All rights reserved.

Discover hidden collaborations