
doi: 10.1007/bfb0035127
In describing a software system, there are three elements that are always considered: objects, functional requirements and business policies. In the traditional approach to software development, these elements are often mixed with one another in a system's definition in such a way that their meanings are embedded into the software, making their identification very difficult. This has the knock-on effect of making maintenance, and hence evolution, difficult.
| 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). | 1 | |
| 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 |
