1 / 10

INGI2255 – LINF2255 Projet de Génie Logiciel: Technologies

INGI2255 – LINF2255 Projet de Génie Logiciel: Technologies. Renaud De Landtsheer. Content. Objective Some Golden Rules Development environment Eclipse Collaborative work Java technologies GUI Network Data Representation. Objective.

dean-chavez
Download Presentation

INGI2255 – LINF2255 Projet de Génie Logiciel: Technologies

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. INGI2255 – LINF2255Projet de Génie Logiciel:Technologies Renaud De Landtsheer

  2. Content • Objective • Some Golden Rules • Development environment • Eclipse • Collaborative work • Java technologies • GUI • Network • Data Representation

  3. Objective • Develop in group a program that implements your LAS program • Be able to make a convincing final demonstration This is a RE project, not a technology project! • More technology is not a good idea • Java is imposed, eclipse is strongly advised

  4. Some (commonsense) Golden Rules • At most ONE technology per physical module (validation of your physical architecture) • Carefully choose your technology • Technology is NOT the ultimate answer to your problem • Technology specialists become module responsible • BEWARE: coder’s optimism “only two days will be fine…” • …

  5. IDE: Eclipse • Plugin environment • “Make” utility: ANT • Build-in support for CVS

  6. Collaborative work tool support: CVS • One central repository • Every uploaded version of every file of your project • Each user has its own copy of all project files • Automated update & checkout mechanisms • Tutorial on the website

  7. GUI SWING (advised) • Look & Feel: java (like ArgoUML) • Written in java (portability! efficiency?) • Good online tutorial • Support for asynchronous GUI update: “invokeLater” SWT • Look & Feel: Platform dependent (like eclipse) • Written in native code (portability~ Efficiency!) • No good online tutorial (only javadoc) Java Servlet and JavaServer Pages • Dynamic Website • Like CGI scripts, but written in java • Need to know HTML • No built-in support for asynchronous update

  8. Network RMI: “Remote Method Invocation” (advised) • Higher level service (well-known paradigm) • Need to use the RMIC “compiler” • Good online tutorial Socket • Low level • Not easy to use Distributed Bus Hidden in dynamic website

  9. Data Representation Data Base (advised if persistence needed) • PostgresQL & JDBC • Cfr. Database course Non-Persistent representation Proprietary Files

  10. Some Useful links • Eclipse • www.eclipse.org • CVS • Project website • Sun tutorials (SWING, RMI, …) • http://java.sun.com/docs/books/tutorial/ • ANT • http://ant.apache.org/manual/ • SWT Javadoc • http://www.erights.org/javadoc/

More Related