Enterprise Architecture:
an approach for Information
Systems Architecture
Pedro Sousa
Pedro Sousa
Forsys, Riga, November 2009
1
Agenda
• Presentation
• Key issues in Information Systems Architecture
• The Enterprise Architecture approach
• A proven Methodology for Information Systems Architecture
• Examples
Pedro Sousa
Forsys, Riga, November 2009
2
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
Pedro Sousa
Forsys, Riga, November 2009
3
Agenda
• Presentation
• Key issues in Information Systems Architecture
• The Enterprise Architecture approach
• A proven Methodology for Information Systems Architecture
• Examples
Pedro Sousa
Forsys, Riga, November 2009
4
Key issues in Information Systems Architecture
How good is a given Information System Architecture ?
•
Does it support organization´s day
to day activities?
P&R
MW Site Data
Maps With BTS Geographic Information
BTS Folder
R
Implementation
BTS Status
New Site Location
Annual BTS General Plan
A
Repeaters
TRX per BTS
BSDS
R
Pathloss
RF-Cell Planning
BTS Folder
NO&M
P&R
R
TRX per BTS
R
Repeaters
Annual BTS General Plan
R
•
Does it provides timely and
accurate information for business
needs?
R
A
Coverage Areas
Planet
Phoenix
Topology information
RF Neighborhood
Planet
Shared Towers
Planet
Changes to Planned BTS
Phoenix
Annual BTS General Plan
Real Estate
R
NE&P
Proposal Annual BTS Plan
Geographical information
A
Phoenix
Synchronization
Planned BTS
Marketing
Proposal Annual BTS Plan
R
BTS General Plan
Mobile BTS
Antennas Stock
RF BTS Status
A
Planet Parser
Preferential new site
Update Stock
R
Shared Towers
Antennas Stock
R
Mobile BTS
R
A
Search Area
NP&D
RF-Tool
Search Area
Drive Test Request
BTS Description
Proposal Annual BTS Plan
RF BTS Status
RF-Tool
RF Neighborhood
BSDS
•
Annual BTS General Plan
Annual BTS General Plan
R
Annual BTS General Plan
Synchronize
Synchronization to GEOSAC
RF-Tool
Network
Inplementation
R
A
NQ&PI
BTS Planned Modifications
CDD
BSDS
R
BSDS
BTS Executed
changes
R
CDD
Network parameters
Network parameters
BTS Implemented Modifications
R
RE&CW
R GEOSAC Network
Parameters
Plot BTS
R
GEOSAC:
Network Statistics
Plot BTS
NMC
BTS Process Workflow
A
Synchronization to CDD
Hardware Changes Request
SDCCH Traffic Data
New W orking BTS
BTS Infrastructure
Status
Lucent MML Commands
Ericsson MML Commands
A
R
CNA
CircGest
BTS Infrastructure Status
BTS Infrastructure Status
BTS Process
BTS Information
Geographical Information
and Address
BTS Infrastructure Status
R
Forsys, Riga, November 2009
Ultimas
BTS Configuration
CDD
P&R
Pedro Sousa
MW
BTS Planned Modifications
Does it supports business changes ?
All the above in addition to support
the evolution of problem models....
R
Ultimas
Annual BTS General Plan
Implementation
BTS Status
A
A
GEOSAC
Compare
CDD/CNA
OMC-2000
R
CDD to GEOSAC Compare
5
Traffic
Key issues in Information Systems Architecture
How 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.
Organization
People,
Units,
Goals
Business
Processes
Information
Systems
Security
Rules
External
Systems
Infra-structure
Conhecimento da
Organização
Pedro Sousa
Forsys, Riga, November 2009
Business Rules
InformationE
ntities
External
Entities
6
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....
Pedro Sousa
Forsys, Riga, November 2009
7
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!
Pedro Sousa
Forsys, Riga, November 2009
8
Agenda
• Presentation
• Key issues in Information Systems Architecture
• The Enterprise Architecture approach
• A proven Methodology for Information Systems Architecture
• Examples
Pedro Sousa
Forsys, Riga, November 2009
9
Enterpriser Architecture
Organizational
Architecture
Alignment
and
Rastreability
Process
Architecture
Business Inf. Entities
Information Life Cicle
Overall ICT Information
Requirements
Vision/Mission/ Strategy
Units/Stakeholders
Regulamentations
Products
•
•
•
•
Business Processes/Rules
Business Services
Roles
Functional Requirements
•
•
•
Systems Architecture
System Requirements
Operational Requirements
System (application)
Architecture
Information
Architecture
•
•
•
•
•
•
•
Technologic
Architecture
Pedro Sousa
Forsys, Riga, November 2009
•
•
•
Technology to be used in each
System Requirements
Operational Requirements
10
Enterpriser Architecture
Business
Organizational
Architecture
IT
Process
Architecture
System (application)
Architecture
Information
Architecture
Technologic
Architecture
Pedro Sousa
Forsys, Riga, November 2009
11
Typical IT cycle in Organizations
1) Processes vs Systems
3
1
• System Development projects
• Focus on Process Automation
2
2) Systems vs Information
• Integration projects
• Focus on Information flow
3) Information vs Processes
• Focus on information meaning
and business information
requirements
Pedro Sousa
Forsys, Riga, November 2009
12
The IS Architecture is a Process!
Process
Architecture
Information
Architecture
IS
Architecture
IMPLEMENT
THIS
WAY!
PLAN
THIS
WAY!
Pedro Sousa
Forsys, Riga, November 2009
13
The IS Architecture is a Process!
Process
Architecture
Information
Architecture
IS
Architecture
In order to achieve normalized (pluggable) software products,
several industries (telcos, retail, banking,..) realize that they first must
normalize business process and information architectures...
Pedro Sousa
Forsys, Riga, November 2009
14
Agenda
• Presentation
• Key issues in Information Systems Architecture
• The Enterprise Architecture approach
• A proven Methodology for Information Systems Architecture
• Examples
Pedro Sousa
Forsys, Riga, November 2009
15
The Methodology for Information Systems Architecture
How to work
Where we are
Where we want to
be
How to get there
Pedro Sousa
Forsys, Riga, November 2009
16
The CRUD Matrix: a key instrument for Information
Systems Architecture
Information Entities
•CRUD stands for:
•Create
•Read
•Update
•Delete
Entidades Informacionais
Business Processes
•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.
Pedro Sousa
Forsys, Riga, November 2009
17
Step 1 – Fill cells with CRUD relations
Pedro Sousa
Forsys, Riga, November 2009
18
Step 2 – Reorder Lines and Columns and cluster them into
Systems
Pedro Sousa
Forsys, Riga, November 2009
19
Agenda
• Presentation
• Key issues in Information Systems Architecture
• The Enterprise Architecture approach
• A proven Methodology for Information Systems Architecture
• Examples
Pedro Sousa
Forsys, Riga, November 2009
20
Step 1
Pedro Sousa
Forsys, Riga, November 2009
21
Step -2
Pedro Sousa
Forsys, Riga, November 2009
22
Pedro Sousa
Forsys, Riga, November 2009
23
Pedro Sousa
Forsys, Riga, November 2009
24
Pedro Sousa
Forsys, Riga, November 2009
25