Internship report Author: Mathieu Fortin date: 12 June 2006

Acknowledgements I wish to thank: •

Liam Dwan, Michael Dolling, Patrick Boyd and Anne-Sophie Luypaerts for their help and their patience, and for all the things I have learnt with them.



The Bureau des Stages (Internship office) of the IFIPS who helped me to find this internship.



Jean Calisti, Françoise Meyer and Abdel Lisser for their support and all the arrangements they made to make my time abroad easier.



My family and my friends for their unconditional support.

Internship report - Mathieu Fortin

Table of Contents Chapter 1. Ci3 presentation............................................................................. 1 1.1. Identity...................................................................................................................... 1 1.1.1. History................................................................................................................ 1 1.1.1.1. Creation...................................................................................................... 1 1.1.1.2. Evolution..................................................................................................... 1 1.1.2. Organization....................................................................................................... 1 1.1.2.1. Company type............................................................................................. 1 1.1.2.2. Organisation Chart...................................................................................... 1 1.2. Business.................................................................................................................... 2 1.2.1. Clients................................................................................................................ 2 1.2.1.1. Financial institutions................................................................................... 2 1.2.2. Market characteristics........................................................................................ 2 1.2.2.1. New market................................................................................................. 2 1.2.2.2. Growing market.......................................................................................... 2 1.3. Products.................................................................................................................... 3 1.3.1. Services.............................................................................................................. 3 1.3.2. Syntinel.............................................................................................................. 3 1.3.3. Sword................................................................................................................. 3 Chapter 2. Project presentation....................................................................... 4 2.1. Operational Risk Management (ORM)........................................................................ 4 2.1.1. Basel committee................................................................................................ 4 2.1.1.1. Basel committee history............................................................................. 4 2.1.1.2. Basel II agreement...................................................................................... 4 2.1.2. Banks and regulators......................................................................................... 4 2.1.2.1. role of regulators......................................................................................... 4 2.1.2.2. relation with banks...................................................................................... 4 2.2. Book of Specifications................................................................................................ 5 2.2.1. Program specifications....................................................................................... 5 2.2.1.1. Sword overview........................................................................................... 5 2.2.1.2. Main functionalities..................................................................................... 5 2.2.1.3. Technologies used...................................................................................... 5 2.2.2. Technical specifications...................................................................................... 6 2.2.2.1. Running system requirements.................................................................... 6 2.2.3. Design specifications.......................................................................................... 8 2.2.3.1. Code specifications..................................................................................... 8 2.2.3.2. user interface specifications....................................................................... 8 Chapter 3. Didactic step................................................................................ 10 3.1. Projects and tasks.................................................................................................... 10 3.1.1. Bug tracking system update............................................................................. 10 3.1.2. Sword new features development.................................................................... 10 3.1.3. Sword “Look & Feel” upgrade.......................................................................... 10 3.2. Existing solutions study........................................................................................... 11 3.2.1. Previous version of Sword................................................................................ 11 3.2.2. Implemented features...................................................................................... 11 3.3. Defining objectives.................................................................................................. 11 3.3.1. Identifying the needs........................................................................................ 11 3.3.2. Setting priorities............................................................................................... 11 3.3.3. Creating a schedule.......................................................................................... 11 3.4. Designing solutions................................................................................................. 11 3.4.1. Using academic knowledge.............................................................................. 11 I

Internship report - Mathieu Fortin 3.4.2. Tools selection.................................................................................................. 12 3.4.3. Reaching objectives......................................................................................... 12 3.4.4. Optimization..................................................................................................... 12 Chapter 4. International experience............................................................... 13 4.1. Internship in Ireland................................................................................................. 13 4.1.1. Living abroad.................................................................................................... 13 4.1.1.1. Ireland Vs France...................................................................................... 13 4.1.1.2. Dublin Vs Paris.......................................................................................... 13 4.1.2. Working abroad................................................................................................ 13 4.1.2.1. New working environment and culture...................................................... 13 4.1.2.2. Take part in the activity............................................................................ 13 4.1.2.3. Benefits..................................................................................................... 14 4.2. Project management............................................................................................... 14 4.2.1. Team leader..................................................................................................... 14 4.2.1.1. Responsibilities......................................................................................... 14 4.2.1.2. Requirements and qualities....................................................................... 14 4.2.2. Teamwork......................................................................................................... 14 4.2.2.1. Cooperation and collaboration.................................................................. 14 4.3. Personal benefits..................................................................................................... 15 4.3.1. Developed qualities.......................................................................................... 15 4.3.1.1. Autonomy & flexibility............................................................................... 15 4.3.1.2. Communication skills................................................................................ 15 4.3.1.3. Open mind................................................................................................ 15 Chapter 5. Impressions and Feelings.............................................................. 16 5.1. Internship................................................................................................................ 16 5.2. Experience............................................................................................................... 16 Chapter 6. Annex documents......................................................................... 17 6.1. Internship Planning.................................................................................................. 17 6.2. Time line.................................................................................................................. 18 6.3. Screenshots............................................................................................................. 19 6.3.1. Organisation Mapping...................................................................................... 19 6.3.2. Risk & Control Assessment............................................................................... 20 6.3.3. Report.............................................................................................................. 21

II

Internship report - Mathieu Fortin

1.

Ci3 presentation

1.1. 1.1.1. 1.1.1.1.

Identity History Creation

Ci3 is an Irish company based in Dublin, founded in 1995 by three Irish directors together with their partners: the Swiss company, COMIT Gruppe. The legal entity for the company is CI Consultancy Ltd.

1.1.1.2.

Evolution

Formerly known as COMIT Ireland and with ten years of experience working with Irish and international clients, Ci3 has proven itself to be an efficient and effective partner, ensuring that its clients are always in control.

Ci3 has realised a strong growth last year and expect to rank in a near future in the first thousand Irish companies. A future collaboration with an US company will bring new clients in northern America, and Ci3 also expect to reach new markets in Arabic countries next year.

1.1.2. 1.1.2.1.

Organization Company type

The company is owned 100% by its employees. Currently, the shareholders are, Richard Pike, Seamus O'Farrell, Liam Dwan, Paul Gaffney, Roisin Kelleher, Lisa Clifford and Amy O'Donovan. Opportunities for other employees to purchase shares arise from time to time and generally any share offer is open to all employees. Ci3 is a small company, there are about thirty employees and this number evolves with the activity. But Ci3 is steadily growing and expect hiring more employees as the Irish economy is healthy and prospects for growth are good. 1.1.2.2.

Organisation Chart

Ci3 is divided in three main departments: Sales & Customer support, Software development and Human ressources.

1

Internship report - Mathieu Fortin

Ci3 Organisation Chart

1.2. 1.2.1. 1.2.1.1.

Business Clients Financial institutions

Ci3 partners with financial institutions to provide them with risk control, compliance and certainty over related management processes and information. Ci3 offers to its clients, insight and intelligence – based on vast experience and an unparalleled knowledge. Ci3 is a partner of choice for many banks in Operational Risk Management (ORM), Ci3 products have more than two thousand users in leading financial firms across 23 countries, including Schroders and Anglo Irish Bank.

1.2.2. 1.2.2.1.

Market characteristics New market

Ci3 original purpose was to provide IT consulting services to the Swiss and Irish Financial Services Market. Over the years the company has evolved into one of the leading suppliers of Risk Management Software (RMS) for the Financial Services industry in the world. Operational Risk Management Software market has recently grown after popular events like Enron accounting fraud urging financial regulation changes. 1.2.2.2.

Growing market

Over the past ten years, the importance of a good Risk Management strategy has been increasingly growing due to high competition between financial companies. The ability to identify and quantify risks is a real asset for financial companies as it may save them millions of euros. The growing need in Risk Management Software has given Ci3 the opportunity to 2

Internship report - Mathieu Fortin develop its business and become a leading company in this market. Chartis forecasts the worldwide Operational Risk Management market to grow to $1.27bn by 2009 [1].

1.3. 1.3.1.

Products Services

Ci3 continues to offer IT consulting services to the Irish market. Over its lifetime, Ci3 has built strong and lasting relationships with many individuals and organisations in Ireland. Ci3 will continue to build these relationships and offer a full range of consulting services, from IT strategy right through, analysis, development and system support.

1.3.2.

Syntinel

Syntinel is a Syndicated Lending Product used by large banks to manage their entire Syndicated Loan process. It is currently used by Bank of Ireland and Ci3 continues to sell the product directly to the market.

1.3.3.

Sword

Sword is an award winning Operational Risk Management System. Ci3 started development of the product in 2000 and now has it installed in many blue-chip Financial Services companies around the world. Ci3 continues to develop the product and sells it directly to the market in UK, Ireland and Europe and through a network of resellers around the world. Sword has been recently awarded as the most mature ORM solution and rank in the top 5 Softwares in Operational Risk Management according to the Chartis Report [1].

3

Internship report - Mathieu Fortin

2.

Project presentation

2.1.

Operational Risk Management (ORM)

Risk management is the process of identifying, assessing risks and then developing strategies to manage these risks. Operational Risk Management is the process to manage day-to-day risks in the work flow and the processes. Operational Risk Management intends to reduce losses due to internal procedure, people and system failures or resulting from external events.

2.1.1. 2.1.1.1.

Basel committee Basel committee history

The Basel Committee on Banking Supervision (BCBS) is an institution created by the central bank Governors of the Group of Ten nations [2]. It was created in 1975 and meets regularly four times a year. The purpose of the committee is to define standards (BASEL II) and guidelines for best practice in banking and encourage compliance from banks and financial institutions. 2.1.1.2.

Basel II agreement

Basel II is the second Basel Accord and represents recommendations by the BCBS to revise the international standards for measuring the adequacy of a bank's capital. It was created to promote greater consistency in the way banks and banking regulators approach risk management across national borders. The final revision of the agreement was issued in June 2004, and the last update has been released in November 2005. Many banks and financial institutions still comply to the Basel I agreement, in most of this companies compliance to the new agreement is expected by 2008. Basel II is based on three concepts: minimum capital requirements, supervisory review and market discipline. The first concept improves risk sensitivity in the capital requirements calculation. Bank capital requirements depends on three main risk: credit risk, operational risk and market risk. The supervisory review gives the regulators improved tools and more control than in Basel I. The third concept gives banks the obligation to give more information on their risk position.

2.1.2. 2.1.2.1.

Banks and regulators role of regulators

Financial regulators can be either government and non-government institutions. In Ireland the financial regulator is the Irish Financial Services Regulatory Authority and in France the Autorité des Marchés Financiers (AMF). Financial regulators role is to enforce applicable laws, prosecute cases of market misconduct like insider trading, protect clients, and investigate complaints. 2.1.2.2.

relation with banks

Banks and regulators work together to watch the market activity and to control and reduce risks like credit risk, financial risk or operational risk. Regulators and financial 4

Internship report - Mathieu Fortin institutions partnership minimise financial loss of depositors in banks or policy holders of insurance companies.

2.2. 2.2.1.

Book of Specifications Program specifications

2.2.1.1.

Sword overview

Sword is an Operational Risk Management Software providing efficient solutions to banks and financial institutions with high requirements. Sword offers a large range of functionalities to fully manage operational risks and assist Risk managers in every part of their work. Included functionalities in Sword are : Organisation Mapping, Risk & Control Assessment, Reporting, Issue Management, etc. 2.2.1.2. 2.2.1.2.1.

Main functionalities Organisation Mapping

Sword introduces powerful features to every aspect of Operational Risk Management. Its adaptative and flexible Organisation Mapping tree structure offers a simplified management of operational risks. Organisation Mapping allows Risk managers to map all locations, organisation units, processes and controls providing a dynamic and flexible system in any context for every institution. See screenshot 6.3.1. Organisation Mapping. 2.2.1.2.2.

Risk & Control Assessment

Risk assessment is the process to identify the risk quantify the losses and approximate its frequency. The Risk and Control Assessment System gives business and risk managers more control on assessment cycles with improved relation and hierarchy between Risk and Control assessments. See screenshot 6.3.2. Risk & Control Assessment. 2.2.1.2.3.

Reporting

Sword provides powerful tools to generate reports from data captured by users. These reports offer an overview of all information in Sword, and give users useful material for Operational Risk Management. Excel spreadsheet export is also supported in Sword offering highly flexible and reliable reports which can easily be published privately or publicly. See screenshot 6.3.3. Report. 2.2.1.3. 2.2.1.3.1.

Technologies used Visual Studio

Sword development is realised with Visual Studio .NET 2005, an Integrated Development Environment (IDE) from Microsoft. Sword conception in based on an Object 5

Internship report - Mathieu Fortin Oriented paradigm using programming languages like ASP, ASP.NET and C#. 2.2.1.3.2.

Visual SourceSafe

Collaboration is empowered by the use of Microsoft Visual SourceSafe, a Revision Control software, which enables a team of developers to work simultaneously on the same project and the same files and keeps a record of all changes applied. 2.2.1.3.3.

SqlServer

To provide an optimized and secure experience to its users, Sword fully integrates Microsoft .NET solutions, and uses a Microsoft SqlServer 2000 database. SqlServer is bundled with two powerful softwares : Enterprise manager and Sql Query Analyser which provides all essential tools to develop, optimize and test queries, stored procedures and functions.

2.2.2.

Technical specifications

2.2.2.1. 2.2.2.1.1.

Running system requirements Operating system, Database & Web Server

The application can be hosted on every Microsoft Windows system since Windows 2000 SP2, with a running Microsoft SqlServer 2000 SP2 and Microsoft IIS. On client side only Internet Explorer version 5.5 or above is required which makes Sword really easy to roll out on several desktop.

6

Internship report - Mathieu Fortin

Sword client-server architecture 2.2.2.1.2.

Benefits of a lightweight client

The lightweight client term is both used for a computer or a program that relies on a server to run the server application an process data. This client-server architecture is used in internet, a web browser is a lightweight client while the web server processes data and returns html which the client just needs to display. A lightweight client application allows low-cost and short installation on a desktop network. Once the server is set up, clients whether need a short configuration or no configuration at all. The upgrade process is also simplified since most of the time only the server needs to be upgraded.

7

Internship report - Mathieu Fortin

2.2.3.

Design specifications

2.2.3.1. 2.2.3.1.1.

Code specifications Object oriented programmation

The application benefits of an Object Oriented paradigm are a better flexibility and maintainability of the code. Sword use both C#.NET and ASP.NET, however the latter is not an Object Oriented language as it is used to generate web pages in html. 2.2.3.1.2.

Basic rules and comments

As many developer are working on the same project, basic programming rules must be respected to facilitate collaboration and maintenance. Every source file includes a header with the changes description and the programmer’s name. 2.2.3.1.3.

Source control & Quality

The project is completely managed under Visual SourceSafe and the program changes are tested. When important changes or breaking features are introduced the development team has to consider changing the version number of the program as a part of the software quality assurance process. 2.2.3.2. 2.2.3.2.1.

user interface specifications Cascading Style Sheets

Using cascading style sheets (CSS) is essential in every important web application for design maintenance and reliability. CSS allows to define multiple font and color styles to be used in all pages of a web site, and gives more flexibility to format a set of pages. 2.2.3.2.2.

Forms organization

The organisation of the forms is a key element of an application Look & Feel, and can increase or decrease user efficiency and productivity. The places of the fields and the buttons must be well chosen to preserve a clear and readable interface. The form behaviour, like automatic validation or input control, is also very important to design an intuitive and secure application. 2.2.3.2.3.

Multilingual

Sword is used by companies all over the world, non-English speaking users can take advantage of the multilingual support system offered by sword: every information can be displayed in different languages. Left to right and right to left languages are both supported which enables a large number of users to use Ci3 products in a more intuitive way.

8

Internship report - Mathieu Fortin

Sword client world map: number of client per country.

9

Internship report - Mathieu Fortin

3.

Didactic step

3.1.

Projects and tasks

An exhaustive list of my tasks is presented in my internship planning (6.1. Internship Planning). During my internship I did many different tasks and I have contributed to different projects, but the most interesting tasks I have done are: improving the internal bug tracking system, developing new features in Sword, supervising and collaborating on a “Look & Feel” upgrade of Sword interface.

3.1.1.

Bug tracking system update

The bug tracking system is used by the quality assurance team which tests the application before product validation to report bugs to the development team and keeps a track of the bug fixing process. The quality assurance team had reported bugs on the internal bug tracking system, and wanted few improvements. Liam Dwan the development manager asked me to work alone on this task. We had a meeting in which he presented me the task and commented the specifications. This task took me about three weeks before its validation, as I was working alone on it I had to report to Liam the task progress and the development hassles that forced the specifications to change.

3.1.2.

Sword new features development

During my internship developing new features in Sword in Michael Dolling's team has been my main task. The commercial release of Sword version 7 is expected at the end of the year 2006 and development is still in progress. I was collaborating with four other developers on this project. I have been working on creating new user-controls for the forms used in many pages of Sword where I learnt programming in C#. User-controls are very useful in a .NET project as they allow complex and customizable web components to be created and included easily in any pages. I also had to create .NET pages based on existing Asp version, this work was a good introduction to .NET programming as I had more to focus on reproducing the same functionalities with few improvements than creating pages from scratch.

3.1.3.

Sword “Look & Feel” upgrade

After Ci3 asked to a professional user interface designer a report on improvements that should be done in Sword, Liam Dwan wrote the specifications to change Sword “Look & Feel”. This upgrade needed to be done on both Asp and .NET side as some Asp pages may still be used in later versions. We were three developers working on this task and I had to introduce and help the other developers as Liam Dwan explain me in details the specifications and wanted me to describe the task and help them. In this project I was supervising and helping -under Liam instructions- two other developers. I made few mistakes and have learnt how to fix them. I also realized that communication was essential when you get more responsibilities as your failures involve the work of other people more directly.

10

Internship report - Mathieu Fortin

3.2. 3.2.1.

Existing solutions study Previous version of Sword

At first Sword was developed with ASP (Active server page), a web oriented language introduced by Microsoft to include dynamic content in web pages. When the .NET framework became available the benefits of a migration were discussed and Ci3 managers finally decided to use .NET for Sword development for its reliability. Discovering such a big program is not easy, and it has taken me a long time to understand important aspects of Sword. I had to do personal research to understand the context (ORM) and ask my colleagues to help me.

3.2.2.

Implemented features

After nearly 10 years of development Sword is a mature product. Sword in its seventh version include thousands of files and even more lines of code. To develop a new version of a program you need to understand existing features and behaviours, and you need to adapt your work to new methods and rules of programming.

3.3. 3.3.1.

Defining objectives Identifying the needs

In this project the general directions and targets are defined by the project management team in specification sheets. Specification sheets translate clients need into developer-friendly information and specifications which enable developers to identify and develop the most adapted solution.

3.3.2.

Setting priorities

During solutions development I was asked to do several tasks in different projects. In order to keep my work organized and efficient, I had to define an importance scale for my tasks and in what order I should do them. Bug fixing in internal software solutions are critical tasks, the work of different teams may depend on it while other important tasks like new features development are not as urgent.

3.3.3.

Creating a schedule

Setting priorities in day-to-day tasks is not sufficient enough to keep the work organized, creating a schedule helps to focus on development time and deadlines. A schedule must be respected, otherwise it becomes useless and ineffective. A schedule is also important to communicate with your manager and be able to give him an idea of your task progress and help him adapting your work load.

3.4. 3.4.1.

Designing solutions Using academic knowledge

Programming methods learnt in College are really important when you contribute to a project, your code is potentially going to be reviewed and modified by someone else. The 11

Internship report - Mathieu Fortin way your code is written will define the legibility of your work and its degree of reusability. Some concepts and paradigms I have learnt in College were useful in my work, the project I was working on was Object Oriented. I have learnt Object Oriented Programming the last two years, thus I was able to understand the project and my work. As for .NET, the programming language, I already had had an experience with .NET in my previous internship where all my knowledge on other programming language had helped me to learn it.

3.4.2.

Tools selection

To perform a task the choice of appropriate tools is essential. Choosing the right software may save you lot of time. I had to do the maintenance of hundreds of pages: the styles needed to be changed to comply with the new design specifications. This task could have taken ages, but with the help of complex regular expressions in Visual Studio I was able to make the changes in few seconds instead of tiresome manual changes.

3.4.3.

Reaching objectives

Reaching objectives is often a matter of understanding the needs and translating them into code specifications and then writing functions. But it’s also designing solutions optimizing the use of ressources, and sometimes reach higher expectations than originally specified.

3.4.4.

Optimization

Optimization should be done anytime you code. However, while designing important functionalities with hundreds of lines of code, it is sometimes easier to focus on creating simple and clear code to reach the objectives first, and focus on optimization later. Reviewing functions can also be a good way to find bugs at an early stage. Improving code efficiency is not easy especially when you can’t get execution statistics of your functions to detect lines that have a long execution time. It is often said that to debug a function you need to be twice more intelligent than to originally write it. It means that if you code a very complex function few days or sometimes few weeks later it will be even more difficult to debug it, and comments become more than essential.

12

Internship report - Mathieu Fortin

4.

International experience

4.1. 4.1.1. 4.1.1.1.

Internship in Ireland Living abroad Ireland Vs France

The life in Ireland is slightly different from the life in France, even if in Europe cultures are similar. The cost of life is the same but the quality of life is not as good as in France, starting with food. As Ireland is an island the food variety is poor and some vegetable are hardly findable or even impossible to find. For example long green beans are not sold in supermarkets, you will mostly find green pees, carrots and potatoes of course. The weather in Ireland is temperate, and temperature variates between 2°c and 22°c. As everybody knows, it often rains in Ireland even during summer with a total of 129 rain days a year. The weather is really changeable and it is wise to always have an umbrella with you as it can be sunny in the morning and raining cats and dogs in the afternoon. 4.1.1.2.

Dublin Vs Paris

One out of three persons lives in Dublin and its suburbs, therefore Dublin is like Paris the center of all activities. However Dublin is a small city with only five hundred thousand inhabitants, there is no subway in Dublin and public transportations are really poor. Public transportations are a real concern in Dublin, and new tramway lines are planed for the next three years which could sensibly reduce traffic jams in the city center. They are also good points living in Dublin, as the city is quite small there is a lot of animation in the city center. The main streets and places are very close, O'Connell, Temple Bar and Grafton street are in a short walking distance from one to another.

4.1.2. 4.1.2.1.

Working abroad New working environment and culture

The working culture is really different in Irish companies. Although communication in teams is not as important than in France, it’s not unusual to go to the pub after work with your colleagues. You have to work 37.5 hours per week wich is more than in France, but people tend to be more strict with their hours and won’t work more than they are paid which is on the contrary quite common in French IT companies. 4.1.2.2.

Take part in the activity

Joining a new company and a new team is an interesting challenge and a valuable experience. In order to become productive you need to be a part of a team and a project, in this process communication is really important.

13

Internship report - Mathieu Fortin 4.1.2.3.

Benefits

Although the cost of life was more important for me in Ireland the average pay for an IT developer is bigger than in France, and the taxes are significantly lower. Working abroad is also very instructive and gives you the opportunity to discover a country politics, economy and social condition, and then have another point of view on your own country.

4.2.

Project management

During my internship I had the opportunity to manage a small project working with two colleague. Working in two different teams with different managers (Liam Dwan and Micheal Dolling), I have been able to take a closer look on the team leader work and understand its specificities in an another country than France.

4.2.1. 4.2.1.1.

Team leader Responsibilities

The key role of the team leader is to organize the work between team members and to ensure communication: choices and issues has to be discussed and explained to the team. Depending on the team leader ability to set a good environment, a good communication will facilitate teamwork and collaboration, and improve the team productivity. When new coding methods need to be observed by team members, it is the team leader responsibility to take appropriate measures: sending email notifications, organizing meetings, etc. Team members support and commitment are essential in a project success and a team leader has to take responsibility for any failure. Thus the team leader must preserve a good working environment, pay attention to its team members and be aware of any difficulty or problem. To control a task progress the team leader needs to discuss it with its team members and estimate the remaining development time considering their remarks. 4.2.1.2.

Requirements and qualities

Communication and human skills are the most important requirements for a team leader. Technical skills are also important, but a team leader must be able to make abstraction of technical details and rely on team members technical skills.

4.2.2. 4.2.2.1.

Teamwork Cooperation and collaboration

Cooperation and collaboration are preconditions for teamwork success. A team must share same objectives and have a good understanding who needs to do what by when. The essence of a team lies in the team members ability to have the sense of belonging and commitment. Complementary, diverse skills and knowledge improve teamwork, and with a clear role definitions and an open communication, enable good work partitioning and avoid gaps and overlap in individuals' assigned work.

14

Internship report - Mathieu Fortin

4.3. 4.3.1.

Personal benefits Developed qualities

Living in another country helps to develop qualities as much important in life as in a company. 4.3.1.1.

Autonomy & flexibility

Before moving to Dublin I used to live in my parents’ house, So I have learnt to be more independent and autonomous in every aspect of my life. I had to share a house with four other young working persons. We shared the same difficulties and we helped each other when we could. 4.3.1.2.

Communication skills

Using every day another language helped me improving my communication skills as I needed to think more about my speech and the words to use to be understood. I needed to organize more my thoughts and be even more concerned about people I was talking to. After one month in Ireland, when I started thinking in English, I realized that the language you use could change the way you think. 4.3.1.3.

Open mind

Living abroad, I have been confronted to new cultures and different ideas, and I had to accept that people may think differently without being wrong. When you consider every different idea with the same interest, you start thinking with a wider point of view and better ideas or solutions may come to you.

15

Internship report - Mathieu Fortin

5. 5.1.

Impressions and Feelings Internship

Working in an other country with an other language has given me the ability and the will to plan a career in many other countries. Once the apprehensions of living and working abroad were gone, I realized that I could work in any other English speaking country and this gave me a great confidence in my career prospects. This internship has also given me an international experience and a much more valuable and interesting resume. Since november I was preparing my application file for an Exchange Student Agreement with the Hong Kong University. This internship gave me more chances to be accepted at the Hong Kong University for the year 2006-2007, as a good level in English was required and an experience living abroad a significant advantage. During my internship I have acquired more experience, developed important qualities and improved my communication skills to adapt myself to a new working environment. For all these reasons it was a very profitable experience and I am thankful to Ci3 which has given me the opportunity to express myself in an interesting project.

5.2.

Experience

Living and working abroad is an invaluable experience. I had a great time in Ireland, I met interesting people from Ireland and many other countries: England, Spain, Italy, Poland, Czech republic, Estonia, Brazil, Uruguay, China, Korea... In this multicultural environment I have opened my mind and learnt from everyone and every culture. Everyone has its own experience to share, and a personal opinion which differs from any other. Communication was the most important thing during those six months, it was a difficult but very instructive daily exercise. When I started thinking in English I realized that language could change your perception and the way you think.

16

Internship report - Mathieu Fortin

6.

Annex documents

6.1.

Internship Planning Objectives

Ressources

(1) Get introduced to Sword Context

Time 3 weeks (13/02 – 03/03)

Sarbanes-Oxley Act (SOX)

[3] [4]

Basel II

[4] [5]

Operational Risk Management

[6] [7] [8] [9]

(2) Get introduced to Sword

4 weeks (13/02 – 12/03)

Bug fixing: [10] After a first development period the quality team has reported several bugs to the development team. Bugs must be fixed without slowing down new features development.

1 week (13/02 – 17/02)

Attestation Unit management features [10] [11] development: Attestation Unit management is a key feature in Sword that allows risk managers to assess their risk and controls. Risks and controls are inter-dependent therefore for each action data processing and control is required.

2 weeks (13/02 – 03/03)

User-control for the form creation: [12] Many forms are used in sword and some of them share same elements that can be gathered and put into one “user control” with additional features.

1 week (6/03 – 10/03)

(3) Bug Tracking System development

3 weeks (13/03 – 31/03)

Bug fixing & improvements: Development of a first release tested by the quality assurance team. Bugs are reported on the first release and fixed to get final validation on the second release.

(4) Sword development

4 month (04/04 – 23/07)

17

Internship report - Mathieu Fortin

Objectives

Ressources

Time

Attestation Unit management : [13] Attestation Units are a key component in ORM, development of a complete and intuitive framework for risks manager is set to a high priority.

2 month (04/04 – 25/05)

New features development.

2 month (05/06 – 23/07)

(5) Sword Look & Feel upgrade

1 month (15/05 – 16/06)

Sword Look & Feel: Older pages of Sword are still in Asp and due to design specification changes they need to be updated and re-designed.

(6) Internship report writing

1 month (08/05 – 12/06)

Template design: [14] [15] [16] To write two reports with identical styles a Template is necessary. I found a great how-to on internet and created a good standard report template that I shared with my schoolmates.

2 weeks (08/05 – 18/05)

English report writing: Writing a report in English with a formal style suitable for an internship report.

4 weeks (08/05 – 02/06)

[17] [18]

Visual SourceSafe Tutorial: Writing a 10 pages How-to on Visual SourceSafe.

2 weeks (29/05 – 12/06)

Reviewing documents: Looking for mistakes or contradictions.

1 week (05/06 – 12/06)

6.2.

Time line

Objectives

February

March

April

(1) (2) (3) (4) (5) (6)

18

May

June

July

Internship report - Mathieu Fortin

19

Internship report - Mathieu Fortin

6.3. 6.3.1.

Screenshots Organisation Mapping

20

Internship report - Mathieu Fortin

COMIT map organisation in Sword: risks and controls can be different in each organisation or country. (linked with: 2.2.1.2.1. Organisation Mapping)

21

Internship report - Mathieu Fortin

6.3.2.

Risk & Control Assessment

Sword risk assessment page: Controls need to be approved by their manager in the risk assessment process. (linked with: 2.2.1.2.2. Risk & Control Assessment)

22

Internship report - Mathieu Fortin

6.3.3.

Report

Sword report graphic: Quantitative comparison between Gross and Residual Risk (linked with: 2.2.1.2.3. Reporting)

23

Internship report - Mathieu Fortin

Alphabetical Index C Company....................................................... Ci3...........................I, 2, 3, 8, 10, 11, 16 Client...................................................... Anglo Irish Bank.................................. 2 Schroders............................................2 COMIT.................................................. 1 Product................................................... Services................................... I, 2, 3, 4 Specification.... I, 5, 6, 8, 10, 11, 12, 18 Sword...........I, 3, 5, 6, 8, 10, 11, 17, 18 Syntinel............................................ I, 3 D Development................................................. Language............................................... ASP.NET...................................... B, 6, 8 C#........................................ B, 6, 8, 10 Software................................................. SqlServer............................................ 6 Visual SourceSafe..................... 6, 8, 18

Visual Studio................................. 5, 12 F Finance.......................................................... BCBS.................................................... 4 Regulator.......................................... I, 4 Risk........................................................ Basel...................................... I, B, 4, 17 Operational Risk............ I, B, 3, 4, 5, 17 Operational risks................................. 5 W Work.............................................................. Organisation........................................... Organisation Chart..............................1 Planning.................................. II, 10, 17 Schedule........................................ I, 11 Work flow............................................ 4 Team work............................................. Collaboration.....................1, II, 6, 8, 14 Commitment..................................... 14 Communication..... II, 10, 13, 14, 15, 16

A

Internship report - Mathieu Fortin

Bibliography [1] Chartis Research "Chartis Report": http://www.chartis-research.com/docRR061.shtm [2] Wikipedia "Group of Ten": http://en.wikipedia.org/wiki/Group_of_Ten_%28economic_1962%29 [3] Wikipedia "Sarbanes-Oxley Act": http://en.wikipedia.org/wiki/Sarbanes-Oxley_Act [4] Contingency Analysis "Financial Risk Management": http://www.contingencyanalysis.com [5] Wikipedia "Basel II": http://en.wikipedia.org/wiki/Basel_2 [6] Wikipedia "Risk management": http://en.wikipedia.org/wiki/Risk_management [7] Wikipedia "Operational Risk": http://en.wikipedia.org/wiki/Operational_risk [8] Amd Conseil "Risque Opérationnel": http://www.marchesfinanciers.net/pages/risque_operationnel.htm [9] Les Echos "L'art de la gestion des risques": http://www.lesechos.fr/formations/risques/art_risques.htm [10] Microsoft Corporation "Microsoft Developer Network": http://www.msdn.com [11] Microsoft Corporation "Transac-Sql": http://msdn.microsoft.com/sql/ [12] Andrew Troelsen "Pro C# 2005 & the .NET 2.0 Platform" - ISBN:1590594193 [13] Bill Evjen "Professional ASP.NET 2.0" - ISBN:0764576100 [14] Christian Paratschek "Text Formatting with OpenOffice.org Writer": http://www.osnews.com/story.php?news_id=8225 [15] OpenOffice.org "OpenOffice.org Forum": http://www.oooforum.org/ [16] 8daysaweek "OpenOffice help & ressources": http://www.8daysaweek.co.uk/ [17] Wiktionary "The free dictionary": http://www.wiktionary.org [18] Chambers Harrap Publishers "Chambers Online": http://www.chambersharrap.co.uk/

B

Internship report

Jun 12, 2006 - the market in UK, Ireland and Europe and through a network of ... The Risk and Control Assessment System gives business and risk managers ... On client side only Internet Explorer version 5.5 or above is required which makes .... him an idea of your task progress and help him adapting your work load.

1MB Sizes 3 Downloads 322 Views

Recommend Documents

Internship Report
Sep 4, 2007 - 2.2.1.2. Asia-Pacific Team. Mathieu joined the EM IT team for Asia-Pacific in Singapore reporting to Stephen. Richards and Steven Mutch. He collaborated which different members of the team on different projects. The team is a perfect ex

Internship Brochure - ScriptEd
choose their career in high school or earlier,3 the work needs to be done when students are choosing a career path, and before they enter college. The ScriptEd ...

internship poject -
developers send data from servers to their Android applications. AWS SNS. Amazon Web Service. Simple Notification Service: It provides a multiprotocol. “push” messaging for applications. Amazon. DynamoDB. It provides a scalable, NoSQL online Data

internship handbook -
mark your report what you know about your HO, what you do in your ... your supervisor to give a specific mark rather than just put a tick (v) or a cross (x) in the.

2015 Internship Open House Poster - Internship Website Project.pdf ...
There was a problem previewing this document. Retrying... Download. Connect more apps... Try one of the apps below to open or edit this item. 2015 Internship ...

Internship
Interns work closely with (OTC) on a part-time. basis ... University of Minnesota graduate students (MS, PhD, MBA, JD) who have completed their coursework.

internship opportunities -
community. If you are interested in working with youth and providing summer programming ... we are looking for you! Closing date: ... students in all Faculties.

Internship Brochure - ScriptEd
may help individual companies attract more diverse talent ... taught by software developers on a volunteer basis. ... all students, ScriptEd internships are paid at.

internship opportunity
charter schools throughout the. Greater Philadelphia region ... programming features large-scale ... possess strong computer and research skills, be familiar with ...

Internship Presentation.pdf
n Ithaca, New York. n Transfer Orientation ... n Student Leader support. n Assessment. Page 4 of 12. Internship Presentation.pdf. Internship Presentation.pdf.

Internship Description MH.pdf
organizations, government, academia and other related public service areas. The MARY'S HOUSE. internship program will provide interns with dynamic work, ...

NowFloats Internship Program.pdf
There was a problem previewing this document. Retrying... Download. Connect more ... NowFloats Internship Program.pdf. NowFloats Internship Program.pdf.

2017 Internship Application.pdf
Page 1 of 4. 1. Open Door Ministries. Internship Application. Applicant Information. Full Name: Date: Last First M.I.. Address: Street Address Apartment/Unit #. City State ZIP Code. Phone: Email. Ministries interested: Please list the name, number an

Internship Opportunity - Northern Texas PGA
Ability to edit using software such as Final Cut Pro X or Adobe Premiere. ▫ Experience with Adobe Creative Suite a plus. ▫ Ability to use Apple Computers and ...

Community Programs Internship -
parking will be provided for Interns. Summary: This intern will be working with the Community Program Manager and team to assist with the grants program,. Breast Cancer Issues Conference, Race for the Cure and related activities, volunteer trainings,

IGLR-Internship 2011_UEH -
and Hanoi with 40 professionals. Today, our clients make up ... 08-2210 1718. Address: R. 903, 9th Floor, Sun Wah Tower, 115 Nguyen Hue St., Dist. 1, HCMC.

Internship Opportunity - Northern Texas PGA
Manage and promote the Junior Tour via social media outlets, including ... Assist with the management of the NTPGA Junior Golf Foundation Website ... The Northern Texas PGA will hire approximately 20 total interns for the summer of 2015.

2017 Internship Flyer.pdf
... on the Hanford site in Richland, Washington. We offer 10-12 week internship assignments with the following companies: Page 2 of 2. 2017 Internship Flyer.pdf.

2017 Internship Flyer.pdf
We offer 10-12 week internship assignments with the following companies: Page 2 of 2. 2017 Internship Flyer.pdf. 2017 Internship Flyer.pdf. Open. Extract.

INTERNSHIP: Web Development/ Graphics - Groups
We need a Website Developer who can create simple, aesthetic, effective and meanin gful websites using platforms such as: HTML5, Drupal or innovative ...

Arl Internship Report.pdf
industry from exploration to production, and refining to marketing of a wide range of. petroleum products in Pakistan. Page 3 of 19. Arl Internship Report.pdf.

Engineering Internship - Swiggy.in -
Engineering Internship - Swiggy.in. We are looking for people ... Who are: good at problem solving and believe in Fire-n-Motion way of approaching solutions.

Internship at FantaCode -
The final and pre-final year students from CSE, IT, ECE and MCA Departments are welcome for the internship program conducted by FantaCode Solutions. 2.