EDBT 2026 Demo / reviewers in the wild / expert
T. Capers Jones
dblp:43/618
· DBLP profile ↗
1ranked-venue papers
1as first author
0since 2021 · last 1984
—ORCID · none
Domains — the database's venue-derived domains; a paper can count in several
Software engineering, systems software and programming languages · 1 · 1 first-author
Expertise — from the expertise taxonomy: the topics of the expert's papers under the CCF categories. A weight counts papers with recency: 1 for a paper about the topic, 0.3 when the topic is its context, halved every five years.
| Software engineering, system software, and programming languages
1 paper |
Software maintenance and evolution · 77% Requirements engineering and software design · 23% |
Topics — the 4 heaviest of 5, each with the papers that count most for it
| Topic | Weight | Papers | Last | Evidence papers |
|---|---|---|---|---|
Software maintenance and evolution › software reuse
reusable software components |
0.0 | 1 | 1984 | Reusability in Programming: A Survey of the State of the Art · IEEE Trans. Software Eng. 1984 |
Software maintenance and evolution
software reuse |
0.0 | 1 | 1984 | Reusability in Programming: A Survey of the State of the Art · IEEE Trans. Software Eng. 1984 |
Requirements engineering and software design › software design
design reuse |
0.0 | 1 | 1984 | Reusability in Programming: A Survey of the State of the Art · IEEE Trans. Software Eng. 1984 |
Requirements engineering and software design › software architecture
reusable architecture |
0.0 | 1 | 1984 | Reusability in Programming: A Survey of the State of the Art · IEEE Trans. Software Eng. 1984 |
| Year | Publication | Venue | Position |
|---|---|---|---|
| 1984 | Reusability in Programming: A Survey of the State of the ArtabstractAs programming passes the 30 year mark as a professional occupation, an increasingly large number of programs are in application areas that have been automated for many years. This fact is changing the technology base of commercial programming, and is opening up new markets for standard functions, reusable common systems, modules, and the tools and support needed to facilitate searching out and incorporating existing code segments. This report addresses the 1984 state of the art in the domains of reusable data, reusable architectures, reusable design, common systems, reusable programs, and reusable modules or subroutines. If current trends toward reusability continue, the amount of reused logic and reused code in commercial programming systems may approach 50 percent by 1990. However, major efforts will be needed in the areas of reusable data, reusable architectures, and reusable design before reusable code becomes a sound basic technology. T. Capers Jones |
IEEE Trans. Software Eng. | 1 |