akondrahman
commented
3 years ago Dec 01 - Dec 15: Task#5: Submit bug reports on detected violations. We both will work on this.
This might be replaced by a survey
Closed akondrahman closed 3 years ago
akondrahman
commented
3 years ago Dec 01 - Dec 15: Task#5: Submit bug reports on detected violations. We both will work on this.
This might be replaced by a survey
akondrahman
commented
3 years ago @fbhuiyan42 As we have majority of the results the paper draft due date has moved. See above.
We will target FSE 2021 for this project. You will leverage the Sec. Software Dev. class at full extent to succeed in this project. For your timely graduation, a successful submission at FSE 2021 is pivotal.
Sep 01 - Oct 15: Task#1: What should be logged to enable forensics in ML? See issue https://github.com/paser-group/MLForensics/issues/2 Oct 15 - Nov 01: Task#2: Build a tool that automatically detects the violations e.g. what needs to be logged but it isn't. Nov 01 - Nov 15: Task#3: Evaluate accuracy of tool with oracle dataset. Build oracle dataset with the help of Justin Murphy. In return you will build the oracle dataset for Justin's FSE project.
Nov 15 - Nov 30: Task#4: Mine datasets from GitHub, GitLab, and existing papers and apply your tool to detect violations. For this you can leverage some of our existing code from SESAME: https://github.com/paser-group/Microservice-Security/blob/master/repo_name_downloader.py and https://github.com/paser-group/Microservice-Security/blob/master/eureka_checker.py
Dec 01 - Dec 15: Task#5: Submit bug reports on detected violations. We both will work on this. Dec 15 - Jan 05: Winter break Jan 12: Task#6: Finish paper writing. Start polishing. I will help you but bulk of the writing will be done by you.
Feb 25: paper due: https://2021.esec-fse.org/track/fse-2021-papers
The structure of the paper will be sth. similar to SESAME ... as a co-author you now have an idea what it takes to get a paper ready.