Acta De Constitucion

“System XYZ 5.0 – Increments 1 &

2”

Project Charter

SYSTEM XYZ 5.0 INCREMENTS 1 & 2

PROJECT CHARTER

Version #: 1.1 Issue Date: 10/2/2006

Company. Company Fund Services Page 2 of 11

Printed on: December 3, 2007

Project Charter Purpose

This Project Charter outlines the purpose, objectives, and scope of the project.

The purpose of a Project Charter is:

· To provide an understanding of the project, the reason it is being conducted, and its justification;

and

· To establish the general scope early on in the project.

o The business needs of the project

o The proposed solution:

§ Major deliverables

§ Timeline

§ Resource requirements

The objective of a Project Charter is:

· To formally authorize a project; and

· Ensure that all the parties involved (business, project, external partners) have a common

understanding about the business issues and proposed solution to ameliorate these issues.

The scope of a Project Charter is:

· The business need that the project was undertaken to address; and

· The proposed solution with high-level requirements to achieve it.

The Project Charter is prepared by:

1. The project sponsor

2. The assigned project manager

It is reviewed and approved by the Project Steering Committee.

Document Information and Revision History

Version Date Author(s) Revision Notes

1.0 10/2/2006 Michael Ahrens New

1.1 10/5/2006 Michael Ahrens Added comments from Rob Hill

SYSTEM XYZ 5.0 INCREMENTS 1 & 2

PROJECT CHARTER

Version #: 1.1 Issue Date: 10/2/2006

Company. Company Fund Services Page 3 of 11

Printed on: December 3, 2007

Table Of Contents

1. INTRODUCTION.................................................................................................................................................................4

1.1. OVERVIEW OF THE PROJECT ...................................................................................................................................4

2. PROJECT OBJECTIVE AND SCOPE............................................................................................................................4

2.1. OBJECTIVE ..................................................................................................................................................................4

2.2. SCOPE..........................................................................................................................................................................5

2.3. MAJOR DELIVERABLES.............................................................................................................................................8

2.4. TIMELINE....................................................................................................................................................................9

2.5. BUSINESS NEED OR OPPORTUNITY...................................................................................................................... 10

2.6. FINANCIAL BENEFITS OF THE PROJECT ............................................................................................................... 10

SYSTEM XYZ 5.0 INCREMENTS 1 & 2

PROJECT CHARTER

Version #: 1.1 Issue Date: 10/2/2006

Company. Company Fund Services Page 4 of 11

Printed on: December 3, 2007

1. Introduction

1.1. Overview of the Project

The objective of the project is to re-engineer the back office related Java processes and Delphi application of

System XYZ 3.4.2 using J2EE based architecture that will give scalability, stability, information reliability,

traceability, functional extensibility and other benefits described in Objectives section (1.1).

For the re-engineering, business analysts will assimilate requirements and will extract business logic from

the reverse-engineering documents prepared by the technical team, and complete the User Requirements

Documents (URDs). The technical team will develop a high level design and a detailed design based on the

approved requirements followed by construction, QA, UAT and deployment.

The scope of work covered in the September 25, 2006 SOW will be delivered in 2 increments, and hence

these streams of work will be referred as Increment 1 and 2. High level scope coverage of these increments is

given below:

· Increment 1: Re-engineering of APost related processes of System XYZ 3.4.2 and some enhancements

· Increment 2: Re-engineering of Account Manager application and related processes of System XYZ

3.4.2 and some enhancements

2. Project Objective and Scope

2.1. Objective

The objectives of the A5 – Increment 1 project are detailed below:

· Re-engineer the JPost related Java processes and Account manager Delphi application of System XYZ

3.4.2 system using latest technologies with a proven track record and aligned to the technologies

identified for A5.

· Re-engineered system will have to be 100% functionally compatible with existing JPost/Account

Manager. Exceptions to this need to be approved by CFS.

· Re-engineered system will have to provide a functionally extensible and scalable design, transaction

traceability, performance throughput better than the existing system, and one that is easily configurable

and maintainable.

· Re-engineered system will have to be multi-client aware. This means that the same server based process

would be able to handle requests from multiple clients.

SYSTEM XYZ 5.0 INCREMENTS 1 & 2

PROJECT CHARTER

Version #: 1.1 Issue Date: 10/2/2006

Company. Company Fund Services Page 5 of 11

Printed on: December 3, 2007

2.2. Scope

The scope of work covered in the September 25th, 2006 SOW falls in 2 major lines of work as given below.

These will be delivered in 2 increments.

· Increment 1: Re-engineering of APost related processes of System XYZ 3.4.2 and some enhancements

· Increment 2: Re-engineering of Account Manager application and related processes of System XYZ

3.4.2 and some enhancements

The detailed scope is as follows:

Increment 1 In-Scope

1. Re-engineer the current posting system using J2EE framework in WebSphere Application Server

(WAS) environment. All posting will continue to use the current databases. The existing database

structures that currently encapsulate various G/L operations will be maintained. These back-end

databases are used by various reports and extracts. Current posting System includes:

a. JPost library

b. Apost server

c. Apost batch

2. Complete the following posting functionality of the existing system in the new framework:

a. PS – Trade date purchase or sale

b. OTE – Literally, “open trade equity”; figuratively, mark-to-market/valuation

c. PSS – Settlement date purchase or sale

d. CVAL – also known as “curval”; f/x valuation mechanism

3. Resulting Bug Fixes - Since the posting system is being rewritten, following old bugs in the current

system will have to be fixed.

a. Add logic to not allow one-sided journal entries in the GL

b. No hanging processes when attempt to post – now the current posting system often needs

to be recycled

c. Allow multiple people to work on the same fund at the same time

d. At times when other people are using the system for posting entries it can take up to 20

seconds to enter a post and have it show up. The new system will perform better than the

current system provided that they have been tested under the same conditions with the

same data inputs.

e. Develop multi client system to simultaneously service multiple (over 200) CFS clients from

the same system maintained in a clustered Websphere container environment.

f. Improve clarity of Posting error messages in the front end for the end user

g. Out of balance (debit versus credit) entries cannot occur (auto, manual or loaded)

4. Framework Work – Needs Resolution

a. Data Access Layer

b. Data Access Object Framework

c. Instrument and Pricing Reference Components

d. Posting Engine Exception Framework

SYSTEM XYZ 5.0 INCREMENTS 1 & 2

PROJECT CHARTER

Version #: 1.1 Issue Date: 10/2/2006

Company. Company Fund Services Page 6 of 11

Printed on: December 3, 2007

5. Existing back office databases in Sybase will be used as-is in Increment 1, except for one new table

that will be added for mapping the trades and the back office transactions.

6. Will include any changes that affect known posting issues (as of September 13th, 2006) in 3.4.2

patch 10 while Increment 1 is in development.

7. APOST will throw an exception if there is a negative FX rate. Front ends and loaders will not be

addressed in Increment one.

8. Maintain existing stored procedure interfaces that currently encapsulate various G/L operations.

These back-end data interfaces are used by various reports and extracts. This would provide

backward compatibility between the new back office data model and other components.

...