I-Power Berhad (Company No: 596299-D)

Integration Strategy

For

<Project Name>

Provided By

I-Power Bhd

DD-MM-YYYY

This document is the property of I-Power Berhad. The information contained herein is PRIVATE & CONFIDENTIAL. Neither the whole document, nor
any part can be reproduced, disclosed to other parties, nor used for purposes other than for which it has been supplied unless prior written permission
is obtained from I-Power.

L4 E-11, Enterprise 4, Technology Park Malaysia, Bukit Jalil, 57000 Kuala Lumpur, Malaysia ● Tel: 603 8996 8080 ● Fax: 603 8996 6880
 I-Power Berhad (Company No: 596299-D)

Revision Chart

Document No: Version No:

IPOWER-EN-T-003-v1.0.0 1.0.0

Title: Owner:
INTEGRATION STRATEGY Ang Kong Yu

Create Date:
01/08/2005

VER. Nature of Change Prepared by: Reviewed by: Approved by: Effective
NO. Date: Date: Date: Date:

<version <what change is being done to this <Name> <Reivewer <Approver <Date when
No> document> <Date of Name> Name> this document
preparation> <Review <Approved is release>
Date> Date>

Private & Confidential © I-Power Bhd 2005 Page 2 of 10

 I-Power Berhad (Company No: 596299-D)

Table of Contents

1 Purpose....................................................................................................4
2 Scope........................................................................................................4
3 Definition of Terms and Acronyms......................................................5
4 High-Level Systems Architecture.........................................................5
5 Integration Approach and High-Level Design....................................6
6 Integration Sequence..............................................................................7
7 Integration Environment Definition.....................................................8
8 Integration Procedure............................................................................9
9 Appendices.............................................................................................10

Private & Confidential © I-Power Bhd 2005 Page 3 of 10

 I-Power Berhad (Company No: 596299-D)

1 Purpose
<State the purpose of this document. Benefits of the strategy may also be stated.
e.g.
The PROJECT1 Interface Strategy defines the strategy used to develop the application’s interfaces in relation
to existing legacy systems, external system A, external system B, and the enterprise application integration
tool.

This document is intended to:

 Define the scope of the PROJECT1 interface development based on the Project Interface List deliverable,
 Define the interface architecture and resulting roles and responsibilities between different
application/development teams involved,
 Define mapping, transformation and routing strategy and standards that will be used for the PROJECT1,
 Define all commonly used interface tables.

By following the PROJECT1 Interface Strategy, the following benefits can be realized:
 Ensured and faster data interfacing through defined standards and procedures,
 Lower interface cost leveraged from repetitive use of interface programs,
 Centralized definition and maintenance of interface practices, designs, and code,
 Minimized use of functional and technical resources to repetitively analyze, design, and deploy interfaces
and
 Minimized number of resources to support the interface tasks.>

2 Scope
<Summarize the contents of the document. State exclusions if applicable.
e.g.
The list of section provided below provides the topics covered by this document:
 Section 4: High-Level Systems Architecture
This section describes the systems from which the application will extract data and to which it will export
data. This also includes a high-level description of how the application and the external systems will
interrelate.
 Section 5: Integration Approach and High Level Design
This section describes the high-level technical approach to the integration’s implementation.
 Etc.
This document does not cover the following topics:
 Topic 1; this is covered in Other-Document-A.
 Etc.>

Private & Confidential © I-Power Bhd 2005 Page 4 of 10

 I-Power Berhad (Company No: 596299-D)

3 Definition of Terms and Acronyms

<Specify in this section the definition of the terms and acronyms used throughout this document. Sort entries
alphabetically.>
<Term 1> - <Definition>
<Term 2> - <Definition>
<ACRONYM> - <Definition>

4 High-Level Systems Architecture

<This is a target application-centric high-level definition of systems from which the application will extract data
and to which it will export data. Include a high-level description of how the application and the external systems
will interrelate.
Internal integration by domains/functional areas is also included here.
Include diagrams/illustrations as applicable.
For each system, provide the following information:
o Description
o Users (e.g., front-end users, system administrator, etc.)
o Localization (for multiple sites, if applicable)
o Business Constraints
o Operating System
o Technical Constraints

Private & Confidential © I-Power Bhd 2005 Page 5 of 10

 I-Power Berhad (Company No: 596299-D)

5 Integration Approach and High-Level Design

<A high-level technical approach to the integration’s implementation.
Include:
o objectives of new interfaces/interface approach
o assumptions
o selected integration solution (the DAR Report detailing the alternative solutions and the reasons for
rejection/selection is included as an appendix to this document)
o outline of steps/workflow followed for the interfaces (e.g., extraction scheduling, data extraction, error
handling, data transformation for target system, error handling for transformation, deposit of data,
transport scheduling, routing, receipt acknowledgement, etc.) and their description (including
responsible system).
o data mapping strategy
o data transformation strategy
o transport and routing strategy
o error handling strategy
o security strategy
o modification on existing application systems (if applicable)

Private & Confidential © I-Power Bhd 2005 Page 6 of 10

 I-Power Berhad (Company No: 596299-D)

6 Integration Sequence
<This refers to the order in which product components will be assembled.
Specifically, identify the selected* order in which the domains/functional areas will be delivered. This will also
be the sequence in which the application will be built.
*The alternative integration sequences and reason for selection/rejection are documented on a DAR Report;
this is included in the appendix.

Private & Confidential © I-Power Bhd 2005 Page 7 of 10

 I-Power Berhad (Company No: 596299-D)

7 Integration Environment Definition

<This section describes the environment requirements for each stage of assembly (i.e., development, string
testing, system testing, integration testing, pilot testing, etc.)
Include diagrams as applicable.>

Private & Confidential © I-Power Bhd 2005 Page 8 of 10

 I-Power Berhad (Company No: 596299-D)

8 Integration Procedure
< This specifies how assembly of the product components would be performed.
Identify the steps required in assembling the components of the application. This will be driven by the
Technical Approach (e.g., platform-specific steps). An example would be the unpack, compile, and register
steps required for integrating a component to the rest of the application.>

Private & Confidential © I-Power Bhd 2005 Page 9 of 10

 I-Power Berhad (Company No: 596299-D)

9 Appendices

<Include other appendices as needed.>

Private & Confidential © I-Power Bhd 2005 Page 10 of 10