Systems in Organisations
A computing system is a dynamic entity, used to solve problems and interact with its environment. Note how the term is used separately from the word computer. A computer is a device. As such, a computing system is composed of hardware, software, and the data that they manage. Computer hardware is a collection of physical elements that make up a machine and its related pieces; the casing, circuit boards, electronic chips, wires, disks, keyboards, monitors, the list goes on. Computer Software is the collection of programs that provide the instructions that a computer can carry out. At the very heart of a computer system is the information that manages.
Planning and system installation
In its most general sense, an organisation is the collective goal which is inextricably linked to its environment. The environment, therefore, defines the limits of an organisation. When systems are built, they are defined by the needs of its creators, and as such, systems are not independent entities but exist in an environment. This environment affects the functioning and the performance of the system. Sometimes, the environment may be thought of as a system in its own right, but, more generally, it consists of a number of other systems which interact with each other.
When a new system is planned, it is generally the result of necessity or a change in the environment. An outdated or archaic systems might exist and as a result of the forward progression of technology, and therefore a more efficient and dynamic entity may replace this system. An example of such a case arose with the development of spreadsheet tools in the late 80s and early 90s. During the beginning of the century, lists, data, and various other records were maintained through the use of physical charts and tables. Today, similar records can be made simply through the use of desktop software, and maintained and edited through the dynamics of these new computer systems.
Moore's law describes the natural progression of technology, and its consequence, therefore, will see the natural development of new systems. These new systems will inevitably do one of the following; be developed as a result of a problem, or replace an older system. In the case of the latter, these new systems will require a fluid transition from one system to another -- and this requires management.
A whole host of errors or incompatibilities may stem from this transition, and the insightful knowledge of an external party or internal expert may reduce the friction between the implementation of the newer systems. An example of an error and solution exists in the following common scenario; data is collected rationally via pen-and-paper, either via the observance of an occurrence or as a result of testing. In any case, the data is prone to some of the following shortcomings; handwriting is incomprehensible, data falls short of significant accuracy, the time-period of the occurrence is so rapid hand-written notation may not suffice, or more fundementally human error. A new system is introduced that is not-bespoke and allows data to be recorded digitally. One problem may be the skill of the observer. Because the software is not bespoke and is developed generally, some end-users may find it difficult to utilise the new system. A solution may be to provide comprehensive and easy-to-read documentation so much so that it eliminates obscurities found by n00bs.
As a result of these new systems, the comfortable and outdated might
User documentation is documentation to support users of computer systems (including both hardware and software). Good user documentation can ensure that users are quickly able to adapt to a new system.
User documentations can include online help, FAQ section on the website and video tutorials.
Users can be taught through formal classes or online training or they can learn by themselves.