| I still think this term means,
in this setting, nothing more than how different parts of your network fit
together, and how not to waste your money in designing, building and running
your collection of computers.
A system is an collection (a design) of parts which interact with
each other within the system's boundaries (form, structure, organization) to
function as a whole. The nature (purpose, operation) of the whole is always
different from, and more than, the sum of its unassembled collection of
parts. If you think of your network and it's usefulness and effect on your
business this is obvious. (taken in part from http://www.umsl.edu/~sauter/analysis/bees/index.html)
One of the more readable papers on the subject is to be found here
:http://www.bnet.fordham.edu/public/ics/msilver/itimhdo.htm, but I make no
bones about not doing or needing to do any formal systems analysis in
building or working on your network. As I know both the building blocks of
your system (the computers, the operating system, the software) and how
computers work together on your local network (LAN) or on your
WAN I
(and any good consultant) can do "systems analysis" (how changes in
any part effect the whole) in my head.
|
