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

Timothy N. Wright

dblp:58/3913 · DBLP profile ↗
← Back
3ranked-venue papers
1as first author
0since 2021 · last 2002
—ORCID · none

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

Software engineering, systems software and programming languages · 1Human-computer interaction and ubiquitous computing · 1Applied, interdisciplinary, general and emerging computing · 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
2 papers
Requirements engineering and software design · 100%
Human-computer interaction and pervasive computing
1 paper
User interface design and tools · 100%
Computer architecture, parallel and distributed computing, and storage systems
1 paper
Distributed systems · 100%

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

TopicWeightPapersLastEvidence papers
Requirements engineering and software design › software architecture
architectural style
0.012000
Dragonfly: linking conceptual and implementation architectures of multiuser interactive systems · ICSE 2000
Requirements engineering and software design
software architecture
0.012000
Dragonfly: linking conceptual and implementation architectures of multiuser interactive systems · ICSE 2000
Distributed systems
distributed implementation
0.012000
Dragonfly: linking conceptual and implementation architectures of multiuser interactive systems · ICSE 2000

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

prototype tool · 0.0
YearPublicationVenuePosition
2002 Evaluating Computer-Supported Collaboration for a Problem-Solving Task
abstract
Computer Science researchers are investigating systems that exploit the benefits of collaborative computing technology in learning. There is, however little empirical evidence of the benefits and costs associated with different modes of computer support for collaborative learning. The authors describe an experiment that compares how well 51 children (aged ten and eleven) learnt to solve a small puzzle in three different collaborative learning conditions. Results showed no significant difference in learning outcomes among the three conditions, but revealed that girls solved the puzzle more slowly when collaborating.
Timothy N. Wright, Andy Cockburn
ICCE1
2000 Dragonfly: linking conceptual and implementation architectures of multiuser interactive systems
abstract
Software architecture styles for developing multiuser applications are usually defined at a conceptual level, abstracting such low-level issues of distributed implementation as code replication, caching strategies and concurrency control policies. Ultimately, such conceptual architectures must be cast into code. The iterative design inherent in interactive systems implies that significant evolution will take place at the conceptual level. Equally, however, evolution occurs at the implementation level in order to tune performance. This paper introduces Dragonfly, a software architecture style that maintains a tight, bidirectional link between conceptual and implementation software architectures, allowing evolution to be performed at either level. Dragonfly has been implemented in the Java-based TeleComputing Developer (TCD) toolkit.
Gary E. Anderson, T. C. Nicholas Graham, Timothy N. Wright
ICSE3
1998 The Vista Environment for the Coevolutionary Design of User Interfaces
abstract
User centered design requires the creation of numerous design artifacts such as task hierarchy, task-oriented specification, user interface design, architecture design and code. It is increasingly accepted that such artifacts cannot be created in isolation, but instead incrementally coevolve, where information obtained from the development of one artifact contributes to the development of the others. In user interface development, these artifacts are typically developed by different people with different backgrounds, hindering the communication necessary for coevolution. This paper demonstrates how different design artifacts can be linked, exposing their common elements. Such links can be developed despite the differing points of view and differing levels of detail of the design artifacts. This paper describes Vista, a prototype tool for examining the links between design artifacts, and demonstrates how making these links explicit supports coevolutionary design.
Judy Brown, T. C. Nicholas Graham, Timothy N. Wright
CHI3