Demo Data from EDBT 2026 / reviewers in the wild / expert
Robin A. Nicholl
dblp:30/4197
· DBLP profile ↗
7ranked-venue papers
4as first author
0since 2021 · last 1990
—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-authorGraphics, computer vision, multimedia, augmented reality and games · 2 · 1 first-authorApplied, interdisciplinary, general and emerging computing · 2 · 2 first-authorHuman-computer interaction and ubiquitous computing · 1
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 |
Compilers and program optimization · 25% Requirements engineering and software design · 25% Program verification · 25% | |
| Computer graphics and multimedia
1 paper |
Rendering · 100% |
Topics — the 3 heaviest of 6, each with the papers that count most for it
| Topic | Weight | Papers | Last | Evidence papers |
|---|---|---|---|---|
Requirements engineering and software design
formal specification |
0.0 | 1 | 1990 | Unreachable States in Model-Oriented Specifications · IEEE Trans. Software Eng. 1990 |
Compilers and program optimization
program transformation |
0.0 | 1 | 1990 | Performing geometric transformations by program transformation · ACM Trans. Graph. 1990 |
Programming languages and type systems › rewriting systems
graph rewriting |
0.0 | 1 | 1988 | An Integrated Life-Cycle Model for Software Maintenance · IEEE Trans. Software Eng. 1988 |
Methods — techniques the papers use, named apart from their topics
program transformation · 0.0program equivalence · 0.0formal specification analysis · 0.0graph rewriting rules · 0.0geometric transformation · 0.0
| Year | Publication | Venue | Position |
|---|---|---|---|
| 1990 | Introducing formality into the software development process: experience with a software project courseabstractOne testbed for examining formal methods is a software project course. The author describes how the software process model used for such a course is now at the point where students are required to adopt an entirely formal approach to the development of their software projects. This software process model also strictly separates the responsibility for building a software system from the responsibility for specifying it; a separation that is facilitated by the use of formal notation to achieve precise communication. The author describes this software development process and assesses it both from an engineering and from an educational perspective. He also identifies areas where the effectiveness of formal methods must be further increased.> Robin A. Nicholl |
COMPSAC | 1 |
| 1990 | Performing geometric transformations by program transformationabstractProblems in geometry often possess symmetry properties that may be exploited in order to develop solutions. Algorithms based on these symmetry properties will frequently use geometric transformations to transform one case into another (symmetric) case. One advantage of this approach is that the algorithm avoids enumeration of cases and thus is shorter and generally easier to read. One disadvantage is that some additional execution time is required to perform these transformations. We describe how simple program equivalences may be used as program transformations to eliminate this additional execution time from programs that use geometric transformations. This approach has been used to develop an efficient implementation of a new algorithm for the two-dimensional line-clipping problem. Robin A. Nicholl, Tina M. Nicholl |
ACM Trans. Graph. | 1 |
| 1990 | Unreachable States in Model-Oriented SpecificationsabstractFormal specification methods are being used to improve the quality of written specifications and to eliminate errors at an early stage of software development. The detection of errors in a specification generally requires that the specification be compared against some loosely defined real-world concepts. A criterion for evaluating the quality of a model-oriented specifications is introduced and the problems associated with specifications which do not meet this criterion are explained. These problems are particularly troublesome when reusable software components are being specified or when a bottom-up implementation strategy is being used.> Robin A. Nicholl |
IEEE Trans. Software Eng. | 1 |
| 1988 | Integrating three tool-based approaches to software engineeringabstractThe author describes a software tool that supports transformation and verification activities, as well as some more widely used dynamic analysis activities. How the design of this tool supports not only the different activities but also their interaction is explained and the advantages of integrating these activities are briefly discussed. The author reports on the current status of the implementation and on enhancements that are being implemented.> Robin A. Nicholl |
COMPSAC | 1 |
| 1988 | An Integrated Life-Cycle Model for Software MaintenanceabstractAn integrated life-cycle model is presented for use in a software maintenance environment. The model represents information about the development and maintenance of software systems, emphasizing relationships between different phases of the software life cycle. It provides the basis for automated tools to assist maintenance personnel in making changes to existing software systems. The model is independent of particular specification, design, and programming languages because it represents only certain 'basic' semantic properties of software systems: control flow, data flow, and data structure. The software development processes by which one phase of the software life cycle is derived from another are represented by graph rewriting rules, which indicate how various components of a software system have been implemented. This approach permits analysis of the basic properties of a software system throughout the software life cycle. Examples are given to illustrate the integrated software life-cycle model during evolution.> Stephen S. Yau, Robin A. Nicholl, Jeffrey J. P. Tsai, Sying-Syang Liu |
IEEE Trans. Software Eng. | 2 |
| 1987 | An efficient new algorithm for 2-D line clipping: Its development and analysisabstractThis paper describes a new alorithm for clipping a line in two dimensions against a rectangular window. This algorithm avoids computation of intersection points which are not endpoints of the output line segment. The performance of this algorithm is shown to be consistently better than existing algorithms, including the Cohen-Sutherland and Liang-Barsky algorithms. This performance comparison is machine-independent, based on an analysis of the number of arithmetic operations and comparisons required by the different algorithms. We first present the algorithm using procedures which perform geometric transformations to exploit symmetry properties and then show how program transformation techniques may be used to eliminate the extra statements involved in performing geometric transformations. Tina M. Nicholl, D. T. Lee, Robin A. Nicholl |
SIGGRAPH | 3 |
| 1980 | Assertion techniques for dynamic monitoring of linear list data structures
Stephen S. Yau, John L. Ramey, Robin A. Nicholl |
J. Syst. Softw. | 3 |