Paper Info
Title
Quality control practice based on design artifacts categories: results from a case study
Abstract
The current empirical literature suggests that discrepancies between software design artifacts and implementation seems inevitable. The goal of this empirical study is to understand the nature and impact of these discrepancies by a detailed analysis of the design and code artifacts. The case study is based on an object-oriented software development project based on a traditional plan-driven software development process and proposed by an industrial collaborator. Case study results show that the code written is based on different sources. Software components can be created from scratch, added after design, adapted from the redesign of a reused component or implemented from the modification of an existing component. It is found that code components based on design artifacts are indeed victims of erosion once implementation begins. This erosion can be linked to the evolution of the team members' project understanding during implementation. However, the study concludes that this evolution is mostly opportunistic and does not necessarily warrant an evolution toward amelioration. This study proposes a quality control practice based on the category of the implemented components.
Year
DOI
Venue
2014
10.1145/2601248.2601249
EASE
Keywords
Field
DocType
pre-implementation design,design,design drift,software quality control,quality control,documentation,software development,case study,management,software evolution,post-implementation design
Software design,Systems engineering,Software design description,Software engineering,Computer science,Software quality control,Software development process,Software construction,Software evolution,Goal-Driven Software Development Process,Software development
Conference
Citations 
PageRank 
References 
0
0.34
20
Authors
3
Name
Order
Citations
PageRank
Pierre N Robillard156865.22
Mathieu Lavallée2435.94
Olivier Gendreau300.34