GithubHelp home page GithubHelp logo

Report Outline about csc-510-group-g HOT 1 CLOSED

cleebp avatar cleebp commented on July 29, 2024
Report Outline

from csc-510-group-g.

Comments (1)

cleebp avatar cleebp commented on July 29, 2024

Finished outlining the report, shared the document with everyones sharelatex accounts (Effat I shared it with both your gmail and your ncsu emails because I couldn't remember which one you preferred, Ran I shared it with your gmail, Arjun your ncsu).

The general outline of the report is as follows:

  • Abstract
  • Introduction
  • Data collection
    • how did we collect our data
    • what was the process like of taking the data and converting it
    • I know the magic scripts did all this for us but we should walk through all the steps of what it did (that way they know we did more than just take a script and run)
    • Anonymization, how did it work
    • Talk about the multi user same user issue (like how it saw Ran as two users), and how we got around it
  • Small Features Detection
    • bulk of our data reporting goes in this section
    • at this point these are just the small individual features we do stats on
    • include graphs, figures, etc. REFERENCE THEM and talk about them, no phantom figures
    • "Define 10-20 feature extractors"
    • don't talk about combining these features into higher level bad smells yet, thats next section
  • Bad Smell Detection
    • this isn't the early bad smell detector, rather its the bit about ranking all the groups for bad smells at the end of project 1
    • "combining the feature extractors, report on the bad smells"
    • so taking all of our little features we reported on, and combining them into more general bad smell categories and how the groups ranked on these.
  • Early Bad Smell Detection
    • What method did we come up with detecting bad smells early
    • Test out our methods on project 1 data at different chronological points: "sort all our data chronologically and map out at what times (t1,t2,etc) these bad smells occur"
  • Conclusion

from csc-510-group-g.

Related Issues (20)

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.