Customer Information System

Final Documentation

Associate ID Name

GUIDED BY:
MENTOR:
TRAINER:
COACH:
LIST OF CONTENTS:

1. Introduction
2. Purpose and Scope of the Document
3. Problem Statement
4. Architecture diagram
5. Functional Requirement
5.1Sources
5.2 Target
5.3 Mapping
5.4 Transformation
5.5 Workflow details
5.6 Task details
6. Target outputs
7. Conclusion
1. Introduction
As per the business requirements the project “Customer Information
System” is performed using Informatica PowerCenter (ETL Tool).
Informatica is a data integration tool based on ETL architecture.
Informatica PowerCenter is the widely used extraction, transformation,
loading tool. The components within Informatica PowerCenter aid in
extracting data from its source, transforming it as per business
requirements and loading it into a target data warehouse.
The software system is used to load a sample Data Warehouse for an
customer information. Data from the source system are provided in a flat
file extract and to be loaded to Data Warehouse in a relational Database.
The customer information will be using the data loaded into Data
Warehouse for decision making.

2. Purpose and Scope of the Document

The purpose of the software requirements document is to systematically

capture requirements for the project and the system “Customer
Information System” to be developed. Functional requirements of this
system are captured in this document. It also serves as the input for the
project scoping.

The scope of this document is limited to addressing the requirements

from a user, quality, and non-functional perspective. It is recommended
that design aspects are not added in this document.

3. Problem Statement
The Customer Information System is an independent software system
developed to create the mapping to load the target from the source file
after applying all the logics that is mentioned in the mapping document.
4. Architecture diagram

Physical Architecture:
A physical architecture is an arrangement of physical elements, (system
elements and physical interfaces) that provides the designed solution
for a product, service, or enterprise. It is intended to satisfy logical
architecture elements and system requirements. Auto Identification
Process follows a three layered architecture namely presentation layer,
business logic layer and data access layer.
Logical Architecture:
The Logical Architecture defines the Processes (the activities and functions)
that are required to provide the required User Services. Many different
Processes must work together and share information to provide a User Service.
The Processes can be implemented via software, hardware, or firmware. The
Logical Architecture is independent of technologies and implementations.
5. Functional Requirement

5.1 Source

Fig1: CDW_SAPP_D_CUSTOMER, CDW_SAPP_D_ITEM, CDW_SAPP_D_CUST_ITEM Source

5.2 Target

Fig2: CDW_SAPP_D_CUSTOMER, CDW_SAPP_D_ITEM, CDW_SAPP_D_CUST_ITEM Target

 5.3 Mapping

The below figure shows the data flow from source to the target table by
applying the necessary transformations to satisfy the business
requirement.

5.3.1 For CDW_SAPP_D_CUSTOMER

Fig 3: Mapping for CDW_SAPP_D_CUSTOMER

5.3.2 For CDW_SAPP_D_ITEM

Fig 4: Mapping for CDW_SAPP_D_ITEM

5.3.3 For CDW_SAPP_D_CUST_ITEM

Fig 5: Mapping for CDW_SAPP_D_CUST_ITEM

5.4 Transformations
5.4.1 For CDW_SAPP_CUSTOMER
5.4.2 For CDW_SAPP_D_ITEM

No transformation is used here in this CDW_SAPP_D_ITEM.

5.4.3 For CDW_SAPP_D_CUST_ITEM

5.5 Workflow Details

Figure represents the workflow for the above mapping, it is used to start the
session.
5.6 Task details
The below figure shows that the session has executed successfully. It also
shows the execution time details.
6. Target Outputs

6.1 CDW_SAPP_D_CUSTOMER
6.2 CDW_SAPP_D_ITEM
6.3 CDW_SAPP_D_CUST_ITEM
7.Conclusion
The system “Customer Information System” has been developed
considering all the business requirements. The functional requirement has been
satisfied by creating mapping to load the target from the source file after
applying all the logics that is mentioned in the mapping document. The system
has been operated only on the modules described in the source document and
has not included additional functionalities.