J
James Noble
Researcher at Victoria University of Wellington
Publications - 343
Citations - 9257
James Noble is an academic researcher from Victoria University of Wellington. The author has contributed to research in topics: Agile software development & Object-oriented programming. The author has an hindex of 45, co-authored 339 publications receiving 8782 citations. Previous affiliations of James Noble include Victoria University, Australia & Microsoft.
Papers
More filters
Proceedings ArticleDOI
Ownership types for flexible alias protection
TL;DR: Ownership types form a static type system that indicates object ownership, which provides a flexible mechanism to limit the visibility of object references and restrict access paths to objects, thus controlling a system's dynamic topology.
Proceedings ArticleDOI
The Qualitas Corpus: A Curated Collection of Java Code for Empirical Studies
Ewan Tempero,Craig Anslow,Jens Dietrich,Ted Han,Jing Li,Markus Lumpe,Hayden Melton,James Noble +7 more
TL;DR: The Qualitas Corpus, a large curated collection of open source Java systems, is described, which reduces the cost of performing large empirical studies of code and supports comparison of measurements of the same artifacts.
Book ChapterDOI
Flexible Alias Protection
TL;DR: Using flexible alias protection, programs can incorporate mutable objects, immutable values, and updatable collections of shared objects, in a natural object oriented programming style, while avoiding the problems caused by aliasing.
Journal Article
Flexible Alias protection
TL;DR: Flexible alias protection as mentioned in this paper is a conceptual model of inter-object relationships which limits the visibility of changes via aliases, allowing objects to be aliased but mitigating the undesirable effects of aliasing.
Journal ArticleDOI
Self-Organizing Roles on Agile Software Development Teams
TL;DR: These roles-Mentor, Coordinator, Translator, Champion, Promoter, and Terminator-are focused toward providing initial guidance and encouraging continued adherence to Agile methods, effectively managing customer expectations and coordinating customer collaboration, securing and sustaining senior management support, and identifying and removing team members threatening the self-organizing ability of the team.