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

Donald F. Utter Jr.

dblp:271/2724 · DBLP profile ↗
← Back
2ranked-venue papers
1as first author
0since 2021 · last 1988
—ORCID · none

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

Computer networks · 1 · 1 first-authorSoftware engineering, systems software and programming languages · 1Applied, interdisciplinary, general and emerging computing · 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.

Software engineering, system software, and programming languages
1 paper
Requirements engineering and software design · 100%

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

TopicWeightPapersLastEvidence papers
Requirements engineering and software design
interface design
0.011982
Writing Requirements for Interfaces Between Computers · IEEE Trans. Commun. 1982
Requirements engineering and software design
requirements specification
0.011982
Writing Requirements for Interfaces Between Computers · IEEE Trans. Commun. 1982

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

design method · 0.0
YearPublicationVenuePosition
1988 Designing software for maintenance and performance
abstract
An approach to addressing the performance issues in the early stages of the design of a software system is presented. The module decomposition of the trouble-analysis subsystem is considered as an example in using this approach. Each module is characterized by its hidden information, external behaviour, and a set of performance parameters. A working system is built using these modules, and it is found that the response time of the working system varies from over an hour to less than a minute by simply varying the value of the performance parameter. Consequently, the system could be tuned by simply varying the value of the performance parameter and not by restructuring the system. The values of the parameters are selected to minimize the response time. The approach is illustrated by a case study involving a pattern recognition system which isolates faults in circuit packs.>
Rajendra P. Mikkilineni, Donald F. Utter Jr.
COMPSAC2
1982 Writing Requirements for Interfaces Between Computers
abstract
This paper describes the form of an interface requirements document and a design method to produce it. Document and design are coupled by embedding the right questions in the document. The completed document answers the questions. Work described in this paper has grown out of practical experience and by reflecting on the general nature of requirements. The paper contains a design method for the construction of interface requirements at an application program level. The general nature of the material makes it applicable to a wide range of device interfaces.
Donald F. Utter Jr.
IEEE Trans. Commun.1