4
views
0
recommends
+1 Recommend
0 collections
    0
    shares
      • Record: found
      • Abstract: found
      • Article: found
      Is Open Access

      On the Benefit of Automated Static Analysis for Small and Medium-Sized Software Enterprises

      Preprint

      Read this article at

      Bookmark
          There is no author summary for this article yet. Authors can add summaries to their articles on ScienceOpen to make them more accessible to a non-specialist audience.

          Abstract

          Today's small and medium-sized enterprises (SMEs) in the software industry are faced with major challenges. While having to work efficiently using limited resources they have to perform quality assurance on their code to avoid the risk of further effort for bug fixes or compensations. Automated static analysis can reduce this risk because it promises little effort for running an analysis. We report on our experience in analysing five projects from and with SMEs by three different static analysis techniques: code clone detection, bug pattern detection and architecture conformance analysis. We found that the effort that was needed to introduce those techniques was small (mostly below one person-hour), that we can detect diverse defects in production code and that the participating companies perceived the usefulness of the presented techniques as well as our analysis results high enough to include the techniques in their quality assurance.

          Related collections

          Most cited references20

          • Record: found
          • Abstract: not found
          • Article: not found

          On the value of static analysis for fault detection in software

            Bookmark
            • Record: found
            • Abstract: found
            • Article: found
            Is Open Access

            Do Code Clones Matter?

            Code cloning is not only assumed to inflate maintenance costs but also considered defect-prone as inconsistent changes to code duplicates can lead to unexpected behavior. Consequently, the identification of duplicated code, clone detection, has been a very active area of research in recent years. Up to now, however, no substantial investigation of the consequences of code cloning on program correctness has been carried out. To remedy this shortcoming, this paper presents the results of a large-scale case study that was undertaken to find out if inconsistent changes to cloned code can indicate faults. For the analyzed commercial and open source systems we not only found that inconsistent changes to clones are very frequent but also identified a significant number of faults induced by such changes. The clone detection tool used in the case study implements a novel algorithm for the detection of inconsistent clones. It is available as open source to enable other researchers to use it as basis for further investigations.
              Bookmark
              • Record: found
              • Abstract: not found
              • Article: not found

              Helping small companies assess software processes

                Bookmark

                Author and article information

                Journal
                2016-11-22
                Article
                10.1007/978-3-642-27213-4_3
                1611.07549
                cf0566fb-4f3e-4ea6-b60a-96d5993b376d

                http://arxiv.org/licenses/nonexclusive-distrib/1.0/

                History
                Custom metadata
                Proc. 4th International Conference on Software Quality. Process Automation in Software Development (SWQD 2012). Springer, 2012
                25 pages, 0 figures
                cs.SE

                Software engineering
                Software engineering

                Comments

                Comment on this article