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

Ian D. Cottam

dblp:50/1932 · DBLP profile ↗
← Back
1ranked-venue papers
1as 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 · 1 · 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 · 70% Software maintenance and evolution · 30%

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

TopicWeightPapersLastEvidence papers
Requirements engineering and software design
formal specification
0.011984
The Rigorous Development of a System Version Control Program · IEEE Trans. Software Eng. 1984
Requirements engineering and software design
software architecture
0.011984
The Rigorous Development of a System Version Control Program · IEEE Trans. Software Eng. 1984
Requirements engineering and software design › formal specification
VDM
0.011984
The Rigorous Development of a System Version Control Program · IEEE Trans. Software Eng. 1984
Software maintenance and evolution › software configuration management
version control
0.011984
The Rigorous Development of a System Version Control Program · IEEE Trans. Software Eng. 1984
Software maintenance and evolution
system evolution
0.011984
The Rigorous Development of a System Version Control Program · IEEE Trans. Software Eng. 1984

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

vienna development method · 0.0formal specification · 0.0
YearPublicationVenuePosition
1984 The Rigorous Development of a System Version Control Program
abstract
A rigorous approach to software development is followed in developing a program to control the various components and versions of systems. This particular approach to systematic program development is known as the Vienna Development Method (VDM). This paper documerits the author's early experiences with VDM on a small, yet nontrivial, application. The functional specification of the version control system is presented in detail. Design decisions taken for a prototype implementation are also included. The version control program developed is based upon the Gandalf System Version Control Environment of Carnegie-Mellon University. Both that system and the subject of this case study support the most common forms of component interdependency relations, and methods of system evolution.
Ian D. Cottam
IEEE Trans. Software Eng.1