Elements of Software Science (Operating and programming systems series)
Elements of Software Science (Operating and programming systems series)
An Experiment in Software Science
Proceedings of a Symposium on Language Design and Programming Methodology
Software defects - a software science perspective
Proceedings of the 1981 ACM workshop/symposium on Measurement and evaluation of software quality
A software study using Halstead metrics
Proceedings of the 1981 ACM workshop/symposium on Measurement and evaluation of software quality
The design of architectures to reduce semantic gap
The design of architectures to reduce semantic gap
| Hi-index | 0.00 |
The attractiveness of software science [HAL77] is to some extent due to the simplicity of its instrumentation. Upon learning the detailed rules of counting operators and operands, the experiments and derivations using various algorithms and languages can be repeated. Proposed or actual applications of software science are quite varied (For example, see [SEN79]). The size and construction time of a program can be estimated from the problem specification and the choice of programming language. An estimate of the number of program bugs can be shown to depend on programming effort. Optimal choice of module sizes for multimodule implementations can be computed. Elements of software science have applications to the analysis of technical prose. The purpose of this experiment is three fold. First, we want to apply software science metrics to the language 'C'. The second purpose of the experiment is to study the effect of including declaration statements while counting operators and operands. Finally, we have set out to determine whether the area of application has any influence on software science metrics.