1 / 35

Bogor-Java Environment for Eclipse

Bogor-Java Environment for Eclipse. MSE Presentation III Yong Peng. Outline. Component Design Assessment Evaluation Project Evaluation Future Work Conclusion Demo Questions & Comments. Component Design. Component design is the detailed design for each component.

lara
Download Presentation

Bogor-Java Environment for Eclipse

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. Bogor-Java Environmentfor Eclipse MSE Presentation III Yong Peng

  2. Outline • Component Design • Assessment Evaluation • Project Evaluation • Future Work • Conclusion • Demo • Questions & Comments

  3. Component Design • Component design is the detailed design for each component. • This project includes three new plug-ins and one updated plug-in. • In the following several slides, incremental compilation plug-in will be used as an example for component design.

  4. Component Design (Cont.) • High-level component diagram of incremental compilation plug-in.

  5. Component Design (Cont.) • This class handles the life cycle of the plug-in. It provides the error and log methods to log errors. Eclipse uses this class and the plug-in configuration XML to register this plug-in into Eclipse environment. Life cycle methods Error and log methods

  6. Component Design (Cont.)

  7. Component Design (Cont.) • This class handles Bytecode-to-BIR full and delta build. Method “createBir” and “deleteBir” are two helper methods. Full and delta build methods use those two helper methods to create and delete BIR files in file system. Full and delta build methods Create and delete BIR methods

  8. Component Design (Cont.) • This is the helper class that perform delete and write BIR files functions. • The “createBir” and “deleteBir” in BytecodeToBirBuilder class use “writeBIR” and “deleteBIR” methods to delete and write BIR files in file system.

  9. Component Design (Cont.) • The details for other plug-ins can be found in component design document. The following is the URL of design document. • http://www.cis.ksu.edu/~yongpeng/phase3/ComponentDesign.pdf

  10. Assessment Evaluation

  11. Assessment Evaluation (Cont.) • TPTP Automated GUI Recorder • This tool allows users to record GUI actions in the Eclipse platform and play them back to verify the functionality of their product. • It is used to do automate regression tests. • It is part of Eclipse TPTP test framework. • This tool comes out on August, 2005. Since this tool is still in the technology preview stage and has incomplete features, I only used its “Quick Run” function. • The “Quick Run” function uses the currently running workbench as the context to run the selected test cases.

  12. Assessment Evaluation (Cont.)

  13. Project Evaluation • Problems Encountered • Comprehending Project Requirements • Require more Bogor and Eclipse knowledge to understand requirement • Understanding Eclipse Frameworks • Steep learning curve • Lacking development document • FSM for the formal specification • System states and actions missing

  14. Project Evaluation(Cont.) • The total SLOC predicted: 6000 • The actual SLOC implemented for each plug-in • Incremental compilation: 556 • BogorVM view: 2556 • Launcher: 1429 • Error trace in Java: 200 • Total: 4741

  15. Project Evaluation(Cont.) • The problems encountered when created formal specifications during the second phase was the cause of delay.

  16. Project Evaluation(Cont.) • Total hours: 242 hours

  17. Project Evaluation – Phase I

  18. Project Evaluation – Phase II

  19. Project Evaluation – Phase III

  20. Future Work • Making the counter example view as usable as the Eclipse Java debugger • add break-point function when tracing errors • change error trace fully to Java level • etc. • Improving configuration tab in launch pad • Adding syntax highlighting function to BogorVM view

  21. Conclusion • Learnt new technology • JFace, SWT Frameworks • JDT, PDE • TPTP’s Automated GUI Recorder • Went through full Software Development Life Cycle • Applied iterative process in this project • Learnt the importance of documentation • For example: Tracing back to Vision Document for the system requirements details

  22. Demo Create a demo java project and Deadlock.java

  23. Add Bytecode-to-BIR Builder Demo (cont.)

  24. BIR files are generated. Demo (cont.)

  25. Open BogorVM BIR View Demo (cont.)

  26. BIR displays in the BogorVM BIR view. Demo (cont.)

  27. BIR is highlighted if click on Java code in Java editor. Demo (cont.)

  28. Open launcher, create a new Bogor VM configuration. Demo (cont.)

  29. Default Bogor configuration will be load from a properties file Demo (cont.)

  30. Add a “test” parameter into config. Demo (cont.)

  31. The newly added parameter shows in the Bogor Config tab. Demo (cont.)

  32. Remove the “test” parameter, and click Run. A bogor-trail file is generated and the result is output in eclipse console. Demo (cont.)

  33. Double click on the trail file, it opens Bogor counter examples view, bogor-trails editor, and Java editor. Demo (cont.)

  34. Demo (cont.) Step through the error trace

  35. Questions & Comments

More Related