Enterprise Architecture, EA, Business Architecture, BA, Small and Medium-Sized Enteprise, SME, Small business, CHOOSE, metamodel, meta-model, method, software, tool, support, adoption models, goals, actor, operations, objects, business process management, bpm

1. Enterprise Architecture in Small
and Medium-Sized Enterprises

2. How to delineate research studies in
DSRM PhD research project?
23/05/2013 MIS Research Seminar 2
• Each phase is a paper DOESN’T WORK
(though each phase as a dissertation chapter makes sense)

3. 23/05/2013 MIS Research Seminar 3
Research review with research agenda
• Valid option – we have examples that WORKED
• Time-consuming
• Contribution of new knowledge is absolute requirement
• Risky strategy

4. 23/05/2013 MIS Research Seminar 4
Evaluation existing solutions
• Valid option – we have examples that WORKED
• Theoretical development to explain evaluation results
is an absolute requirement
• Risky strategy

5. 23/05/2013 MIS Research Seminar 5
Incremental studies based on multiple artifacts
• Best option (so far)
• Challenge = define artifact set with relatively independent
components that each present a significant contribution

6. Typical research study
(6 to 12 months throughput time)
• Preliminary study
• Problem analysis
• Planning solution
design
1 to 2 months
• Solution design
• Demonstration
• Planning evaluation
• Write conference paper
3 to 4 months
• Evaluation studies
• Seminar
• Refinement solution (?)
• Revise conference paper
2 to 4 months
• Conference
presentation
• Incorporate
feedback
• Prepare
publication
1 to 2 months
23/05/2013 6Prof. dr. Geert Poels, director AOG Information and Knowledge Management

7. Part 0.0: Exploring the problem
• Integrating the semantics of events,
processes and tasks across requirements
engineering layers
• Conference: 3th Phd day (2010)
• Conference: Proceedings of the CAiSE Doctoral Consortium 2010 (CEUR Workshop
Proceedings) (2010)

8. Three orthogonal dimensions of Events
(UFO)
Atomic event Complex event
Instantaneous event
Time-extended event
Non-action event
Action event

9. Three orthogonal dimensions of Events
(BWW)
Event Process
Internal event
External event
Poorly-defined event
Well-defined event

10. 1.6. Results
• Example of results:
– Construct overload
– Construct excess
– Construct redundancy
– Construct deficit

11. Part 0.1: Getting an idea
• The quest for know-how, know-why, know-
what and know-who : using KAOS for
enterprise modelling
• Conference: 4th Phd day (2011)
• Conference: BUSITAL (CAiSE): Lecture Notes in Business Information Processing (2011)
• Conference: EIS/SIKS: CEUR Workshop Proceedings (2011)

12. Modelling an SME with KAOS

13. Part 0.1: Getting an idea
• De zoektocht naar know-how, know-
why, know-what en know-who : architectuur
voor kleinere bedrijven in vier dimensies
• Journal: INFORMATIE (AMSTERDAM) (2011)

14. Integrated Model

15. Research Steps

16. Part 1: Problem/Motivation

17. Part 1: Problem/Motivation
• Enterprise architecture for small and
medium-sized enterprises
• Conference: 5th Phd day (2012)
• Conference: Confenis Doctoral Consortium, Proceedings (2012)

18. Part 1: Problem/Motivation

19. Part 1: Problem/Motivation
• Enterprise architecture for small and
medium-sized enterprises : a starting point
for bringing EA to SMEs, based on adoption
models
• Book chapter: Information systems and small and medium-sized enterprises (SMEs) : state of
art of IS research in SMEs (2013)
• Conference: EIS/SIKS: CEUR Workshop Proceedings (2012)

20. Enterprise Architecture for SMEs
• EA for SMEs???4,5
– Not known in SMEs
– Not used in SMEs
4De Nil S, Deprost E, Bernaert M, Poels G (2012) Van Strategie tot Procesmodellering in Kleine en
Middelgrote Organisaties: Een Exploratief Onderzoek. University of Ghent, Ghent
5Devos J (2011) IT Governance for SMEs. University of Ghent, Ghent

21. Adoption Models
• Method Evaluation Model

22. Enterprise Architecture for SMEs
• EA for SMEs???
– Increase the perceived usefulness
• Increase actual effectiveness
• Advantages for SMEs in practice
– Increase the perceived ease of use
• Adapt methods to an SME context (in practice)
• Complexity10 (= 1/actual efficiency) must be decreased
– From actual to perceived efficacy
• Test in SMEs: feedback + EA gets better known
10Rogers EM, Shoemaker FF (1971) Communication of Innovations: A Cross-Cultural Approach.
The Free Press, New York

23. Enterprise Architecture for SMEs
• Design Science11
11Hevner AR, March ST, Park J, Ram S (2004) Design Science in Information Systems Research. MIS
Q 28 (1):75-105

24. Part 2: Metamodel

25. Part 2: Metamodel
• CHOOSE: Towards a Metamodel for
Enterprise Architecture in Small and Medium-
Sized Enterprises
• Journal: Information Systems Frontiers (2013)?

26. Part 2: Metamodel

27. Enterprise Architecture for SMEs
• Existing EA techniques

28. Part 2: Metamodel
mentioned. In the strategy-operations column, a minus indicates that a translation from strategy
(business or IT) to operations (organizational or IT) is not clearly supported.
Table 1 Analysis of EA frameworks
WHAT HOW WHERE WHO WHEN WHY
BUSINESS
IS
IT
STRATEGY
-
OPERATIONS
Zachman What How Where Who When Why B/IS/IT +
TOGAF
Data entity,
...
Process, ...
Infrastructure
extension
Organization unit,
actor, role, ...
Event, ...
Motivation
extension
B/IS/IT +
ArchiMate Information Behavior Network, ... Structure Event, ... Motivation B/IS/IT +
DoDAF Resource Activity Location Performer - Capability Blend +
CARP Resource Activity - Performer - Capability B +
IAF Object Activity Interaction Actor, role, ... Event Why, goal, ... B/IS/IT +
E2AF
Business
objects,
resources, ...
Business
activities,
...
With who?
Organization
structure, actors,
...
When? Why? B/IS/IT +
FEA: FEAF Objects, ...
Business
process, ...
Business
locations, ...
- - - IS/IT -
FEA: TEAF
Information,
...
Business
process, ...
Information
exchange, ...
Organization
chart, ...
Event, ...
Mission, vision,
...
B/IS/IT +
GEAM - - - - -
Requirements
vision
B/IS/IT +
ARIS
Input, output,
...
Function -
Organizational
unit, ...
Event Goal Blend +-
(BMM) -
(Business
process) -
(Organization
unit) - End B +
DYA
Product,
data, ...
Process Network Organization, ... -
Business
objectives
B/IS/IT +
Enterprise
modelling /
EKD
Concepts
model
Business
process
model
-
Actors and
resources model
- Goals model B/IS +
REA Resource Event - Agent - Goals B -
SEAM - - - - - Strategies B/IS +
LEAP Object Operation - Object Condition OCL constraint B/IS/IT -

29. Enterprise Architecture for SMEs
• CHOOSE metamodel

30. Part 2: Metamodel

31. Part 2: Metamodel

32. Part 2: Metamodel

33. Part 2: Metamodel

34. Part 2: Metamodel

35. Part 2: Metamodel

36. Part 2: Metamodel

37. Part 2: Metamodel
• -- CONSTRAINTS
• constraints
•
• -- GOAL
•
• --Constraint 1) Hard constraint: a Goal cannot have a Conflict with itself
• context Goal
• inv GOALSELFCONFLICT: (self.ConflictGoal1->union(self.ConflictGoal2))->excludes(self)
•
• --Constraint 2) Soft constraint: the Goal model may not contain Refinement cycles
• context Goal
• inv GOALCYCLICREFINEMENT: self.allHigherGoals()->excludes(self)
•
• -- GOAL-ACTOR
•
• --Constraint 3) Soft constraint: favour Assignments of Goals to Actors Wishing one of the related higher-level Goals
• context Actor
• inv WISHASSIGNMENT:
• if self.AssignmentGoal->notEmpty
• then
• if self.WishGoal->notEmpty
• then self.AssignmentGoal.allHigherGoals().WishActor->union(self.AssignmentGoal.WishActor)->includes(self)
• else true endif
• else true endif
•
• --Constraint 4) Hard constraint: a Role, SofwareActor or Device cannot have a Wish relationship with a Goal
• context Goal
• inv ACTORWISH: self.WishActor.SubRole->isEmpty and self.WishActor.SubSoftwareActor->isEmpty and self.WishActor.SubDevice->isEmpty
•
• --Constraint 5) Soft constraint: if an Actor has an Assignment relationship with a Goal and is part of another Actor, then the encompassing Actor should have an Assignment relationship
with the same or a related higher-level Goal
• context Actor
• inv ASSIGNMENTAGGREGATION:
• if self.AssignmentGoal->notEmpty
• then
• if self.WholeActor->notEmpty
• then ((self.AssignmentGoal.allHigherGoals().AssignmentActor->union(self.AssignmentGoal.AssignmentActor))->intersection(self.allWholeActors()))->notEmpty
• else true endif
• else true endif
•
• --Constraint 6) Soft constraint: if a HumanActor has an Assignment relationship with a Goal, then one of its Supervisors should have an Assignment relationship with the same or a related
higher-level Goal
• context HumanActor

38. Part 3: Method

39. Part 3: Method
• Enterprise Architecture Modelling for Small
and Medium-Sized Enterprises: Case Study
Research to Refine and Evaluate the CHOOSE
Method and Metamodel
• Journal: Enterprise Information Systems (2013)?

40. Part 3: Method

41. Part 3: Method

42. Enterprise Architecture for SMEs

43. Part 3: Method

44. Part 4: Software Tools

45. Enterprise Architecture for SMEs

46. Part 4: Software Tools
• Development of Software Tool Support for
Enterprise Architecture in Small and Medium-
Sized Enterprises
• Conference: BUSITAL (CAiSE): Lecture Notes in Business Information Processing (2013)

47. Step 1
Step 3
Step 4
Step 5
Step 6
Step 2

49. Part 4: Software Tools
• Enterprise Architecture Software Tool
Support for Small and Medium-Sized
Enterprises: EASE
• Conference: Proceedings of the Nineteenth Americas Conference on Information Systems
(2013)

50. Part 4: Software Tools

51. Part 4: Software Tools

52. Part 4: Software Tools

53. Part 4: Software Tools
• Software Tool Support voor Enterprise
Architectuur in Kleine en Middelgrote
Ondernemingen: EASE
• Journal: INFORMATIE (AMSTERDAM) (2013)

54. Part 4: Software Tools
• An Android Tablet Tool for Enterprise
Architecture Modelling in Small and Medium-
Sized Enterprises
• Conference: Practice of Enterprise Modeling (2013)?

59. Part 5: Integration/Translation

60. Part 5: Integration/Translation
• Development of a common base for
enterprise architecture: building the bridge
between CHOOSE and ArchiMate
• Journal: ?

61. Part 5: Integration/Translation

62. Part 5: Integration/Translation