Research project oriented at improving the process of translation of Business Requirements into Enterprise Architecture at the Schiphol Airport, Amsterdam.

1. 1

2. Petra Wouter van Bartosz
Gárdai der Loop Wojenka
Special thanks to our supervisors:
Patrick van der Linden
IT Architect at Schiphol Group
Prof. Tom van Engers
Lecturer of Information Science at the University of Amsterdam
Drs. Toon Abcouwer
Lecturer of Information Science at the University of Amsterdam
2

3.  Introduction to our approach
 Problem statement
 Research question
 Scope
 Direction of the study
 Analyzed methodologies
 The proposed process
 Conclusions
 Q&A
3

4.  Problem statement
 Schiphol Airport wants to introduce Enterprise Architecture within
their baggage handling system. They needed a general guide on
how to translate business requirements into applications.
 As the task and limited clearance to access detailed information
about the Airports luggage system, the direction we’ve taken is
abstract, and the result will probably be applicable to many other
luggage handling scenarios.
4

5. We have decided that the question we will be answering during this
project is as follows:
„Literature review research on generating requirements for Enterprise
Architecture in luggage handling scenarios.”
5

6.  Initial research scope was broader, but needed to be downsized of
scheduling purposes
 Identification of the main business modeling standards and languages
 Take into consideration what Schiphol BH already uses
 Problems with acquiring sufficient knowledge on DYA
6

7. 1. Introduction to business aspects
2. Analysis of available languages / business modeling standards
3. Establish EA definitions used in scientific literature
4. Analysis of available EA frameworks
5. Case study analysis
6. Proposed processes
7. Final remarks
7

8. • “the fundamental conception of a system [the enterprise] in its
environment embodied in its elements, their relationships to each other
and to its environment, and the principles guiding its design and
evolution (ISO, 2007).”
 enterprise architecture is a formal description of a system, or a detailed plan of the
system at component level to guide its implementation.
 enterprise architecture is the structure of components, their inter-relationships, and
the principles and guidelines governing their design and evolution over time
(The Open Group, 2011)
8

9. • Framework types:
 Generic EAF
 Specific EAF
 Classic EAF
 Federated EAF
• Comparing Frameworks:
 Difficult, like apples and pears
 Interviews
 Based on goals, input and output
9

10. • Framework types:
 Generic EAF
 Specific EAF
 Classic EAF
 Federated EAF
• Comparing Frameworks: • Final remark:
 Difficult, like apples and  Organizations don’t use one
pears standard. They take what
 Interviews they need from different
 Based on goals, input and frameworks and build their
output own
10

11. • Zachman
 The strength of the Zachman framework is that it provides a way to
structure and model an enterprise or systems architecture
• TOGAF
 Provide a framework for design, evaluation and building of
architectures for enterprises
• DYA
 Working with Enterprise Architecture
11

12. Formulated explicit business Build requirements based on Choose the viewpoints and
strategy Adjust to your chosen
the Goals and illustrate any analyse resulting
Enterprise Architecture
constraints and principles metamodels for Business-IT
Framework
that limit them. Alignment
Compile a set of Goals which Completed Framework of
Illustrate additional drivers Verify with Stakeholders
are driving the strategy Enterprise Architecture
and assessments behind the
motivation
12

13. • Previously written Strategy documents
• Previously undertaken analysis
 Porters 5 forces
 SWOT
 Others
• Managment activities
 Programme Management
 Project Management
Compile a set of Goals which are
driving the strategy
13

14.  Usually long-term.
 Goal is an end-state that a stakeholder needs to achieve.
 Both i* and KAOS can be used, but ArchiMate 2.0
Business Motivation Modelling works just fine.
Formulated explicit business Build requirements based on the Goals and illustrate any
strategy constraints and principles that limit them .
14

15. • Requirements are a list of things needed to be achieved before the
Enterprise Architecture/Organization can reach the previously
derived Goals.
Here we also tackle two different aspects of Requirements Engineering:
 Restrictions, which is what doesn’t allow us to pursue the
requirements.
 Principles, which are normative properties which have to be taken
into consideration.
Compile a set of Goals which are Illustrate additional drivers and assessments
driving the strategy behind the motivation
15

16. In order to boost the understanding of the context in which the
Enterprise Architecture will be functioning, two additional elements
will be described:
 Drivers, are something that influences the EA/Organization.
 Assessments, are outcomes of analyses of the Drivers.
Build requirements based on the Goals and illustrate any Choose the viewpoints and analyse resulting
constraints and principles that limit them . metamodels for Business-IT Alignment
16

17. Goal
Stakeholder
realization
viewpoint
viewpoint
Goal
Principles
contribution
viewpoint
viewpoint
Requirements
Motivation
realization
viewpoint;
viewpoint
Illustrate additional drivers and assessments
Verify with Stakeholders
behind the motivation
17

18. To fully understand if the metamodels satisfy the needs of the
Stakeholders during this step we describe who and what are the
relations between them and the elements of our motivation
framework.
Choose the viewpoints and analyse resulting Adjust to your chosen Enterprise
metamodels for Business-IT Alignment Architecture Framework
18

19. • Based on case study analysis we concluded that ArchiMate 2 was an
appropriate modeling tool for generating EAF.
• The general frames of TOGAF and DYA were used to build the proposed
Enterprise Architecture framework
Completed Framework of
Verify with Stakeholders
Enterprise Architecture
19

20. (The Open Group, 2012)
(Smeets 2009)
Adjust to your chosen Enterprise
Architecture Framework
20

21. 21

22. 2013
Master of Science Information Science
Business Information Systems
Integrated Cases
22

23.  The Open Group, 2012. ArchiMate 2.0 Framework. [Online]
Available at: http://pubs.opengroup.org/architecture/archimate2-doc/
[Accessed 17 1 2013].
 Smeets, M., 2009. Introducing enterprise architecture at TNT
post, Master thesis, Delft University of Technology, Delft
 The Open Group. (2011). TOGAF Version 9.1 - TOGAF Series. Van Haren
Publishing.
23