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

John A. Dallen

dblp:92/2238 · DBLP profile ↗
← Back
2ranked-venue papers
0as first author
0since 2021 · last 1987
—ORCID · none

Domains — the database's venue-derived domains; a paper can count in several

Systems, architecture and hardware · 1Software engineering, systems software and programming languages · 1

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.

Interdisciplinary, comprehensive, and emerging computing
1 paper
Computing education · 100%
Computer architecture, parallel and distributed computing, and storage systems
1 paper
Electronic design automation · 100%
Software engineering, system software, and programming languages
1 paper
Requirements engineering and software design · 100%

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

TopicWeightPapersLastEvidence papers
Computing education
software engineering education
0.011987
Exercises in Software Design · IEEE Trans. Software Eng. 1987
Electronic design automation › CAD framework
VLSI design environment
0.011983
A vertically integrated VLSI design environment · DAC 1983
Requirements engineering and software design
software design principles
0.011987
Exercises in Software Design · IEEE Trans. Software Eng. 1987

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

hands-on exercises · 0.0
YearPublicationVenuePosition
1987 Exercises in Software Design
abstract
Typical software engineering courses teach principles in lectures and readings, then apply them in the development of a single program (requiring several months). We recently taught a software engineering class that incorporated many smaller exercises (requiring several hours). The class was successful: students were able to experiment with a broad set of ideas, and make interesting mistakes without jeopardizing the grades of their development team. This paper describes some tools and techniques we taught, and suggests how they might be incorporated into typical software engineering classes.
Jon Louis Bentley, John A. Dallen
IEEE Trans. Software Eng.2
1983 A vertically integrated VLSI design environment
Jonathan B. Rosenberg, David G. Boyer, John A. Dallen, Stephen W. Daniel, Charles J. Poirier, John Poulton, C. Durward Rogers, Neil Weste
DAC3