
doi: 10.1007/bfb0042363
One of the many confusing issues in today's software world is the use of many names that describe different aspects of the software sciences, but which have widely overlapping activities. One such area is the distinction between computer science and software engineering. Undergraduate programs to teach software sciences should decide upon an area in which to concentrate, either computer science or software engineering. The distinction is more than semantics; there are practical differences in the philosophy of each of these subjects. Computer science, though beyond its infancy, is still a dynamic area, but is suitable for undergraduate curricula due to the body of knowledge which exists to support it. Software engineering, in contrast, is still in its infancy and is not yet well enough understood to warrant a separate undergraduate curriculum.
| selected citations These citations are derived from selected sources. This is an alternative to the "Influence" indicator, which also reflects the overall/total impact of an article in the research community at large, based on the underlying citation network (diachronically). | 3 | |
| popularity This indicator reflects the "current" impact/attention (the "hype") of an article in the research community at large, based on the underlying citation network. | Average | |
| influence This indicator reflects the overall/total impact of an article in the research community at large, based on the underlying citation network (diachronically). | Average | |
| impulse This indicator reflects the initial momentum of an article directly after its publication, based on the underlying citation network. | Average |
