1 / 15

JAVA TO C# CONVERTER

Final Iteration. iConverter. JAVA TO C# CONVERTER. TEAM 1 Denesh Kumar Krishnan Rajaram Sumanth Meda Jayaprakash Kapil Vyas. Goals – Final Iteration. JUnit test cases Static analysis Multiple accessibility Documentation (In progress). [estimate] [actual]

lars-gentry
Download Presentation

JAVA TO C# CONVERTER

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Final Iteration iConverter JAVA TO C# CONVERTER TEAM 1 Denesh Kumar Krishnan Rajaram Sumanth Meda Jayaprakash Kapil Vyas

  2. Goals – Final Iteration • JUnit test cases • Static analysis • Multiple accessibility • Documentation (In progress)

  3. [estimate][actual] • Final Iteration: April 30[15h][11] • JUnit testing • Static analysis • Documentation Final Iteration Reflection

  4. edu.uta.iconverter.converter • Classes for converter engine, RegEx, Parsing the file, etc. • edu.uta.iconverter.test • Test cases for the conversion validation • edu.uta.iconverter.ui • Class to provide simple GUI for the application • edu.uta.iconverter.util • Class to read and write to/from a text file(Java/C#) Package structure

  5. Testing results • Ten test cases – various java classes with diverse functionality • All test cases • succeeds

  6. Warning priority: Low (Find high, medium and low priority bugs) Static Analysis

  7. Warning priority: Medium (Find high and medium priority bugs) Static Analysis…

  8. Warning priority: High (Find high priority bugs only) Static Analysis…

  9. Cost-per-Person month = $3600 • Cost-per-hour: $18 • SLOC: 600 • Evasion of few risks • Implementing few innovative algorithms COCOMO2 Estimates

  10. Syntactic analysis  • Hello World!  • Main and other methods  • Data Types  • Operators  • Flow control (switch statements)  • Looping statements  • Class fundamentals  • Exception handling  • Arrays  • Comments  • Compiler Services (!) • Code testing  • Static analysis  What we promised?

  11. IDE: Eclipse Indigo Service Release 1 Debugger: Eclipse Code/Documents Repository: SVN through Subclipse and TortoiseSVN Project Management: Google Code Issue Tracking: Google Code Testing Tools: Junit Static Analysis Tool: FindBugs COCOMO2: http://diana.nps.edu/~madachy/tools/COCOMOII.php Tools used

  12. 1. source control? Yes “Google SVN” 2. build in one step? Yes “ANT build” 3. daily builds? Yes 4. bug database? Yes “Issue tracker on Google code” 5. fix bugs before writing new code? Yes 6. up-to-date schedule? Yes 7. spec? Yes 8. quiet working conditions? Yes 9. best tools? Yes 10. Testing? Yes 11. Hallway usability testing? - Yes Joel Test – Score 10/10

  13. More RegEx More test cases Cover more java functionalities Semantic conversion Compiler services Bytecode conversion Future work

  14. deneshkumar.krishnanrajaram@mavs.uta.edu kapil.vyas@mavs.uta.edu sumanth.medajayaprakash@mavs.uta.edu Contacts

  15. reflections opinions uncertainties

More Related