Scribd
Upload
16 views7 pages

Big Data - Work Program - 05 - Data Architecture Analysis and Design (10 24 2013)

Uploaded by

DefaultUsr
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
16 views7 pages

Big Data - Work Program - 05 - Data Architecture Analysis and Design (10 24 2013)

Uploaded by

DefaultUsr
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 7

Data Architecture, Analysis and Design

Scope
Date

Client Name
Protiviti Team:
(Insert Team Member Name)
(Insert Team Member Name)
Big Data Work Program – Data Architecture, Analysis & Design

Process Overview

Data architecture is an integrated set of specification artifacts used to define data requirements, guide integration and control of data
assets, and align data investments with business strategy. It is also an integrated collection of master blueprints at different levels of
abstraction. Data architecture includes formal data names, comprehensive data definitions, effective data structures, precise data
integrity rules, and robust data documentation. Data architecture analysis and design consist of defining the blueprint for managing
data assets, including the development and maintenance of enterprise data architecture and its connection with the application
system solutions and projects that implement enterprise architecture.

Table of Contents
1. Understand Enterprise Information Needs...............................................................................................................3
2. Develop and Maintain the Enterprise Data Model....................................................................................................3
3. Analyze and Align With Other Business Models..................................................................................................... 5
4. Define and Maintain the Database Architecture.......................................................................................................5
5. Define and Maintain the Data Integration Architecture...........................................................................................6
6. Define and Maintain the Data warehouse / Business Intelligence Architecture...................................................6
7. Define and Maintain Enterprise Taxonomies and Namespaces.............................................................................7
8. Define and Maintain the Meta-data Architecture......................................................................................................8

** CONFIDENTIAL ** For internal use only Page of


Big Data Work Program – Data Architecture, Analysis
& Design

Ref Control Objectives Testing Procedures Test Results


1. Understand Enterprise Information Needs
Related Risk: Enterprise information needs are not understood, resulting in inadequate information for business functions, inconsistency between
information requirements and application development, and inefficient planning of IT-enabled investment programs.
1.1 An enterprise information model is Test results should be detailed here and work paper
established and maintained to enable references should be included at the end of each
applications development and decision- sentence as follows [WPXX]. Once fieldwork is
supporting activities, consistent with IT complete, each work paper should be assigned a
plans. unique number (e.g., WP01, WP02, WP03, etc.).
Exception related text should be in red font and
summarized in the “Observations” section.

Observations:
Section to be populated with any exceptions or “No
exceptions noted”.

Work Papers:
WPXX – Work Paper File Name.doc
1.2 The model facilitates the optimal creation,
use and sharing of information by the
business in a way that maintains integrity
and is flexible, functional, cost-effective,
timely, secure and resilient to failure.
2. Develop and Maintain the Enterprise Data Model
Related Risk: Enterprise Data model is not consistent with IT plans, rigidity of models, security-cost-effectiveness issues and non-up gradation of
models.
2.1 The information architecture model is
established and maintained in the context of
the entire organization and is documented
in an understandable manner for business
and IT Management.
2.2 The information architecture model is
developed in alignment with the
organization’s strategy and the strategic and
** CONFIDENTIAL ** For internal use only Page of
Big Data Work Program – Data Architecture, Analysis
& Design

Ref Control Objectives Testing Procedures Test Results


tactical IT plans.
2.3 The architecture model is regularly checked
for adequacy regarding flexibility,
functionality, cost-effectiveness, security,
failure resiliency, compliance, and user
satisfaction.

Ref Control Objective Testing Procedures Test Results

3. Analyze and Align With Other Business Models


Related Risk: The enterprise information model does not align with other business models, resulting in reduced effectiveness and efficiency of
organizational data utilization.
3.1 The enterprise information model (current
and target) is clearly defined and aligned with
the application, business or service-oriented
architectures.
3.2 Applications and databases are inventoried
and cross-referenced to the enterprise
information model.

3.3 Naming taxonomies and standards are


clearly defined and aligned with industry and
business terminology.

3.4 Conceptual, logical and physical data


structures are defined for enterprise and
solution architectures.

3.5 Specific enterprise data integration


architectures are designed to meet
operational or reporting needs, such as
Operational Data Store, Data Hub and Data
Warehouse architectures.

** CONFIDENTIAL ** For internal use only Page of


Big Data Work Program – Data Architecture, Analysis
& Design

Ref Control Objectives Testing Procedures Test Results


4. Define and Maintain the Database Architecture
Related Risk: Without defining and maintaining database architecture, data standards for all data systems and integration are not possible.
4.1 Data technology architecture defines
standard tool categories, preferred tools in
each category, and technology standards
and protocols for technology integration.
4.2 Data architecture, analysis and design are
focused on the actual elements to be used
in the implementation of the data
architecture design.

5. Define and Maintain the Data Integration Architecture


Related Risk: Data Management is inconsistent and criteria are not well-defined leading to distorted information, unreliable external reports and data
integrity errors and incidents.
5.1 Procedures are defined and implemented to
ensure the integrity and consistency of all
data in electronic form, such as databases,
data warehouses, and data archives.
5.2 Collaboration with business management to
define the required integrity and consistency
of the criteria.

5.3 Procedures are implemented to manage


and maintain data integrity and consistency
throughout the complete data process and
lifecycle (e.g., input, processing, output,
migration, extraction, archiving).
5.4 A data quality program is implemented to
ensure data integrity and consistency
through regular validation.

6. Define and Maintain the Data warehouse / Business Intelligence Architecture


Related Risk: DW-BIM architecture is not sufficient to meet the business’s Business Intelligence needs.
** CONFIDENTIAL ** For internal use only Page of
Big Data Work Program – Data Architecture, Analysis
& Design

Ref Control Objectives Testing Procedures Test Results


6.1 Technical requirements including
performance, availability, and timing are
documented and considered when
developing the DW-BIM architecture.
6.2 Clear rules are established for what data
needs to be available for publishing via
operational reporting.

6.3 Sign-off by the business is obtained on the


data during User Acceptance Testing of BI
initiatives.

6.4 Service Level Agreements define response


time, data retention and availability
requirements of DW-BIM projects.

7. Define and Maintain Enterprise Taxonomies and Namespaces


Related Risk: Lack of clear understanding on how taxonomies can be used to help improve search, increase content value or facilitate compliance.
7.1 A content inventory has been performed that
lists all content that currently exists in the
content landscape. The purpose is to
identify what content is developed and
maintained, who can use it and why they
need it.
7.2 Clear understanding of the semantic
relationships and patterns between the
existing content is demonstrated.

7.3 The taxonomy is evaluated with appropriate


validation techniques using qualitative or
quantitative validation; or combination of
both.
7.4 Attributes are attached to existing and new
content. The taxonomy attributes can be
** CONFIDENTIAL ** For internal use only Page of
Big Data Work Program – Data Architecture, Analysis
& Design

Ref Control Objectives Testing Procedures Test Results


terms from a controlled vocabulary; a list of
standardized terms that describes concepts
within the domain. This can reduce potential
for misinterpretation.
7.5 The performance of taxonomy is regularly
reviewed and revised, when needed.

8. Define and Maintain the Meta-data Architecture.


Related Risk: Data-set and meta-data repository used are not clearly defined; terminologies are intertwined, ambiguous and inconsistent.
8.1 Defined meta-data repository architecture
exists (Centralized, Distributed or
Federated/Hybrid).

8.2 Clear terminology is utilized to ensure that


data is properly reconciled (e.g. “Clients”,
“customers”, “revenue” and “sales”).

8.3 Ambiguity and inconsistencies are resolved


when determining the associations between
entities stored throughout data environment.

** CONFIDENTIAL ** For internal use only Page of

You might also like