ORRCA – case study of enterprise architecture governance

Faculty of Electrical Engineering, Automatics, Computer Science and
Biomedical Engineering
Department of Applied Computer Science
ORRCA - case study of enterprise
architecture governance
PART I/II
KIS Seminar, 5th of November 2013
Agenda
1. Introduction – selected governance aspects
PART I
1. Governance strategy
2. Enterprise Architecture Landscape Modeling
3. Next Generation Enterprise Landscape Evolving
Part II
1. Enterprise Architecture Modeling - IT Project Management
Case
2. Architecture Evaluation and Architecture Decisions (ATAM
case)
3. Architect Competency Development and Assessment
4. Developing and enforcing guidelines - ORRCA Road Map
5. Conclusions
Jan Werewka
SP ZPI W03– PMBOK jako metodyka zarządzania projektami
2
1
1. INTRODUCTION –
SELECTED GOVERNANCE
ASPECTS
Enterprise
• Collection of organizations that has a
common set of goals …[The Open Group Architecture
Framework]
• Enterprise can be:
• government agency
• whole corporation
• a division of a corporation
• a single department
• geographically distant organizations linked
by common ownership
Jan Werewka
SP ZPI W03– PMBOK jako metodyka zarządzania projektami
4
2
Enterprise types
• Business enterprises
– run to make a profit
• Social enterprises
– provide services in the community
Jan Werewka
SP ZPI W03– PMBOK jako metodyka zarządzania projektami
5
Enterprise as activity
• An activity or a project that produces
services or products:
– An undertaking, especially one of some scope,
complication, and risk.
– A business organization.
– Industrious, systematic activity, especially when
directed toward profit
– …
Jan Werewka
SP ZPI W03– PMBOK jako metodyka zarządzania projektami
6
3
Enterprise in Polish
• Przedsięwzięcie
• Przedsiębiorstwo
• Korporacja (pojęcie nadużywane)
– rodzaj organizacji której Członkostwo stanowi istotę
korporacji. Bez członków korporacja nie istnieje.
– Rozgałęzione przedsiębiorstwa (spółki), często o
charakterze międzynarodowym.
– Large corporations and government agencies [TOGAF]
• may comprise multiple enterprises
• hence there may be separate enterprise architecture
projects
Jan Werewka
SP ZPI W03– PMBOK jako metodyka zarządzania projektami
7
Unusual enterprises in Kenya
Jan Werewka
SP ZPI W03– PMBOK jako metodyka zarządzania projektami
8
4
Unusual enterprises in Kenya
Jan Werewka
SP ZPI W03– PMBOK jako metodyka zarządzania projektami
9
Architecture
IEEE Computer Society
• fundamental organization of a system
– embodied in its components,
– their relationships
• to each other
• and to the environment,
– principle guiding its design and evolution
Jan Werewka
SP ZPI W03– PMBOK jako metodyka zarządzania projektami
10
5
Enterprise Architecture
• A coherent whole of
– principles
– methods
– models used in
• design and
• realization of an enterprise’s organizational
structure
– business processes
– information systems, and
– infrastructure
Jan Werewka
SP ZPI W03– PMBOK jako metodyka zarządzania projektami
11
Architectural thinking
Key point for any achitecture
Safari Enterprise Architecture
Lodge (System) Architecture
Chaotic solution (no architecture thinking)
6
Enterprise Architecture by illustration
Beware
proliferation of
IT systems
Architecture Governance
• practice and orientation by which …
architectures are managed and controlled
at an enterprise-wide level [TOGAF]
• Main task
– Implementing a system of controls over
the creation and monitoring of all
architectural components and activities
Jan Werewka
SP ZPI W03– PMBOK jako metodyka zarządzania projektami
14
7
Governance in Polish
• Ład architektoniczny (lepiej rozwój i
utrzymanie ładu architektonicznego)
• Nadzór architektoniczny
• Panowanie nad architekturą
• Rozróżniamy pomiędzy zarządzaniem
(management) a ładem (governance)
Jan Werewka
SP ZPI W03– PMBOK jako metodyka zarządzania projektami
15
Governance thinking (Kenya)
16
8
Enterprise Architecture
• Represents structure and behavior
– of an enterprise's IT landscape
– in relation to its business environment
• Reflects the current and future use of IT in
the enterprise
• Provides a roadmap to reach a future
state.
Jan Werewka
SP ZPI W03– PMBOK jako metodyka zarządzania projektami
17
Core activities of EA governance
• Governance strategy
• Enterprise Architecture Landscape
Modeling
• Next Generation Enterprise Landscape
Evolving
• Enterprise Architecture Modeling
• Architecture Evaluation and Architecture
Decisions
• Architect Competency Development and
Assessment
Jan Werewka
SP ZPI W03– PMBOK jako metodyka zarządzania projektami
18
9
Discussion
• Is architecture thinking important in software
systems development?
• Should architecture governance be build in
development process?
19
1. GOVERNANCE
STRATEGY
10
Governance strategy
• To what extent does the EA group focus on strategic
planning
• Does EA follow the one “great vision,” or—at the other
extreme—is there no long-term planning at all?
Jan Werewka
SP ZPI W03– PMBOK jako metodyka zarządzania projektami
Governance viewpoints
21
(from safari lodge)
What viewpoint does the EA group take?
Jan Werewka
SP ZPI W03– PMBOK jako metodyka zarządzania projektami
22
11
Viewpoints
Jan Werewka
SP ZPI W03– PMBOK jako metodyka zarządzania projektami
23
Viewpoints
Jan Werewka
SP ZPI W03– PMBOK jako metodyka zarządzania projektami
24
12
Viewpoints
Jan Werewka
SP ZPI W03– PMBOK jako metodyka zarządzania projektami
25
Holistic Approach
Jan Werewka
SP ZPI W03– PMBOK jako metodyka zarządzania projektami
26
13
Solution ways
Jan Werewka
SP ZPI W03– PMBOK jako metodyka zarządzania projektami
27
To deep?
Depends on common granularity level
Jan Werewka
SP ZPI W03– PMBOK jako metodyka zarządzania projektami
28
14
Architecture thinking
Jan Werewka
SP ZPI W03– PMBOK jako metodyka zarządzania projektami
29
To closed
Why governance should be open?
Jan Werewka
SP ZPI W03– PMBOK jako metodyka zarządzania projektami
30
15
Competeny importance
Architect or IT solution specialist?
Jan Werewka
SP ZPI W03– PMBOK jako metodyka zarządzania projektami
31
CALL FOR
HELP
Jan Werewka
SP ZPI W03– PMBOK jako metodyka zarządzania projektami
32
16
ORRCA
Software Architecture Governance
• ORRCA (Open Robust and Reference
Component's Architecture) environment
• Basing in the solutions, standards and
own experience
• ORRCA is described basing on ArchiMate
notation to ensure correct understanding
• Invitation open
Jan Werewka
SP ZPI W03– PMBOK jako metodyka zarządzania projektami
33
ORRCA
Goal contribution viewpoint
Jan Werewka
SP ZPI W03– PMBOK jako metodyka zarządzania projektami
34
17
35
Strategy
Driving to GRID 2020
36
18
Goals and hopes bounded with EA
• Simplify IT
• Controlling the complexity and cost of IT
while enabling the desired change and
competitiveness for the business
• Apply architectural thinking to simplify the
management of a complex enterprise IT
landscape
• Alignment business and IT
Jan Werewka
SP ZPI W03– PMBOK jako metodyka zarządzania projektami
37
ARCHITECTURE DEVELOPMENT IN ATSI
CASE STUDY ORRCA MOTIVATION LAYER
•
•
•
•
•
•
3.1.
3.2.
3.3.
3.4.
3.5.
3.6.
Jan Werewka
Drivers
Goals
Assessments
Principles
Requirements
Constraints
SP ZPI W03– PMBOK jako metodyka zarządzania projektami
38
19
Mapping ORRCA motivation layer to
business layer
Jan Werewka
SP ZPI W03– PMBOK jako metodyka zarządzania projektami
39
Discussion
• What architecture governance is suitable for your
purpose?
40
20
2. ENTERPRISE
ARCHITECTURE
LANDSCAPE MODELING
Problems Using EA problems
• EA does not scale
• EA is not equipped with
– right approach
– toolset to cover the entire scope of work
• EA fails to keep pace with the speed of
change
• EA seems fulfill some promises but failing
others
Jan Werewka
SP ZPI W03– PMBOK jako metodyka zarządzania projektami
42
21
Kenya (touristic) Landscape
43
Archimate
2.0
44
22
TOGAF content
model
Jan Werewka
SP ZPI W03– PMBOK jako metodyka zarządzania projektami
45
TOGAF ADM
Architecture
development
Cycle
Jan Werewka
SP ZPI W03– PMBOK jako metodyka zarządzania projektami
46
23
ArchiMate – simplified metamodel
47
Landscape map (Archimate)
• Vertical axis
– behavior like business processes or
functions
• Horizontal axis
– represents “cases” for which those
functions or processes must be executed,
such as:
• different products, services market segments, scenarios
• Third dimension
– assigning resources
• like information systems, infrastructure, or human resources.
Jan Werewka
SP ZPI W03– PMBOK jako metodyka zarządzania projektami
48
24
Landscape map (Archimate)
• Provide generation and publication of
– overview tables
• for managers, process, and system owners.
• Architects may use landscape maps as
– a resource allocation instrument and as
– an analysis tool for the detection of
patterns and changes in this allocation
Jan Werewka
SP ZPI W03– PMBOK jako metodyka zarządzania projektami
49
Insurance Enterprise Landscape
Jan Werewka
SP ZPI W03– PMBOK jako metodyka zarządzania projektami
50
25
Enterprise Landscape
KIS
Graduate
study
Business layer Educate
students
Competency
in computer
science
teaching
Postgraduate
study
Doctoral
Study
Research
Projects
Organization
Educate
students
Expertise in
applied
computer
science
Educate PhD
students.
Competency
to lead
research
study
Research
on defined
areas.
Delivering
research
value
Readiness
for leading
and
executing
projects
Efficient
organization
Executing
project and
obtain
deliverables
Organizing and
issue
management
Application
layer
Conducting teaching and knowledge
assessment
Conducting
research to
obtain vale
Infrastructure
layer
Teaching staff availability, students
availability , lecture rooms, laboratories,
computers, software
Resources availability
Jan Werewka
Rooms,
administration
staff
availability
SP ZPI W03– PMBOK jako metodyka zarządzania projektami
51
Enterprise IT Landscape
KIS
Education
support
Business layer Services:
zakładanie kursu i
podstawowe funkcje
administracyjne,
zapisywanie
uczestników i dzielenie
ich na grupy,
tworzenie i
odtwarzanie kopii
zapasowej,
tworzenie zasobów
tekstowych,
załączanie plików,
załączanie linków
zewnętrznych
Students
assessment
Education
assets
Education
offer
Supporting
students
assessment
Access to
education
assets
Delivery of
interesting
education
programme
Enabling
communicat
ion
Enabling usage
of technology
solutions
Open AGH
SYLLABUS
AGH
e-mail
systems
AGH-portals
- Open source
- Microsoft
System
infrastructu
re
System
System
infrastructur infrastructure
e
Application
layer
Moodle
E-learning
Virtual
Dean`s
Office
Infrastructure
layer
AGH
E-learning
Center
OZE System
infrastructure open
educational
resources
Jan Werewka
Exchange
SP ZPI W03– PMBOK jako metodyka zarządzania projektami
Technology
software
52
26
Research
• Grzegorz Rogus, Paweł Skrzynski, Piotr
Szwed, Michal Turek, Jan Werewka
• SMESDaD – Synergetic Methodology for
Enterprise Software Development and
Deployment
– Effective cooperation between a company
developing software and enterprise in
which software is to be deployed.
– A model of cooperation based on the
synergetic relationships
Jan Werewka
SP ZPI W03– PMBOK jako metodyka zarządzania projektami
53
Driving to GRID 2020
[Grid-Interop 2012, Monday, December 3, 2012 to Friday, December 7, 2012 Irving Convention Center ]
54
27
OSIMM
maturity
matrix
Jan Werewka
SP ZPI W03– PMBOK jako metodyka zarządzania projektami
55
SOA (Service Oriented Architecture)
transformations
•
•
•
•
•
•
Business-centric design
Reuse of functionality
Flexibility
Multichanneling
Decoupling of functionality and technology
Stability
28
Gap determination between current and
target maturity
The Open Group SOA Integration Maturity Model (OSIMM)
provides means to assess an organization’s Service
Oriented Architecture (SOA) maturity level.
Jan Werewka
SP ZPI W03– PMBOK jako metodyka zarządzania projektami
57
Poland vs Kenya Export Treemap (Landscape)
Harvard Economic Complexity Observator
58
29
Movement constraints
Some phrases of ORRCA software architects
“Integration over creation”
“Maximizing software common part doesn’t
mean minimizing development effort”
Discussion
• Is architecture landscape important in software
systems development?
• How perform an effective research on landscape
construction and analysis?
60
30
3. NEXT GENERATION
ENTERPRISE EVOLVING
Seeking BIG Five in Africa
31
"Big Five" IT trends
A tectonic technology shift
• Dion Hinchcliffe: The
"Big Five" IT trends of
the next half decade:
Mobile, social, cloud,
consumerization, and
big data
http://www.zdnet.com
Jan Werewka
SP ZPI W03– PMBOK jako metodyka zarządzania projektami
63
Next-Gen Mobile - Smart
Devices and Tablets
• 2015 market
– tablets 479 million
– PC 535 million units
Jan Werewka
SP ZPI W03– PMBOK jako metodyka zarządzania projektami
64
32
Challenges to smart device
adoption
• Smart devices have a poor enterprise ecosystem today
• Many inherent advantages of smart mobile are anathema
to structured IT
Jan Werewka
SP ZPI W03– PMBOK jako metodyka zarządzania projektami
65
Social Media - Social Business
and Enterprise 2.0
• social media already surpassed
workhorse of the modern
enterprise, e-mail
• leading organizations are
becoming social enterprises
Jan Werewka
SP ZPI W03– PMBOK jako metodyka zarządzania projektami
66
33
Challenges to social media
adoption
• Social media is not an IT
competency
• peer production of
product
development
• customer care
• and marketing
– require deeper
rethinking of
business processes
• more significant value
propositions of social
requires business
transformation
Jan Werewka
SP ZPI W03– PMBOK jako metodyka zarządzania projektami
67
Enterprise 2.0
• is "the use of emergent social software
platforms within companies, or
between companies and their partners
or customers„
• help employees, customers and
suppliers collaborate, share, and
organize information via Web 2.0
technologies.
Jan Werewka
SP ZPI W03– PMBOK jako metodyka zarządzania projektami
68
34
Cloud computing
• Cloud computing
adopted steadily for
non-mission critical
applications
• Business agility, vendor
choice, and access to
next-generation
architectures
Jan Werewka
SP ZPI W03– PMBOK jako metodyka zarządzania projektami
69
Challenges to cloud computing
adoption
• Concerns of control
• Reliability and
performance perceptions
• adoption favored largely
for greenfield development
• companies invest in cloud
standards to build private
clouds to be in position to
start selectively
transferring services out
on a trial basis
Jan Werewka
SP ZPI W03– PMBOK jako metodyka zarządzania projektami
70
35
Innovation for
technology is coming
largely from the
consumer world
Consumerization has
very much to do with its
usage model
Jan Werewka
SP ZPI W03– PMBOK jako metodyka zarządzania projektami
71
Challenges to applying
consumerization to IT
• Vendors provide the
UX (user experience)
• Consumer technology
often isn't enterprise
ready
Jan Werewka
SP ZPI W03– PMBOK jako metodyka zarządzania projektami
72
36
Big data
• Businesses are drowning in
data more than ever before
• most companies are still
addressing their big data
needs with data warehousing.
Jan Werewka
SP ZPI W03– PMBOK jako metodyka zarządzania projektami
73
Challenges to adopting big data
• Big data requires many new
skills
• Meaningful use of big data
requires considerable crossfunctional buy-in.
– Big data requires tapping
into
• Silos
• Warehouses
• External systems
– using new techniques
Jan Werewka
SP ZPI W03– PMBOK jako metodyka zarządzania projektami
74
37
OPEN GROUP
• Forums open to members of The Open
Group
– ArchiMate® Forum
– Architecture Forum
– Enterprise Management Forum
– Open Platform 3.0™ Forum
– Real -time & Embedded Systems Forum
Jan Werewka
SP ZPI W03– PMBOK jako metodyka zarządzania projektami
75
OPEN GROUP
• Work Groups open to all members of The
Open Group:
–
–
–
–
–
Business Architecture
Cloud Computing
Quantum Lifecycle Management
Semantic Interoperability
Service Oriented Architecture
Jan Werewka
SP ZPI W03– PMBOK jako metodyka zarządzania projektami
76
38
Dion Hinchcliffe
The Enterprise IT
Landscape in 2012:
Consumerization Rules
The Roost,
http://www.ebizq.net
Internet of Things (IoT)
• 4A vision - anywhere, anytime, by
anyone and anything
• network of interconnected
things/objects that are uniquely
addressable”.
• traditional ‘things’ digital items
such as RFID, mobile phones,
motor vehicles and computers;
• ‘things’ include human beings,
plants, domestic/wild animals,
basically ‘anything’.
Jan Werewka
SP ZPI W03– PMBOK jako metodyka zarządzania projektami
78
39
Wild Animals Monitoring System
Based on 3G and Internet of Things
• Satellite-Linked Cameras Could Keep
Rhinos Safe
• A set of motion-sensitive cameras could
keep rhinos and other wildlife safer by
letting anyone in the world help keep an
eye on them.
Jan Werewka
SP ZPI W03– PMBOK jako metodyka zarządzania projektami
79
Generic architecture for IoT services
Case of an integrated drought early warning system
• The greatest potential is within wireless sensor
networks (WSNs) that cooperatively monitor large
environments.
• Instead of creating a homogenous solutions
– a system made up of heterogeneous weather information sources
•
•
•
•
•
such as sensors,
mobile phones
conventional weather stations
indigenous drought forecasters (rainmakers)
mobile phones
• smart billboards and so on)
– would suffice.
[Muthoni Masinde, University of Nairobi, Kenya, Computing and Informatics]
Jan Werewka
SP ZPI W03– PMBOK jako metodyka zarządzania projektami
80
40
BYOT
Bring Your Own Technology
• BYOT also called BYOD
(Device)
• BYOP (Phone)
• BYOPC (PC)
• permitting employees using
personally owned mobile
devices in workplace
• use those devices to access
privileged company
information and applications.
Jan Werewka
SP ZPI W03– PMBOK jako metodyka zarządzania projektami
81
BYOT
Bring Your Own Technology
• practice
applied to
students
using
personally
owned
devices in
education
settings
Jan Werewka
SP ZPI W03– PMBOK jako metodyka zarządzania projektami
82
41
Gamification
(pl. Grywalizacja)
• Use of game thinking and game
mechanics in non-game contexts to
engage users in solving problems.
• Gamification is used in applications and
processes to improve user engagement,
return on investment, data quality,
timeliness, and learning
Jan Werewka
SP ZPI W03– PMBOK jako metodyka zarządzania projektami
83
Research
• ECORA Architecture approaches
– Assessment and Relation Mapping of Different Specific
Solutions basing on ECORA (Extended Common Reference
Architecture) Presentation Layer Model
– Grzegorz Rogus, Kamil Sztandera, Michał Turek, Jan Werewka,
• ORRCA – software system comparison and
synergy
Jan Werewka
SP ZPI W03– PMBOK jako metodyka zarządzania projektami
84
42
Assessment and Relation Mapping of Different Specific Solutions
basing on ECORA (Extended Common Reference Architecture)
Presentation Layer Model
Kamil Sztandera, Michał Turek, Jan Werewka, Grzegorz Rogus
43
Driving to GRID 2020 (once more)
[Grid-Interop 2012, Monday, December 3, 2012 to Friday, December 7, 2012 Irving Convention Center ]
87
Discussion
• Schould a tectonic technology shift make
• tectonic changes in computer science?
88
44
8. CONCLUSIONS
PART I (disscussed)
PART II (to be disscussed)
• Governance strategy
• Enterprise Architecture Landscape
Modeling
• Next Generation Enterprise Landscape
Evolving
• Enterprise Architecture Modeling
• Architecture Evaluation and Architecture
Decisions
• Architect Competency Development and
Assessment
Jan Werewka
SP ZPI W03– PMBOK jako metodyka zarządzania projektami
90
45
ORRCA - case of software
architecture governance modeling
Thank you
Questions?
Jan Werewka
SP ZPI W03– Ontologia w zarządzania projektami
91
References
1. A Guide to the Project Management Body of Knowledge Fifth Edition (PMBOK® Guide), pp. 589
2. TOGAF® Version 9.1, Open Group Standard, The Open Group, 2009-2011 pp. 692
3. COBIT 5, A Business Framework for the governance and Management of Enterprise IT, ISACA,
2012, pp. 94
4. M. Lankhorst, Enterprise Architecture at Work: Modelling, Communication and Analysis, 2nd ed.
Berlin: Springer, 2009, pp. 352
5. ArchiMate® 2.0 Specification, Open Group Standard, 2009-2012, pp. 183,
http://pubs.opengroup.org/architecture/archimate2-doc/toc.html
46