module 3 - information systems architectures.pdf

7/27/2019 Module 3 - Information Systems Architectures.pdf

1/15

1

Mahindra Satyam 2009

Enterprise Architecture Professional

Training and Certification(EA Phase-2 Training)

Architecture Development Model

Module 3- ADM Phase C- Information SystemsArchitecture


2/15

2

Mahindra Satyam 2009 Mahindra Satyam 2009

Phase C :Information Systems

Architectures Overview

Application

Architecture

Data

Architecture


3/15

3


Module ObjectivesThe aim of this module is to understand:

The objectives of Phase C, Information Systems Architectures

The Approach

A brief overview of the inputs and outputs

This module is an introduction to the next two modules that look at

the two Information Systems Architectures


4/15

4


Information SystemsArchitecture

ObjectivesData architecture:

To define the types and sources of data needed to support the

business, in a way that can be understood by the stakeholders.

Application architecture:

To define the kinds of application systems necessary to process the

data and support the business


5/15

5


ApproachPhase C involves Data and Applications Architecture, in either

Order

Advocates exist for both sequences:

SpewaksEnterprise Architecture Planning recommends a data driven

sequence

Major applications systems (ERP, CRM, ) often combine technology

infrastructure and application logic. An application-driven approach takes

core applications(underpinning mission-critical business processes) as

the primary focus of the architecture effort.

Integration issues often constitute a major challenge.

Continued


6/15


7/157


Alternative Approach: Data-Driven

Sequence Implementation

1. First implement application systems that create data

2. Then applications that process the data

3. Finally, applications that archive data


8/158


Approach: Architecture

Repository

Consider generic models relevant to an organizations industry vertical

Data Architecture ResourcesGeneric data models, for example the ARTS data model (Retail

industry), Energistics data model (Petrotechnical industry)

Application Architecture Resources

Generic application models, for example the TeleManagement

Forum (telecommunications industry), the OMG has a number ofsoftware models for specific verticals (Healthcare,

Transportation, Finance etc)


9/159


Considerations for Data

Architecture

Data Management

Data Migration

Data Governance


10/1510


Phase C: Inputs

Request for Architecture Work

Capability Assessment

Communications Plan

Organization model for enterprise Architecture

Tailored Architecture Framework

Data/Application principles

Statement of Architecture Work

Continued


11/1511


Phase C: Inputs

Architecture Vision

Architecture Repository

Draft Architecture Definition Document

Draft Architecture Requirements

Specification, including:

Gap analysis results

Relevant technical requirements

Business Architecture components of an

Architecture Roadmap


12/1512


Steps

The details for these steps will be

covered in the next two modules

The steps follow a common pattern

with Phases B and D


13/1513


Phase C: Outputs: Data Architecture

Statement of Architecture Work

Validated data principles, or new principles

(data/application)

Draft Architecture Definition Document, containing :

Baseline Application/Data Architecture

Target Application/Data Architecture

Application/Data Architecture views of keystakeholder

concerns

Draft Architecture Requirements Specification,

including

Gap analysis results

Application / Data interoperability requirements

Relevant technical requirements Constraints on

the

Technology Architecture

Updated business requirements

Data / Application Architecture components of an

Architecture

Roadmap


14/1514


Summary

The objective of Phase C is to document the

fundamental organization of an organizations IT

System.

Embodied in the major types of

information and the application systems

that process them

Their relationships to each other and the

environment

The principles governing its design and

evolution It should document how the IT systems

meets the business goals of the

organization


15/151

Mahindra Satyam 2009

mahindrasatyam.net

Safe Harbor

This document contains forward-looking statements within the meaning of section 27A of Securities Act of 1933, as amended, and

section 21E of the Securities Exchange Act of 1934, as amended. The forward-looking statements contained herein are subject to

certain risks and uncertainties that could cause actual results to differ materially from those reflected in the forward-lookingstatements. Satyam undertakes no duty to update any forward-looking statements. For a discussion of the risks associated with our

business, please see the discussions under the heading Risk Factors in our report on Form 6-K concerning the quarter ended

September 30, 2008, furnished to the Securities and Exchange Commission on 07 November, 2008, and the other reports filed with

the Securities and Exchange Commission from time to time. These filings are available at http://www.sec.gov

Thank you

module 3 - information systems architectures.pdf

Documents