Talk:Ontological reductionism
The following was removed from the page:
- It is evident in the dominant discourses in the business of commercial and academic study of the management of software development. This provides an illustration of how ontological reductionism is often present as an unquestioned pre-understanding by members of these communities.
- As an example consider the use of the term "process" as it is commonly used to describe the of development of software products. Here a "process" is used as a representation of a system of transformation applied to defined inputs and which produces defined outputs. Defined inputs are transformed through a process to produce a defined output. At its simplest conception a process is an open-ended input/output system similar to or equivalent to algorithmic functions in mathematics and physics. This use is clearly described when reading either ISO 9001:2000 or ISO/IEC 12207 and conveys the unsubstantiated and unchallenged assumption that a process is a separable standalone unit of work, production or product transformation. Furthermore, a "process" is assumed to be coupleable such that the outputs of one process can be coupled to the input of another process. In this way separate ontologically reduced atomic processes can be coupled, joined or grouped together to create a larger system of processes which may in turn be represented as a higher-level process.
Reason: this blatantly breaks the NPOV, writes in an arguing tone and make absolute statements in vague areas. Sources, names and references, please. Nixdorf 23:56, 29 December 2005 (UTC)
Nothing here...Delete?[edit]
I propose we delete this page. People can add material to the page on reductionism as a section and if it grows too large, we can spin it off. Cazort 19:10, 14 November 2007 (UTC)