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

H. G. Stuebing

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

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

Software engineering, systems software and programming languages · 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
1 paper
Software testing · 100%
Computer architecture, parallel and distributed computing, and storage systems
1 paper
Distributed systems · 100%

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

TopicWeightPapersLastEvidence papers
Software testing
regression testing
0.011984
A Software Engineering Environment (SEE) for Weapon System Software · IEEE Trans. Software Eng. 1984
Distributed systems
distributed network
0.011984
A Software Engineering Environment (SEE) for Weapon System Software · IEEE Trans. Software Eng. 1984
YearPublicationVenuePosition
1984 A Software Engineering Environment (SEE) for Weapon System Software
abstract
A software engineering environment (SEE) has been designed, developed, and used for the life-cycle support of weapon system software. This SEE consists of two types of facilities: software production and integration. The software production facility consists of a software system that runs on a commercial multicomputer configuration. The approach features increased management visibility of the software development process, increased programmer productivity through automation, reducing the cost-of-change during maintenance, and the use of automated regression testing to improve software quality. These facilities have been used for eight years to develop and maintain weapon system software for several projects. This paper describes accomplishments, refinements to the code and test functions, and a general approach to extend the capabilities into the requirements and design phases. Techniques are described that simultaneously allow different methodologies, programming languages, and target computers to be implemented on the same host computer. Also discussed is the Implementation of a SEE in a distributed computer network.
H. G. Stuebing
IEEE Trans. Software Eng.1
1983 Industrialization of weapon system software
H. G. Stuebing
J. Syst. Softw.1