Systemology: Difference between revisions
No edit summary |
|||
| (4 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
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 == | ||
System = People + Machines + Methods + Benefits | |||
People = Users + Administrators + Engineers | People = Users + Administrators + Engineers | ||
Latest revision as of 07:06, 2 June 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
[edit | edit source]System = People + Machines + Methods + 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)