Personal tools
You are here: Home / EARF meetings: Documentation / Documents relevant to 20 April 2011

Documents relevant to 20 April 2011

by Alta van der Merwe last modified 03 May, 2011 12:15 PM
All the documentation relevant to the meeting on 20 April 2011
File PDF document EARF Minutes: 20 April 2011 by Alta van der Merwe — last modified 03 May, 2011 12:16 PM
Minutes from the EARF meeting
File PDF document AOGEA comments on Jan Hoogenvorst by Alta van der Merwe — last modified 03 May, 2011 12:17 PM
Paul van der Merwe gave a short overview on the discussion that followed at the AOGEA after Prof Hoogenvorst presented his arguments on TOGAF
File Jan Hoogervorst on TOGAF by Alta van der Merwe — last modified 03 May, 2011 12:18 PM
Slides that accompanied the discussion from Jan Hoogervorst
File Microsoft PowerPoint presentation Question raised to Prof Jan Hoogenvorst by Alta van der Merwe — last modified 03 May, 2011 12:33 PM
Marne posed a question on the difference (or relationship) about the transaction categories Jan Dietz uses in his book enterprise ontology and the enterprise design domains mentioned in the TOGAF article. Prof Jan sent us the attached sheet that shows the difference. According to a mail received from him you could question the practical value in strictly distinguishing infological and datalogical transactions and 'ontological' transactions, since that distinction is in reality often blurred. Indeed, the label B for ontological transactions can be confusing given the 'business' functional enterprise design domain. Notheless, transactions refer to activities. Other categorizations of activities could be envisioned. The design domains (the main domains shown in the sheet and their sub domains) refer to enterprise facets where design needs to take place such that activities are performed in a unified and integrated manner, while also addressing certain areas of concern. These areas of concern are for example user friendliness, security, flexibility, compliance, etc. For that (I repeat myself) design guidance in the form of architecture is needed. So a principle that states that process control must be separated from process execution addresses (among other things) the concern flexibility. That principle applies in my view to all transaction types. Since the domain 'processes' is a sub design domain of the main design domain organization' the architecture principle applies to all three cells in the organization column.

Document Actions

« April 2019 »
April
MoTuWeThFrSaSu
1234567
891011121314
15161718192021
22232425262728
2930