System fundamentals: Difference between revisions

From Computer Science Wiki
Line 41: Line 41:
* [[Illustrate system requirements]] (see also [[design process]])
* [[Illustrate system requirements]] (see also [[design process]])
* [[Prototypes]] (see also [[design process]])
* [[Prototypes]] (see also [[design process]])
* [[Iteration]] (see also [[design process]])
* [[Why end-users matter so much]] (see also [[design process]])


==== Human interaction with the system ====
==== Human interaction with the system ====

Revision as of 15:20, 29 November 2016

System Fundamentals[1]

We are concerned with how systems integrate into organizations and how people use them. I used the standards from the IB[2], but added some other topics I think fit into this category (but not included by the IB).

The big ideas in system fundamentals[edit]

Systems in Organizations[edit]

A computer program or computer system is used by people who work in organizations. It is very helpful to understand how people, computers, and organizations work together.

Planning and system installation[edit]

User Focus[edit]

System Backup[edit]

Software Deployment[edit]

System Design[edit]

Components of a computer system[edit]

System Design and analysis[edit]

Human interaction with the system[edit]

Standards[edit]

  • 1.1.1 Identify the context for which a new system is planned.
  • 1.1.2 Describe the need for change management.
  • 1.1.3 Outline compatibility issues resulting from situations including legacy systems or business mergers.
  • 1.1.4 Compare the implementation of systems using a client’s hardware with hosting systems remotely.
  • 1.1.5 Evaluate alternative installation processes.
  • 1.1.6 Discuss problems that may arise as a part of data migration.
  • 1.1.7 Suggest various types of testing.
  • 1.1.8 Describe the importance of user documentation.
  • 1.1.9 Evaluate different methods of providing user documentation.
  • 1.1.10 Evaluate different methods of delivering user training.
  • 1.1.11 Identify a range of causes of data loss.
  • 1.1.12 Outline the consequences of data loss in a specified situation.
  • 1.1.13 Describe a range of methods that can be used to prevent data loss.
  • 1.1.14 Describe strategies for managing releases and updates.
  • 1.2.1 Define the terms: hardware, software, peripheral, network, human resources.
  • 1.2.2 Describe the roles that a computer can take in a networked world.
  • 1.2.3 Discuss the social and ethical issues associated with a networked world.
  • 1.2.4 Identify the relevant stakeholders when planning a new system.
  • 1.2.5 Describe methods of obtaining requirements from stakeholders.
  • 1.2.6 Describe appropriate techniques for gathering the information needed to arrive at a workable solution.
  • 1.2.7 Construct suitable representations to illustrate system requirements.
  • 1.2.8 Describe the purpose of prototypes to demonstrate the proposed system to the client.
  • 1.2.9 Discuss the importance of iteration during the design process.
  • 1.2.10 Explain the possible consequences of failing to involve the end-user in the design process.
  • 1.2.11 Discuss the social and ethical issues associated with the introduction of new IT systems
  • 1.2.12 Define the term usability.
  • 1.2.13 Identify a range of usability problems with commonly used digital devices.
  • 1.2.14 Identify methods that can be used to improve the accessibility of systems.
  • 1.2.15 Identify a range of usability problems that can occur in a system.
  • 1.2.16 Discuss the moral, ethical, social, economic and environmental implications of the interaction between humans and machines.

References[edit]