( en | de | ru )

 

Disambiguation of "Lethbridge, Timothy"

Author of the publication

copydeleteadd this publication to your clipboard
CodeSnippets Plug-in to Eclipse: Introducing Web 2.0 Tagging to Improve Software Developer Recall.

, , and . SERA, page 451-460. IEEE Computer Society, (2007)

Please choose a person to relate this publication to

To differ between persons with the same name, the academic degree and the title of an important publication will be displayed. You can also use the button next to the name to display some publications already assigned to the person.

Stefanie Lethbridge

Stefanie Lethbridge

Timothy Saunders

Timothy Sulo

Timothy Leung

 

Other publications of authors with the same name

Metrics for Concept-Oriented Knowledge Bases.. International Journal of Software Engineering and Knowledge Engineering, 8 (2): 161-188 (1998)Applying Umple to the rover control challenge problem: A case study in model-driven engineering., and . MoDELS (Workshops), volume 2245 of CEUR Workshop Proceedings, page 386-395. CEUR-WS.org, (2018)Umple: An Open-Source Tool for Easy-To-Use Modeling, Analysis, and Code Generation.. MoDELS (Demos), volume 1255 of CEUR Workshop Proceedings, CEUR-WS.org, (2014)IEEE-CS/ACM computing curricula: software engineering volume., and . ITiCSE, page 217-218. ACM, (2003)Software engineering 2004: ACM/IEEE-CS guidelines for undergraduate programs in software engineering., , , , and . ICSE, page 623-624. ACM, (2005)A Little Knowledge Can Go a Long Way Towards Program Understanding., , and . WPC, page 111-117. IEEE Computer Society, (1997)Enhancing Program Comprehension with Recovered State Models., and . IWPC, page 85-93. IEEE Computer Society, (2002)How Software Engineers Use Documentation: The State of the Practice., , and . IEEE Software, 20 (6): 35-39 (2003)The relevance of software documentation, tools and technologies: a survey., and . ACM Symposium on Document Engineering, page 26-33. ACM, (2002)Mixing Software Engineering Research and Development-What Needs Ethical Review and What Does Not?. Empirical Software Engineering, 6 (4): 319-321 (2001)