Nina Dzamashvili-Fogelström

Learn More
Software inspection is an effective method to detect faults in software artefacts. Several empirical studies have been performed on reading techniques, which are used in the individual preparation phase of software inspections. Besides new experiments, replications are needed to increase the body of knowledge in software inspections. We present a(More)
Software inspections have proved to be an effective means to find faults in different software artifacts, and the application of software inspections on requirements specifications is believed to give a high return on investment as problems are caught early. However, despite the existing evidence of positive effects requirements inspections are not a common(More)
Selecting requirements for a release of software is a difficult undertaking as people have trouble comparing requirements of different types and have natural biases towards short-terms gains over longer-term sustainability. Portfolio theory is proposed as a solution to this problem, as it provides a method for balancing investment options to maximize the(More)
In market-driven software product development, requirements that can potentially go into a product or a product release represent different kinds of investments. Requirements differ in the type of value that they provide and level of risk associated to investing in them. In this paper we investigate how business risk associated with different requirement(More)
Agile development methods such as extreme programming (XP), SCRUM, Lean Software Development (Lean SD) and others have gained much popularity during the last years. Agile methodologies promise faster time-to-market, satisfied customers and high quality software. While these prospects are appealing, the suitability of agile practices to different domains and(More)
The need of understanding and supporting requirements engineering decisions in market-driven product development is motivated by the complexity and economical impact of these decisions. While being a key for success, correct and timely decisions are dependent on the availability and the quality of decision material (requirements, business cases, cost-value(More)
Background: Continuous software product development is increasingly becoming the norm. New requirements come in a constant stream and need to be assigned to projects to make it into a release. However, in the literature requirements management practices are project based and no longer naturally fit to this new setting. Aim: Thus, it is of interest to(More)
  • 1