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

Bryan Ratcliff

dblp:45/514 · DBLP profile ↗
← Back
7ranked-venue papers
4as 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 · 5 · 3 first-authorApplied, interdisciplinary, general and emerging computing · 3 · 3 first-authorHuman-computer interaction and ubiquitous computing · 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
3 papers
Requirements engineering and software design · 91% Empirical software engineering · 9%
Interdisciplinary, comprehensive, and emerging computing
1 paper
Computing education · 100%

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

TopicWeightPapersLastEvidence papers
Requirements engineering and software design › design process
program design
0.021989
Specification Influences in Program Design · Int. J. Man Mach. Stud. 1989
An Empirical Investigation into Problem Decomposition Strategies Used in Program Design · Int. J. Man Mach. Stud. 1985
Requirements engineering and software design
software design methodology
0.011991
PRESTIGE: A CASE Workbench for the JSD Implementor · ICSE 1991
Computing education
programming education
0.011985
An Empirical Investigation into Problem Decomposition Strategies Used in Program Design · Int. J. Man Mach. Stud. 1985

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

empirical study · 0.0
YearPublicationVenuePosition
1994 Automated dismemberment of JSD process specifications
Andrew P. Bass, Bryan Ratcliff
Inf. Softw. Technol.2
1991 Re-affirming support for a transformational approach to software development: theory and practice
abstract
Inherent virtues, allied to proper in-the-large support, make the transformational paradigm a potent weapon for the software engineer. A taxonomic model of software transformational space is sketched. The main vertical in-the-large transformations needed for Jackson system development are described; these are provided within the CASE workbench PRESTIGE.>
Bryan Ratcliff
COMPSAC1
1991 PRESTIGE: A CASE Workbench for the JSD Implementor
Andrew P. Bass, Maeve Boyle, Bryan Ratcliff
ICSE3
1990 An inversion capability for the PRESTIGE workbench: some basic issues
abstract
The PRESTIGE workbench is an integrated CASE (computer-aided software environment) intended to provide full implementation support for Jackson System Development (JSD). JSD is an operational software development method, and thus implementation in JSD is essentially a transformational process. The main objective is to offer a generalized transformational facility that the JSD implementor can apply as desired to suit the needs of any particular implementation scenario, although a default implementation capability is also provided. Many of the transformations required can be automated, and the so-called 'inversion' transformations play a pivotal role in that capability. The author addresses a variety of technical issues that need to be considered in providing a user-controlled inversion facility within the PRESTIGE environment. The issues discussed include schedulerless implementation, rough merges, multiple inversion, buffering, and write inversions.>
Bryan Ratcliff
COMPSAC1
1989 Specification Influences in Program Design
Jawed I. A. Siddiqi, Bryan Ratcliff
Int. J. Man Mach. Stud.2
1988 Early and not-so-early prototyping-rationale and tool support
abstract
A taxonomy is advanced that classifies prototyping in software engineering according to its application to different stages of the software development process. The prototyping categories are termed early, middle, and late. The rationale and tool support for each category are described and compared. Whereas early prototyping is the traditional perception of the activity, middle and late prototyping are separate categories that are supported by operational methods of software development. In particular, late prototyping evaluates performance, rather than functionality and interface, and is made cost-effectively feasible by operational methods.>
Bryan Ratcliff
COMPSAC1
1985 An Empirical Investigation into Problem Decomposition Strategies Used in Program Design
Bryan Ratcliff, Jawed I. A. Siddiqi
Int. J. Man Mach. Stud.1