Are developers complying with the process

Zazworka, Nico; Stapel, Kai; Knauss, Eric; Shull, Forrest; Basili, Victor R.; Schneider, Kurt

doi:10.1145/1852786.1852805

Cited by 39 publications

(65 citation statements)

References 10 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…Rather complex networks of solid and fluid information and experience flows were identified, modeled, and discussed with domain experts. In one case, a repository was mined as an indicator of document-based (solid) information flows to complement interview results [14]. The FLOW elicitation technique has not yet been applied to elicit and model complex information flows in very large organizations.…”

Section: Information Flow Modelingmentioning

confidence: 99%

FLOW-assisted value stream mapping in the early phases of large-scale software development

Ali

Petersen

Schneider

2016

Journal of Systems and Software

Self Cite

View full text Add to dashboard Cite

PostprintThis is the accepted version of a paper published in Journal of Systems and Software. This paper has been peer-reviewed but does not include the final publisher proof-corrections or journal pagination.Citation for the original published paper (version of record):Ali, N b. (2016) FLOW-assisted value stream mapping in the early phases of large-scale software development. Systems and Software, Access to the published version may require subscription. Journal of AbstractValue Stream Mapping (VSM) has been successfully applied in the context of software process improvement. However, its current adaptations from Lean manufacturing focus mostly on the flow of artifacts and have taken no account of the essential information flows in software development. A solution specifically targeted towards information flow elicitation and modeling is FLOW. This paper aims to propose and evaluate the combination of VSM and FLOW to identify and alleviate information and communication related challenges in large-scale software development. Using case study research, FLOW-assisted VSM was used for a large product at Ericsson AB, Sweden. Both the process and the outcome of FLOW-assisted VSM have been evaluated from the practitioners' perspective. It was noted that FLOW helped to systematically identify challenges and improvements related to information flow. Practitioners responded favorably to the use of VSM and FLOW, acknowledged the realistic nature and impact on the improvement on software quality, and found the overview of the entire process using the FLOW notation very useful. The combination of FLOW and VSM presented in this study was successful in systematically uncovering issues and characterizing their solutions, indicating their practical usefulness for waste removal with a focus on information flow related issues.

show abstract

Section: Information Flow Modelingmentioning

confidence: 99%

FLOW-assisted value stream mapping in the early phases of large-scale software development

Ali

Petersen

Schneider

2016

Journal of Systems and Software

Self Cite

View full text Add to dashboard Cite

show abstract

“…Preliminary analysis showed that data quality varied considerably between available projects, reflecting the level of process conformance [25] with which developers recorded defects in JIRA. We chose the project with the best data quality (according to the three criteria below) to reduce the influence of incomplete or noisy data on the results:…”

Section: A Study Contextmentioning

confidence: 99%

Investigating Automatic Static Analysis Results to Identify Quality Problems: An Inductive Study

Vetrò

Zazworka

Shull

et al. 2012

2012 35th Annual IEEE Software Engineering Workshop

Self Cite

View full text Add to dashboard Cite

Background: Automatic static analysis (ASA) tools examine source code to discover "issues", i.e. code patterns that are symptoms of bad programming practices and that can lead to defective behavior. Studies in the literature have shown that these tools find defects earlier than other verification activities, but they produce a substantial number of false positive warnings. For this reason, an alternative approach is to use the set of ASA issues to identify defect prone files and components rather than focusing on the individual issues.Aim: We conducted an exploratory study to investigate whether ASA issues can be used as early indicators of faulty files and components and, for the first time, whether they point to a decay of specific software quality attributes, such as maintainability or functionality. Our aim is to understand the critical parameters and feasibility of such an approach to feed into future research on more specific quality and defect prediction models. Method: We analyzed an industrial C# web application using the Resharper ASA tool and explored if significant correlations exist in such a data set.Results: We found promising results when predicting defectprone files. A set of specific Resharper categories are better indicators of faulty files than common software metrics or the collection of issues of all issue categories, and these categories correlate to different software quality attributes.Conclusions: Our advice for future research is to perform analysis on file rather component level and to evaluate the generalizability of categories. We also recommend using larger datasets as we learned that data sparseness can lead to challenges in the proposed analysis process.Automatic static analysis, software quality, defect prediction

show abstract

“…In their work on formulating approaches for analysis of process compliance, Zazworka et al [3] defined and studied a metric of "truck factor". They evaluate the approach for analysis of non conformance in a case study on XP, where non conformance can be detected through a metric for truck factor.…”

Section: Related Workmentioning

confidence: 99%

“…where c is a percentage, and cov x (n) is the coverage, defined as the percentage of components that would still be known by the developers if n developers were Torchiano et al [4] build on the work by Zazworka et al [3] and investigate threshold values for the truck factor, and they look at data from a set of 20 open source projects. Ricca et al [5] continue this work and present a tool for calculating the truck factor and investigate the sensibility of the truck factor metric.…”

Section: Related Workmentioning

confidence: 99%

“…There are, of course, other ways to obtain knowledge, such as through training, participating in inspections, or other ways. However, contributing to the code has been used as an indication of knowledge in other studies ( [2][3][4]), and it is at least an intuitive indication of knowledge. Fritz et al [7] investigated the relationship between activity for a piece of code and knowledge about it and found that activity could be used as an indicator, although additional factors could also be considered such as role and professional work experience.…”

Section: Fig 2 Markov Modelmentioning

confidence: 99%

See 1 more Smart Citation

Modeling the Effects of Project Management Strategies on Long-Term Product Knowledge

Höst

2012

Product-Focused Software Process Improvement

View full text Add to dashboard Cite

Are developers complying with the process

Cited by 39 publications

References 10 publications

FLOW-assisted value stream mapping in the early phases of large-scale software development

FLOW-assisted value stream mapping in the early phases of large-scale software development

Investigating Automatic Static Analysis Results to Identify Quality Problems: An Inductive Study

Modeling the Effects of Project Management Strategies on Long-Term Product Knowledge

Contact Info

Product

Resources

About