Systemology: Difference between revisions

From Noisebridge
Jump to navigation Jump to search
m (Stan moved page Systems to Systemology: Adding systemology, systems is a sub-set)
(changed this page to Systemology)
Line 1: Line 1:


== Systemology ==


The science and discipline organizing knowledge about systems.  A set of components that functions as a whole because of the interactions between its parts, subject to influence of interaction with its environment.
The science and discipline organizing knowledge about systems.  A set of components that functions as a whole because of the interactions between its parts, subject to influence of interaction with its environment. (Word first used by Russell L. Ackoff. https://en.wikipedia.org/wiki/Russell_L._Ackoff )


== Glossary ==
== Glossary ==
Line 19: Line 18:


Specification = Objectives + Requirements
Specification = Objectives + Requirements
current
 
Objectives = attributes + measurement methods
Objectives = attributes + measurement methods


Line 37: Line 36:


[[PROGRAMMING]]
[[PROGRAMMING]]
current
 
[[DATA]]
[[DATA]]


Line 49: Line 48:


[[BENEFITS]]
[[BENEFITS]]
current
 
[[ENGINEERING]]
[[ENGINEERING]]


[[ADMINISTRATION]]
[[ADMINISTRATION]]


[[Category:FUN]]F
[[Category:FUN]]

Revision as of 19:20, 20 April 2018


The science and discipline organizing knowledge about systems. A set of components that functions as a whole because of the interactions between its parts, subject to influence of interaction with its environment. (Word first used by Russell L. Ackoff. https://en.wikipedia.org/wiki/Russell_L._Ackoff )

Glossary

System = People + Machines + Metods + Benefits

People = Users + Administrators + Engineers

Machines = Hardware (Components and Firmware) + Software (Programs and Data)

Methods = Documentation + Training + Culture

Benefits = Advantages (Social, Economic, Personal)`

engineer = a person who uses scientific knowledge to solve practical problems (eg. cause a system to evolve & improve)

Specification = Objectives + Requirements

Objectives = attributes + measurement methods

Requirements = true / false measurement methods

administrator = someone whose job is to keep a system operating correctly

user = someone who derives some or all of the benefit of a system

Testing = Unit Tests + Integration Tests + System Tests

Quality Assurance = Inspections + Verification + Feedback (note: test construction is engeineering)

Also See

Computerology

PROGRAMMING

DATA

ALGORITHMS

Graphics

Security

Networks

BENEFITS

ENGINEERING

ADMINISTRATION