Scribd
Upload
7 views

C - Information Systems Phase

Togaf C - Information Systems phase

Uploaded by

Bruno Correia
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
7 views

C - Information Systems Phase

Togaf C - Information Systems phase

Uploaded by

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

- ADM - C.

Information Systems Architectures Phase

The Data & Application Architecture enables the Business Architecture &
Vision

Phase C consists of two parts(in either order):


1. Development of the Application Architecture
2. Development of Data Architecture

Purpose:

Develop the target Information Systems Architectures(Application & Data


Architecture) to support an agreed Architecture Vision.
...
See Purpose of Phase B: Business Architecture(they are the same)

Objectives:

1. Develop the Target Information Systems Architectures (Data &


Appplications Architecture), describing how the enterprises Information Systems
Architecture will enable the Business Architecture and the Architecture Vision, in
a way that addresses the Statement of Architecture Work and stackholders concerns.
2. Identify candidate Architecture Roadmap components based upon gaps
between the Baseline and Target Information Systems Architecture (Data &
Application Architecture).

Steps (Same as in phases B and D)

Artifacts

Application:

- Application Protifolio Catalog

"Enterprise architects always try to think in terms


of logical and physical components.
Logical component => describes an implementation
independent functionality that is implemented by a concrete software solution, the
Physical component.
Physical component => Is an application, application
module, service or other deployable componente of funcitionality.
"
- Provides a foundation for other matrices and
diagrams
- Contains logical application components and
physical application components
- Often the starting point of the Application
Architecture phase

{Application Architecture - Protifoli Catalog.png}

- Interface Catalog
- Application/Organization Matrix

- Defines the application set used by a particular


organization unit.
- Shows which organizational units are supported by which
applications.
- Helps to understand the application support requirements.
- Suports the gap analysis by determining missing or
inappopriate applications

- Role/Application Matrix
- Application/Function Matrix
- Application Interaction Matrix
- Application Communication Diagram

- Interfaces may be associated with data entities


- Applications may be associated with business services
- Communication should be logical and only show technology
where it is relevant

- Application and User Location Diagram


- Application Use-Case Diagram
- Enterprise Manageability Diagram
- Process/Application Realization Diagram
- Software Engineering Diagram
- Application Migration Diagram
- Software Distribution Diagram

Approach:
- Use Application models relevant to common high-level
business functions (e-commerce)
- Use generic business models and related application
models relevant to the organizations industry sector procided by
- Open Group Forum
- Object Management Group
- TM Forum
- The OpenGroup has reference Model for Integrated
Information Infrastructure (III-RM) focuses on the application-kevel components and
services necessary to provide an integrated informations infrastructure.

Data:

- Data Entity/Business Function Matrix


- Data Entity/Data Component Catalog
- Application/Data Matrix
- Conceptual Data Diagram
- Data Dissemination Diagram
- Logical Data Diagram
- Data Security Diagram
- Data Migration Diagram
- Data Livecycle Diagram

Approach(3 Keys):

1. Data Management:
- Define which application components server as
enterprise master data.
- Understand how data entities are utilized by
business capabilities, business functions, processes and business and application
services.
- Understand how and where enterprise data entities
are created, stored, transported and reported.

2. Data Migration:
- Identify data migration requirements.
- Provide indicators for data transformation, weeding
and cleansing.
- Ensure an enterprise-wide common data definition to
support the transformation & migration.

3. Data Governance:
- Ensure that the enterprise has the necessary
structures, management system and people in place to enable the transformation.

Data Architecture is created by using 3 metamodel entities:

1. Data Entity: used to create conceptual data models to


help the IT developers unsdertand the concepts they will be dealing with.
2. Logical data entity: used to create logical data models
as a requirement on the data stored in application (at rest), data moved between
application (in motion), or data at the user interface of applications(data in use)
3. Physical data entity: used to create data models that
have been implemented

Data Architecture should be able to handle:

- Data at rest - data in stores


- Data in motion - data transactions or services/APIs
- Data in use - data at the border of the application (GUI)
- Open data - data thatthe organization provides for public
usage.

You might also like