4.2.1Organisational Goals
Organisations have mission and vision statements which state their future direction and what they aim to achieve. 
The departments and individuals within the organisation support these goals using appropriate information systems and procedures.

4.2.2Networks and Data Communications Systems
A computer network system connects two or more computers by telephone, cable or wireless technology. 
The networked equipment can share data, applications and peripheral devices. 
here is a range of standards for networks developed by The Institute of Electrical and Electronic Engineers (IEEE). These standards define the specifications for:
  • technical components
  • connections
  • network management. There are three main types of computer network:
  • Local Area Network (LAN)
  • Metropolitan Area Network (MAN)
  • Wide Area Network (WAN).

4.2.3Network Topologies
In different types of network, the server and workstations can be arranged in different ways. The shape of the arrangement is called the topology. The most common topologies are:
  • Star
  • Bus
  • Ring
  • Tree Mesh topologies are sometimes used in special situations.

4.2.4Network Operating Systems, Architecture and Components
Network systems have specialised operating systems. Some other network-specific requirements include:
  • a design for the interconnections of the components, known as the architecture
  • a set of rules for the way the components interact, known as a protocol
  • components such as network cards, switches and routers.

4.2.5Systems Development Life Cycle
System development involves finding out what is required of the system and working out how best to meet the requirements. This could involve designing improvements to an existing system or designing a completely new system. 
The processes required to solve the problems of system development are the same as those for information problem solving: 
  • analysis, 
  • design, 
  • development, 
  • testing, 
  • implementation and 
  • evaluation. 

Documentation occurs throughout the cycle.

4.2.6Impetus for Change
Changes to an information system may be necessary due to social, economic or technological reasons. 
In some cases, the organisation may have a choice about what to change and how to change it. These choices will often be in response to consumer demand. If the changes are likely to increase the market share or productivity of the organisation then they are worthwhile. 
Other kinds of changes are compulsory, due to changes in legislation. 
Change is rarely all positive or all negative, it is usually a combination of both. The important thing is to balance out the advantages and disadvantages and make the best decision.

4.2.7Factors Affecting Choices
Before you make a decision to change a system, you need to assess the feasibility of the changes. The changes must be practical, workable and possible. This includes all elements of the design—the hardware, the software and the procedures. 
Aspects of feasibility include: 
  • cost
  • compatibility of components
  • reliability
  • efficiency and ease of use
  • effectiveness.

4.2.8Implementing Changes
Implementation of system changes involves ensuring that the users:
  • are well informed about and accept the need for change
  • are well trained in the new procedures and processes
  • have good quality and easily available technical support
  • have the appropriate health and safety information and equipment.

4.2.9Methods of Changeover
Changeover implementation must be carefully planned and managed. 
Different changeover methods will suit different types of organisations and system changes. 
Changeover methods include:
  • direct changeover
  • parallel conversion
  • phased conversion
  • pilot conversion.

4.2.10Project Management Tools and Techniques
Gantt and PERT charts both allow you to plan the tasks, time and resources for a project.
  • Gantt charts are simple graphic representations of the tasks to be done, plotted as timelines.
  • PERT charts require more analysis of the project tasks and the identification of those tasks which must be completed within specific timeframes. These tasks are called critical tasks and are plotted along a critical pathway.

4.2.11Evaluating Changes
The new system must meet expectations. To evaluate whether or not this has been achieved you need to establish a set of criteria, for example:
  • Have the changes increased efficiency and effectiveness?
  • Is the new system cost-effective and easy to maintain?
  • Has it met the organisation’s goal? 

To evaluate some of these criteria you will have to measure and count, for example to measure productivity and cost. For other criteria you could survey the users or audience.