Eclipse DemoCamps November 2009/Karlsruhe/Presenters
- 1 Demos and Presenters
- 1.1 Automatic Ontology Extraction with SMILA
- 1.2 Das ist hier Usus...
- 1.3 EclipseRT (Runtime Project)
- 1.4 Horus - Business Process Management based on Eclipse RCP
- 1.5 Running OSGi-based applications in the Cloud
- 1.6 SoMoX - The SOftware MOdel eXtractor is able to reverse engineer component models from source code
- 1.7 Write once, test everywhere? Cross platform development and testing with Eclipse
Demos and Presenters
Automatic Ontology Extraction with SMILA
SMILA (SeMantic Information Logistics Architecture) is an extensible framework for building information management solutions to access unstructured information in the enterprise. Besides providing essential infrastructure components and services, SMILA also delivers ready-to-use add-on components, like connectors to most relevant data sources and some data processing services. Using the framework as basis will enable developers to concentrate on the creation of higher value solutions, like search or semantic driven applications. In this demo we will show how automatic ontology extraction can be realized by simply integrating an entity extraction web service (provided by OpenCalais) in SMILA.
|Igor Novakovic is Deputy Director Development at Empolis GmbH. After joining empolis in 2000, he was at first responsible for the development of some server-side components written in C + + and Java. Later on, beside designing and developing J2EE applications, he successfully introduced company-wide the application lifecycle management based on open source tools. From 2006 he led the development of the solution "empolis Service Lifecycle Suite". Since late 2007 he is the co-lead of the SeMantic Information Logistics Architecture (SMILA) project.|
Das ist hier Usus...
In Software-Teams sind gemeinsame Vorstellungen über Coding-Praxis und Design-Ideen eine wichtige Voraussetzung für erfolgreiche und nachhaltige Entwicklungsarbeit. In guten Teams bildet sich schnell ein 'Usus', eine allseits geteilte Vorgehensweise. Diese erstreckt sich auch (und besonders) auf die Verwendung von Tools und die Einhaltung von Qualitätskriterien.
Um den in unseren Teams geltenden 'Usus' zu unterstützen haben wir einige Plug-Ins für die Eclipse-IDE entwickelt, die verbreitete Tools wie CheckStyle und EclEmma integrieren, erprobte Qualitätsindikatoren 'on-the-fly' berechnen, und das Einstellen von Compiler- und Tool-Optionen zum reinen Vergnügen werden lassen.
EclipseRT (Runtime Project)
Many projects at Eclipse produce technology that is useful in a wide range of runtime scenarios. Responding to a lack of integration scenarios, this demo connects the dots for runtime technologies at Eclipse. We'll bring together topics such as Equinox, RAP, EclipseLink, BIRT and Riena into a coherent package, showing how the pieces can fit together to accelerate development solutions.
|Benjamin Muskalla works as a software developer and consultant at EclipseSource in Karlsruhe, Germany. He is one of the core team of committers on the Rich Ajax Platform (RAP) project and contributes to several other Eclipse projects including E4, Platform UI and JDT. His interests include squash, billiards and generally spreading the word about RAP.|
Horus - Business Process Management based on Eclipse RCP
Mit Horus wird ein modernes Instrumentarium für das Business Process Engineering zur Verfügung gestellt. Auf Basis wissenschaftlich fundierter Konzepte (z.B. XML-Netze) werden Software Tools geboten, die in Verbindung mit der Horus Methode™ ein durchgängiges agiles Modellierungsverfahren unterstützen. Horus unterstützt das kooperative Arbeiten in Business Communities, auch über Unternehmensgrenzen hinweg.
Running OSGi-based applications in the Cloud
Watch a live demonstration that shows the complete life cycle of running an application on a Compute Cloud. Starting with a workspace crammed with Equinox/OSGi-based components, we set up a distributed, virtual infrastructure with the help of g-Eclipse on the Amazon cloud. Then we show the export of our Equinox based application and how to use p2 to deploy the application from our workspace into the cloud.
SoMoX - The SOftware MOdel eXtractor is able to reverse engineer component models from source code
The component extraction supports basic components, composite structures, interfaces, ports, as well as connectors. The extracted models are suitable to improve understanding of existing software and enable further quality analyses. Analyses for software performance, reliability, and maintenance are already available as part of a complementary tool chain. SoMoX extraction is based on the evaluation of multiple source code metrics. The Extraction can be guided by metric settings which allow the adaptation of SoMoX to the specific component definitions and needs of individual projects. Currently, SoMoX supports source code of the languages C/C++, Delphi, and Java. However, its general source code model can be easily extended to further programming languages. SoMoX has been developed within the context of the EU project Q-ImPrESS.
Write once, test everywhere? Cross platform development and testing with Eclipse
How platform independent are Eclipse applications in practice? This talk looks at some of the differences between operating systems supported by Eclipse with respect to RCP applications and examines their effects on usability, development and testing.
The talk is aimed at developers, project managers and testers (automated and manual) working on RCP applications that are intended to run on more than one platform. Participants will learn about large and small differences between the platforms. Some of these differences must simply be considered in the development and testing process, others mean that testing, documentation and development are affected.
Some of the points raised include:
How widgets can behave differently on the platforms Variation in the library support for each platform Other GUI considerations such as tooltips, toolbars, buttons and focus
Automated testers will also benefit from the information and examples in the talk. Ideally, only one automated test should be necessary to test all versions of an application. Some of the differences between the platforms make this aim difficult, and some differences mean finding a lowest common denominator to be able to write tests. The variation between the platforms is therefore something which must be considered at the test planning stage, and in the test design itself.
Participants will learn to consider and deal with any variations between platforms to make cross-platform projects a success.
|Markus Tiede studied at the University of Applied Sciences in Braunschweig. After receiving his diploma in 2008, he started working as a software and test developer at BREDEX GmbH. His responsibilities include development of the GUI-test tool GUIdancer as well as design and maintenance of automated tests for internal and external projects.|