For a school project, we’re to take Eclipse and critique its algorithms. I know Eclipse is open source, but how exactly do we navigate through the mess of folders and actually see some code that would be able to be critiqued?
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
For a school project, we’re to take Eclipse and critique its algorithms. I know Eclipse is open source, but how exactly do we navigate through the mess of folders and actually see some code that would be able to be critiqued?
The technics below help to spot code with poor design.
If you realy meant algorithms, instead of design, then eclipse will not help you much,
it then is only a text viewer, project browser.
You are left alone with your “natural” intelligence.
How to spot hints for poor design
In Eclipse, open the project to be reviewed:
Install FindBugs, PMD amd Checkstyle
Critical:
findBugs Prio1 and 2
PMD 1 – 3?
Further Install “Metrics“: (I forgot the exact name)
Look at high “cyclomatic complexity”, to spot critical code.
In Checkstyle you would find that measure, too