Skip to content
Free planNo credit card requiredStart writing
AI for Research home
AI for Research home
Dashboard
Sign inGet started

article · Electronic Systems and Software · 2006

Static control [source-code analysis]

A. Cothard

Cited by 0Abstract and details only

Abstract

Source-code analysis lets you pick up programming errors without running the software. Spotting errors early in the process is the cheapest and usually the easiest way of avoiding problems and project delays, as with any design and production process. The problem with software is that you have to have a lot of it ready before you can test it fully. But what if you could subject even individual modules to scrutiny without demanding that the code actually runs? This is where source code analysis (SCA) comes in.

Cite this paper

APA 7

Cothard, A. (2006). Static control [source-code analysis]. Electronic Systems and Software, 4(4), 30–33. https://doi.org/10.1049/ess:20060406

MLA 9

Cothard, A. “Static control [source-code analysis].” Electronic Systems and Software, vol. 4, no. 4, 2006, pp. 30–33, https://doi.org/10.1049/ess:20060406.

Chicago

Cothard, A. 2006. “Static control [source-code analysis].” Electronic Systems and Software 4 (4): 30–33. https://doi.org/10.1049/ess:20060406.

Harvard

Cothard, A. (2006) ‘Static control [source-code analysis]’, Electronic Systems and Software, 4(4), pp. 30–33. Available at: https://doi.org/10.1049/ess:20060406.

BibTeX
@article{cothard2006static,
  title = {{Static control [source-code analysis]}},
  author = {Cothard, A.},
  journal = {Electronic Systems and Software},
  volume = {4},
  number = {4},
  pages = {30--33},
  year = {2006},
  doi = {10.1049/ess:20060406}
}

Made from the index record. Check names, capitalisation and page numbers against the paper. Need another style? AI for Research has over 10,000.

Related papers