Gerald M. Berns
Skip Abstract Section
Abstract
How easy is it to maintain a program? To a large extent, that depends on how difficult the program is to understand. A technique to measure program difficulty yields encouraging results.
- 1 American National Standard Programming Language Fortran, X3, 9-1978. American National Standards Institute, New York, 1978.Google Scholar
- 2 Berns, G. M. Reference Guide to MAT, Maintenance Analysis Tool, Science Applications, Inc., Crystal City, Virginia, 1983.Google Scholar
- 3 Berns, G. M. Vflecs, a Fortran pre-processor that produces structured VAX-11 Fortran from Flecs and Fortran programs, Science Applications, Inc., Crystal City, Virginia, 1983.Google Scholar
- 4 Flecs: User's Manual, Department of Computer Science, University of Oregon, 1975.Google Scholar
- 5 Shen, V. Y., Conte S. D. and Dunsmore, H. E. Software Science Revisited: A Critical Analysis of the Theory and its Empirical Support, IEEE Trans. Software Engineer. 9, 2 (March, 1983), 155-164.Google Scholar
- 6 VAX-11 Fortran Language Reference Manual, Digital Equipment Corp. (Order No. AA-DO34B-TE), Maynard, Massachusetts, 1980.Google Scholar
Index Terms
- Assessing software maintainability
Recommendations
CP-Miner: Finding Copy-Paste and Related Bugs in Large-Scale Software Code
Recent studies have shown that large software suites contain significant amounts of replicated code. It is assumed that some of this replication is due to copy-and-paste activity and that a significant proportion of bugs in operating systems are due to ...
Finding Atomicity-Violation Bugs through Unserializable Interleaving Testing
Multicore hardware is making concurrent programs pervasive. Unfortunately, concurrent programs are prone to bugs. Among different types of concurrency bugs, atomicity violations are common and important. How to test the interleaving space and expose ...
Comments