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

Richard H. Thayer

dblp:23/5576 · DBLP profile ↗
← Back
4ranked-venue papers
4as first author
0since 2021 · last 2007
—ORCID · none

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

Software engineering, systems software and programming languages · 3 · 3 first-authorHuman-computer interaction and ubiquitous computing · 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 · 100%

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

TopicWeightPapersLastEvidence papers
Empirical software engineering › practitioner studies
practitioner survey
0.011981
Major Issues in Software Engineering Project Management · IEEE Trans. Software Eng. 1981
Empirical software engineering
software project management
0.011981
Major Issues in Software Engineering Project Management · IEEE Trans. Software Eng. 1981
Empirical software engineering
software economics
0.011981
Major Issues in Software Engineering Project Management · IEEE Trans. Software Eng. 1981

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

survey · 0.0
YearPublicationVenuePosition
2007 IEEE Software Engineering Standards: A Student's Version
abstract
This paper describes the uses of software engineering standards in a university curriculum. The paper points out the importance of software engineering standards, the issues relating to their use in software engineering and computer science courses, and which of these courses would benefit from using these standards. This information is documented in a new textbook, the IEEE software engineering standards: a students' version published by the IEEE Computer Society Press in 2007. This textbook lists the standards necessary to support the software engineering laboratory and other software courses. The book also provides a detailed description of each of these listed standards that have been tailored to match the requirements of a university course in software development. These tailored standards are based on the "look and feel" of as well as the structure of the IEEE's commercial software engineering standards. In addition, the book is "salted" with stories from both software development work places and the university classroom, both of which provide illustrations relating to some of the problems in developing software, and in some cases solutions to these problems.
Richard H. Thayer, Andrew D. McGettrick
CSEE&T1
1984 Guest Editorial: Software Engineering Project Management
Richard H. Thayer, Arthur B. Pyster
IEEE Trans. Software Eng.1
1981 Major Issues in Software Engineering Project Management
abstract
Software engineering project management (SEPM) has been the focus of much recent attention because of the enormous penalties incurred during software development and maintenance resulting from poor management. To date there has been no comprehensive study performed to determine the most significant problems of SEPM, their relative importance, or the research directions necessary to solve them. We conducted a major survey of individuals from all areas of the computer field to determine the general consensus on SEPM problems. Twenty hypothesized problems were submitted to several hundred individuals for their opinions. The 294 respondents validated most of these propositions. None of the propositions was rejected by the respondents as unimportant. A number of research directions were indicated by the respondents which, if followed, the respondents believed would lead to solutions for these problems.
Richard H. Thayer, Arthur B. Pyster, Roger C. Wood
IEEE Trans. Software Eng.1
1980 Organizational structures used in software development by the U.S. aerospace industry
Richard H. Thayer
J. Syst. Softw.1