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

Kenneth E. Schoman Jr.

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

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

Software engineering, systems software and programming languages · 2

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
2 papers
Requirements engineering and software design · 100%

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

TopicWeightPapersLastEvidence papers
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 › specification
functional specification
0.011977
Structured Analysis for Requirements Definition · IEEE Trans. Software Eng. 1977
Requirements engineering and software design › requirements analysis
structured analysis
0.011976
Structured Analysis for Requirements Definition (Abstract) · ICSE 1976

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

structured analysis · 0.0
YearPublicationVenuePosition
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.2
1976 Structured Analysis for Requirements Definition (Abstract)
Douglas T. Ross, Kenneth E. Schoman Jr.
ICSE2