I had the opportunity to continue the preceding mission. During this stage, I have been more and more involved in the quality process. On this purpose, I was in charge of settling and managing weekly meetings aiming at enhancing quality at various levels:

• readability, maintenance, frameworking and documentation of the source code,
• systematic writting of unitary tests (especially via JUnit and CppUnit),
• technical indicators settling: use of jMetra for the metrics, Simian for redundancy,
• continuous integration lying on nightly build (I built the nightly build system via Ant buildfiles Ant now available for every components, and I evaluated AntHill on that purpose),
• the component delivery process,
• taking into account the production teams needs and constraints, the help to clients.

On my own initiative, I have extracted a Java framework that is now used by all components as a versionned library: this emphasizes a component paradigm, and avoided a source code redundancy very costly as far as liability is concerned and prevented to get rid of the maintenance problem.

I have developed and set up an XML/XSLT framework that enables to output documents on the intranet, but also release notes: the latter is used by all components from now on. So as to improve communication, I had the opportunity to install and administer a Plone V1.0.1 server, in order to enable the team to directly publish content. By the way, I have been developing a Plone product with the help of Archetypes, which integrates the previous framework.

In parallel, I was still working on the migration project: I have been in charge with programming new clients using the new services, in order to automate the referential update through procedures dedicated to the production team. Moreover, I used the SSL Foundation Classes API Java in order to enhance our services as far as real-time is concerned.

The project is managed by a team in charge with market sales IT applications, more precisely on legacy applications dealing with securities. The development is well balanced between C++ - through Visual C++ V6.0 IDE - and Java - with Together Control Center V6 and IDEA V3.

Beforehand, I have been in charge with a legacy C++ application aiming at exporting and exporting market data under XML format. On that purpose, an import grammar, close to SQL has been defined with ANTLR, and then the corresponding parser is generated in C++: this parser enables to interprete queries supposed to conform the grammar.

Then, I have been asked to improve the CORBA services developed by the team: those service handle market data and have been complementarily developed in C++ and Java; the implementation of the bus is ORBIX V3.0.1. From exception handling, to non-regretion testing, I have been developing a framework that makes the building, load testing, reporting of every service totally automatic. I used the open-source CppUnit V1.6.2 and Log4Cpp V0.2.7 and report the result under XML format, which enables to transform that result in HTML for instance. All this automation was made possible thanks Ant, which I have been massively using, so as to industrialize the process managment.

During the integration process I have been involved in, the purpose of the project was to validate a web application aimed at Virtual Internet Services Provider (VISP) (Siris customers).

The services delivered by this application offer web pages hosting, the e-mail, the internet web e-mail, a domain name declaration to DNS. In order to highlight the issue of that project, I had to understand more closely how the DNS works.

The application, which is written in Java V1.3, has been developed with the J2EE V1.3 framework: the GUI part is based on Struts framework, whereas the businees object part makes use of EJB V1.1. The application server is not a single block, since it is made, on the one side, of two iPlanet Application Server V6.0 clustered servers (as far as web and Servlet/JSP containers is concerned), on the other side, of various EJB V1.1 containers implemented by JBoss V2.4.0. The iPlanet Application Server V6.0 application server massively makes use of an LDAP  server, implemented by iPlanet Directory Server V4: this is the reason why I had to make aknowlegment with the LDAP  standard. All code development uses Log4j so as to enhance runtime execution logging. Moreover, I had the opportunity to use Ant V1.3 in order to automate the service deployment on each machine hosting the EJB V1.1 containers.

At last, in order to validate this application, I developed another web application enabling the initialization and handling of the database used by the previous VISP application: this application has been developed and tested with the Servlet/JSP container Tomcat V4. It uses JDBC standard in order to interface with the database, it it based on the Model View-Controller (MVC) Struts, also uses Log4j logging framework, and is fully administered by an Ant script.

Ce projet, pendant lequel j'ai eu l'occasion d'encadrer trois collègues, a permis de produire un prototype pour un éventuel client. Ce prototype devait mettre en valeur le savoir-faire de la société en matière de conception d'une application web permettant aux employés d'une compagnie d'assurance, d'accéder aux données relatives aux assurés et à leurs contrats d'assurance. Le client souhaitait incorporer à cette application la technologie J2EE V1.3, ainsi que JMS afin de pouvoir réaliser une migration progressive de base de données depuis un système de base de données hérité (système de fichiers "à plat") sur AS400 vers une base de données Oracle V8.

Le prototype a été développé (en Java V1.3) autour de la plate-forme J2EE V1.3. Le conteneur de Servlet/JSP était Tomcat V5.0 lors du développement. Quant au déploiement, c'est le conteneur d'EJB V1.1 WebLogic V6.0 qui a été utilisé. Le bus JMS V1.0 retenu était Sonic MQ V3.5; l'annuaire LDAP  utilisé était iPlanet Directory Server V4. La partie graphique cliente