ScholarGate
アシスタント

手法を比較

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

静的コード解析×等価パーティショニング・テスト×
分野ソフトウェア工学ソフトウェア工学
系統Process / pipelineProcess / pipeline
提唱年20011979
提唱者David Engler and William PughGlenford Myers
種類automated analysispartitioning strategy
原典Chess, B., & West, J. (2007). Secure Programming with Static Analysis. Addison-Wesley Professional. link ↗Myers, G. J. (1979). The Art of Software Testing. John Wiley & Sons. link ↗
別名static analysis, code inspection, automated reviewequivalence partitioning, BVA, boundary value analysis
関連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.Equivalence partitioning divides input domains into equivalence classes—sets of inputs expected to behave identically—then selects test cases from each class. Introduced by Myers (1979), this technique reduces test cases while maintaining effectiveness. Boundary value analysis (BVA) complements partitioning by testing values at partition boundaries where failures often occur.
ScholarGateデータセット
  1. v1
  2. 3 出典
  3. PUBLISHED
  1. v1
  2. 3 出典
  3. PUBLISHED

検索へ スライドをダウンロード

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