Visualization of Feature Survival in Platform-Based Embedded Systems Development for Improved Understanding of Scope Dynamics

Wnuk, Krzysztof; Regnell, Björn; Karlsson, Linda

doi:10.1109/rev.2008.6

Cited by 11 publications

(9 citation statements)

References 19 publications

(16 reference statements)

Supporting

Mentioning

Contrasting

Order By: Relevance

“…As a remedy, the Feature Survival Chart (FSC) concept was proposed by the authors and acknowledged by the practitioners as a valuable support. This paper extends the contributions of [3] with (1) findings from industrial application in three projects and (2) scope tracking measurements. The proposed visualization shows the decision process of including or excluding features that are candidates for the next release.…”

Section: Introductionsupporting

confidence: 54%

What Happened to Our Features? Visualization and Understanding of Scope Change Dynamics in a Large-Scale Industrial Setting

Wnuk

Regnell

Karlsson³

2009

2009 17th IEEE International Requirements Engineering Conference

Self Cite

View full text Add to dashboard Cite

show abstract

Section: Introductionsupporting

confidence: 54%

What Happened to Our Features? Visualization and Understanding of Scope Change Dynamics in a Large-Scale Industrial Setting

Wnuk

Regnell

Karlsson³

2009

2009 17th IEEE International Requirements Engineering Conference

Self Cite

View full text Add to dashboard Cite

show abstract

“…In software projects, modifications are considered agreed upon scope of the project. These modifications are due [5] Agile EVM [26] Burn-down charts [46] Burn-up charts [46] Function Points [48] Work-Breakdown Structure [49] Expert judgement [51] Performance analysis [52] Feature Transition Charts [53] Story Mapping [54] Stakeholder analysis [55] Benefit analysis [56] Requirement Matrix [56] Scope Change Control System [57] Functional Size Measurement (FSM) [58] Feature Survival Charts [59] Feature Growth Charts [60] SPSRI [61] Activity Based (top down) [62]- [63] Task based (bottom up) [62]- [63] PERT [64] Object point [65] Source line of code (SLOC) [65] Analogy technique [65] Price-to-win [62] VOLUME , 2020 to inevitable change and complexity of the project scope. According to [50] author "Half of the system requirements change till deployment".…”

Section: B Scope Definition Techniques/toolsmentioning

confidence: 99%

Measuring the Impact of Scope Changes on Project Plan Using EVM

et al. 2020

View full text Add to dashboard Cite

Earned Value Management (EVM) measures project performance against a baseline plan. It identifies deviations in budget and schedule, aids project managers in taking earlier corrective actions against cost and schedule overruns. Although the literature highlights the significance of scope by adopting it as a leading indicator to measure project success or failure. However, EVM does not include scope when evaluating the performance of any software project. While considering the importance of scope and its ever-changing nature, it is imperative to measure the effect of changes in scope on the project plan. To analyse such effects, this study aims to enhance the traditional EVM by incorporating scope into it. The main objectives of this paper are: i) to extract the effects of project scope changes, ii) to map extracted effects of project scope changes with Software Project Scope Rating Index (SPSRI) elements, and iii) to quantify the extracted effects and integrate them with EVM. An extensive literature review is conducted to achieve the first objective, which results in the seventeen unique effects; that were used to map with SPSRI elements. To forecast the variations in scope for a given project budget, Monte Carlo simulations were run on the top eight scope elements, whereas, the results were incorporated with EVM to identify the deviations between actual and projected values of scope's score and cost. Finally, the multivariate regression model was used to evaluate the influence of individual element on the overall estimated cost of the project. The correlation between the independent variables (SPSRI elements) and the dependent variable (overall cost) was calculated along with the valuation of each independent variable on the dependent variable. Moreover, the effects are statistically shown that independent variables have influenced the dependent variable. This technique could assist the project managers to forecast deviations in project scope earlier.

show abstract

“…This makes these charts effective at executing plans with minimal confusion [5]. Similarly, Wnuk et al explored how one can represent feature life cycles in a two dimensional graph [23]. Kanban visualizes workflow of a development team [2].…”

Section: Visualizations For General Software Developmentmentioning

confidence: 99%

“…bar graphs, line graphs, etc.) [3,23], these are typically focused on simple bivariate relationships, unable to depict the complex, multivariate relationships inherent in release planning. Several researchers have explored using different visual representations to support release planning.…”

Section: Visualizations For Release Planningmentioning

confidence: 99%

Stratos

Aseniero

Wun

Ledo

et al. 2015

Proceedings of the 33rd Annual ACM Conference on Human Factors in Computing Systems

View full text Add to dashboard Cite

Software is typically developed incrementally and released in stages. Planning these releases involves deciding which features of the system should be implemented for each release. This is a complex planning process involving numerous trade-offs-constraints and factors that often make decisions difficult. Since the success of a product depends on this plan, it is important to understand the tradeoffs between different release plans in order to make an informed choice. We present STRATOS, a tool that simultaneously visualizes several software release plans. The visualization shows several attributes about each plan that are important to planners. Multiple plans are shown in a single layout to help planners find and understand the trade-offs between alternative plans. We evaluated our tool via a qualitative study and found that STRATOS enables a range of decision-making processes, helping participants decide on which plan is most optimal.

show abstract

Visualization of Feature Survival in Platform-Based Embedded Systems Development for Improved Understanding of Scope Dynamics

Cited by 11 publications

References 19 publications

What Happened to Our Features? Visualization and Understanding of Scope Change Dynamics in a Large-Scale Industrial Setting

What Happened to Our Features? Visualization and Understanding of Scope Change Dynamics in a Large-Scale Industrial Setting

Measuring the Impact of Scope Changes on Project Plan Using EVM

Stratos

Contact Info

Product

Resources

About