Level of Abstraction

Revision as of 20:03, 2 June 2009 (view source)

Jfromm (Talk | contribs)

← Older edit

Latest revision as of 21:45, 11 February 2011 (view source)

Admin (Talk | contribs)

m (Reverted edits by Eboxytezi (Talk) to last version by Jfromm)

Line 1:

-

A '''level of abstraction''' ~~is an explanation for~~ a certain [[Level_of_Organization|level ~~of organization~~]] ~~in a system~~. It is ~~related to~~ [[Emergence|emergence]]. Strong emergence requires at least one completely new level of abstraction, if it is defined as the appearance of a new code. The "level of abstraction" is related to the "level of detail", the "scope of view" or the "degree of generality", ~~since~~ abstraction is a ~~concept~~ or ~~idea not~~ associated with any specific instance. A "level of abstraction" for computing is the number of layers between the physical layer (of bits and binary code) and the current representation. A layer is a code, language or protocol which offers a certain service. For example in a computer we have the language cascade from binary code to machine code, byte code and high level code, or the OSI Reference Model.

+

A '''level of abstraction''' describes a system at a certain scope or resolution, and it used to explain the system at a certain [[Level_of_Organization|level]]. The relationship between different levels of abstraction is described by [[Emergence|emergence]]. The different types and classes of [[Emergence|emergence]] describe different relationships between higher and lower levels of abstractions. Strong emergence requires at least one completely new level of abstraction, if it is defined as the appearance of a new code. The "level of abstraction" is related to the "level of detail", the "scope of view" or the "degree of generality". The higher the level, the less detail. The lower the level, the more detail. The highest level of abstraction is the single system itself. The next level would be only a handful of components, and so on, while the lowest level could be millions of objects or agents. Abstraction comes from the Latin word 'abstrahere', which means to 'drag away from, remove, abort': we remove the details associated with any specific instance of the system.

+

A "level of abstraction" for computing is the number of abstraction layers between the physical layer (of bits and binary code) and the current representation. A layer is a code, language or protocol which offers a certain service. For example in a computer we have the language cascade from binary code to machine code, byte code and high level code, or the OSI Reference Model. The most common abstraction layer is the programming interface (API) between an application and a framework or operating system. High-level calls are made to the system, which executes the necessary instructions to perform the task.

+

Russ Abbott has argued in "The reductionist blind spot" that the best way to understand [[Emergence|emergence]] is through the lens of implementation - emergent properties can be described as a high level abstraction which is implemented by low level elements. The lower level of abstraction implements the higher level.

+

== Links ==

Level of Abstraction

From CasGroup

Latest revision as of 21:45, 11 February 2011

Views

Personal tools

Navigation

Search

Toolbox

@@ Line 1: / Line 1: @@
-A '''level of abstraction''' is an explanation for a certain [[Level_of_Organization|level of organization]] in a system. It is related to [[Emergence|emergence]]. Strong emergence requires at least one completely new level of abstraction, if it is defined as the appearance of a new code. The "level of abstraction" is related to the "level of detail", the "scope of view" or the "degree of generality", since abstraction is a concept or idea not associated with any specific instance. A "level of abstraction" for computing is the number of layers between the physical layer (of bits and binary code) and the current representation. A layer is a code, language or protocol which offers a certain service. For example in a computer we have the language cascade from binary code to machine code, byte code and high level code, or the OSI Reference Model.
+A '''level of abstraction''' describes a system at a certain scope or resolution, and it used to explain the system at a certain [[Level_of_Organization|level]]. The relationship between different levels of abstraction is described by [[Emergence|emergence]]. The different types and classes of [[Emergence|emergence]] describe different relationships between higher and lower levels of abstractions. Strong emergence requires at least one completely new level of abstraction, if it is defined as the appearance of a new code. The "level of abstraction" is related to the "level of detail", the "scope of view" or the "degree of generality". The higher the level, the less detail. The lower the level, the more detail. The highest level of abstraction is the single system itself. The next level would be only a handful of components, and so on, while the lowest level could be millions of objects or agents. Abstraction comes from the Latin word 'abstrahere', which means to 'drag away from, remove, abort': we remove the details associated with any specific instance of the system.
+A "level of abstraction" for computing is the number of abstraction layers between the physical layer (of bits and binary code) and the current representation. A layer is a code, language or protocol which offers a certain service. For example in a computer we have the language cascade from binary code to machine code, byte code and high level code, or the OSI Reference Model. The most common abstraction layer is the programming interface (API) between an application and a framework or operating system. High-level calls are made to the system, which executes the necessary instructions to perform the task.
+Russ Abbott has argued in "The reductionist blind spot" that the best way to understand [[Emergence|emergence]] is through the lens of implementation - emergent properties can be described as a high level abstraction which is implemented by low level elements. The lower level of abstraction implements the higher level.
 == Links ==