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.

Arthur G. Ryman

dblp:81/6041 · DBLP profile ↗
← Back
3ranked-venue papers
0as first author
0since 2021 · last 2010
—ORCID · none

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

Software engineering, systems software and programming languages · 3

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
3 papers
Empirical software engineering · 64% Program verification · 21% Requirements engineering and software design · 10%

Topics — the 7 heaviest of 8, each with the papers that count most for it

TopicWeightPapersLastEvidence papers
Empirical software engineering
developer studies
0.112010
Timesheet assistant: mining and reporting developer effort · ASE 2010
Empirical software engineering
mining software repositories
0.112010
Timesheet assistant: mining and reporting developer effort · ASE 2010
Program verification
constraint checking
0.012003
Visual Constraint Diagrams: Runtime Conformance Checking of UML Object Models versus Implementations · ASE 2003
Program verification › dynamic verification
runtime verification
0.012003
Visual Constraint Diagrams: Runtime Conformance Checking of UML Object Models versus Implementations · ASE 2003
Requirements engineering and software design
software architecture
0.012003
Visual Constraint Diagrams: Runtime Conformance Checking of UML Object Models versus Implementations · ASE 2003
Empirical software engineering
software project management
0.012010
Timesheet assistant: mining and reporting developer effort · ASE 2010
Program analysis › static analysis
dependency analysis
0.011992
Visualizing and Querying Software Structures · ICSE 1992

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

statistical analysis · 0.1runtime checking · 0.0constraint diagrams · 0.0graphlog · 0.0
YearPublicationVenuePosition
2010 Timesheet assistant: mining and reporting developer effort
abstract
Timesheets are an important instrument used to track time spent by team members in a software project on the tasks assigned to them. In a typical project, developers fill timesheets manually on a periodic basis. This is often tedious, time consuming and error prone. Over or under reporting of time spent on tasks causes errors in billing development costs to customers and wrong estimation baselines for future work, which can have serious business consequences. In order to assist developers in filling their timesheets accurately, we present a tool called Timesheet Assistant (TA) that non-intrusively mines developer activities and uses statistical analysis on historical data to estimate the actual effort the developer may have spent on individual assigned tasks. TA further helps the developer or project manager by presenting the details of the activities along with effort data so that the effort may be seen in the context of the actual work performed. We report on an empirical study of TA in a software maintenance project at IBM that provides preliminary validation of its feasibility and usefulness. Some of the limitations of the TA approach and possible ways to address those are also discussed.
Renuka Sindhgatta, Nanjangud C. Narendra, Bikram Sengupta, Karthik Visweswariah, Arthur G. Ryman
ASE5
2003 Visual Constraint Diagrams: Runtime Conformance Checking of UML Object Models versus Implementations
abstract
This paper presents visual constraint diagrams (VCD), an extension to UML (Unified Modeling Language) object diagrams for expressing constraints over object models. VCD allows designers to express well-formedness constraints that cannot be expressed using class diagrams alone; an example of such a constraint is that a linked list data structure cannot have any loops. VCD offers two advances over existing techniques: (1) they allow constraints to be expressed within the visual notation of UML, without resorting to complex textual notations such as OCL; and (2) VCD can be checked at runtime, increasing the value of design documents to developers. An editor and a checker for VCD have been implemented as part of the Rosetta software design tool.
Christopher J. Turner, T. C. Nicholas Graham, Christopher Wolfe, Julian Ball, David Holman, Hugh D. Stewart, Arthur G. Ryman
ASE7
1992 Visualizing and Querying Software Structures
abstract
Software engineering problems often involve large sets of objects and complex relationships among them.This report proposes that graphical visualization techniques can help engineers understanci and solve a class of these problems.To illustrate this, two problems are analyzed and recast using the graphical language GraphLog.The fwst problem is that of simplifying dependencies among components of a system, which translates into removing cycles from a graph.The second problem is that of designing an efficient code overlay structure, which is facilitat cd in several ways through graphical techniques.
Mariano P. Consens, Alberto O. Mendelzon, Arthur G. Ryman
ICSE3