As part of my work at CGI, I participated in the creation of a web application to allow graduate students to apply for master or doctorate.

Version 0 is a rapid development to cover some parts of the process:

• Allow people to support the candidacy of an applicant by uploading a file.
• Enable internal reviewers to McGill as external reviewers to search and visualize the applications according to their permissions.
• Allow McGill coordinators to manage permissions.

Responsibilities:

• Manage and follow tasks for the team.
• Create files for the installation of the database, configuration and deployment of the package.
• Deploy the application to the test environment.
• Guide and answer questions from testers.

Specifics:

• Grails Application.
• Secure access to the application using Spring security (local database and LDAP for internal reviewers).
• Implement a system that locks people trying to connect several times with an invalid password. They are blocked for one hour.
• Encrypt all passwords in the configuration file.
• Manage the external reviewers (create, assign applications to look at, change their password).
• Communicate with a SOAP web service to save uploaded documents to Documentum.
• Daily jobs to notify and remind referees by e-mail for applications that the system waits for their response.
• The internal and external reviewers can search and view the applications assigned to them by departments and applications list.

The web site (needs an account)

Technologies: BlueprintCSS, CSS, Grails, Groovy, Hibernate, HTML, Java, JavaScript, jQuery, jUnit, Spring Source, Tomcat, WSDL, ZKUI

As part of my work at CGI, I participated in the creation of a web application to allow external users to McGill to create accounts to access multiple McGill`s systems.

McGill needed a system that can connect to multiple web applications with a local account, LDAP, OpenID, and others. That is why they chose to use CAS which allows using many different accounts services.

Responsibilities:

• Manage and follow tasks for the team.
• Create files for the installation of the database, configuration and the package to deploy.
• Deploying the application to the test environment.
• Guide and answer questions from testers.

• Login system
  • Customizing the CAS software.
  • Integration of design in HTML and CSS.
  • Create a basic configuration to allow users to connect to a local database and internal users at McGill.
• User management system in the local database
  • Grails application.
  • Integration of design in HTML and CSS.
  • Secure access to the application using Spring security.
  • Administration section
    • View users and enable / disable them.
    • Make a search in events (audit).
  • Create account section
    • Registration.
    • Forgot password mechanism.
  • My account section
    • Edit our name, email and password.
• Create daily maintenance jobs activated by a web service call.
• Allow to login with different Spring Security “providers” depending on the accessed page.
  • According to the page, LDAP or CAS is used.
  • The login pages are different depending on the case.

Technologies: BlueprintCSS, CAS, CSS, CXF, Grails, Groovy, Hibernate, HTML, Java, JavaScript, jQuery, Spring Source, Tomcat

As part of my work at CGI, I participated in the creation of a new site for L.L.Bean direct to business. This service allows companies to buy clothes of this company and add their logo.

Specifics:

• User Management
  • registration, login, logout and  change password
  • list of shipping addresses
• Subcategories page
  • Display products and their prices
  • Pagination
• Product page
  • Choose a color
  • Show grid sizes and models (male / female) to enter quantities
• Gift cards page
  • Manage the available values ​​dynamically
• Users logos management
  • Upload logos
  • Apply logos on the products
  • Receiving digitized logos by an XML feed
• Management of personalization fees
  • Fees to create new logos
  • Fees to apply logos
• Estimation via email (sending cart by email)
• Management of static pages
• Volume discounts
• Inventory management
• SEO
  • Metadata descriptions
  • Google Remarketing Ads
  • Automatic generation of sitemap.xml
• Performance Optimization
  • Using jProfiler
  • Using ATG cache
  • Using the Transaction Droplet on JSP pages
• Document used libraries licences

The web site

Technologies: Apache HTTP, CSS, HTML, Java, JavaScript, JAXB, JBoss, jMock, jProfiler, jQuery, jUnit, Oracle ATG, Oracle Database XE, Servlet

As part of my work at Morgan Stanley, I improved the external customers reports distribution system. The software already existed and I modified as much of the frontends than the backends components.

Responsibilities:

• Create files for the installation of the database, configuration and the package to deploy.
• Deploying the application to the test and production environments by coordinating with various teams involved.
• Guide and answer questions from testers.
• Train new developers on the team.
• Technical support when the team’s first level could not resolve a problem.

Specifics:

• Frontend
  • Usage of Flex, BlazeDS and Cairngorm libraries.
  • Allow users to save their column layout.
  • Create a new graphic style to integrate the application into a Morgan Stanley’s software suite.
• Backend
  • Create reports cleanup scripts.
  • Create scripts to help with technical support.
  • Improve the archiving processes to make it more robust to failures.
• Documentation
  • Create training documentation for new developers.
  • Creation of documents explaining the use of the system for the first level support team.
• Technical interviews for hiring developers for other teams.

Technologies: Flex, HTML, Java, Perl, Servlet, Spring Source, SyBase

As part of my work at IBM, I had to improve a booking software that was used to book some testing computers and to create a proof of concept of a web console to eventually migrate the current desktop console.

Specifics:

• Improve the phpScheduleIt software to keep more details about the computers that can be booked
  • Add fields to the form information from one machine and add them to the database.
• Creating a Proof of Concept on using Google Web Toolkit as a tool to build a web console
  • Create sample applications.
  • Try libraries like GWT-Ext for other graphic elements.
  • Do performances testing.

Technologies: Google Web ToolKit, HTML, MySQL, PHP