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

Holly Hildreth

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

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

Software engineering, systems software and programming languages · 2 · 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
Requirements engineering and software design · 100%
Computer architecture, parallel and distributed computing, and storage systems
1 paper
Embedded and real-time systems · 100%

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

TopicWeightPapersLastEvidence papers
Requirements engineering and software design › formal specification
formal requirements specification
0.011994
Requirements Specification for Process-Control Systems · IEEE Trans. Software Eng. 1994
Requirements engineering and software design
requirements specification
0.011994
Requirements Specification for Process-Control Systems · IEEE Trans. Software Eng. 1994
Embedded and real-time systems › industrial control systems
process control
0.011994
Requirements Specification for Process-Control Systems · IEEE Trans. Software Eng. 1994

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

formal specification language · 0.0formal modeling · 0.0
YearPublicationVenuePosition
1994 Reverse Engineering Requirements for Process-Control Software
abstract
A method of reverse engineering requirements for process-control system software is presented, along with a domain-specific functional structure. Techniques are demonstrated on the executable pseudocode of a commercial avionics control system. Resulting requirements are expressed as a state-based model of externally visible behavior specified completely in the language of process control.>
Holly Hildreth
ICSM1
1994 Requirements Specification for Process-Control Systems
abstract
The paper describes an approach to writing requirements specifications for process-control systems, a specification language that supports this approach, and an example application of the approach and the language on an industrial aircraft collision avoidance system (TCAS II). The example specification demonstrates: the practicality of writing a formal requirements specification for a complex, process-control system; and the feasibility of building a formal model of a system using a specification language that is readable and reviewable by application experts who are not computer scientists or mathematicians. Some lessons learned in the process of this work, which are applicable both to forward and reverse engineering, are also presented.>
Nancy G. Leveson, Mats P. E. Heimdahl, Holly Hildreth, Jon Damon Reese
IEEE Trans. Software Eng.3