Another solution is the use of abstraction (see Sect. 6.3.3). Humans are only
good at working with models that do not include more than 30 elements (Horton
1991). Even more restricting is the rule by Miller (1956), based on the capacity of
our short-term memory, which states that humans are only good at processing seven
plus or minus two elements at a time. If the number of elements in a model exceeds
this limit, elements should be grouped and substituted with an aggregate, abstract
object. Based on this principle, one can create models with different levels of
abstraction: on the highest level, only the key concepts and key relations are
shown. Such high-level models show the essentials of the enterprise architecture
and abstract from details, for instance regarding implementation of processes or
distribution aspects. Each concept and relation on this highest level may be an
abstraction for a more complex set of concepts and relations. In a model with
different layers of abstraction, the more detailed concepts and relations can be
reached by zooming in on the composite object. This process is iterative: in each
layer, concepts and relations may in turn be compositions of more detailed concepts
and relations. However, to maintain an overview of the model, enterprise architecture
models should not apply more than three layers of abstraction (Koning 2002).
Another solution is the use of abstraction (see Sect. 6.3.3). Humans are onlygood at working with models that do not include more than 30 elements (Horton1991). Even more restricting is the rule by Miller (1956), based on the capacity ofour short-term memory, which states that humans are only good at processing sevenplus or minus two elements at a time. If the number of elements in a model exceedsthis limit, elements should be grouped and substituted with an aggregate, abstractobject. Based on this principle, one can create models with different levels ofabstraction: on the highest level, only the key concepts and key relations areshown. Such high-level models show the essentials of the enterprise architectureand abstract from details, for instance regarding implementation of processes ordistribution aspects. Each concept and relation on this highest level may be anabstraction for a more complex set of concepts and relations. In a model withdifferent layers of abstraction, the more detailed concepts and relations can bereached by zooming in on the composite object. This process is iterative: in eachlayer, concepts and relations may in turn be compositions of more detailed conceptsand relations. However, to maintain an overview of the model, enterprise architecturemodels should not apply more than three layers of abstraction (Koning 2002).
การแปล กรุณารอสักครู่..
