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
Problem frame patterns: an exploration of patterns in the problem space
TL;DR: In this article, the authors present five patterns, one for each of Jackson's original problem frames, to make the frames themselves and their structure more explicit, and so expose problem frames to a wider audience.
From Abstraction to Realization: Canonical Abstract Prototypes for User Interface Design REVISED
TL;DR: The basic concepts of abstract prototypes are introduced and recent refinements in the modeling notation and the set of canonical abstract components are covered.
Proceedings ArticleDOI
Change detection for aggregate objects with aliasing
James Noble,John Potter +1 more
TL;DR: This work describes a program monitoring technique which takes account of aggregation and aliasing, and which can be used to detect changes automatically, which can simplify programming and design, so producing more reliable systems with less effort.
Proceedings ArticleDOI
Programmers are from Mars, customers are from Venus: a practical guide for customers on XP projects
TL;DR: In this paper, the authors present a set of patterns describing the key roles on a customer team, and the practices that enable customers to fill those roles, so that customers and development teams can increase the velocity and reliability of their projects, and ensure all participants in a project, not just the developers, can work at a sustainable pace.
Book ChapterDOI
Understanding the impact of collection contracts on design
TL;DR: The results indicate that objects which enter collections behave very differently to objects which do not, which should help developers understand the impact of design choices they make, and guide future language designers when adding support for collections and/or equality.