Demonstration venue · read-only. Every page can be browsed; the buttons that would change it are switched off. Create an account to run TaxoReview on your own data. A simulation from public publication records: the people listed were not invited and did not agree to review.
? Tutorial for this page

Karl E. Hewitt

dblp:97/3951 · DBLP profile ↗
← Back
1ranked-venue papers
1as first author
0since 2021 · last 1975
—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
Empirical software engineering · 50% Requirements engineering and software design · 50%

Topics — the 2 heaviest of 2, each with the papers that count most for it

TopicWeightPapersLastEvidence papers
Empirical software engineering › software engineering research methodology
meta-evaluation
0.011975
Towards a Programming Apprentice · IEEE Trans. Software Eng. 1975
Requirements engineering and software design › specification
software contracts
0.011975
Towards a Programming Apprentice · IEEE Trans. Software Eng. 1975

Methods — techniques the papers use, named apart from their topics

knowledge representation · 0.0justification · 0.0
YearPublicationVenuePosition
1975 Towards a Programming Apprentice
abstract
The Planner Project is constructing a programming apprentice to assist in knowledge based programming. The programming apprentice is designed for interactive use by expert programmers in the meta-evaluation of implementations in the context of their contracts and background knowledge. Meta-evaluation produces a justification which makes explicit exactly how the module depends on the contracts of other modules and on the background knowledge. The justification is used in answering questions on the behavioral dependencies between modules and in analyzing the implications of perturbations in specifications and/or implementation.
Karl E. Hewitt, Brian Cantwell Smith
IEEE Trans. Software Eng.1