System fundamentals: Difference between revisions

From Computer Science Wiki
Line 12: Line 12:
* [[Legacy system]]
* [[Legacy system]]
* [[Testing implementation]]
* [[Testing implementation]]
* [[Installation process]]
* [[Implementation methods]]
* [[Implementation methods]]
* [[Data migration]]
* [[Data migration]]

Revision as of 13:24, 11 July 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. Level 2
  • 1.1.2 Describe the need for change management. Level 2
  • 1.1.3 Outline compatibility issues resulting from situations including legacy systems or business mergers. Level 2
  • 1.1.4 Compare the implementation of systems using a client’s hardware with hosting systems remotely. Level 3
  • 1.1.5 Evaluate alternative installation processes. Level 3
  • 1.1.6 Discuss problems that may arise as a part of data migration. Level 3
  • 1.1.7 Suggest various types of testing. Level 3
  • 1.1.8 Describe the importance of user documentation. Level 2
  • 1.1.9 Evaluate different methods of providing user documentation. Level 3
  • 1.1.10 Evaluate different methods of delivering user training. Level 3
  • 1.1.11 Identify a range of causes of data loss. Level 2
  • 1.1.12 Outline the consequences of data loss in a specified situation. Level 2
  • 1.1.13 Describe a range of methods that can be used to prevent data loss. Level 2
  • 1.1.14 Describe strategies for managing releases and updates. Level 2
  • 1.2.1 Define the terms: hardware, software, peripheral, network, human resources. Level 1
  • 1.2.2 Describe the roles that a computer can take in a networked world. Level 2
  • 1.2.3 Discuss the social and ethical issues associated with a networked world. Level 3
  • 1.2.4 Identify the relevant stakeholders when planning a new system. Level 2
  • 1.2.5 Describe methods of obtaining requirements from stakeholders. Level 2
  • 1.2.6 Describe appropriate techniques for gathering the information needed to arrive at a workable solution. Level 2
  • 1.2.7 Construct suitable representations to illustrate system requirements. Level 3
  • 1.2.8 Describe the purpose of prototypes to demonstrate the proposed system to the client. Level 2
  • 1.2.9 Discuss the importance of iteration during the design process. Level 3

References[edit]