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
Demo Data from SIGIR 2026 / reviewers in the wild / expert

Richard Jordan

dblp:89/4792 · DBLP profile ↗
← Back
2ranked-venue papers
1as first author
0since 2021 · last 2016
—ORCID · none

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

Artificial intelligence and machine learning · 1Software engineering, systems software and programming languages · 1 · 1 first-authorDatabases, data management, data science and information retrieval · 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
1 paper
Requirements engineering and software design · 100%

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

TopicWeightPapersLastEvidence papers
Requirements engineering and software design › object-oriented analysis and design
object-oriented design		 0.011994
Streamlining the Project Cycle With Object-Oriented Requirements · OOPSLA 1994
YearPublicationVenuePosition
2016 PULSE: A Real Time System for Crowd Flow Prediction at Metropolitan Subway Stations
Ermal Toto, Elke A. Rundensteiner, Richard Jordan, Mariya Ishutkina, Kajal T. Claypool, Jun Luo 0007, Fan Zhang 0019
 ECML/PKDD (3)4
1994 Streamlining the Project Cycle With Object-Oriented Requirements
abstract
We have succeeded in streamlining the product development cycle by incorporating object-oriented technology into the requirements definition phase. We have developed a general format, supporting tools and a methodology for describing requirements in an object-oriented fashion. We have validated our approach by incorporating it into the new object-oriented methods being applied to our current project and observing the benefits that resulted. We describe the problems with our earlier requirements specifications which make them unsuitable for developing good object-oriented systems and then explain our approach which eliminates these pitfalls.
Richard Jordan, Ruth Smilan, Alex Wilkinson
 OOPSLA1