Standard

Quality of Just-in-Time Requirements : Just-Enough and Just-in-Time. / Heck, PM.

Delft : Petra Heck, 2016. 173 p.

Research output: ThesisDissertation (TU Delft)Scientific

Harvard

APA

Vancouver

Author

Heck, PM. / Quality of Just-in-Time Requirements : Just-Enough and Just-in-Time. Delft : Petra Heck, 2016. 173 p.

BibTeX

@phdthesis{1fa43762e2b041079c578a74d96094d0,
title = "Quality of Just-in-Time Requirements: Just-Enough and Just-in-Time",
abstract = "The goal of this thesis was to obtain a deeper understanding of the notion of quality for Just-in-Time (JIT) Requirements. JIT requirements are the opposite of up-front requirements. JIT requirements are not analyzed or defined until they are needed meaning that development is allowed to begin with incomplete requirements. We started our analysis by investigating one specific format of JIT requirements: open source feature requests. We discovered that in open source projects there is the problem of many duplicate feature requests. We found seven different categories for those duplicates. Analyzing the duplicates has also led to recommendations for manual search and creation of feature requests. Furthermore we have indicated possible tool support to avoid duplicate feature requests. One possibility for tool support is to visualize so-called feature request networks. For this one needs to have the links between feature requests. We show that it is possible to detect horizontal traceability links between feature requests by using a Vector Space Model with TF-IDF as a weighing scheme. We have determined the optimal preprocessing steps for the feature requests to be used for our text-based analysis. Using a more advanced technique like Latent Semantic Analysis takes significantly more processing time without yielding better results in the three open source projects that we have included in our experiment. Then we took a step back to look at quality criteria for JIT requirements in general. We developed a framework for those quality criteria and constructed a specific list of quality criteria for open source feature requests. We used agile user stories to indicate how the framework could be customized for other types of JIT requirements. We conducted interviews with agile practitioners to evaluate our framework. After their positive feedback we conducted a case study in three open source projects in which we used our framework to score the quality of feature requests. This case study also led to recommendations for practitioners working with feature requests. We conclude this thesis with a broader perspective on JIT requirements quality by presenting the results of a systematic literature review on quality criteria for agile requirements. This review resulted in a list of 28 quality criteria for JIT requirements, recommendations for practitioners working on quality assessment of agile requirements and a research agenda on quality of agile requirements. To conclude we claim that the quality of Just-in-Time Requirements can be characterized as ‘Just-Enough and Just-in-Time Quality’. Our framework can be used to define what Just-Enough and Just-in-Time mean for the specific JIT environment.",
keywords = "quality, requirement, agile, Just-in-Time, verification, feature request",
author = "PM Heck",
year = "2016",
doi = "10.4233/uuid:5890f1cb-2a90-4bfa-83ba-81b602dca0d5",
language = "English",
isbn = "978-94-6186-600-4",
publisher = "Petra Heck",
school = "Delft University of Technology",

}

RIS

TY - THES

T1 - Quality of Just-in-Time Requirements

T2 - Just-Enough and Just-in-Time

AU - Heck, PM

PY - 2016

Y1 - 2016

N2 - The goal of this thesis was to obtain a deeper understanding of the notion of quality for Just-in-Time (JIT) Requirements. JIT requirements are the opposite of up-front requirements. JIT requirements are not analyzed or defined until they are needed meaning that development is allowed to begin with incomplete requirements. We started our analysis by investigating one specific format of JIT requirements: open source feature requests. We discovered that in open source projects there is the problem of many duplicate feature requests. We found seven different categories for those duplicates. Analyzing the duplicates has also led to recommendations for manual search and creation of feature requests. Furthermore we have indicated possible tool support to avoid duplicate feature requests. One possibility for tool support is to visualize so-called feature request networks. For this one needs to have the links between feature requests. We show that it is possible to detect horizontal traceability links between feature requests by using a Vector Space Model with TF-IDF as a weighing scheme. We have determined the optimal preprocessing steps for the feature requests to be used for our text-based analysis. Using a more advanced technique like Latent Semantic Analysis takes significantly more processing time without yielding better results in the three open source projects that we have included in our experiment. Then we took a step back to look at quality criteria for JIT requirements in general. We developed a framework for those quality criteria and constructed a specific list of quality criteria for open source feature requests. We used agile user stories to indicate how the framework could be customized for other types of JIT requirements. We conducted interviews with agile practitioners to evaluate our framework. After their positive feedback we conducted a case study in three open source projects in which we used our framework to score the quality of feature requests. This case study also led to recommendations for practitioners working with feature requests. We conclude this thesis with a broader perspective on JIT requirements quality by presenting the results of a systematic literature review on quality criteria for agile requirements. This review resulted in a list of 28 quality criteria for JIT requirements, recommendations for practitioners working on quality assessment of agile requirements and a research agenda on quality of agile requirements. To conclude we claim that the quality of Just-in-Time Requirements can be characterized as ‘Just-Enough and Just-in-Time Quality’. Our framework can be used to define what Just-Enough and Just-in-Time mean for the specific JIT environment.

AB - The goal of this thesis was to obtain a deeper understanding of the notion of quality for Just-in-Time (JIT) Requirements. JIT requirements are the opposite of up-front requirements. JIT requirements are not analyzed or defined until they are needed meaning that development is allowed to begin with incomplete requirements. We started our analysis by investigating one specific format of JIT requirements: open source feature requests. We discovered that in open source projects there is the problem of many duplicate feature requests. We found seven different categories for those duplicates. Analyzing the duplicates has also led to recommendations for manual search and creation of feature requests. Furthermore we have indicated possible tool support to avoid duplicate feature requests. One possibility for tool support is to visualize so-called feature request networks. For this one needs to have the links between feature requests. We show that it is possible to detect horizontal traceability links between feature requests by using a Vector Space Model with TF-IDF as a weighing scheme. We have determined the optimal preprocessing steps for the feature requests to be used for our text-based analysis. Using a more advanced technique like Latent Semantic Analysis takes significantly more processing time without yielding better results in the three open source projects that we have included in our experiment. Then we took a step back to look at quality criteria for JIT requirements in general. We developed a framework for those quality criteria and constructed a specific list of quality criteria for open source feature requests. We used agile user stories to indicate how the framework could be customized for other types of JIT requirements. We conducted interviews with agile practitioners to evaluate our framework. After their positive feedback we conducted a case study in three open source projects in which we used our framework to score the quality of feature requests. This case study also led to recommendations for practitioners working with feature requests. We conclude this thesis with a broader perspective on JIT requirements quality by presenting the results of a systematic literature review on quality criteria for agile requirements. This review resulted in a list of 28 quality criteria for JIT requirements, recommendations for practitioners working on quality assessment of agile requirements and a research agenda on quality of agile requirements. To conclude we claim that the quality of Just-in-Time Requirements can be characterized as ‘Just-Enough and Just-in-Time Quality’. Our framework can be used to define what Just-Enough and Just-in-Time mean for the specific JIT environment.

KW - quality

KW - requirement

KW - agile

KW - Just-in-Time

KW - verification

KW - feature request

UR - http://resolver.tudelft.nl/uuid://1fa43762-e2b0-4107-9c57-8a74d96094d0

U2 - 10.4233/uuid:5890f1cb-2a90-4bfa-83ba-81b602dca0d5

DO - 10.4233/uuid:5890f1cb-2a90-4bfa-83ba-81b602dca0d5

M3 - Dissertation (TU Delft)

SN - 978-94-6186-600-4

PB - Petra Heck

CY - Delft

ER -

ID: 3049702