Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "CDT/Archive/designs/StaticAnalysis/GSoC"

(Requirements)
(Ideas)
Line 15: Line 15:
 
== Ideas ==
 
== Ideas ==
  
Checkers - come up with set of checkers for the area of interest such as code style, programming errors, security vulnerabilities and corresponding software transformation tools
+
* Checkers - come up with set of checkers for the area of interest such as code style, programming errors, security vulnerabilities and corresponding software transformation tools
Searchers - advanced seach capabilities for software, such as "find a function foo which has null as second parameter" - all parameters are provided by user
+
* Searchers - advanced seach capabilities for software, such as "find a function foo which has null as second parameter" - all parameters are provided by user
Metrics - framework, UI and tools to collect and display various software metrics
+
* Metrics - framework, UI and tools to collect and display various software metrics
Architecture - checkers or tool to display software architecture (reverse engineered from the source)
+
* Architecture - checkers or tool to display software architecture (reverse engineered from the source)
Code Clones - utility to find code clones within the software
+
* Code Clones - utility to find code clones within the software
Software Models - build other software models, export to exiting standard models, etc
+
* Software Models - build other software models, export to exiting standard models, etc
  
 
== Template ==
 
== Template ==

Revision as of 14:26, 6 April 2010

Requirements

Mandatory courses/experience with:

  • Compiler Technologies
  • Programming in Java
  • Programming in C/C++ (either)

Recommended experience with:

  • Eclipse Plugin Development
  • Bugzilla - bug tracking system
  • CVS - source control system
  • Contributing to open source project

Ideas

  • Checkers - come up with set of checkers for the area of interest such as code style, programming errors, security vulnerabilities and corresponding software transformation tools
  • Searchers - advanced seach capabilities for software, such as "find a function foo which has null as second parameter" - all parameters are provided by user
  • Metrics - framework, UI and tools to collect and display various software metrics
  • Architecture - checkers or tool to display software architecture (reverse engineered from the source)
  • Code Clones - utility to find code clones within the software
  • Software Models - build other software models, export to exiting standard models, etc

Template

It is not really a template but section that your proposal should have:

  • What you are intending to do and why it is exciting
  • What open source project you want to work with and why, you can mention what license you will use (EPL)
  • Include your background and why are interested in doing this specific project
  • Details on what you want to implement, including design of software and additional parts such as unit testing, documentation etc
  • Scope of work and plan
  • Future plans if any

Back to the top