ScholarGate
アシスタント

手法を比較

選択した手法を並べて確認できます。異なる行はハイライト表示されます。

静的コード解析×欠陥予測モデル×
分野ソフトウェア工学ソフトウェア工学
系統Process / pipelineProcess / pipeline
提唱年20012005
提唱者David Engler and William PughThomas Ostrand, Elaine Weyuker, Robert Bell
種類automated analysismachine learning model
原典Chess, B., & West, J. (2007). Secure Programming with Static Analysis. Addison-Wesley Professional. link ↗Ostrand, T. J., Weyuker, E. J., & Bell, R. M. (2005). Predicting the location and number of faults in large software systems. IEEE Transactions on Software Engineering, 31(4), 340–355. DOI ↗
別名static analysis, code inspection, automated reviewfault prediction, bug prediction, defect classification
関連44
概要Static code analysis automatically examines source code without execution, detecting potential bugs, security vulnerabilities, code smells, and style violations. Pioneered by Engler and Pugh (2001), automated analysis tools scan codebases at scale, identifying defect patterns faster than manual review. Organizations integrate static analysis into continuous integration pipelines to prevent defects early.Defect prediction models forecast the likelihood of software faults in code modules using statistical or machine learning approaches. Pioneered by Ostrand, Weyuker, and Bell (2005), these models correlate code metrics (complexity, churn, coupling) with historical defect data to identify high-risk components. Organizations use predictions to allocate testing resources, guide code review, and prioritize refactoring.
ScholarGateデータセット
  1. v1
  2. 3 出典
  3. PUBLISHED
  1. v1
  2. 3 出典
  3. PUBLISHED

検索へ Download slides

ScholarGate手法を比較: Static Code Analysis · Defect Prediction Model. 2026-06-15に以下より取得 https://scholargate.app/ja/compare