Coder Social home page Coder Social logo

l5-dissertation's People

Contributors

twsswt avatar

Watchers

 avatar  avatar  avatar

l5-dissertation's Issues

Identify Quality Metrics and Write up

  1. Identify a selection of metrics, e.g.:
  • Readability scores
  • Presence of stack traces
  • Presence of screenshots (or other image attachments)
  • ?? See data quality papers for others
  • Links to related documents

What dimensions of an issue to be measured?

E.g. comment thread history? Does the structure of the discussion make a difference?

Topic diversity? Is there a metric for telling how wide ranging a topic is?

Number of comments; does a large number of comments indicate hight or low quality?

Use of markdown format - does presentation make a difference (e.g. paragraph structure, use of bullets...?).

Email Cuezilla Authors

Send a flattering email, stating you found their paper and are interested in their prototype. CC Tim in the email. Also note you appreciate the software may be in a prototype form, but might potentially be interested in developing it further with them.

Project idea to focus on Measuring what makes for high quality tickets

Relevant papers are the Secret Life of Bugs and this one

@Article{Korkala2014WasteIdentification,
author = {Mikko Korkala and Frank Maurer},
title = {Waste identification as the means for improving communication in globally distributed agile software
development },
journal = {The Journal of Systems and Software},
year = 2014,
volume = 95,
pages = {122--140}}

A qualitative study looking at the causes of communication waste in software projects (different types of waste, which implies additional unnecessary communication costs, e.g. repetition, inaccurate).

That some good insight into potentially measuring cost of poor quality?

Maybe focus on high priority tickets, since duration and cost are likely to have a closer relationship (or equally, look at tickets at the same criticality).

Different types of waste might have different impacts.

Then what are the quality attributes of a ticket in different contexts?

  • Stack trace
  • Textual description
  • Language level
  • Spelling/grammar bugs, particulalrly for proper nouns ?
  • Screen shots
  • Comments, discussion (equally what quality attributes cause discussion).

Other things that could be written future work: sentiment analysis. Apply these techniques to the comments applied to issues?

Reading:

  • Sentiment analysis tools and how they work.
  • Available data sets

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.