| 1. |
- Dzamashvili Fogelström, Nina
(författare)
-
How to develop student´s skills in indepedent learning and enquiry
- 2021
-
Rapport (populärvet., debatt m.m.)abstract
- We live in the age of rapid technological innovations, with intelligent technology on the front and capable to perform tasks normally solely conducted by humans. This creates need for universities to focus on developing student’s skills in independent learning and readiness to orient in ever changing technological landscape. The need is well recognized by many universities, BTH included. If we look at program goals of our engineering programs, most of the programs have clearly defined goals to produce independent problem solvers.
|
|
| 2. |
- Dzamashvili-Fogelström, Nina, et al.
(författare)
-
Investigating impact of business risk on requirements selection decisions
- 2009
-
Konferensbidrag (refereegranskat)abstract
- 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 types is considered by the decision makers and how it affects requirement selection decisions. The results of the conducted case study indicate that due to lacking methods for handling the requirements business risk, requirements with low level of risk are preferred over other type of requirements such as innovations and architectural improvements.
|
|
| 3. |
- Dzamashvili-Fogelström, Nina, et al.
(författare)
-
Needs Oriented Framework for Producing Requirements Decision Material : NORM
- 2008
-
Konferensbidrag (refereegranskat)abstract
- 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, costvalue estimations etc). This paper presents a needsoriented framework (NORM) for identifying and assuring the creation of appropriate decision material for RE decisions. NORM is based on analysis of the applied RE process and characteristics of separate RE decisions, focusing mainly on pre-project activities. The framework is developed in close cooperation with industry with the intention to ensure that resources are spent on producing just-the-necessary information at the right time and to be able to monitor and control this production effort.
|
|
| 4. |
- Dzamashvili-Fogelström, Nina, et al.
(författare)
-
Test-case Driven versus Checklist-based Inspections of Software Requirements – An Experimental Evaluation
- 2007
-
Konferensbidrag (refereegranskat)abstract
- 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 practice in industry. The reason is believed to be the cost associated with inspections as a technology. This paper presents an evaluation of test-case driven inspections (TCD) - an emerging inspection technique that aims to cut costs associated with traditional requirements inspections. To formally test the efficiency and effectiveness of TCD inspections an experiment was conducted, in a controlled environment, where checklist based inspections was used as a point of reference. The experiment results indicate that TCD inspections perform better when it comes to effectiveness in finding major faults in a requirements specification.
|
|
| 5. |
- Dzamashvili-Fogelström, Nina, et al.
(författare)
-
The Impact of Agile Principles on Market-Driven Software Product Development
- 2010
-
Ingår i: Software Process. - : interscience.wiley. - 1077-4866 .- 1099-1670. ; 22:1, s. 53-80
-
Tidskriftsartikel (refereegranskat)abstract
- Agile development methods such as XP, SCRUM, Lean Software Development 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 business contexts still remains unclear. In this paper we investigate the applicability of agile principles in the context of market-driven software product development (MDPD), focusing on pre-project activities. This paper presents results of a comparison between typical properties of agile methods to the needs of MDPD, as well as findings of a case study conducted at Ericsson, an early adopter of agile product development. The results show misalignment between the agile principles and needs of pre-project activities in market-driven development. This misalignment threatens to subtract from the positive aspects of agile development, but maybe more importantly, threaten the overall product development by disabling effective product management.
|
|
| 6. |
- Dzamashvili-Fogelström, Nina
(författare)
-
Understanding and supporting requirements engineering decisions in market-driven software product development
- 2010
-
Licentiatavhandling (övrigt vetenskapligt/konstnärligt)abstract
- Context: Requirements engineering (RE) for software products offered to a mass market is concerned with deciding which of the diverse and large amounts of potential requirements to implement into future releases of a product. While being the key for achieving success, these decisions are very complex. Therefore, the need for decision support is well acknowledged. However, despite a growing body of research in this area, software companies are still experiencing problems in making informed decisions on which requirements to include in the software, or knowing how to maximize the potential ROI of a software release. Objective: The purpose of this thesis is to provide an increased understanding of how better decisions regarding the content of software products can be achieved. The research addresses two currently unresolved areas: balancing investments in different requirement types (commercial requirements, internal quality aspects and innovations) and identifying reasonable requirement analysis effort for informed requirements selection decisions. In order to address these areas the thesis focuses on investigating: 1) how uncertainty in the value proposition of a requirement is influencing the balance between investments in different requirement types; and 2) challenges and opportunities introduced by agile practices to RE decisions. Method: The presented research has an exploratory character and consists of empirical studies conducted both in industrial and academic settings. Results: The results include findings from an academic experiment and an industrial case study indicating that commercial requirements will be preferred over innovations and internal quality aspects. This is because innovations and internal quality aspects are associated with higher uncertainty in their value offering compared to commercial requirements and thereby are perceived to have higher level of business risk. The thesis also offers findings from an industrial case study, showing a misalignment between agile principles and the ability to take informed release planning decisions. Further, a framework (NORM) for finding an appropriate balance between information needs of RE decisions and requirements analysis effort is suggested. Conclusions: Uncertainty associated with the value proposition of different requirement types influences the requirements selection decisions, resulting in a dominance of commercial requirements. Thus, in order to achieve a better balance between investments in commercial requirements, internal quality and innovation it is important that uncertainty in the value offering of requirements is explicitly managed by methods providing support for RE decisions in a market-driven context. Agile methods provide opportunities to minimize overhead caused by excessive analysis of requirements, however adopting agile approaches in their current form pose challenges for performing product management and taking informed RE decisions in a market-driven context. Therefore, a balance between agility and information needs of RE decisions must be found. In combination, the thesis results offer a new insight and form a ground for defining improved approaches for supporting requirement selection decisions.
|
|
| 7. |
- Dzamashvili-Fogelström, Nina, et al.
(författare)
-
Using Portfolio Theory to Support Requirements Selection Decisions
- 2010
-
Konferensbidrag (refereegranskat)abstract
- Abstract—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 likelihood of a given return. This approach is explored generally and through an example. The results suggest portfolio theory can be applied for this purpose. Applying portfolio theory to determine the amount of development time that should be spent on different types of requirements shows the most potential, especially when data on expected risks and returns is limited.
|
|
| 8. |
- Dzamashvili-Fogelström, Nina, et al.
(författare)
-
When Product Managers Gamble with Requirements : Attitudes to Value and Risk
- 2009
-
Konferensbidrag (refereegranskat)abstract
- Context and motivation: Finding a balance between commercial (customer specific, market pull and external quality requirements) and internal quality requirements is a recognized challenge in market driven software product development (MDSPD). In order to address this challenge it is important to understand the preferences and biases influencing decision makers selecting requirements for software releases. Question/problem: Prospect theory has been successfully applied to many disciplines. Applying it to MDSPD suggests decision makers will avoid risk when selecting between commercial requirements, take risk with internal quality requirements, and prefer commercial requirements over internal quality requirements in order to maximize their perceived value. This paper seeks to investigate this claim. Principal ideas/results: This paper presents an experiment investigating whether the biases proposed by prospect theory can be seen operating in MDSPD requirements engineering (RE). The results indicate risk avoidance when dealing commercial requirements, while greater risk is taken when dealing with internal quality requirements. Contribution: As this is the first paper to use prospect theory to explain requirements selection decisions, it presents opportunity to educate people in the biases they bring to the RE process, and facilitate the creation of strategies for balancing the different requirements types.
|
|
| 9. |
|
|
| 10. |
- Khurum, Mahvish, et al.
(författare)
-
Requirements Management for Continuous Software Product Development
- 2010
-
Konferensbidrag (refereegranskat)abstract
- 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 understand the industrial practices for the identification of requirements and associated artifacts put under configuration control. Method: An industrial survey with five companies was conducted to find out these industrial practices. Results: The results of this survey show that with the need to manage more requirements also comes the need for greater control. Large companies, however, often place similar control on products of all size. Moreover, regardless of size and requirements management practices, companies face the same problems. Conclusions: All companies should keep requirements associated material under some form of control and updates to them should be communicated to the involved stakeholders and should be easy to access. The type of associated artifacts kept under control can be decided by the criteria given.
|
|
