Enterprise Architecture: an approach for Information ...fp0804.emu.ee/pdf/PedroSousa.pdf · Lucent...
-
Upload
vuongthien -
Category
Documents
-
view
258 -
download
8
Transcript of Enterprise Architecture: an approach for Information ...fp0804.emu.ee/pdf/PedroSousa.pdf · Lucent...
Enterprise Architecture:an approach for Information Systems Architecture
Pedro SousaForsys, Riga, November 2009
1
Pedro Sousa
Agenda
• Presentation
• Key issues in Information Systems Architecture
• The Enterprise Architecture approach
• A proven Methodology for Information Systems Architecture
• Examples
Forsys, Riga, November 2009 2
Pedro Sousa
Presentation – Research and Professional Activities
• Associate Professor at Lisbon Technical University – Courses of IS & Information Systems Architecture– Active research in the area
• Senior Consultant at Link consulting for Enterprise Architecture Projects in several industry sectors:– Private:
• Finance, Telecommunications , Pulp & Paper, Retail– Public:
• Health, Justice and Central Banking
Forsys, Riga, November 2009
Pedro Sousa3
Agenda
• Presentation
• Key issues in Information Systems Architecture
• The Enterprise Architecture approach
• A proven Methodology for Information Systems Architecture
• Examples
Forsys, Riga, November 2009 4
Pedro Sousa
Key issues in Information Systems Architecture
Forsys, Riga, November 2009
Pedro Sousa5
RF-Cell Planning
RE&CW
NQ&PI
Real Estate
NP&D
NE&P
NO&M
NMC
P&R
Marketing
NetworkInplementation
A
GEOSACCompareCDD/CNA
A
BTS Process
A
Planet Parser
A
OMC-2000A
CircGest
A
Pathloss
A
CDD
A
RF-Tool
A
Planet
A
Phoenix
R Traffic
R ImplementationBTS Status
R BTS Executedchanges
R ImplementationBTS Status
R GEOSAC:Network Statistics
R CNA
R GEOSAC NetworkParameters
R MW
R BTS General Plan
R Planet
R RF-Tool
R Phoenix
R CDD
R Shared Towers
R Mobile BTS
R Ultimas
R Plot BTS
R BTS Folder
R Repeaters
R Antennas Stock
R TRX per BTS
R RF BTS Status
P&R
P&R
CDD to GEOSAC Compare
BTS Information
New Site Location
BTS Infrastructure StatusBTS Infrastructure Status
BTS Infrastructure Status
BTS InfrastructureStatus
Annual BTS General Plan
Annual BTS General Plan
Annual BTS General Plan
Annual BTS General Plan
Geographical Informationand Address
Hardware Changes Request
BTS Process Workflow
Shared Towers
Mobile BTS
Ultimas
Plot BTS
BTS Folder
Repeaters
Antennas Stock
Update Stock
TRX per BTS
RF BTS Status
RF Neighborhood
RF Neighborhood
Annual BTS General Plan
Annual BTS General Plan
Planned BTS
Changes to Planned BTS
BTS Implemented Modifications
BTS Planned Modifications
BTS Planned Modifications
Phoenix
Topology information
CDD
SDCCH Traffic Data
Lucent MML Commands
Network parameters
Network parameters
Ericsson MML Commands
Synchronization to CDD
Search Area
BSDS
BSDS
BSDS
BSDS
Synchronization to GEOSAC
Drive Test RequestBTS Description
Synchronize
Planet
Annual BTS General Plan
New Working BTS
Proposal Annual BTS Plan
Synchronization
RF-ToolProposal Annual BTS Plan
Maps With BTS Geographic Information MW Site Data
Geographical information
BTS Configuration
Preferential new site
Coverage Areas
Search Area
Proposal Annual BTS Plan
How good is a given Information System Architecture ?
• Does it support organization´s day to day activities?
• Does it provides timely and accurate information for business needs?
• Does it supports business changes ?
All the above in addition to support the evolution of problem models....
Forsys, Riga, November 2009
Pedro Sousa6
Key issues in Information Systems ArchitectureHow well the IS fits into the organization ?• One must model organization structure and operations in order to align the
different IT artefacts• One must ensure traceability from those artefacts up to the IT
architectures artefacts.
Conhecimento da Organização
Information Systems InformationE
ntities
Business Rules
External Systems
People, Units,Goals
Infra-structure
Business Processes
Organization
External Entities
Security Rules
Forsys, Riga, November 2009
Pedro Sousa7
Key issues of IS Architectures
A good Information System Architecture should allow:
• Adequate support for business activities
• Timely and accurate information
• Easy adjustment to organization and business changes
• Overall cost minimization
• All the above in addition to support the evolution of domain
problem models....
Why functional requirements are not enough ?
• Requirements Engineering captures the domain problem and users needs but fails do capture organization overall requirements and information's flows.
• In fact, how can we verify that a given set of requirements do support organization needs ?
• Business Processes and Information Entities are central concepts for modelling organization operations and to derive IT requirements and architecture!
Forsys, Riga, November 2009
Pedro Sousa8
Agenda
• Presentation
• Key issues in Information Systems Architecture
• The Enterprise Architecture approach
• A proven Methodology for Information Systems Architecture
• Examples
Forsys, Riga, November 2009 9
Pedro Sousa
Enterpriser Architecture
Forsys, Riga, November 2009
Pedro Sousa10
OrganizationalArchitecture
Technologic Architecture
System (application)Architecture
Information Architecture
Process Architecture
Alignment and
Rastreability
• Vision/Mission/ Strategy • Units/Stakeholders• Regulamentations• Products
• Business Processes/Rules• Business Services• Roles• Functional Requirements
• Business Inf. Entities• Information Life Cicle• Overall ICT Information
Requirements
• Systems Architecture• System Requirements• Operational Requirements
• Technology to be used in each • System Requirements• Operational Requirements
Enterpriser Architecture
Forsys, Riga, November 2009
Pedro Sousa11
OrganizationalArchitecture
Technologic Architecture
System (application)Architecture
Information Architecture
Process Architecture
Business
IT
Typical IT cycle in Organizations
Forsys, Riga, November 2009
Pedro Sousa12
1) Processes vs Systems• System Development projects• Focus on Process Automation
1
22) Systems vs Information
• Integration projects• Focus on Information flow
3
3) Information vs Processes• Focus on information meaning
and business information requirements
The IS Architecture is a Process!
Forsys, Riga, November 2009
Pedro Sousa13
Process Architecture
Information Architecture
IS Architecture
IMPLEMENTTHISWAY!
PLANTHIS WAY!
The IS Architecture is a Process!
In order to achieve normalized (pluggable) software products, several industries (telcos, retail, banking,..) realize that they first must
normalize business process and information architectures...
Forsys, Riga, November 2009
Pedro Sousa14
Process Architecture
Information Architecture
IS Architecture
Agenda
• Presentation
• Key issues in Information Systems Architecture
• The Enterprise Architecture approach
• A proven Methodology for Information Systems Architecture
• Examples
Forsys, Riga, November 2009 15
Pedro Sousa
Forsys, Riga, November 2009
Pedro Sousa
The Methodology for Information Systems Architecture
How to work
Where we are
Where we want to be
How to get there
16
Forsys, Riga, November 2009
Pedro Sousa
The CRUD Matrix: a key instrument for Information Systems Architecture
Entidades Informacionais
Information Entities
Business Processes
17
•CRUD stands for:•Create•Read•Update•Delete
•Each cell states the relation between the processes and the information
•IS appear as grouped cells, in such a manner so that processes and information are well supported.
Step 1 – Fill cells with CRUD relations
Forsys, Riga, November 2009
Pedro Sousa18
Step 2 – Reorder Lines and Columns and cluster them into Systems
Forsys, Riga, November 2009
Pedro Sousa19
Agenda
• Presentation
• Key issues in Information Systems Architecture
• The Enterprise Architecture approach
• A proven Methodology for Information Systems Architecture
• Examples
Forsys, Riga, November 2009 20
Pedro Sousa
Step 1
Forsys, Riga, November 2009
Pedro Sousa21
Step -2
Forsys, Riga, November 2009
Pedro Sousa22
Forsys, Riga, November 2009
Pedro Sousa23
Forsys, Riga, November 2009
Pedro Sousa24
Forsys, Riga, November 2009
Pedro Sousa25