unidad 2 - arquitectura de datos
Post on 05-Jul-2018
224 Views
Preview:
TRANSCRIPT
-
8/16/2019 Unidad 2 - Arquitectura de Datos
1/31
Análisis y Diseño de Arquitectura Empresarial
Phase C: Information Systems
ArchitecturesData Architecture
-
8/16/2019 Unidad 2 - Arquitectura de Datos
2/31
Fase CData Architecture
-
8/16/2019 Unidad 2 - Arquitectura de Datos
3/31
Objetivos
The objectives of the Data Architecture part ofPhase C are to:
• Develop the Target Data Architecture thatenables the Business Architecture and theArchitecture Vision, while addressing the Reuestfor Architecture !or" and sta"eholder concerns#
• $dentif% candidate Architecture Road&apco&ponents based upon gaps between theBaseline and Target Data Architectures#
ADM – Fase C (Data Architecture)
-
8/16/2019 Unidad 2 - Arquitectura de Datos
4/31
Approach – Data Architecture
Key Considerations for Data Architecture'!hen an enterprise has chosen to underta"e largescale architecturaltransfor&ation(
Data Management
• A clear de)nition of which application co&ponents in the landscape willserve as the s%ste& of record or reference for enterprise &aster data* !ill there be an enterprise+wide standard that all application co&ponents,including software pac"ages, need to adopt* nderstand how data entities are utili-ed b% business functions, processes,
and services* nderstand how and where enterprise data entities are created, stored,transported, and reported* !hat is the level and co&ple.it% of data transfor&ations reuired tosupport the infor&ation e.change needs between applications/* !hat will be the reuire&ent for software in supporting data integrationwith the enterprise0s custo&ers and suppliers
ADM – Fase C
-
8/16/2019 Unidad 2 - Arquitectura de Datos
5/31
Approach – Key Considerations for Data Architecture
Data Migration
!hen an e.isting application is replaced, there will be a critical needto &igrate data '&aster, transactional, and reference( to the new
application# The Data Architecture should identif% data &igration reuire&entsand also provide indicators as to the level of transfor&ation,weeding, and cleansing that will be reuired to present data in afor&at that &eets the reuire&ents and constraints of the targetapplication#
The objective being that the target application has ualit% datawhen it is populated#
Another "e% consideration is to ensure that an enterprise+wideco&&on data de)nition is established to support the transfor&ation#
ADM – Fase C (Data Architecture)
-
8/16/2019 Unidad 2 - Arquitectura de Datos
6/31
Approach – Key Considerations for Data Architecture
Data GovernanceData governance considerations ensure that the enterprise has thenecessar% di&ensions in place to enable the transfor&ation, asfollows:
• Structure: This di&ension pertains to whether the enterprise hasthe necessar% organi-ational structure and the standards bodiesto &anage data entit% aspects of the transfor&ation#
• Management System: 1ere enterprises should have thenecessar% &anage&ent s%ste& and data+related progra&s to
&anage the governance aspects of data entities throughout itslifec%cle#
• People: This di&ension addresses what data+related s"ills androles the enterprise reuires for the transfor&ation# $f theenterprise lac"s such resources and s"ills, the enterprise shouldconsider either acuiring those critical s"ills or training e.istinginternal resources to &eet the reuire&ents through a well+
ADM – Fase C (Data Architecture)
-
8/16/2019 Unidad 2 - Arquitectura de Datos
7/31
Approach – Architecture Repository
As part of this phase, the architecture tea& will need to considerwhat relevant Data Architecture resources are available in theorgani-ation0s Architecture Repositor%, in
particular, generic data &odels relevant to the organi-ation0sindustr% 22vertical00 sector# 3or e.a&ple:
• ART4 has de)ned a data &odel for the Retail industr%#
• 5nergistics has de)ned a data &odel for the Petrotechnicalindustr%
ADM – Fase C (Data Architecture)
-
8/16/2019 Unidad 2 - Arquitectura de Datos
8/31
InputsReference Materials External to the Enterprise
• Architecture reference &aterialsNonArchitectural !nputs• Reuest for Architecture !or"• Capabilit% Assess&ent• Co&&unications PlanArchitectural !nputs
• 6rgani-ational 7odel for 5nterprise Architecture, including:8 4cope of organi-ations i&pacted8 7aturit% assess&ent, gaps, and resolution approach8 Roles and responsibilities for architecture tea&'s(8 Constraints on architecture wor"8 Budget reuire&ents
8 9overnance and support strateg%• Tailored Architecture 3ra&ewor", including:
8 Tailored architecture ðod8 Tailored architecture content 'deliverables and artifacts(8 Con)gured and deplo%ed tools
ADM – Fase C (Data Architecture)
-
8/16/2019 Unidad 2 - Arquitectura de Datos
9/31
Inputs• Data principles, if e.isting• 4tate&ent of Architecture !or"• Architecture Vision• Architecture Repositor%, including:
8 Re+usable building bloc"s 'in particular, de)nitions of currentdata(8 Publicl% available reference &odels8 6rgani-ation+speci)c reference &odels8 6rgani-ation standards
• Draft Architecture De)nition Docu&ent, including:8 Baseline Business Architecture, Version #; 'detailed(, ifappropriate8 Target Business Architecture, Version #; 'detailed(
8 Baseline Data Architecture, Version ;#, if available8 Target Data Architecture, Version ;#, if available8 Baseline Application Architecture, Version #; 'detailed( orVersion ;# 'Vision(8 Target Application Architecture, Version #; 'detailed( or Version;# 'Vision(
8 Baseline Technolog% Architecture, Version ;# 'Vision(8 Target Technolog% Architecture, Version ;# 'Vision(
ADM – Fase C (Data Architecture)
-
8/16/2019 Unidad 2 - Arquitectura de Datos
10/31
Steps
The level of detail addressed in Phase C will depend on the scope and
goals of the overall architecture e
-
8/16/2019 Unidad 2 - Arquitectura de Datos
11/31
1. Steps - Select Reference Models" #ie$points" and%ools
• Review and validate 'or generate, if necessar%( the set ofdata principles# These will nor&all% for& part of anoverarching set of architecture principles#
• 4elect relevant Data Architecture resources 'reference
&odels, patterns, etc#( on the basis of the business drivers,sta"eholders, concerns, and Business Architecture#
• 4elect relevant Data Architecture viewpoints 'for e.a&ple,sta"eholders of the data 8 regulator% bodies, users,generators, subjects, auditors, etc#(#
• $dentif% appropriate tools and techniues 'including for&s( tobe used for data capture, &odeling, and anal%sis, inassociation with the selected viewpoints# Depending on thedegree of sophistication warranted, these &a% co&prisesi&ple docu&ents or spreadsheets, or &ore sophisticated
&odeling tools and techniues such as data &anage&ent&odels data &odels etc#
ADM – Fase CADM – Fase C (Data Architecture)
-
8/16/2019 Unidad 2 - Arquitectura de Datos
12/31
1. Steps - Select Reference Models" #ie$points" and%ools
5ntit%+relationship diagra&
ADM – Fase CADM – Fase C (Data Architecture)
-
8/16/2019 Unidad 2 - Arquitectura de Datos
13/31
1. Steps - Select Reference Models" #ie$points" and%ools
Class diagra&s
ADM – Fase CADM – Fase C (Data Architecture)
-
8/16/2019 Unidad 2 - Arquitectura de Datos
14/31
1. Steps - Select Reference Models" #ie$points" and%ools
Determine Overall Modeling Process
3or each viewpoint, select the &odels needed to support thespeci)c view reuired, using the selected tool or ðod#
5nsure that all sta"eholder concerns are covered# $f the% arenot, create new &odels to address concerns not covered, oraug&ent e.isting &odels#
The reco&&ended process for developing a Data Architectureis as follows:
Collect data+related &odels fro& e.isting BusinessArchitecture and Application Architecture &aterials#
Rationali-e data reuire&ents and align with an% e.istingenterprise data catalogs and &odels> this allows thedevelop&ent of a data inventor % and entit% relationship
pdate and develop &atrices across the architecture b%relating data to business service, business function,
ADM – Fase CADM – Fase C (Data Architecture)
-
8/16/2019 Unidad 2 - Arquitectura de Datos
15/31
1. Steps - Select Reference Models" #ie$points" and%ools
$nfor&ation &odel Archi&ate
ADM – Fase CADM – Fase C (Data Architecture)
-
8/16/2019 Unidad 2 - Arquitectura de Datos
16/31
1. Steps - Select Reference Models" #ie$points" and%ools
Identify Required Catalogs of Data Building Blocks
The organi-ation0s data inventor% is captured as a catalog within the Architecture Repositor%# Catalogs are hierarchical innature and capture a deco&position of a &eta&odel entit% and also deco&positions across related &odel entities 'e#g#, logicaldata co&ponent H ph%sical data co&ponent H data entit%(#
Catalogs for& the raw &aterial for develop&ent of &atrices and diagra&s and also act as a "e% resource for portfolio&anaging business and $T capabilit%#
During the Business Architecture phase, a Business 4erviceI$nfor&ation diagra& was created showing the "e% data entitiesreuired b% the &ain business services#
sing the traceabilit% fro& application to business function to data entit% inherent in the content fra&ewor", it is possible tocreate an inventor % of the data needed to be in place to support the Architecture Vision#
6nce the data reuire&ents are consolidated in a single location, it is possible to re)ne the data inventor % to achieve se&anticconsistenc% and to re&ove gaps#
The following catalogs should be considered for develop&ent within a Data Architecture: Data 5ntit%IData Co&ponent catalog
ADM – Fase CADM – Fase C (Data Architecture)
-
8/16/2019 Unidad 2 - Arquitectura de Datos
17/31
1. Steps - Select Reference Models" #ie$points" and%ools
Identify Required Matrices7atricesshowthecorerelationshipsbetweenrelated&odelentities#
7atricesfor& theraw &aterial fordevelop&ent ofdiagra&sandalsoactasa"e% resourcefori&pact assess&ent#
At thisstage, anentit% to applications&atri. couldbeproducedtovalidatethis&apping#1ow dataiscreated,&aintained, transfor&ed, andpassedtootherapplications, or usedb% otherapplications,will now start to beunderstood#
6bviousgapssuchasentitiesthat neversee& tobecreatedb% anapplicationordatacreatedbut neverused, needto benotedforlatergapanal%sis#
6ncetheseupdateshavebeen&ade, it &a% beappropriatetodropintoashortiterationof ApplicationArchitecturetoresolvethechangesidenti)ed#
Thefollowing&atricesshouldbeconsideredfordevelop&ent withinaDataArchitecture:
Data5ntit%I Business3unction' showing whichdata supportswhichf unctionsand whichbusinessfunctio nownswhi chdata(
Business4erviceI $nfor&ation'dev elopedduring theBusinessA rch#phase(
ApplicationIData'developedacrosstheApplicationandData Arch# phases(
ADM – Fase CADM – Fase C (Data Architecture)
-
8/16/2019 Unidad 2 - Arquitectura de Datos
18/31
1. Steps - Select Reference Models" #ie$points" and%ools
Identify Required Matrices
ADM – Fase CADM – Fase C (Data Architecture)
Entity Register
Accept #aluate Pay
Custo&e
r
Crea I
pd
Read Act
Clai& Crea I Read Cr R
-
8/16/2019 Unidad 2 - Arquitectura de Datos
19/31
1. Steps - Select Reference Models" #ie$points" and %ools
Identify Required Diagrams
Diagra&s present the Data Architecture infor&ation fro& a set ofdi
-
8/16/2019 Unidad 2 - Arquitectura de Datos
20/31
1. Steps - Select Reference Models" #ie$points" and %ools
Identify Types of Requirement to e Collected
6nce the Data Architecture catalogs, &atrices, and diagra&shave been developed, architecture &odeling is co&pleted b%for&ali-ing the data+focused reuire&ents for i&ple&enting the
Target Architecture# These reuire&ents &a%:
Relate to the data do&ain Provide reuire&ents input into the Application, and
Technolog% Architectures
Provide detailed guidance to be reJected during designand i&ple&entation to ensure that the solution addressesthe original architecture reuire&ents
!ithin this step, the architect should identif% reuire&ents thatshould be &et b% the architecture#
ADM – Fase CADM – Fase C (Data Architecture)
-
8/16/2019 Unidad 2 - Arquitectura de Datos
21/31
2. Steps - Develop Baseline Data Architecture Description
Develop a Baseline Description of the e.isting DataArchitecture, to the e.tent necessar% to support the
Target Data Architecture# The scope and level of detailto be de)ned will depend on the e.tent to which
e.isting data ele&ents are li"el% to be carried overinto the Target Data Architecture, and on whetherarchitectural descriptions e.ist# To the e.tent possible,identif% the relevant Data Architecture buildingbloc"s, drawing on the Architecture Repositor%#
!here new architecture &odels need to be developedto satisf% sta"eholder concerns, use the &odelsidenti)ed within 4tep as a guideline for creating
new architecture content to describe the Baseline
ADM – Fase CADM – Fase C (Data Architecture)
-
8/16/2019 Unidad 2 - Arquitectura de Datos
22/31
. Steps - Develop Target Data !rc"itectureDescription
Develop a Target Description for the DataArchitecture, to the e.tent necessar% to support theArchitecture Vision and Target Business Architecture#
The scope and level of detail to be de)ned willdepend on the relevance of the data ele&ents toattaining the Target Architecture, and on whetherarchitectural descriptions e.ist# To the e.tent possible,identif% the relevant Data Architecture building
bloc"s, drawing on the Architecture Repositor%#
!here new architecture &odels need to be developedto satisf% sta"eholder concerns, use the &odels
identi)ed within 4tep as a guideline for creating
ADM – Fase CADM – Fase C (Data Architecture)
-
8/16/2019 Unidad 2 - Arquitectura de Datos
23/31
!. Steps - Perform Gap !nalysis
Verif% the architecture &odels for internal consistenc%and accurac%:
Perfor& trade+o< anal%sis to resolve conJicts 'if
an%( a&ong the di
-
8/16/2019 Unidad 2 - Arquitectura de Datos
24/31
". Steps - De#ne Candidate RoadmapComponents
3ollowing creation of a Baseline Architecture, TargetArchitecture, and gap anal%sis, a data road&ap isreuired to prioriti-e activities over the co&ing
phases#
This initial Data Architecture road&ap will be used asraw &ater ial to support &ore detailed de)nition of aconsolidated, cross+discipline road&ap within the
6pportunities K 4olutions phase#
ADM – Fase CADM – Fase C (Data Architecture)
-
8/16/2019 Unidad 2 - Arquitectura de Datos
25/31
#. Steps - Resolve Impacts !cross t"e !rc"itecture $andscape
6nce the Data Architecture is )nali-ed, it is necessar%to understand an% wider i&pacts or i&plications#
At this stage, other architecture artifacts in theArchitecture andscape should be e.a&ined toidentif%:
Does this Data Architecture create an i&pact on
an% pre+e.isting architectures/1ave recent changes been &ade that i&pact the
Data Architecture/Are there an% oppor tunities to leverage wor "
fro& this Data Architecture in other areas of the
ADM – Fase CADM – Fase C (Data Architecture)
-
8/16/2019 Unidad 2 - Arquitectura de Datos
26/31
$. Steps - Conduct %ormal &take"older Revie'
Chec" the original &otivation for the architectureproject and the 4tate&ent of Architecture !or"against the proposed Data Architecture# Conduct ani&pact anal%sis to identif% an% areas where the
Business and Application Architectures 'e#g#, businesspractices( &a% need to change to cater for changes inthe Data Architecture 'for e.a&ple, changes to for&sor procedures, applications, or database s%ste&s(#
$f the i&pact is signi)cant, this &a% warrant theBusiness and Application Architectures beingrevisited#
$dentif% an% areas where the Application Architecture
'if generated at this point( &a% need to change to
ADM – Fase CADM – Fase C (Data Architecture)
-
8/16/2019 Unidad 2 - Arquitectura de Datos
27/31
%. Steps - %inali(e t"e Data !rc"itecture
• 4elect standards for each of the building bloc"s, re+using as &uch as possible fro& the reference&odels selected fro& the Architecture Repositor%#
• 3ull% docu&ent each building bloc"#
• Conduct )nal cross+chec" of overall architectureagainst business reuire&ents> docu&ent rationalefor building bloc" decisions in the architecturedocu&ent#
• Docu&ent )nal reuire&ents traceabilit% report#
• Docu&ent )nal &apping of the architecture withinthe Architecture Repositor%> fro& the selectedbuilding bloc"s, identif% those that &ight be re+used, and publish via the Architecture Repositor%#
• 3inali-e all the wor" products, such as gap anal%sis#
ADM – Fase CADM – Fase C (Data Architecture)
-
8/16/2019 Unidad 2 - Arquitectura de Datos
28/31
&. Steps - Create !rc"itecture De#nitionDocument
Docu&ent rationale for building bloc" decisions in theArchitecture De)nition Docu&ent#
Prepare Data Architecture sections of the ArchitectureDe)nition Docu&ent, co&prising so&e or all of:Business data &odel#ogical data &odel#Data &anage&ent process &odel#
Data 5ntit%IBusiness 3unction &atri.#Data interoperabilit% reuire&ents 'e#g#, L7
sche&a, securit% policies($f appropriate, use reports andIor graphics
generated b% &odeling tools to de&onstrate "e%
ADM – Fase CADM – Fase C (Data Architecture)
-
8/16/2019 Unidad 2 - Arquitectura de Datos
29/31
-
8/16/2019 Unidad 2 - Arquitectura de Datos
30/31
Output (Arte'actos core)
The outputs &a% include so&e or all of the following:
• Catalogs:8 Data 5ntit%IData Co&ponent catalog
• 7atrices:8 ApplicationIData &atri.
• Diagra&s:8 Conceptual Data diagra&8 ogical Data diagra&
8 Data Disse&ination diagra&8 Data 4ecurit% diagra&8 Data 7igration diagra&8 Data ifec%cle diagra&8 Data 5ntit%IBusiness 3unction &atri.
ADM – Fase C (Data Architecture)
-
8/16/2019 Unidad 2 - Arquitectura de Datos
31/31
Análisis y Diseño de Arquitectura Empresarial
Phase C: Information Systems
ArchitecturesData Architecture
top related