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.

Douglas T. Ross

dblp:31/2488 · DBLP profile ↗
← Back
7ranked-venue papers
7as first author
0since 2021 · last 1989
—ORCID · none

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

Software engineering, systems software and programming languages · 5 · 5 first-authorSystems, architecture and hardware · 2 · 2 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
5 papers
Requirements engineering and software design · 50% Empirical software engineering · 49% Compilers and program optimization · 0%
Human-computer interaction and pervasive computing
1 paper
Interaction techniques and input · 100%

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

TopicWeightPapersLastEvidence papers
Empirical software engineering
software engineering history
0.011989
The NATO Conferences form the Perspective of an Active Software Engineer · ICSE 1989
Requirements engineering and software design
requirements definition
0.021977
Structured Analysis for Requirements Definition · IEEE Trans. Software Eng. 1977
Structured Analysis for Requirements Definition (Abstract) · ICSE 1976
Requirements engineering and software design › requirements analysis
structured analysis
0.021977
Structured Analysis (SA): A Language for Communicating Ideas · IEEE Trans. Software Eng. 1977
Structured Analysis for Requirements Definition (Abstract) · ICSE 1976
Requirements engineering and software design › specification
functional specification
0.011977
Structured Analysis for Requirements Definition · IEEE Trans. Software Eng. 1977
Processor architecture and microarchitecture › execution model
decoupled access/execute architecture
0.011965
Current status of AED · DAC 1965

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

structured analysis · 0.0graphical language · 0.0
YearPublicationVenuePosition
1989 The NATO Conferences form the Perspective of an Active Software Engineer
abstract
No abstract available.
Douglas T. Ross
ICSE1
1977 Guest Editorial - Reflections on Requirements
Douglas T. Ross
IEEE Trans. Software Eng.1
1977 Structured Analysis (SA): A Language for Communicating Ideas
abstract
Structured analysis (SA) combines blueprint-like graphic language with the nouns and verbs of any other language to provide a hierarchic, top-down, gradual exposition of detail in the form of an SA model. The things and happenings of a subject are expressed in a data decomposition and an activity decomposition, both of which employ the same graphic building block, the SA box, to represent a part of a whole. SA arrows, representing input, output, control, and mechanism, express the relation of each part to the whole. The paper describes the rationalization behind some 40 features of the SA language, and shows how they enable rigorous communication which results frorn disciplined, recursive application of the SA maxim: "Everything worth saying about anything worth saying something about must be expressed in six or fewer pieces."
Douglas T. Ross
IEEE Trans. Software Eng.1
1977 Structured Analysis for Requirements Definition
abstract
Requirements definition encompasses all aspects of system development prior to actual system design. We see the lack of an adequate approach to requirements definition as the source of major difficulties in current systems worlk This paper examines the needs for requirements definition, and proposes meeting those objectives with three interrelated subjects: context analysis, functional specification, and design constraints. Requirements definition replaces the widely used, but never well-defined, term "requirements analysis."
Douglas T. Ross, Kenneth E. Schoman Jr.
IEEE Trans. Software Eng.1
1976 Structured Analysis for Requirements Definition (Abstract)
Douglas T. Ross, Kenneth E. Schoman Jr.
ICSE1
1967 The design and programming of a display interface system integrating multi-access and satellite computers
abstract
This paper describes a system for providing mixed graphical and verbal communications with a multi-access computer via a satellite computer with a display. We assume that such an arrangement is necessary to satisfy an on-line user's large-scale computation and storage requirements economically, and to provide graphical facilities at remote terminals. The general-purpose Display Interface System, parts of which reside in each machine, acts as an interface between the user's programs and the display terminal. It provides means for communication as well as system functions required in each machine. Since it is general purpose, and no user will require all the features it provides, the software exists in the form of system libraries from which a user may select an appropriate subset for his particular application. The user's interface with this system in each machine is intended to be hardware independent
Douglas T. Ross, Robert H. Stotz, Daniel E. Thornhill
DAC1
1965 Current status of AED
abstract
At the previous SHARE Design Automation Workshop a general description of the then current activities of the MIT Computer-Aided Design Project was given. The principal activities which were outlined were: (1) The cooperative AED-1 Project in which visiting staff programmers from industry join with our MIT staff in the research and development of advanced compiler and language processing techniques to serve as the foundation for a total Computer-Aided Design System for man-machine problem solving, (2) Studies of mixed verbal and graphical language processing by the uniform techniques of the Algorithmic Theory of Language. Since that time extensive progress has been made in both of these areas.
Douglas T. Ross
DAC1