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

Kent Johnson

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

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

Artificial intelligence and machine learning · 1Systems, architecture and hardware · 1Software engineering, systems software and programming languages · 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
2 papers
Software maintenance and evolution · 52% Empirical software engineering · 26% Programming languages and type systems · 22%
Artificial intelligence
1 paper
Robot manipulation · 100%

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

TopicWeightPapersLastEvidence papers
Empirical software engineering
collaborative software development
0.011988
Orwell - A Configuration Management System for Team Programming · OOPSLA 1988
Software maintenance and evolution
software configuration management
0.011988
Orwell - A Configuration Management System for Team Programming · OOPSLA 1988
Software maintenance and evolution › software configuration management
version control
0.011988
Orwell - A Configuration Management System for Team Programming · OOPSLA 1988
Robotics › Robot manipulation › robot programming
robot programming languages
0.011987
Smalltalk as a programming language for robotics? · ICRA 1987

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

symbolic processing · 0.0object-oriented programming · 0.0source code sharing · 0.0object code sharing · 0.0
YearPublicationVenuePosition
1988 Orwell - A Configuration Management System for Team Programming
abstract
In this paper, we describe the design and implementation of Orwell, a configuration management tool for multiperson Smalltalk projects. Although the system described has been implemented for Smalltalk, the design is applicable to other languages such as C++, Objective-C or ADA. Smalltalk is well recognized as a productive programming environment for an individual programmer, but its lack of team support is currently a major obstacle in using Smalltalk for a large software project. To support multiperson Smalltalk programming, Orwell provides both source and object code sharing as well as version control on a network of personal workstations. Class ownership is used as the primary means for dividing work among programmers during the lifecycle of a project. Orwell also supports groups of programmers not physically connected to a common file server. We describe our implementation which preserves the productive exploratory environment of Smalltalk. Seamless integration and performance are essential for Orwell to be accepted and used by Smalltalk programmers.
Dave A. Thomas, Kent Johnson
OOPSLA2
1987 Smalltalk as a programming language for robotics?
abstract
Programming languages for robotics applications are continually being developed and extended as the applications become more sophisticated. Language evolution is proceeding along two directions: (1) providing more and better facilities for task-level as opposed to robot-level programming and (2) providing better facilities for simulation, graphics and symbolic manipulation. The trend makes it clear that the full capabilities of a general purpose programming language are needed. Instead of developing a new language from the ground up, it is easier and more productive to take an existing language with all the requisite general purpose facilities and specialize it for robotics. Because of its symbolic processing facilities, its object-oriented nature, its usefulness as a simulation language, and its sophisticated graphical interface, Smalltalk is an ideal candidate for specialization. We discuss in more detail why this is the case and we show how a programming language that approaches the power of AL can be imbedded in Smalltalk within 2-4 person-months of effort.
Wilf R. LaLonde, Dave A. Thomas, Kent Johnson
ICRA3